Changes between Version 11 and Version 12 of CMDI 1.2/Specification


Ignore:
Timestamp:
11/25/14 10:28:44 (9 years ago)
Author:
Twan Goosen
Comment:

added todo for local extensions

Legend:

Unmodified
Added
Removed
Modified
  • CMDI 1.2/Specification

    v11 v12  
    184184
    185185 Potential problems, intentionally left vague are how to deal with changed metadata files: should the !MdCreator and !MdCreationDate be adjusted? If yes, how persistent is the !MdSelfLink? As the metadata is created during the archiving state of a resource, potential updates are currently not dealt with.
     186
     187{{{#!comment
     188TODO: Include support for attributes as local extensions
     189
     190Accepted proposal by Twan & Menzo (2014-11-20 by e-mail to the members of the CMDI taskforce):
     191
     192* Allow attributes of a foreign namespace (i.e. not the general CMDI namespace) anywhere in the Header, Resources sections and on the 'Component' element (but not on any of its children) of a CMDI record, i.e. a profile instance
     193* This is achieved by modifying the component specification to XSD stylesheet
     194* There will be no consequence for existing components, profiles or records
     195* The change will be part of both CMDI 1.1 and CMDI 1.2
     196* The first application of this extension will be at TLA with the 'lat:localURI' attribute on ResourceRef elements
     197
     198Additional formal constraints proposed by Oliver:
     199
     200These local attributes
     201a) MUST be ignored by tools that don't understand them (or don't want
     202    to deal with them) and therefore MAY be removed during processing
     203b) the Namespace-Name MUST NOT contain fragments of official CLARIN
     204    namespaces, i.e. don't start with the "http://www.clarin.eu",
     205    "http://clarin.eu", etc.
     206}}}
    186207==      The resources section ==
    187208The resources section in a metadata file list all information relevant for the individual resource, but does not describe the resource as such. The description is part of the components, the resource section provides the location of the resource or its parts if it consists of more than one, provenance information on the resource, information on the relation between the parts of the resource, if applicable and information of a greater body the resource is part of, also if applicable.