Changes between Version 5 and Version 6 of CMDI 1.2/Cues/Display information

Timestamp:

01/15/14 07:48:19 (10 years ago)

Author:

oddrun.ohren@nb.no

Comment:

--

CMDI 1.2/Cues/Display information

@@ -8 +8 @@
 
 CMDI profiles provide the blueprint for a logical structuring of metadata instances. They provide very little information about ''how'' the information contained in the records should be presented (with the notable exception of the displayPriority attribute, which has not proven to be a very popular or well understood feature). It would be desirable to have some unified (and preferably extensible) way of providing (sets of) display cues related to but physically separate from the description of the logical structure - think of a model like (conceptually) CSS and XML, although the display information should probably go beyond styling (otherwise plain CSS might as well be used).
-[[Image(ClassDiagram2.png,400)]]
 
 Display aspects that might be included:
@@ -75 +74 @@
 Oddrun: I for one think it's a great idea to provide more display information! To the open questions:
 * Where to store the information? NOT in the component/profile specification! One strong reason for this is that changes in display information should not be allowed to affect (complicate) the versioning of the profile. One idea could be to extend the CMDI metamodel with the class DisplayComponent, each instance of which specifying one display configuration of one specific component, and stored in a separate registry. A "display configuration" could be along the lines mentioned above (grouping of elements/profiles, salient elements/components)
+[[Image(ClassDiagram2.png,200)]]
 * Yes, multiple display configurations should be allowed per component/profile.
 * Metadata modellers and tool developers should generate such display configurations. Metadata modelers at component-design-time (sort of "default display"). Tool developers could pick and choose from existing display configurations, and generate his own. At profile level, there will probably be a need to generate some kind of stylesheet based on the selected display configurations?