Talk:Reusability of information objects

Remark for the paragraph Facilitating Collective Structured Learning:

Should the stated critical features not also be addeded to the list of assessment workspace functions in the paragraph Facilitating Collaborative Work in the article COLLABORATIVE WORK? At this moment, the assessment workspace functions are dispered. --Sjuurd 17:55, 18 May 2007 (EEST)

Possible ways to operationalise classes in Mediawiki:

Use dpl tag on item pages (i.e. the pages that share the common property of a class). Search category is the name of the item page. The class page must be categorised to Category:Class and to Category:Item page. The latter category does not need exist. It is a way to tell the system that the class has that page as item, and the dpl tag can find the class. The scope of the class is put between <section begin=class /> and <section end=class />. As a side effect, the class page will have a large number of non-existing categories.

I tried in the way that the category was class for all pages, and the section name varied. This did not work, because then all class names are listed on the item page, while only the right properties are shown.

OR

Use a category page for a class, and put the scope into a template (together with the category of the class). Then this template is called from the item page, and it is automatically listed as an item in the class category. Side effects: Class page goes into category namespace which is not good; You need also a template page.

OR

Ideal case (operationalisation not solved): use a simple {{class|class name}} template for each class the page belongs to. The template will contain the code that extracts the scope from the class page. This will create some kind of mark on the item page, and all pages marked are automatically listed on the class page under result. It is better to call the class from the item than vice versa.