Changes between Version 95 and Version 96 of CMDI 1.2/Specification
- Timestamp:
- 01/19/16 14:31:30 (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
CMDI 1.2/Specification
v95 v96 146 146 147 147 === Typographic and XML Namespace conventions === 148 [=#typography_namespaces] 148 149 The following typographic conventions for XML fragments will be used throughout this specification: 149 150 * `<prefix:Element>` \\ An XML element with the Generic Identifier ''Element'' that is bound to an XML namespace denoted by the prefix ''prefix''. … … 189 190 * `<ResourceRelationList>,` containing a list of `<ResourceRelation>` elements, each representing a relationship between 2 resource files (as listed in the `<ResourceProxyList>`) 190 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 191 * 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.192 193 The 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`).194 195 A 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).192 * The `<Components>` element, containing one subelement corresponding to – and in turn structured according to - the CMD profile applied. Here the descriptive metadata of the resource are found. 193 194 The 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`), possibly adorned with attributes in the cmd namespace. 195 196 A 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 [#typography_namespaces 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). 196 197 197 198 === Examples === … … 251 252 252 253 ||||=Name=||=Value type=||=Occurrences=||=Description=|| 253 ||||`<Header>`||`xs:complexType`||1||Encapsulates core admi strative data about the CMDI file||254 ||||`<Header>`||`xs:complexType`||1||Encapsulates core administrative data about the CMDI file|| 254 255 || ||`<MdCreator>`||`xs:string`||0 to unbounded||Denotes the creator of this metadata file|| 255 256 || ||`<MdCreationDate>`||`xs:date`||0 or 1||The date this metadata file was created|| 256 257 || ||`<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|| 257 258 || ||`<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|| 258 || ||`<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.||259 || ||`<MdCollectionDisplayName>`||`xs:string`||0 or 1||The collection to which the described resource belongs, given as a human-readable name. Exploitation tools can use this name to present metadata collections.|| 259 260 260 261 === Examples === … … 284 285 || ||||||`<ResourceProxy>` ||`xs:complexType`||0 to unbounded||Represents a file which is a part of or closely related to the described resource|| 285 286 || || ||||`@id`||`xs:ID`||1||Local identifier for the parent `<ResourceProxy>`, unique within this CMDI file|| 286 || || ||||`<ResourceType>` || Value from controlled set (`cmd:Resourcetype_simple`): `Resource`,`Metadata`,`LandingPage`,`SearchService`,`SearchPage`||1||The type of the file represented by this `<ResourceProxy>`||287 || || ||||`<ResourceType>` ||`xs:string` ("Resource", "Metadata", "LandingPage", "SearchService", "SearchPage")||1||The type of the file represented by this `<ResourceProxy>`|| 287 288 || || || ||`@mimeType`||`xs:string`||0 or 1||The media type of the file|| 288 || || ||||`<ResourceRef>`||`xs:anyURI`||1||A reference to the file represented by this `<ResourceProxy>`, in the form of a Clarincompliant PID or a regular URL||289 || || ||||`<ResourceRef>`||`xs:anyURI`||1||A reference to the file represented by this `<ResourceProxy>`, in the form of a CLARIN-compliant PID or a regular URL|| 289 290 290 291 … … 295 296 ||||||`<JournalFileProxyList>` ||`xs:complexType`||1||Contains a list of journal file proxies (see below)|| 296 297 || ||||`<JournalFileProxy>` ||`xs:complexType`||0 to unbounded||Represents a file containing provenance information about the described resource|| 297 || || ||`<JournalFileRef>`||`xs:anyURI`||1||A reference to the file represented by this `<JournalFileProxy>`, in the form of a C larincompliant PID or a regular URL||298 || || ||`<JournalFileRef>`||`xs:anyURI`||1||A reference to the file represented by this `<JournalFileProxy>`, in the form of a CLARIN-compliant PID or a regular URL|| 298 299 299 300 === The list of relations between resource files === … … 301 302 302 303 ||||||||||=Name=||=Value type=||=Occurrences=||=Description=|| 303 ||||||||||`<ResourceRelationList>`||`xs:complexType`||1|| A representation of a relation between 2 resource proxies listed in `<ResourceProxyList>`||304 ||||||||||`<ResourceRelationList>`||`xs:complexType`||1||Contains a list of journal file proxies (see below)|| 304 305 || ||||||||`<ResourceRelation>`||`xs:complexType`||0 to unbounded||A representation of a relation between 2 resource proxies listed in `<ResourceProxyList>`|| 305 306 || || ||||||`<RelationType>`||`xs:string`||1||The type of the relation represented by its parent `<ResourceRelation>`|| 306 || || || ||||`@ConceptLink`||`xs:anyURI`||0 or 1||A reference to some concept registry (C larinConcept Registry by default), indicating the semantics of `<RelationType>`||307 || || || ||||`@ConceptLink`||`xs:anyURI`||0 or 1||A reference to some concept registry (CLARIN Concept Registry by default), indicating the semantics of `<RelationType>`|| 307 308 || || ||||||`<Resource>`||`xs:complexType`||2||References one of the resource proxies participating in the relationship|| 308 309 || || || ||||`@ref`||`xs:IDREF`||1||A reference to the `<ResourceProxy>` with id=ref (the `<ResourceProxy>` represented by its parent `<Resource>` element)|| 309 310 || || || ||||`<Role>`||`xs:string`||0 or 1||Indicates the role its parent Resource plays in the relationship|| 310 || || || || ||`@ConceptLink`||`xs:anyURI`||0 or 1||A reference to some concept registry (C larin Concept Registry by default), indicating the semantics of `<RelationType>`||311 || || || || ||`@ConceptLink`||`xs:anyURI`||0 or 1||A reference to some concept registry (CLARIN Concept Registry by default), indicating the semantics of `<Role>`|| 311 312 312 313 … … 316 317 ||||=Name=||=Value type=||=Occurrences=||=Description=|| 317 318 ||||`<IsPartOfList>` ||`xs:complexType`||0 or 1||Contains a list of `<IsPartOf>`(see below)|| 318 || ||`<IsPartOf>` ||`xs:anyURI`||0 to unbounded||A reference to an external resource of which the described resource is a part, in the form of a C larincompliant PID or a regular URL||319 || ||`<IsPartOf>` ||`xs:anyURI`||0 to unbounded||A reference to an external resource of which the described resource is a part, in the form of a CLARIN-compliant PID or a regular URL|| 319 320 320 321 === Examples === … … 339 340 340 341 == The components == 341 This part of the CMDI file forms what may be referred to as «real»metadata about the described resource. Both content and structure are completely defined by the CMD Profile referenced by the XML element`<MdProfile>` in `<Header>`.342 This part of the CMDI file forms what may be referred to as descriptive metadata about the described resource. Both content and structure are completely defined by the CMD Profile referenced by the XML element`<MdProfile>` in `<Header>`. 342 343 343 344 ||||||||=Name=||=Value type=||=Occurrences=||=Description=|| 344 345 ||||||||`<Components>` ||`xs:complexType`||1||Contains 1 occurrence of an XML element named according to selected CMD profile|| 345 346 || ||||||`<{CMDProfile}>` ||`xs:complexType`||1||The XML element housing all the metadata about the described resource, complying with the {CMDProfile} schema || 347 || || ||||`@cmd:ref`||xs:IDREF||0 or 1||Reference to a `<ResourceProxy>` with id=ref, to which this substructure specifically applies|| 348 || || ||||`@{CMDAttribute}`||Subset of XSD datatypes||As specified||Custom attribute, defined as an allowed or mandatory child in a component specification|| 346 349 || || ||||`<{CMDElement}>`||Subset of XSD datatypes||0 to unbounded||Atomic piece of information about the described resource|| 347 350 || || || ||`@xml:lang`||`xs:string`||0 or 1||Indicates the language of the {CMDElement} content, by a 2 letter language tag from ISO 639|| 348 || || || ||`@ConceptLink`||`xs:anyURI`||0 or 1||Reference to a concept in an external vocabulary. Used in case the value {CMDElement} is selected from a controlled vocabulary|| 351 || || || ||`@cmd:ref`||xs:IDREF||0 or 1||Reference to a `<ResourceProxy>` with id=ref, to which this substructure specifically applies|| 352 || || || ||`@cmd:ValueConceptLink`||`xs:anyURI`||0 or 1||Reference to a concept in an external vocabulary. Used in case the value {CMDElement} is selected from a controlled vocabulary|| 353 || || || ||`@{CMDAttribute}`||Subset of XSD datatypes||As specified||Custom attribute, defined as an allowed or mandatory child in a component specification|| 349 354 || || ||||`<{CMDComponent}>`||`xs:complexType`||0 to unbounded||A chunk of information about the described resource, recursively composed of CMD Elements and other CMD Components|| 350 || || || ||`@ComponentId`||`xs:anyURI`||0 or 1||Reference to the specification of {{CMDComponent} in Component Registry. If not present, {CMDComponent} is defined locally within its parent CMD component || 355 || || || ||`@cmd:ComponentId`||`xs:anyURI`||0 or 1||Reference to the specification of {CMDComponent} in Component Registry. If not present, {CMDComponent} is defined locally within its parent CMD component || 356 || || || ||`@cmd:ref`||xs:IDREF||0 or 1||Reference to a `<ResourceProxy>` with id=ref, to which this substructure specifically applies|| 357 || || || ||`@{CMDAttribute}`||Subset of XSD datatypes||As specified||Custom attribute, defined as an allowed or mandatory child in a component specification|| 351 358 352 359 = The CMDI Component Specification Language (CCSL)=