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

Timestamp:

11/12/15 09:17:31 (9 years ago)

Author:

Twan Goosen

Comment:

CMD component properties table

CMDI 1.2/Specification/TransformationCCSLSchema

@@ -20 +20 @@
 ||= Property =||= XML schema attribute =||= Derived from =||= Use =||
 || Name of the XML element || `@name` || `@name` || `REQUIRED` ||
-|| Minimal number of occurrences || `@minOccurs` || `@CardinalityMin` || `REQUIRED` ||
+|| Minimal number of occurrences || `@minOccurs` || `@CardinalityMin` '''unless''' `@Multilingual` is true,\\in which case MUST be 'unbounded',\\or '1' if neither XML attribute is present || `REQUIRED` ^[#note1 1]^ ||
+|| Maximal number of occurrences || `@maxOccurs` || `@CardinalityMax`, or '1' if XML attribute not present || `REQUIRED` ^[#note1 1]^ ||
+|| Concept link || `@dcr:datcat` || `@ConceptLink` || `OPTIONAL` ||
+|| Component id || `@cmd:ComponentId` || `@ComponentId` || `OPTIONAL` ||
+^[=#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
 
 {{{#!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.