Changes between Version 232 and Version 233 of CMDI 1.2/Specification
- Timestamp:
- 10/04/16 08:58:31 (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
CMDI 1.2/Specification
v232 v233 196 196 = Structure of CMDI files = 197 197 [=#structureOfCmdi] 198 {{{#!div class="notice system-message" 199 Responsible for this section: Oddrun 200 }}} 201 202 '''{TODO}:''' finish and embed UML diagram ([https://drive.google.com/file/d/0B6mqjTCSImiVdFJYV2kwMVJDcTg/view?usp=sharing working version], [https://drive.google.com/file/d/0B6mqjTCSImiVQXRlNnltOXB2Ums/view?usp=sharing PDF snapshot]) 203 204 ''(Caption): The structure of a CMDI file (CMD instance). Colour scheme: Green boxes represent elements that are potentially present in all CMDI files (the CMD instance envelope). Blue boxes represent elements defined by the CMD profile (the CMD instance payload). The diagram is meant for overview and illustration; full details to be found in the tables below.'' 198 199 [[Image(CMDI_structure.png, 100%)]] 200 {{{#!comment 201 draw.io source: https://www.google.com/url?q=https://drive.google.com/drive/folders/0B6mqjTCSImiVSjhRMmJWUUQ0Nm8?usp%3Dsharing&sa=D&ust=1475574644205000&usg=AFQjCNHCfLam062408yACw1r8Qk5IvfP2w 202 }}} 203 ''The structure of a CMDI file (CMD instance). Colour scheme: Green boxes represent elements that are potentially present in all CMDI files (the CMD instance envelope). Blue boxes and associations represent elements defined by the CMD profile (the CMD instance payload). The diagram is meant for overview and illustration; full details to be found in the tables below.'' 204 ---- 205 205 206 206 A CMDI file contains the actual metadata of one specific resource (hereafter referred to as the ''described resource''), and might also be referred to as a ''CMD record'' or ''CMD instance''. All CMDI files have the same structure at the top level. At a lower level, parts of its structure are defined by the CMD profile upon which it is based. … … 487 487 ---- 488 488 = The CMDI Component Specification Language (CCSL) = 489 {{{#!div class="notice system-message"490 Responsible for this section: Thomas491 }}}492 489 493 490 The CMDI Component Specification Language (CCSL) is used to describe a CMD component or CMD profile. Hence, a CCSL document provides the structure for describing an aspect of a resource or (in the case of a profile specification) the complete payload structure of the CMD instance. It is also basis for the generation of the XML schema file that is used to validate a CMD instance (see section [#transformationIntoSchema Transformation of CCSL into a CMD schema definition] for details). … … 833 830 = Transformation of CCSL into a CMD profile schema definition = 834 831 [=#transformationIntoSchema] 835 {{{#!div class="notice system-message"836 Responsible for this section: Twan837 }}}838 832 A CMD instance document that is serialised as XML according to this specification `SHOULD` contain a reference to 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 Relax NG ([#REF_ISO-IEC_19757-2:2003 ISO/IEC 19757-2:2003]). A CMD profile schema `MUST` be derived from a CMD profile specification. 839 833