Context Navigation

Display information

-                      v15
+                      v16
  * Merging of components contained within one other
 * Salient element selection - an alternative/replacement for display priorities allowing the client to select one or  elements representing the component in which they are contained for summarised display (e.g. in a tree). Logic might be more sophisticated than a single priority number.
-Open questions:
-* Where to store this information? (In the profile/schema, in a separate file linked from the profile/schema?)
-* Will we allow multiple sets per profile for different scenarios (like CSS)?
-* How will this information be generated and by whom? (Part of component registry/separate editor,separate registry?)
 == Proposed solution ==
 …
 === Pros ===
+Pros of this solution
+* A pure extension, it's optional for any tool to support this
+* Multiple styles can be created for each component or profile
+* Generic styles are possible (but probably of limited use)
+* Instances can point a styled schema for a default visualisation or to the unstyled schema just as easily
 === Cons ===
+* XSLT's cannot be constrained to only add style info (i.e. arbitrary transformations are possible)
+* Cues may not always be applicable, so tools will have to be tolerant and unexpected (side) effects cannot be prevent completely (as with CSS)
 Cons of this solution