Difference between revisions of "dcterms:available"
m (Dublin Core Properties in the terms namespace → Dublin Core terms namespace) |
m (Dublin Core Properties in the terms namespace → Dublin Core terms namespace) |
||
| Line 14: | Line 14: | ||
}} | }} | ||
{{Concept scheme relation | {{Concept scheme relation | ||
| − | |scheme=Audubon Core | + | |scheme=Audubon Core Development |
}} | }} | ||
{{Concept relation | {{Concept relation | ||
Revision as of 11:38, 15 November 2013
| Date Available |
Search for values  |
Notes: Audubon Core: The date (often a range) that the resource became or will become available. The date and time must comply with the World Wide Web Consortium (W3C) datetime practice, which requires that date and time representation correspond to ISO 8601:1998, but with year fields always comprising 4 digits. This makes datetime records compliant with 8601:2004. AC datetime values may also follow 8601:2004 for ranges by separating two IS0 8601 datetime fields by a solidus ("forward slash", '/'). See also the wikipedia IS0 8601 entry for further explanation and examples.
A use case is the harvesting of metadata published before the media are available, which are pending a formal publication elsewhere. One important example is the case of metadata that documents an occurrence, which metadata harvesters might exploit without use of the media.See also the wikipedia IS0 8601 entry for further explanation and examples.
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:available”, i.e. the right side in the triple)
