Changes between Version 13 and Version 14 of CMDI 1.2/Specification/TransformationCCSLSchema

Timestamp:

11/12/15 14:26:27 (8 years ago)

Author:

Twan Goosen

Comment:

section levels

CMDI 1.2/Specification/TransformationCCSLSchema

@@ -1 @@
-== Transformation of CCSL into a CMD profile schema definition ==
+= Transformation of CCSL into a CMD profile schema definition =
 
 A CMD instance document that is serialised as XML according this specification `SHOULD` contain a reference the location of a CMD profile schema. The infrastructure `MUST` provide a mechanism to derive such a schema for any specific CMD profile on basis of its definition and that of the CMD components that it references. This section specifies how different aspects of a CMD specification should be transformed into elements of a schema definition. The primary schema language targeted is XML Schema, although the infrastructure `MAY` provide support for other schema languages, such as DDML or Relax NG.
@@ -6 +6 @@
 The transformation as described here is assumed to take place on the fully expanded CMD profile, i.e. a version of the specification that has all referenced (non-inline) CMD Component definitions are resolved and substituted, recursively, by their full definitions.
 
-=== General properties of the CMD profile schema definition ===
+== General properties of the CMD profile schema definition ==
 
 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.
@@ -15 +15 @@
 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 ===
+== 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:
 
@@ -32 +32 @@
 XML attributes of CMD Components in the 'cue' namespace `SHOULD` be copied into the XML element declaration, in which case the XML attribute name, namespace and value `SHOULD` be preserved.
 
-==== Document structure prescribed by the schema ====
+=== Document structure prescribed by the schema ===
 
 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.
@@ -41 +41 @@
 CMD attributes that are defined in the CCSL within "Attribute" XML elements within an "AttributeList" XML element that is a direct descendant of a CMD Component MUST be mapped to XML attribute definitions on the XML container element to which it is transformed.
 
-=== Interpretation of CMD element definitions in the CCSL ===
+== Interpretation of CMD element definitions in the CCSL ==
 CMD elements, represented as `<Element>` XML elements in the CCSL, `MUST` be realised as XML element declarations with the following property mapping:
 
@@ -61 +61 @@
 The derivation of a content model for the XML element declaration on basis of a CMD element is described below.
 
-=== Interpretation of CMD attribute definitions in the CCSL ===
+== Interpretation of CMD attribute definitions in the CCSL ==
 CMD attributes, represented as `<Attribute>` XML elements in the CCSL, `MUST` be realised as XML attribute declarations with the following property mapping:
 
@@ -78 +78 @@
 The derivation of a content model for the XML attribute declaration on basis of a CMD attribute is described below.
 
-=== Content model for CMD elements and CMD attributes in the schema definition ===
+== Content model for CMD elements and CMD attributes in the schema definition ==
 If a CMD element or CMD attribute in the CCSL has a `@ValueScheme` XML attribute, its value `MUST` be interpreted as the name of the XML Schema Datatype (declared in the `@type` attribute of the XML element or attribute declaration in XML Schema) that defines the allowed value range of the XML element/attribute derived from the CMD element/attribute.