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


Ignore:
Timestamp:
11/12/15 10:35:49 (9 years ago)
Author:
Twan Goosen
Comment:

Interpretation of CMD attribute definitions in the CCSL

Legend:

Unmodified
Added
Removed
Modified

  • CMDI 1.2/Specification/TransformationCCSLSchema

    v6 v7  
    4242CMD 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.
    4343
     44CMD 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.
     45
    4446=== Interpretation of CMD element definitions in the CCSL ===
    4547CMD elements, represented as `<Element>` XML elements in the CCSL, `MUST` be realised as XML element declarations with the following property mapping:
    … …  
    4951|| 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]^ ||
    5052|| Maximal number of occurrences || `@maxOccurs` || `@CardinalityMax`, or '1' if XML attribute not present || `REQUIRED` ^[#ioceditc-note1 1]^ ||
     53|| Type of the XML element || `@type` || See section 'Content model' || ||
    5154|| Concept link || `@dcr:datcat` || `@ConceptLink` || `OPTIONAL` ||
    5255{{{#!comment
    … …  
    6467
    6568The derivation of a content model for the XML element declaration on basis of a CMD element is described below.
     69
     70=== Interpretation of CMD attribute definitions in the CCSL ===
     71CMD attributes, represented as `<Attribute>` XML elements in the CCSL, `MUST` be realised as XML attribute declarations with the following property mapping:
     72
     73||= Property =||= XML schema attribute =||= Derived from =||= Use =||
     74|| Name of the XML element || `@name` || `@name` || `REQUIRED` ||
     75|| Use of the XML attribute || `@use` || 'required' if and only if `@Required` is present and equals true, otherwise 'optional' || `REQUIRED` ^[#iocaditc-note1 1]^ ||
     76|| Type of the XML attribute || `@type` |||| See section 'Content model' ||
     77|| Concept link || `@dcr:datcat` || `@ConceptLink` || `OPTIONAL` ||
     78{{{#!comment
     79TODO
     80- [ ] AutoValue
     81}}}
     82^[=#iocaditc-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
     83
     84`<Documentation>` XML elements contained in CMD attributes `MAY` be transformed into documentation elements embedded in the XML attribute declaration In these, the content language information contained in the `@xml:lang` XML attribute `SHOULD` be preserved.
     85
     86The derivation of a content model for the XML attribute declaration on basis of a CMD attribute is described below.
     87
     88{{{#!comment
     89TODO
     90    - [ ] display cues (all attributes in cue namespace should be copied)
     91}}}