Difference between revisions of "dcterms:identifier"
From TDWG Terms Wiki
m (1 revision: scheme: Audubon Core → Audubon Core Development) |
Gabi Dröge (Talk | contribs) |
||
| Line 15: | Line 15: | ||
{{Concept scheme relation | {{Concept scheme relation | ||
|scheme=Audubon Core Development | |scheme=Audubon Core Development | ||
| + | }} | ||
| + | {{Concept scheme relation | ||
| + | |scheme=GGBN Data Standard | ||
| + | |property cardinality=0..1 | ||
}} | }} | ||
{{Concept relation | {{Concept relation | ||
| Line 31: | Line 35: | ||
|relation=rdfs: subproperty of | |relation=rdfs: subproperty of | ||
|internal page=dc:identifier | |internal page=dc:identifier | ||
| + | }} | ||
| + | {{Concept relation | ||
| + | |relation=skos: collection | ||
| + | |internal page=GGBN Gel Image Vocabulary | ||
}} | }} | ||
Revision as of 20:48, 27 May 2014
| 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)
Constraints in the context of GGBN Data Standard:
- cardinality 0..1 (=optional single occurrence)
