Changes between Version 68 and Version 69 of CMDI 1.2/Specification


Ignore:
Timestamp:
11/19/15 08:15:35 (9 years ago)
Author:
oddrun.ohren@nb.no
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • CMDI 1.2/Specification

    v68 v69  
    170170}}}
    171171
    172 = Structure of CMDI-files =
     172= Structure of CMDI files =
    173173{{{#!div class="notice system-message"
    174174Responsible for this section: Oddrun
    … …  
    179179}}}
    180180
    181 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 CMDI record. All CMDI files have the same structure at the top level. At a lower level, parts of its structure  are defined by the CMDI profile upon which it is based.
     181A 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. 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.
    182182== The main structure ==
    183183A CMDI file has the root element `<CMD>` with 4 subelements:
    … …  
    188188  * `<ResourceRelationList>,` containing a list of `<ResourceRelation>` elements, each representing a relationship between 2 resource files (as listed in the `<ResourceProxyList>`)
    189189* The `<IsPartOfList>` element, containing a list of `<IsPartOf>` elements, each referencing a larger external resource of which the described resource (as a whole) forms a part
    190 * The `<Components>` element, containing one subelement corresponding to – and in turn structured according to - the CMDI profile applied.
    191 
    192 The  profile substructure exist in the profile-specific namespace, all the rest within the cmd namespace.
    193 
    194 <About local attributes here>
    195 
    196 In the following the main parts are described in detail
     190* The `<Components>` element, containing one subelement corresponding to – and in turn structured according to - the CMD profile applied. Here the "real" metadata of the reosurce are to be found.
     191
     192The first three elements (`<Header>`, `<Resources>`and `<IsPartOfList>`) constitute the ''CMD instance envelope''and reside in the `cmd` namespace. The ''CMD instance payload'' contains the `<Components>`element, which (profile specific) substructure  exists in the profile-specific namespace (prefix `cmdp`) or cues-for-tools namespace (`cue`). 
     193
     194A detailed specification of the above mentioned parts of a CMD instance is given in the next four sections. In addition to this,  foreign attributes (XML attributes of other namespaces than those defined in the [Typographic and XML Namespace conventions])  `MAY` occur anywhere in `<Header>`, `<Resources>`and `<IsPartOfList>`elements and on the `<Components>` element (but not on any of its children).
    197195
    198196