This HTML5 document contains 46 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

PrefixNamespace IRI
dctermshttp://purl.org/dc/terms/
foafhttp://xmlns.com/foaf/0.1/
pwdrhttp://www.w3.org/2007/05/powder-s#
dchttp://purl.org/dc/elements/1.1/
skoshttp://www.w3.org/2004/02/skos/core#
rdfshttp://www.w3.org/2000/01/rdf-schema#
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
n9http://dublincore.org/usage/terms/history/#
n10http://purl.org/dc/elements/1.1/coverage#
xsdhhttp://www.w3.org/2001/XMLSchema#
n8http://ods-qa.openlinksw.com:8896/about/id/entity/http/purl.org/dc/elements/1.1/
Subject Item
dc:coverage
rdf:type
rdf:Property
dcterms:modified
2008-01-14 2008-01-14
rdfs:comment
The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant. The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant. The spatial or temporal topic of the resource, spatial applicability of the resource, or jurisdiction under which the resource is relevant.
rdfs:isDefinedBy
dc:
rdfs:label
Coverage Coverage
pwdr:describedby
n8:relation n8:contributor n8:creator n8: n8:rights n8:description n8:date n8:identifier n8:type n8:language n8:subject n8:title
foaf:topic
dc:type dc:creator dc:date dc:contributor dc: dc:source dc:title dc:publisher dc:relation dc:identifier dc:language dc:description dc:format dc:subject n10:this dc:rights
dcterms:description
Spatial topic and spatial applicability may be a named place or a location specified by its geographic coordinates. Temporal topic may be a named period, date, or date range. A jurisdiction may be a named administrative entity or a geographic place to which the resource applies. Recommended best practice is to use a controlled vocabulary such as the Thesaurus of Geographic Names [TGN]. Where appropriate, named places or time periods can be used in preference to numeric identifiers such as sets of coordinates or date ranges. Spatial topic and spatial applicability may be a named place or a location specified by its geographic coordinates. Temporal topic may be a named period, date, or date range. A jurisdiction may be a named administrative entity or a geographic place to which the resource applies. Recommended best practice is to use a controlled vocabulary such as the Thesaurus of Geographic Names [TGN]. Where appropriate, named places or time periods can be used in preference to numeric identifiers such as sets of coordinates or date ranges. Spatial topic and spatial applicability may be a named place or a location specified by its geographic coordinates. Temporal topic may be a named period, date, or date range. A jurisdiction may be a named administrative entity or a geographic place to which the resource applies. Recommended practice is to use a controlled vocabulary such as the Getty Thesaurus of Geographic Names [[TGN](https://www.getty.edu/research/tools/vocabulary/tgn/index.html)]. Where appropriate, named places or time periods may be used in preference to numeric identifiers such as sets of coordinates or date ranges.
dcterms:issued
1999-07-02 1999-07-02
dcterms:hasVersion
n9:coverage-006
skos:note
A second property with the same name as this property has been declared in the dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the document "DCMI Metadata Terms" (http://dublincore.org/documents/dcmi-terms/) for an explanation. A [second property](/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/coverage) with the same name as this property has been declared in the [dcterms: namespace](http://purl.org/dc/terms/). See the Introduction to the document [DCMI Metadata Terms](/specifications/dublin-core/dcmi-terms/) for an explanation. A second property with the same name as this property has been declared in the dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the document "DCMI Metadata Terms" (http://dublincore.org/documents/dcmi-terms/) for an explanation.