Changes between Version 4 and Version 5 of CMDI 1.2/Specification/TransformationCCSLSchema
- Timestamp:
- 11/12/15 09:25:52 (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
CMDI 1.2/Specification/TransformationCCSLSchema
v4 v5 9 9 10 10 A CMD profile schema `MUST` be a single document {or set of linked documents with a single entry point}(?) that allows for the evaluation of a CMD instance on all levels of description defined in one specific CMD profile. 11 The schema `MUST` require the presence of a CMD instance envelope as described in section "Structure of CMDI-files". The value of the ` MdProfile` header item`MUST` only be valid if it is equal to the profile id as specified in the associated CMD profile.11 The schema `MUST` require the presence of a CMD instance envelope as described in section "Structure of CMDI-files". The value of the `<MdProfile>` header item in the CMD instance envelope `MUST` only be valid if it is equal to the profile id as specified in the associated CMD profile. 12 12 13 13 The CMD profile schema `MAY` include, as a matter of annotation, a copy of (a subset of) the information contained in the `Header` section of the CMD profile from which it is derived. … … 26 26 ^[=#note1 1]^The implementation may make use of default evaluation of the schema language if it matches these requirements, as is the case with XML Schema, and therefore omit explicit declaration of these properties 27 27 28 An optional XML Attribute `@cmd:ref` of type ''xs:IDREFS'' `MUST` be allowed on the XML container element derived from any CMD component. 29 30 `<Documentation>` XML elements contained in CMD Components `MAY` be transformed into documentation XML elements embedded in the XML element declaration. In these, the content language information contained in the `@xml:lang` XML attribute `SHOULD` be preserved. 31 28 32 {{{#!comment 29 - The first CMD component defined in the CMD profile (the 'root component') MUST be mapped as the mandatory, only direct descendant of the "Components" XML element of the CMD instance envelope. 30 - CMD components that are defined as direct descendants of another CMD component MUST be mapped as direct descendants of the XML element declaration to which it is transformed and MUST be required to be included in the same order as defined in the CMD specification, the first of the resulting XML elements appearing after the last XML element derived from a CMD element at the same level, if present. These CMD Components MUST be mapped to XML element declarations recursively as described in this specification. 31 - An optional XML Attribute "cmd:ref" of type "xs:IDREFS" MUST be allowed on the XML container element derived from any CMD component. 32 - "Documentation" XML elements contained in CMD Components MAY be transformed into documentation XML elements embedded in the XML element declaration, in which case the content language information contained in the "xml:lang" XML attribute SHOULD be preserved. 33 TODO 33 34 - [ ] display cues (all attributes in cue namespace should be copied) 34 35 }}} 36 37 ==== Document structure prescribed by the schema ==== 38 39 The first CMD component defined in the CMD profile (the "root component") `MUST` be mapped as the mandatory, only direct descendant of the `<Components>` XML element of the CMD instance envelope. 40 CMD components that are defined as direct descendants of another CMD component `MUST` be mapped as direct descendants of the XML element declaration to which it is transformed. XML components at the CMD component level in the metadata instance `MUST` be required to be included in the same order as defined in the CMD specification, the first of the resulting XML elements appearing after the last XML element derived from a CMD element at the same level, if present. These descendant CMD Components `MUST` also be mapped to XML element declarations recursively as described in this specification. 41