Changes between Version 46 and Version 47 of CMDI 1.2/Specification


Ignore:
Timestamp:
11/17/15 12:34:15 (9 years ago)
Author:
oddrun.ohren@nb.no
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • CMDI 1.2/Specification

    v46 v47  
    183183A 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.
    184184== The main structure ==
    185 A CMDI file has the root element CMD with 4 subelements:
    186 * The `Header` element, containing certain administrative information about the CMDI file, i.e. metadata about the file itself
    187 * The `Resources` element, listing resource proxies and their interrelations, by the following subelements (ordered)
    188   * `ResourceProxyList`, containing a list of `ResourceProxy` elements, each referencing a file contained in or closely related to the described resource
    189   * `JournalFileProxyList`, containing a list of `JournalFileProxy` elements, each referencing a file (“journal file”) containing provenance information about the described resource
    190   * `ResourceRelationList,` containing a list of `ResourceRelation` elements, each representing a relationship between 2 resource files (as listed in the ResourceProxyList)
    191 * 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
    192 * The `Components` element, containing one subelement corresponding to – and in turn structured according to - the CMDI profile applied.
     185A CMDI file has the root element `<CMD>` with 4 subelements:
     186* The `<Header>` element, containing certain administrative information about the CMDI file, i.e. metadata about the file itself
     187* The `<Resources>` element, listing resource proxies and their interrelations, by the following subelements (ordered)
     188  * `<ResourceProxyList>`, containing a list of `<ResourceProxy>` elements, each referencing a file contained in or closely related to the described resource
     189  * `<JournalFileProxyList>`, containing a list of `<JournalFileProxy>` elements, each referencing a file (“journal file”) containing provenance information about the described resource
     190  * `<ResourceRelationList>,` containing a list of `<ResourceRelation>` elements, each representing a relationship between 2 resource files (as listed in the `<ResourceProxyList>`)
     191* 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
     192* The `<Components>` element, containing one subelement corresponding to – and in turn structured according to - the CMDI profile applied.
    193193
    194194The  profile substructure exist in the profile-specific namespace, all the rest within the cmd namespace.
     
    199199
    200200
    201 ==      The `Header` element==
     201==      The `<Header>` element==
    202202
    203203{{{#!comment
     
    224224The header of a CMDI file mainly contains administrative information about the metadata, that is metadata about the CMDI file itself. The following elements may be included in the order indicated:
    225225
    226 ||Name||Value type||Occurrences||Description||
    227 ||`Header`||xs:complexType||1||Encapsulates core admistrative data about the CMDI file||
    228 ||...`MdCreator`||xs:string||0 to unbounded||Denotes the creator of this metadata file||
    229 ||...`MdCreationDate`||xs:date||0 or 1||The date this metadata file was created||
    230 ||...`MdSelfLink`||xs:anyURI||0 or 1||A reference to this metadata file in its home repository, in the form of a PID (preferred) or a URL||
    231 ||...`MdProfile`||xs:anyURI||1||The CMDI profile  upon which this metadata file is based, given by its identifier in the Component Registry, e.g. clarin.eu:cr1:p_1407745711925||
    232 ||...`MdCollectionDisplayName`||xs:string||0 or 1||The collection to which the described resource belongs, given as a human-readable name. In VLO this name will be assigned to the Collection facet.||
     226||=Name=||=Value type=||=Occurrences=||=Description=||
     227||`<Header>`||xs:complexType||1||Encapsulates core admistrative data about the CMDI file||
     228||...`<MdCreator>`||`xs:string`||0 to unbounded||Denotes the creator of this metadata file||
     229||...`<MdCreationDate>`||`xs:date`||0 or 1||The date this metadata file was created||
     230||...`<MdSelfLink>`||`xs:anyURI`||0 or 1||A reference to this metadata file in its home repository, in the form of a PID (preferred) or a URL||
     231||...`<MdProfile>`||`xs:anyURI`||1||The CMDI profile  upon which this metadata file is based, given by its identifier in the Component Registry, e.g. clarin.eu:cr1:p_1407745711925||
     232||...`<MdCollectionDisplayName>`||`xs:string`||0 or 1||The collection to which the described resource belongs, given as a human-readable name. In VLO this name will be assigned to the Collection facet.||
    233233 
    234234