Context Navigation

Display information

v6	v7
74	74	Oddrun: I for one think it's a great idea to provide more display information! To the open questions:
75	75	* 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)
76		[[Image(ClassDiagram2.png,200)]]
	76	[[Image(ClassDiagram2.png,300)]]
77	77	* Yes, multiple display configurations should be allowed per component/profile.
78	78	* 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?