|Creator:||DCMI Usage Board|
|Description of Document:||This editorial clarification to the description of a DCMI metadata term was approved by the DCMI Usage Board.|
The following change was approved by the DCMI Usage Board in May 2012.
To delete the sentence
To describe the spatial or temporal topic of the resource, use the Coverage element.
from the usage comments for dc:subject and dcterms:subject, which currently read:
Typically, the subject will be represented using keywords, key phrases, or classification codes. Recommended best practice is to use a controlled vocabulary. To describe the spatial or temporal topic of the resource, use the Coverage element.
The definitions of Subject [1,2] and Coverage [3,4] clearly overlap because a "spatial or temporal topic of the resource" is also a "topic of the resource"). The intent of the usage comment was to provide guidance for users who prefer to use Dublin Core elements in non-overlapping ways. It has however been suggested that this comment creates ambiguity, for some readers, about whether the definitions really overlap. This ambiguity can be avoided by simply removing the sentence.
 http://dublincore.org/documents/dcmi-terms/#elements-subject  http://dublincore.org/documents/dcmi-terms/#terms-subject  http://dublincore.org/documents/dcmi-terms/#elements-coverage  http://dublincore.org/documents/dcmi-terms/#elements-coverage
It was noticed in October 2010  that the (correct) statement:
dcterms:AgentClass rdfs:subClassOf rdfs:Class .
had inexplicably been replaced by the statement -- incorrect but not "wrong":
dcterms:AgentClass rdfs:subClassOf rdfs:AgentClass .
Tom Baker traced this back to an editorial error in the sources used to build the documentation:
$ diff 2008-01-14/xmldata/dcterms-classes.xml 2010-10-11/xmldata/dcterms-classes.xml < <Narrower-Than>http://www.w3.org/2000/01/rdf-schema#Class</Narrower-Than> --- > <Narrower-Than>http://purl.org/dc/terms/AgentClass</Narrower-Than>
As the error was at the time considered "harmless though redundant," its correction was postponed until the next regular build of DCMI Metadata Terms.
The DCMI Type Vocabulary, hitherto published (redundantly) as part of both DCMI Metadata Terms and a separate DCMI Type Vocabulary document, will henceforth be published only as part of DCMI Metadata Terms. The "latest version" URI of the separate document for the DCMI Type Vocabulary, http://dublincore.org/documents/dcmi-type-vocabulary/, will henceforth be redirected to DCMI Metadata Terms. This change is reflected in the definition for the Vocabulary Encoding Scheme DCMIType, the description of which will no longer point to the separate document for DCMI Type Vocabulary.