|
WORKING DRAFT |
This Version: <http://www.mailbase.ac.uk/lists/dc-usage/files/wd-dcq-19991222.html>
Latest Version: <http://www.mailbase.ac.uk/lists/dc-usage/files/wd-dcq-10.html>
Editors: Renato Iannella <renato@dstc.edu.au> Eric Miller <emiller@oclc.org>
Copyright 1999 Dublin Core Metadata Initiative. All Rights Reserved.
This document is a Working Draft of the Dublin Core Metadata Initiative [DCMI], and is intended to reflect consensus reached by the DC Usage Committee [DCUSAGE] of the DCMI.
This is a public version of the Working Draft. Publication as a Working Draft does not imply endorsement by the DCMI.
Comments and feedback should be sent to the Editors of this Working Draft.
.
The qualifiers described in this document are recommended for the elements of the Dublin Core Metadata Element Set [DCMES]. The DCMES recommendation forms a normative part of this document. A set of citeria for evaluating Dublin Core Qualifiers was also observed [CRITERIA].
The framework behind the qualifiers is described in the DC Reference Model 1.0 [DCRM]. The DCRM recommendation forms a normative part of this document.
Refer to V1.1 of DCMES and DC Reference Model documents as important to this document
The qualifiers are based on the following Final Working Drafts from the DCMI Element Working Groups:
This document summarises the proposed new DCMES Qualifiers. Each Qualifier is defined using a set of five attributes, which include:
There are also a set of six attributes that are common to all the Dublin Core qualifiers. These are, with their respective values:
The above attributes will not be repeated in the below definitions, however, they do represent part of the formal qualifier definitions.
The qualifiers below are recommended for the Title element.
| Name: | Alternative |
|---|---|
| Identifier: | alternative |
| Qualifier Type: | Element Qualifier |
| Definition: | The alternative title to which the resource is also known. |
| Comment: | This qualifier can include Title abbreviations as well as translations. |
The qualifiers below are recommended for the Creator, Contributor and Publisher elements (collectively called the Agent elements). The qualifiers are aimed at identifying the Agent, not for providing descriptive information about the agent. (However, the latter can still be accommodated.) The identification of Agents is not universal, and as such, different communities will require different qualifiers for this purpose. The qualifiers for the Agent elements are a proposed set of core of qualifiers to address this requirement.
| Name: | Agent Type |
|---|---|
| Identifier: | agentType |
| Qualifier Type: | Element Qualifier |
| Definition: | Indicates the type of the entity for the named Agent |
| Comment: |
The values are sourced from the DCMI maintained Dublin Core Agent Type vocabulary. Other terms may be used but are not recommended. |
| Name: | Dublin Core Agent Type Vocabulary | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Identifier: | DCAT1 | |||||||||||||||
| Qualifier Type: | Vocabulary Value Qualifier | |||||||||||||||
| Definition: | Set of terms for describing the Agent Type | |||||||||||||||
| Permissible Values: |
|
|||||||||||||||
| Comment: |
The Identifier value must be used for instances of Dublin Core Metadata. |
| Name: | Agent Name |
|---|---|
| Identifier: | agentName |
| Qualifier Type: | Element Qualifier |
| Definition: | The formal or common name of the Agent |
| Comment: | Typically, this would be the name which is used to refer to the Agent. The Family Name First Encoding Value Qualifier may also be used to express the order of the components of the Name. Vocabularies of Names may also be used as values for this qualifier. Examples:
|
| Name: | Family Name First |
|---|---|
| Identifier: | FNF |
| Qualifier Type: | Encoding Value Qualifier |
| Definition: | The encoding rule in which the family name of the Agent appears first, followed by a comma, then all other names. |
| Comment: | The FNF Encoding is primarily used for the Agent Name qualifier and when the Agent Type has the value "Person". Examples:
|
| Name: | Agent Affiliation |
|---|---|
| Identifier: | agentAff |
| Qualifier Type: | Element Qualifier |
| Definition: | The organization with which the named Agent was associated when involved with the resource |
| Comment: | The named Agent can be further identified with reference to its affiliated organization Examples:
|
| Name: | Agent Role |
|---|---|
| Identifier: | agentRole |
| Qualifier Type: | Element Qualifier |
| Definition: | Indicates the role played by the named Agent |
| Comment: | The values are defined in externally maintained and controlled Vocabulary Value Qualifiers. Such lists of terms may be used and should be clearly identified with a unique vocabulary name. Some vocabularies may contain values which would not make sense when used with one or more of the three agent elements. It is important that such usage be identified and not recommended. Values for Agent Role may also come from uncontrolled lists of terms The recommended Vocabularies for the Role qualifier include: |
| Name: | MARC Code List for Relators |
|---|---|
| Identifier: | MARCRelator |
| Qualifier Type: | Vocabulary Value Qualifier |
| Definition: | A vocabulary of roles used in the Library community |
| Comment: | The MARC Code List for Relators is defined by this formal specification [MARC]. Examples:
NOTE: In the MARC Relator vocabulary, the "Publisher" value should not be used with the Creator or Contributor elements. Also, the MARC Relator vocabulary is not recommended for use with the Publisher element. |
| Name: | Getty Art and Architecture Thesaurus |
|---|---|
| Identifier: | ATT |
| Qualifier Type: | Vocabulary Value Qualifier |
| Definition: | A vocabulary of roles used in the Cultural community |
| Comment: | The Getty Art and Architecture is defined by this formal specification [AAT]. Examples:
NOTE: Only the Agents Facet terms from the AAT thesaurus are allowed |
| Name: | Agent Identifier |
|---|---|
| Identifier: | agentId |
| Qualifier Type: | Element Qualifier |
| Definition: | An unambiguous reference to the named Agent within a given context |
| Comment: | Recommended best practice is to identify the named Agent by means of a string or number conforming to a formal identification system. The recommended Encoding Value Qualifier is the Uniform Resource Identifier. In some cases, the Agent Identifier may provide or lead to more information about the named Agent. Examples:
|
The qualifiers below are recommended for the Subject element.
| Name: | Classification |
|---|---|
| Identifier: | classification |
| Qualifier Type: | Element Qualifier |
| Definition: | Subject identified by notation (code) taken from a controlled classification scheme |
| Comment: | The name of the controlled classification scheme from which the classification is derived should always be identified as a value qualifier Existing resource discovery implementations treat classification notation (codes) differently to 'words' describing subject. Typically notation is used to create a browsing structure whereas words are not, notation is not displayed in retrieved lists whereas 'subject words' are displayed. It is important for software to precisely recognise notations as different from 'subject words'. Looking for numeric strings cannot be relied on as notations may be alphanumeric so it is useful to identify them by means of a qualifier. It is unrealistic to expect software to identify notations as such by means of the value qualifier for subject, as there is a potentially huge list of value qualifiers which cover subject headings, and thesauri as well as classification notations. Examples:
|
| Name: | Library of Congress Subject Headings |
|---|---|
| Identifier: | LCSH |
| Qualifier Type: | Vocabulary Value Qualifier |
| Definition: | |
| Comment: | Identification of the controlled vocabulary from which the subject values are taken enables manipulation of the values to enhance effectiveness of retrieval. For Subject value qualifiers, only a core list has been enumerated. These represent schemes that are of general use. Of course there are many more schemes that are being used in implementations and many more schemes that might be used in future. At some stage it would be helpful for implementations to be given the means to register schemes in use in order to share information about deployment. This is seen as a different activity to defining key qualifiers. |
| Name: | Dewey Decimal Classification |
|---|---|
| Identifier: | DDC |
| Qualifier Type: | Vocabulary Value Qualifier |
| Definition: | |
| Comment: |
|
| Name: | Universal Decimal Classification |
|---|---|
| Identifier: | UDC |
| Qualifier Type: | Vocabulary Value Qualifier |
| Definition: | |
| Comment: |
|
| Name: | Medical Subject Headings |
|---|---|
| Identifier: | MESH |
| Qualifier Type: | Vocabulary Value Qualifier |
| Definition: | |
| Comment: |
|
The qualifiers below are recommended for the Desciption element.
| Name: | Abstract |
|---|---|
| Identifier: | abstract |
| Qualifier Type: | Element Qualifier |
| Definition: | A summary of the content of the resource |
| Comment: |
|
| Name: | Note |
|---|---|
| Identifier: | note |
| Qualifier Type: | Element Qualifier |
| Definition: | Any additional information about the content of the resource |
| Comment: |
|
| Name: | Table of Contents |
|---|---|
| Identifier: | toc |
| Qualifier Type: | Element Qualifier |
| Definition: | A list of subunits of the content of the resource |
| Comment: |
|
| Name: | Release |
|---|---|
| Identifier: | release |
| Qualifier Type: | Element Qualifier |
| Definition: | An identification of the edition, release or version of the resource |
| Comment: | There is a possible overlap with Release being used as a value component of the TITLE element. The Citation and Title WG's recommended to the Subdesc WG that Release be included as a proposed qualifier for DESCRIPTION. In a spirit of co-operation we have included this. Much of the justification for this recommendation is that qualifying TITLE with Release breaks the 'dumb down' rule. The possibility of identifying Release as a value component of the TITLE value, and therefore circumventing 'dumb-down' and 'refinement' criteria was not discussed. |
The qualifiers below are recommended for the Date element.
| Name: | Created |
|---|---|
| Identifier: | created |
| Qualifier Type: | Element Qualifier |
| Definition: | Date of creation of the resource |
| Comment: | The date of creation or origin of a resource is widely recognized as a noteworthy date across many communities. This qualifier should be encoded using the W3C Date Time Format. |
| Name: | Issued |
|---|---|
| Identifier: | issued |
| Qualifier Type: | Element Qualifier |
| Definition: | Date of formal issuance (eg, publication) of the resource |
| Comment: | The precise meaning of this concept may vary by community, but formal release or publication/issuing of a resource is considered noteworthy by many communities. This qualifier should be encoded using the W3C Date Time Format. |
| Name: | Modified |
|---|---|
| Identifier: | modified |
| Qualifier Type: | Element Qualifier |
| Definition: | Date on which the resource was changed |
| Comment: | Appropriate only in cases where a metadata object references a resource that has dynamic (ie periodically modified/updated) content (eg, a Web site). Date Modified may serve as evidence of a resource's currency. This qualifier should be encoded using the W3C Date Time Format. |
| Name: | Valid |
|---|---|
| Identifier: | valid |
| Qualifier Type: | Element Qualifier |
| Definition: | Date (often a range) of validity of a resource |
| Comment: | Appropriate when the relevance and/or veracity of a resource is judged to relate to specific points in time and/or time intervals. This qualifier should be encoded using the W3C Date Time Format. |
| Name: | Available |
|---|---|
| Identifier: | available |
| Qualifier Type: | Element Qualifier |
| Definition: | Date (often a range) that the resource will become or did become available |
| Comment: | Appropriate to resources known or anticipated to be offered for access for specific points in time and/or time intervals. This qualifier should be encoded using the W3C Date Time Format. |
| Name: | W3C Date Time Format |
|---|---|
| Identifier: | W3CDTF |
| Qualifier Type: | Encoding Value Qualifier |
| Definition: | Encoding rules for dates and times - based on ISO8601 |
| Comment: | The W3C Date Time Format
is defined by this W3C NOTE [W3CDTF].
Examples:
|
The qualifiers below are recommended for the Type element.
| Name: | Dublin Core Type Vocabulary | ||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Identifier: | DCT1 | ||||||||||||||||||||||||||||||||||||||||||
| Qualifier Type: | Vocabulary Value Qualifier | ||||||||||||||||||||||||||||||||||||||||||
| Definition: | A controlled vocabulary indicating the nature or genre of the resource> | ||||||||||||||||||||||||||||||||||||||||||
| Permissible Values: |
|
||||||||||||||||||||||||||||||||||||||||||
| Comment: |
The Identifier value must be used for instances of Dublin Core Metadata. In the absense of an application-specific list, DCT1 is provided as a general list . In cases where a specific list is used, best practice is to use a value from DCT1 in addition to any from the specific list. Many implementors tend to use their own lists of values for types, developed for their particular applications. The Vocabulary Value Qualifier is used to specify the specific list. Type may be repeated as necessary to include different categories. Examples are multimedia resources, which should include each appropriate category, and collections, which should include "collection" and any other appropriate type(s) (eg "text", "image", etc.). Examples:
|
The qualifiers below are recommended for the Format element.
| Name: | Medium |
|---|---|
| Identifier: | meduim |
| Qualifier Type: | Element Qualifier |
| Definition: | The media-type of the resource |
| Comment: | This element qualifier for Format allows the metadata creator to indicate the media-type of the resource. Recommended best practice is to select a value from a controlled vocabulary (for example, the list of Internet Media Types [MIME] defining computer media formats). Examples:
Recommended best practice for digital resources is to use this element qualifier for Format in conjunction with the IMT value qualifier. |
| Name: | Extent |
|---|---|
| Identifier: | extent |
| Qualifier Type: | Element Qualifier |
| Definition: | The size or duration of the resource |
| Comment: | This element qualifier for Format allows the metadata creator to indicate the physical dimensions, filesize or duration of the resource.
Examples:
No specific recommendations about how units should be associated with the value are made. |
| Name: | Internet Media Types |
|---|---|
| Identifier: | IMT |
| Qualifier Type: | Vocabulary Value Qualifier |
| Definition: | The Internet MIME Type of the resource |
| Comment: | This value qualifier for Format allows the metadata creator to indicate the Internet MIME Type of the resource. This is the standard mechanism for indicating the media-type of a digital resource on the Internet. Examples:
Recommended best practice for digital resources is to use the IMT value qualifier in conjunction with the Medium element qualifier for Format. |
The qualifiers below are recommended for the Identifier element.
| Name: | Uniform Resource Identifier |
|---|---|
| Identifier: | URI |
| Qualifier Type: | Encoding Value Qualifier |
| Definition: | A simple and extensible compact string of restricted characters used for identifying a resource. |
| Comment: | The Uniform Resource Identifier is defined by this formal Internet Engineering Task Force specification [URI. Examples:
Absolute URIs are recommended over Relative URIs. |
The qualifiers below are recommended for the Source element.
The qualifiers below are recommended for the Language element.
| Name: | RFC 1766 - Tags for the identification of language |
|---|---|
| Identifier: | RFC1766 |
| Qualifier Type: | Vocabuary Value Qualifier |
| Definition: | Internet RFC 1766 specifies a two letter language code taken from ISO 639, followed optionally by a two letter country code taken from ISO 3166. |
| Comment: | Internet RFC 1766 is defined by this formal specification [RFC1766] consisting of a two letter language code [ISO639]followed optionally by a two letter country code [ISO3166]. |
The qualifiers below are recommended for the Relation element.
The qualifiers below are recommended for the Coverage element.
The qualifiers below are recommended for the Rights element.
[AAT] Gettys Art and Architecture Thesaurus
<http://shiva.pub.getty.edu/aat_browser/titles.html>
[DCRM] Dublin
Core Reference Model 1.0
<http://www.mailbase.ac.uk/lists/dc-datamodel/files/wd-dcrm.htm>
[CRITERIA] Dublin
Core Criteria for Evaluating Qualifiers
<http://www.mailbase.ac.uk/lists/dc-general/1999-11/0029.html>
[DCMES] Dublin
Core Metadata Element Set: Reference Description
<http://purl.org/dc/about/element_set.htm>
[DCMI] Dublin Core
Metadata Initiative Home Page
<http://purl.org/dc/>
[IMT] Internet Media Types (MIME)
<http://www.isi.edu/in-notes/iana/assignments/media-types/media-types>
[ISO639] Codes for the representation of names of languages
<ftp://dkuug.dk/iUse of uninitialized value in concatenation (.) or string at E:\listplex\SYSTEM\SCRIPTS\filearea.cgi line 455,
[ISO3166] Codes for the representation of names of countries
<ftp://dkuug.dk/i18n/ISO_3166>
[MARC] MARC Code List for Relators
<http://www.loc.gov/marc/relators/re9802r1.html>
[RFC1766] Tags for the Identification of Languages
<http://www.ietf.org/rfc/rfc1766.txt>
[URI] Uniform Resource Identifiers (URI): Generic Syntax, Internet RFC 2396
<http://www.ietf.org/rfc/rfc2396.txt>
[W3CDTF] Date and Time Formats, W3C Note.
<http://www.w3.org/TR/NOTE-datetime>
The Editors wish to thank the Cahirs and all members of the Element Working Groups and the DC Usage Committee who helped to develop the ideas expressed here and the editors apologise if any of their inputs have been misrepresented in this document.