Changes between Version 5 and Version 6 of CMDI 1.2/Specification/TransformationCCSLSchema


Ignore:
Timestamp:
11/12/15 09:36:19 (9 years ago)
Author:
Twan Goosen
Comment:

Interpretation of CMD element definitions in the CCSL

Legend:

Unmodified
Added
Removed
Modified

  • CMDI 1.2/Specification/TransformationCCSLSchema

    v5 v6  
    1616
    1717=== Interpretation of CMD component definitions in the CCSL ===
    18 CMD Components which are represented as `Component` XML elements in the CCSL, `MUST` be realised as XML element declarations with the following property mapping:
     18CMD Components which are represented as `<Component>` XML elements in the CCSL, `MUST` be realised as XML element declarations with the following property mapping:
    1919
    2020||= Property =||= XML schema attribute =||= Derived from =||= Use =||
    2121|| Name of the XML element || `@name` || `@name` || `REQUIRED` ||
    22 || 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]^ ||
    23 || Maximal number of occurrences || `@maxOccurs` || `@CardinalityMax`, or '1' if XML attribute not present || `REQUIRED` ^[#note1 1]^ ||
     22|| Minimal number of occurrences || `@minOccurs` || `@CardinalityMin`, or '1' if XML attribute not present || `REQUIRED` ^[#ioccditc-note1 1]^ ||
     23|| Maximal number of occurrences || `@maxOccurs` || `@CardinalityMax`, or '1' if XML attribute not present || `REQUIRED` ^[#ioccditc-note1 1]^ ||
    2424|| Concept link || `@dcr:datcat` || `@ConceptLink` || `OPTIONAL` ||
    2525|| Component id || `@cmd:ComponentId` || `@ComponentId` || `OPTIONAL` ||
    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
     26^[=#ioccditc-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
    2727
    2828An optional XML Attribute `@cmd:ref` of type ''xs:IDREFS'' `MUST` be allowed on the XML container element derived from any CMD component.
    2929
    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.
     30`<Documentation>` XML elements contained in CMD Components `MAY` be transformed into documentation elements embedded in the XML element declaration. In these, the content language information contained in the `@xml:lang` XML attribute `SHOULD` be preserved.
    3131
    3232{{{#!comment
    … …  
    4040CMD 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.
    4141
     42CMD elements `MUST` be mapped as direct descendants of the XML element declaration derived from the CMD component of which they are direct descendants, and `MUST` be required to be included in the same order as defined in the CMD specification.
     43
     44=== Interpretation of CMD element definitions in the CCSL ===
     45CMD elements, represented as `<Element>` XML elements in the CCSL, `MUST` be realised as XML element declarations with the following property mapping:
     46
     47||= Property =||= XML schema attribute =||= Derived from =||= Use =||
     48|| Name of the XML element || `@name` || `@name` || `REQUIRED` ||
     49|| 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` ^[#ioceditc-note1 1]^ ||
     50|| Maximal number of occurrences || `@maxOccurs` || `@CardinalityMax`, or '1' if XML attribute not present || `REQUIRED` ^[#ioceditc-note1 1]^ ||
     51|| Concept link || `@dcr:datcat` || `@ConceptLink` || `OPTIONAL` ||
     52{{{#!comment
     53TODO
     54- [ ] AutoValue
     55}}}
     56^[=#ioceditc-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
     57
     58`<Documentation>` XML elements contained in CMD elements `MAY` be transformed into documentation elements embedded in the XML element declaration In these, the content language information contained in the `@xml:lang` XML attribute `SHOULD` be preserved.
     59
     60{{{#!comment
     61TODO
     62    - [ ] display cues (all attributes in cue namespace should be copied)
     63}}}
     64
     65The derivation of a content model for the XML element declaration on basis of a CMD element is described below.