Browse wiki

en:<b>Audubon Core:</b> 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 ([http://www.w3.org W3C]) [http://www.w3.org/TR/NOTE-datetime 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 [http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=40874 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 [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.

<b>Audubon Core:</b> 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 ([http://www.w3.org W3C]) [http://www.w3.org/TR/NOTE-datetime 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 [http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=40874 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 [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.

[[SMW::off]] <tr id="dcterms:available"> <td id="Date_Available" width="100px" style="text-align:right; vertical-align:bottom;background:#EEE; border-bottom: 1px solid #CCC; padding:1.1em 0.5em 0.5em 0.5em;">Concept Name:</td> <td style="text-align:left; vertical-align:bottom;background:#EEE;border-right: 1px solid #CCC; border-bottom: 1px solid #CCC; padding:1.1em 0.5em 0.5em 0.5em;">'''[[dcterms:available]]'''</td> </tr><tr> <td style="text-align:right;vertical-align:top;background:#EEE;border-right:1px solid #CCC; border-bottom: 1px solid #CCC; padding:0.5em;">Normative URI</td> <td style="border-right: 1px solid #CCC; border-bottom: 1px solid #CCC; padding:0.5em;">http://purl.org/dc/terms/available</td> </tr><tr> <td style="text-align:right;vertical-align:top;background:#EEE;border-right:1px solid #CCC; border-bottom: 1px solid #CCC; padding:0.5em;">Label</td> <td style="border-right: 1px solid #CCC; border-bottom: 1px solid #CCC; padding:0.5em;">Date Available</td> </tr><tr> <td style="text-align:right;vertical-align:top;background:#EEE;border-right:1px solid #CCC; border-bottom: 1px solid #CCC; padding:0.5em;">Definition</td> <td style="border-right: 1px solid #CCC; border-bottom: 1px solid #CCC; padding:0.5em;">Date (often a range) that the resource became or will become available.</td> </tr><tr> <td style="text-align:right;vertical-align:top;background:#EEE;border-right:1px solid #CCC; border-bottom: 1px solid #CCC; padding:0.5em;">Defined By</td> <td style="border-right: 1px solid #CCC; border-bottom: 1px solid #CCC; padding:0.5em;">http://dublincore.org/documents/dcmi-terms/#terms-available</td> </tr><tr> <td style="text-align:right;vertical-align:top;background:#EEE;border-right:1px solid #CCC; border-bottom: 1px solid #CCC; padding:0.5em;"> </td> <td style="border-right: 1px solid #CCC; border-bottom: 1px solid #CCC; padding:0.5em;">'''Required: ''' No — '''Repeatable: ''' No<span class="debug-required-repeatable" style="display:none;">http://purl.org/dc/terms/available, </span></td> </tr><tr> <td style="text-align:right;vertical-align:top;background:#EEE;border-right:1px solid #CCC; border-bottom: 1px solid #CCC; padding:0.5em;">Notes:</td> <td style="border-right: 1px solid #CCC; border-bottom: 1px solid #CCC; padding:0.5em;"><b>Audubon Core:</b> 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 ([http://www.w3.org W3C]) [http://www.w3.org/TR/NOTE-datetime 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 [http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=40874 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 [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.</td></tr>[[SMW::on]]