Difference between revisions of "dcterms:identifier"
From TDWG Terms Wiki
m (Dublin Core Properties in the terms namespace → Dublin Core terms namespace) |
m (subproperty of) |
||
Line 27: | Line 27: | ||
|relation=skos: collection | |relation=skos: collection | ||
|internal page=Audubon Core Layer 1 | |internal page=Audubon Core Layer 1 | ||
+ | }} | ||
+ | {{Concept relation | ||
+ | |relation=rdfs: subproperty of | ||
+ | |internal page=Dublin Core terms namespace | ||
}} | }} |
Revision as of 17:06, 16 November 2012
Identifier |
Search for values |
Notes: Dublin Core: Recommended best practice is to identify the resource by means of a string conforming to a formal identification system. Audubon Core: An arbitrary code that is unique for the resource, with the resource being either a provider, collection, or media item. Using multiple identifiers implies that they have a same-as relationship, i.e. they all identify the same object (e. g. an object may have an http-URL, an lsid-URI, and a UUID-number).
Required for media collections, No for media resources (but preferred if available).
Constraints in the context of Dublin Core:
- rdfs:range: http://www.w3.org/2000/01/rdf-schema#Literal (=the class or datatype of the values or objects that are assigned to “dcterms:identifier”, i.e. the right side in the triple)