Difference between revisions of "dcterms:available"

From TDWG Terms Wiki
Jump to: navigation, search
m (1 revision: skos: in scheme is handled by template: Concept scheme relation)
(One intermediate revision by the same user not shown)
Line 1: Line 1:
 
{{Concept
 
{{Concept
| is defined by = http://dublincore.org/documents/dcmi-terms/#terms-available
+
|label=Date Available
| label = Date Available
+
|definition=Date (often a range) that the resource became or will become available.
| definition =  
+
|notes=<b>Audubon Core:</b> The date (often a range) that the resource became or will become available. {{Audubon Core datetime explanation}}
| notes = <b>Audubon Core:</b> The date (often a range) that the resource became or will become available. {{Audubon Core datetime explanation}}
+
  
 
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 [http://en.wikipedia.org/wiki/ISO_8601 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 [http://en.wikipedia.org/wiki/ISO_8601 wikipedia IS0 8601 entry] for further explanation and examples.
| hidden notes = Crosswalk: NBII = Date Published; KeyToNature = (not supported); Dublin Core = same as {{NS dcterms | available}}; Morphbank = dateToPublish // Repeatable = No
+
|is defined by=http://dublincore.org/documents/dcmi-terms/#terms-available
| concept type = property
+
|concept type=property
 +
|hidden notes=Crosswalk: NBII = Date Published; KeyToNature = (not supported); Dublin Core = same as {{NS dcterms | available}}; Morphbank = dateToPublish // Repeatable = No
 
}}
 
}}
 
{{Concept scheme relation
 
{{Concept scheme relation
 
|scheme=Dublin Core
 
|scheme=Dublin Core
 +
|property range=http://www.w3.org/2000/01/rdf-schema#Literal
 
}}
 
}}
 
{{Concept scheme relation
 
{{Concept scheme relation
 
|scheme=Audubon Core
 
|scheme=Audubon Core
 +
}}
 +
{{Concept relation
 +
|relation=skos: collection
 +
|internal page=Dublin Core Properties in the terms namespace
 
}}
 
}}
 
{{Concept relation
 
{{Concept relation

Revision as of 13:36, 15 November 2012

Schemes: Dublin Core Pencil.png, Audubon Core Development Pencil.png
Collections: Dublin Core terms namespace Pencil.png, Audubon Core Management Vocabulary Pencil.png, Audubon Core Layer 2 Pencil.png
Date Available
Search for values Crystal Clear action find.png
Date Available: Date (often a range) that the resource became or will become available.

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: