Changes between Version 2 and Version 3 of CMDI 1.2/Specification/TransformationCCSLSchema

Timestamp:

11/11/15 16:28:21 (9 years ago)

Author:

Twan Goosen

Comment:

Interpretation of CMD component definitions in the CCSL (partial)

CMDI 1.2/Specification/TransformationCCSLSchema

@@ -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.
 
-The transformation `MAY` make use of embedded component identifiers to derive (complex) types that can be reused throughout the schema definition.
+The transformation `MAY` make use of embedded component identifiers in the CMD component definition to derive (complex) types that can be reused throughout the schema definition.
+
+=== Interpretation of CMD component definitions in the CCSL ===
+CMD Components which are represented as `Component` XML elements in the CCSL, `MUST` be realised as XML element declarations with the following property mapping:
+
+||= Property =||= XML schema attribute =||= Derived from =||= Use =||
+|| Name of the XML element || `@name` || `@name` || `REQUIRED` ||
+|| Minimal number of occurrences || `@minOccurs` || `@CardinalityMin` || `REQUIRED` ||
+
+{{{#!comment
+- CMD Components, represented as "Component" XML elements in the CCSL, MUST be realised as XML element declarations with the following property mapping:
+    - MANDATORY: Name of the XML element: @name
+    - MANDATORY: Minimal number of occurrences: @CardinalityMin, MUST be evaluated as '1' if this XML attribute is missing
+    - MANDATORY: Maximal number of occurrences: @CardinalityMax unless @Multilingual is true, in which case MUST be 'unbounded', otherwise MUST be evaluated as '1' if @CardinalityMax is not present
+    - OPTIONAL: Concept link by means of an XML attribute "dcr:datcat" on the XML element within the schema definition: @ConceptLink
+    - OPTIONAL: Component id by means of an XML attribute "cmd:ComponentId" on the XML element within the schema definition: @ComponentId
+- 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.
+- 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.
+- An optional XML Attribute "cmd:ref" of type "xs:IDREFS" MUST be allowed on the XML container element derived from any CMD component.
+- "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.
+- [ ] display cues (all attributes in cue namespace should be copied)
+}}}