Changes between Version 16 and Version 17 of CMDI 1.2/Cues/Display information
- Timestamp:
- 02/11/14 13:44:54 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
CMDI 1.2/Cues/Display information
v16 v17 34 34 * The 'style registry' could be integrated with the Component Registry though. 35 35 36 The required '''infrastructure''' extensions can be developed at a later stage, but for CMDI 1.2 it is important to '''prepare the model''' for inclusion of display style attributes. This would be achieved by allowing any attribute from the display cues namespace on component, element and attribute specifications. 37 36 38 === Pros === 37 39 … … 44 46 45 47 * XSLT's cannot be constrained to only add style info (i.e. arbitrary transformations are possible) 46 * Cues may not always be applicable, so tools will have to be tolerant and unexpected (side) effects cannot be prevent completely (as with CSS) 47 48 Cons of this solution 48 * Cues may not always be applicable in every context, so tools will have to be tolerant and unexpected (side) effects cannot be prevent completely (as with CSS) 49 49 50 50 === Centre impact === … … 65 65 Cues will be represented on the model level only (component specification -> XSD), not on the instance level 66 66 67 ==== Implementation on model level ====67 ==== Implementation on component model level ==== 68 68 69 69 Allowing any attribute in the cues namespace on components, elements and attributes (or maybe different namespaces).
