Changes between Version 22 and Version 23 of CMDI 1.2/Specification


Ignore:
Timestamp:
11/09/15 16:15:30 (9 years ago)
Author:
Twan Goosen
Comment:

dumped first notes for "Transformation of CCSL into a CMD profile schema" section

Legend:

Unmodified
Added
Removed
Modified
  • CMDI 1.2/Specification

    v22 v23  
    271271==      Attributes for elements and components ==
    272272
    273 =       Transformation of CCSL into a schema =
     273=       Transformation of CCSL into a CMD profile schema =
    274274{{{#!div class="notice system-message"
    275275Responsible for this section: Twan
    276276}}}
    277277
    278 
    279 ==      Interpretation of hierarchies of the CCSL ==
    280 
    281 ==      Interpretation of the order or elements ==
    282 
    283 ==      Interpretation of attributes ==
     278A CMD instance document that is serialised as XML according this specification SHOULD 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 document. The primary schema language targeted is XML Schema, although the infrastructure MAY provide support for other schema languages, such as DDML or Relax NG.
     279    - CMD profile schemas SHOULD NOT (MUST NOT?) be derived from CMD specifications that are not CMD profiles.
     280
     281Global schema properties
     282    - Linked components should be included, expanded
     283    - 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 CMD instance on all levels of description defined in one specific CMD profile.
     284    - The CMD profile schema MAY include, as a matter of annotation, a copy of (a subset of) the header information contained in the CMD profile from which it is defined.
     285    - The CMD profile schema MUST use the following namespaces:
     286        - {cmd} http://www.clarin.eu/cmd/
     287
     288            - targeted namespace
     289        - {ann} http://www.clarin.eu
     290
     291            - for annotation and documentation purposes that are outside the scope of instance validation
     292        - {dcr} http://www.isocat.org/ns/dcr
     293
     294            - for embedded semantic annotation
     295== Interpretation of CMD header ==
     296== Interpretation of CMD component definitions in the CCSL ==
     297    - Interpretation of hierarchies in the CCSL
     298    - concept links
     299    - order of children
     300    - elements -> see elements
     301    - attributes -> see attributes
     302== Interpretation of CMD element definitions in the CCSL ==
     303    - content model (value scheme)
     304    - concept links
     305    - order of children
     306    - attributes -> see attributes
     307== Interpretation of CMD attribute definitions in the CCSL ==
     308    - content model (value scheme) - same as element??
     309    - concept links
     310
    284311
    285312= Appendices =