2012-01-05. Frozen archive - links may not resolve - see directory of files at MoinMoin wiki archive

> DCTermsChanges

Editorial changes to terms in the DCTERMS namespace

2007-03-13

In Barcelona, we have the opportunity to finalize a batch of changes to terms in the DCTERMS namespace. Attached is a draft decision text showing "before" and "after" versions of term declarations, along with an introductory section describing categories of change.


1. About this decision text

In 2006, the DCMI Usage Board undertook an editorial revision of terms in the Dublin Core Metadata Element Set (DCMES) in order to clarify intended semantics and bring the wording of their definitions and usage comments into line with the language of the DCMI Abstract Model [DCAM]. After a Public Comment period, these changes were finalized as a Usage Board decision [DCMES-CHANGES].

The changes reflected in this document follow the change categories used to revise terms of the Dublin Core Metadata Element Set and apply them to terms of DCTERMS namespace. In addition to these "systematic" changes, other editorial corrections or updates have been undertaken, as noted below.

The wordings recorded here are reflected in revised versions of the documents "DCMI Metadata Terms" [DCTERMS], and "DCMI Metadata Terms: A complete historical record" [DCTERMS-HISTORY].

All of the changes recorded here were evaluated by the DCMI Usage Board in light of the DCMI Namespace Policy [NAMESPACE]. The namespace policy says that DCMI terms are identified using Uniform Resource Identifiers (URIs). In accordance with the principle that distinct URIs should be assigned to distinct resources, the policy sets limits on the range of editorial changes that may allowably be made to the official labels, definitions, and usage comments associated with DCMI terms. By policy, any changes of meaning judged "likely to have a substantial impact on either machine processing of DCMI terms or the functional semantics of the terms" must trigger the creation of a new, distinct term with a new, distinct URI.

In the opinion of the Usage Board, the changes described in this document are unlikely to have a substantial impact on either machine processing of DCMI terms or the functional semantics of the terms -- i.e., they fall within the allowable range of editorial change. The changes constitute clarifications of term semantics in light of improved theoretical understanding, user feedback, and implementation experience. They provide the final twist of the lens that brings intended meanings more sharply into focus.

General categories of change

Free-standing descriptive labels

[Two or three sentences may be needed here on why "qualifiers" were named as adjectives in the first place?]

This change is relevant to the definitions of:

Replacement of "content of the resource" with just "the resource"

This change is relevant to the definitions of:

Replacement of "reference to a resource" with just "a resource"

This change is relevant to the definitions of:

"Use a controlled vocabulary"

Replacement of phrases such as "use a value from an encoding scheme" and "select a value from a controlled vocabulary" with "use a controlled vocabulary". NOTE: REMOVED THESE!!

"Qualifies" statements

In the DCMI Abstract Model, the only connection between a property (e.g., dcterms:subject) and a Vocabulary Encoding Scheme is

Thus, if it's a collection of Dates, they fit as values of dc:date, etc, all according to the range of the relevant property.

The set of terms itself does not say anything about their usefulness for a given property. Naturally, the documentation of a VES might say that the terms are all useful as values of dc:subject etc, but we have no formal way of saying that (and should not have I think).

Subproperty relations between terms in the /1.1/ namespace

Is this the time to add those relations to the copied terms in the /terms/ namespace?

Changes term-by-term

http://purl.org/dc/terms/creator

http://purl.org/dc/terms/source

http://purl.org/dc/terms/audience

After:

Changes:

http://purl.org/dc/terms/alternative

After:

Changes:

http://purl.org/dc/terms/tableOfContents

After:

Changes:

http://purl.org/dc/terms/abstract

After:

Changes:

http://purl.org/dc/terms/created

After:

Changes:

http://purl.org/dc/terms/valid

After:

Changes:

http://purl.org/dc/terms/available

After:

Changes:

http://purl.org/dc/terms/issued

After:

Changes:

http://purl.org/dc/terms/modified

After:

Changes:

http://purl.org/dc/terms/extent

After:

Changes:

http://purl.org/dc/terms/medium

After:

Changes:

http://purl.org/dc/terms/isVersionOf

After:

Changes:

http://purl.org/dc/terms/hasVersion

After:

Changes:

http://purl.org/dc/terms/isReplacedBy

After:

Changes:

http://purl.org/dc/terms/replaces

After:

Changes:

http://purl.org/dc/terms/isRequiredBy

After:

Changes:

http://purl.org/dc/terms/requires

After:

Changes:

http://purl.org/dc/terms/isPartOf

After:

Changes:

http://purl.org/dc/terms/hasPart

After:

Changes:

http://purl.org/dc/terms/isReferencedBy

After:

Changes:

http://purl.org/dc/terms/references

After:

Changes:

http://purl.org/dc/terms/isFormatOf

After:

Changes:

http://purl.org/dc/terms/hasFormat

After:

Changes:

http://purl.org/dc/terms/conformsTo

After:

Changes:

http://purl.org/dc/terms/spatial

After:

Changes:

http://purl.org/dc/terms/temporal

After:

Changes:

http://purl.org/dc/terms/mediator

After:

Changes:

http://purl.org/dc/terms/dateAccepted

After:

Changes:

http://purl.org/dc/terms/dateCopyrighted

After:

Changes:

http://purl.org/dc/terms/dateSubmitted

After:

Changes:

http://purl.org/dc/terms/educationLevel

After:

Changes:

http://purl.org/dc/terms/accessRights

After:

Changes:

http://purl.org/dc/terms/bibliographicCitation

After:

Changes:

http://purl.org/dc/terms/license

After:

Changes:

http://purl.org/dc/terms/rightsHolder

After:

Changes:

http://purl.org/dc/terms/provenance

After:

Changes:

http://purl.org/dc/terms/instructionalMethod

After:

Changes:

http://purl.org/dc/terms/accrualMethod

After:

Changes:

http://purl.org/dc/terms/accrualPeriodicity

After:

Changes:

http://purl.org/dc/terms/accrualPolicy

After:

Changes:

http://purl.org/dc/terms/LCSH

After:

Changes:

http://purl.org/dc/terms/MESH

After:

Changes:

http://purl.org/dc/terms/DDC

After:

Changes:

http://purl.org/dc/terms/LCC

After:

Changes:

http://purl.org/dc/terms/UDC

After:

Changes:

http://purl.org/dc/terms/DCMIType

After:

Changes:

http://purl.org/dc/terms/IMT

After:

Changes:

http://purl.org/dc/terms/ISO639-2

After:

Changes:

http://purl.org/dc/terms/RFC1766

After:

Changes:

http://purl.org/dc/terms/URI

After:

Changes:

http://purl.org/dc/terms/Point

After:

Changes:

http://purl.org/dc/terms/ISO3166

After:

Changes:

http://purl.org/dc/terms/Box

After:

Changes:

http://purl.org/dc/terms/TGN

After:

Changes:

http://purl.org/dc/terms/Period

After:

Changes:

http://purl.org/dc/terms/W3CDTF

After:

Changes:

http://purl.org/dc/terms/RFC3066

After:

Changes:

http://purl.org/dc/terms/NLM

After:

Changes:

http://purl.org/dc/terms/RFC4646

After:

Changes:

REFERENCES