Meta Tags - Dublin Core

DCMI Metadata Terms

Title:	DCMI Metadata Terms
Creator:	DCMI Usage Board
Identifier:	http://dublincore.org/documents/2005/06/13/dcmi-terms/
Date Issued:	2005-06-13
Latest Version:	http://dublincore.org/documents/dcmi-terms/
Replaces:	http://dublincore.org/documents/2005/01/10/dcmi-terms/
Translations:	http://dublincore.org/resources/translations/
Document Status:	This is a DCMI Recommendation.
Description:	This document is an up-to-date specification of all metadata terms maintained by the Dublin Core Metadata Initiative, including elements, element refinements, encoding schemes, and vocabulary terms (the DCMI Type Vocabulary).
Date Valid:	2005-06-13

Section 1: Introduction and Definitions

This document is an up-to-date, authoritative specification of all metadata terms maintained by the Dublin Core Metadata Initiative -- elements, element refinements, encoding schemes, and vocabulary terms (the DCMI Type Vocabulary). Links to other relevant documentation may be found on the "Overview of Documentation for DCMI Metadata Terms" [OVERVIEW].

Legacy documents covering subsets of this document are in the public domain, including the IETF RFC 2413 [RFC2413], the CEN Workshop Agreement CWA 13874 [CWA13874], NISO Standard Z39.85-2001 [Z3985], and a variety of national standards that include some or all of the Dublin Core Metadata Set.

Each term is specified with the following minimal set of attributes:

Name:	The unique token assigned to the term.
URI:	The Uniform Resource Identifier used to uniquely identify a term.
Label:	The human-readable label assigned to the term.
Definition:	A statement that represents the concept and essential nature of the term.
Type of Term:	The type of term, such as Element or Encoding Scheme, as described in the DCMI Grammatical Principles.
Status:	Status assigned to term by the DCMI Usage Board, as described in the DCMI Usage Board Process.
Date issued:	Date on which a term was first declared.

Where applicable, the following attributes provide additional information about a term:

Comment:	Additional information about the term or its application.
See:	A link to authoritative documentation.
References:	A citation or URL of a resource referenced in the Definition or Comment.
Refines:	A reference to a term refined by an Element Refinement.
Qualifies:	A reference to a term qualified by an Encoding Scheme.
Broader Than:	A reference from a more general to a more specific Vocabulary Term.
Narrower Than:	A reference from a more specific to a more general Vocabulary Term.

Anchors have been embedded in this document so that users may cite a particular entry with the form "http://dublincore.org/documents/dcmi-terms/#term-name" (e.g., "http://dublincore.org/documents/dcmi-terms/#title"). While this form of citation is supported for documentary convenience, note that the URI assigned to each term in accordance with the DCMI Namespace Policy serves as its unique identifier (e.g., "http://purl.org/dc/elements/1.1/title") [NAMESPACE].

Readers desiring further information about the change history or Usage Board decisions that support these terms should consult the document "DCMI Metadata Terms -- A Complete Historical Record" [HISTORY].

This documentation is maintained by the DCMI Usage Board. Although DCMI is committed to ensuring a high degree of stability of the specifications it maintains, changes may occur as a result of the work of the Usage Board. The policies and processes governing the identification and maintenance of metadata terms are described in "DCMI Namespace Policy" [NAMESPACE], "DCMI Grammatical Principles" [PRINCIPLES], and "DCMI Usage Board Administrative Processes" [PROCESS]. Usage Board decisions with respect to DCMI metadata terms are summarized on the Web page "DCMI Usage Board Decisions" [DECISIONS]. Three attributes of terms -- Label, Definition, and Comment -- have natural-language values which may be translated into Japanese, Norwegian, or other languages. Although there is currently no mechanism in place to validate or certify such translations in an official sense, DCMI maintains a Web page with pointers to known translations of semantic specifications and related DCMI documents [TRANSLATIONS]

References

[RFC2413]	http://www.ietf.org/rfc/rfc2413.txt
[Z3985]	http://www.niso.org/standards/resources/Z39-85.pdf
[CWA13874]	CEN Workshop Agreement CWA 13874. March 2000 (no longer available).
[NAMESPACE]	http://dublincore.org/documents/dcmi-namespace/
[HISTORY]	http://dublincore.org/usage/terms/history/
[OVERVIEW]	http://dublincore.org/usage/documents/overview/
[PRINCIPLES]	http://dublincore.org/usage/documents/principles/
[PROCESS]	http://dublincore.org/usage/documents/process/
[DECISIONS]	http://dublincore.org/usage/decisions/
[TRANSLATIONS]	http://dublincore.org/resources/translations/

Section 2: The Dublin Core Metadata Element Set

Section 3: Other Elements and Element Refinements

Term Name: alternative
URI:	http://purl.org/dc/terms/alternative
Label:	Alternative
Definition:	Any form of the title used as a substitute or alternative to the formal title of the resource.
Comment:	This qualifier can include Title abbreviations as well as translations.
Type of Term:	element-refinement
Refines:	http://purl.org/dc/elements/1.1/title
Status:	recommended
Date Issued:	2000-07-11
Term Name: available
URI:	http://purl.org/dc/terms/available
Label:	Available
Definition:	Date (often a range) that the resource will become or did become available.
Type of Term:	element-refinement
Refines:	http://purl.org/dc/elements/1.1/date
Status:	recommended
Date Issued:	2000-07-11
Term Name: bibliographicCitation
URI:	http://purl.org/dc/terms/bibliographicCitation
Label:	Bibliographic Citation
Definition:	A bibliographic reference for the resource.
Comment:	Recommended practice is to include sufficient bibliographic detail to identify the resource as unambiguously as possible, whether or not the citation is in a standard form.
Type of Term:	element-refinement
Refines:	http://purl.org/dc/elements/1.1/identifier
Status:	conforming
Date Issued:	2003-02-15
Term Name: conformsTo
URI:	http://purl.org/dc/terms/conformsTo
Label:	Conforms To
Definition:	A reference to an established standard to which the resource conforms.
Type of Term:	element-refinement
Refines:	http://purl.org/dc/elements/1.1/relation
Status:	recommended
Date Issued:	2001-05-21
Term Name: created
URI:	http://purl.org/dc/terms/created
Label:	Created
Definition:	Date of creation of the resource.
Type of Term:	element-refinement
Refines:	http://purl.org/dc/elements/1.1/date
Status:	recommended
Date Issued:	2000-07-11
Term Name: dateAccepted
URI:	http://purl.org/dc/terms/dateAccepted
Label:	Date Accepted
Definition:	Date of acceptance of the resource (e.g. of thesis by university department, of article by journal, etc.).
Type of Term:	element-refinement
Refines:	http://purl.org/dc/elements/1.1/date
Status:	conforming
Date Issued:	2002-07-13
Term Name: dateCopyrighted
URI:	http://purl.org/dc/terms/dateCopyrighted
Label:	Date Copyrighted
Definition:	Date of a statement of copyright.
Type of Term:	element-refinement
Refines:	http://purl.org/dc/elements/1.1/date
Status:	conforming
Date Issued:	2002-07-13
Term Name: dateSubmitted
URI:	http://purl.org/dc/terms/dateSubmitted
Label:	Date Submitted
Definition:	Date of submission of the resource (e.g. thesis, articles, etc.).
Type of Term:	element-refinement
Refines:	http://purl.org/dc/elements/1.1/date
Status:	conforming
Date Issued:	2002-07-13
Term Name: educationLevel
URI:	http://purl.org/dc/terms/educationLevel
Label:	Audience Education Level
Definition:	A general statement describing the education or training context. Alternatively, a more specific statement of the location of the audience in terms of its progression through an education or training context.
Type of Term:	element-refinement
Refines:	http://purl.org/dc/terms/audience
Status:	conforming
Date Issued:	2002-07-13
Term Name: extent
URI:	http://purl.org/dc/terms/extent
Label:	Extent
Definition:	The size or duration of the resource.
Type of Term:	element-refinement
Refines:	http://purl.org/dc/elements/1.1/format
Status:	recommended
Date Issued:	2000-07-11
Term Name: hasFormat
URI:	http://purl.org/dc/terms/hasFormat
Label:	Has Format
Definition:	The described resource pre-existed the referenced resource, which is essentially the same intellectual content presented in another format.
Type of Term:	element-refinement
Refines:	http://purl.org/dc/elements/1.1/relation
Status:	recommended
Date Issued:	2000-07-11
Term Name: hasPart
URI:	http://purl.org/dc/terms/hasPart
Label:	Has Part
Definition:	The described resource includes the referenced resource either physically or logically.
Type of Term:	element-refinement
Refines:	http://purl.org/dc/elements/1.1/relation
Status:	recommended
Date Issued:	2000-07-11
Term Name: hasVersion
URI:	http://purl.org/dc/terms/hasVersion
Label:	Has Version
Definition:	The described resource has a version, edition, or adaptation, namely, the referenced resource.
Type of Term:	element-refinement
Refines:	http://purl.org/dc/elements/1.1/relation
Status:	recommended
Date Issued:	2000-07-11
Term Name: instructionalMethod
URI:	http://purl.org/dc/terms/instructionalMethod
Label:	Instructional Method
Definition:	A process, used to engender knowledge, attitudes and skills, that the resource is designed to support.
Comment:	Instructional Method will typically include ways of presenting instructional materials or conducting instructional activities, patterns of learner-to-learner and learner-to-instructor interactions, and mechanisms by which group and individual levels of learning are measured. Instructional methods include all aspects of the instruction and learning processes from planning and implementation through evaluation and feedback.
Type of Term:	element
Status:	conforming
Date Issued:	2005-06-13
Term Name: isFormatOf
URI:	http://purl.org/dc/terms/isFormatOf
Label:	Is Format Of
Definition:	The described resource is the same intellectual content of the referenced resource, but presented in another format.
Type of Term:	element-refinement
Refines:	http://purl.org/dc/elements/1.1/relation
Status:	recommended
Date Issued:	2000-07-11
Term Name: isPartOf
URI:	http://purl.org/dc/terms/isPartOf
Label:	Is Part Of
Definition:	The described resource is a physical or logical part of the referenced resource.
Type of Term:	element-refinement
Refines:	http://purl.org/dc/elements/1.1/relation
Status:	recommended
Date Issued:	2000-07-11
Term Name: isReferencedBy
URI:	http://purl.org/dc/terms/isReferencedBy
Label:	Is Referenced By
Definition:	The described resource is referenced, cited, or otherwise pointed to by the referenced resource.
Type of Term:	element-refinement
Refines:	http://purl.org/dc/elements/1.1/relation
Status:	recommended
Date Issued:	2000-07-11
Term Name: isReplacedBy
URI:	http://purl.org/dc/terms/isReplacedBy
Label:	Is Replaced By
Definition:	The described resource is supplanted, displaced, or superseded by the referenced resource.
Type of Term:	element-refinement
Refines:	http://purl.org/dc/elements/1.1/relation
Status:	recommended
Date Issued:	2000-07-11
Term Name: isRequiredBy
URI:	http://purl.org/dc/terms/isRequiredBy
Label:	Is Required By
Definition:	The described resource is required by the referenced resource, either physically or logically.
Type of Term:	element-refinement
Refines:	http://purl.org/dc/elements/1.1/relation
Status:	recommended
Date Issued:	2000-07-11
Term Name: issued
URI:	http://purl.org/dc/terms/issued
Label:	Issued
Definition:	Date of formal issuance (e.g., publication) of the resource.
Type of Term:	element-refinement
Refines:	http://purl.org/dc/elements/1.1/date
Status:	recommended
Date Issued:	2000-07-11
Term Name: isVersionOf
URI:	http://purl.org/dc/terms/isVersionOf
Label:	Is Version Of
Definition:	The described resource is a version, edition, or adaptation of the referenced resource. Changes in version imply substantive changes in content rather than differences in format.
Type of Term:	element-refinement
Refines:	http://purl.org/dc/elements/1.1/relation
Status:	recommended
Date Issued:	2000-07-11
Term Name: license
URI:	http://purl.org/dc/terms/license
Label:	License
Definition:	A legal document giving official permission to do something with the resource.
Comment:	Recommended best practice is to identify the license using a URI. Examples of such licenses can be found at http://creativecommons.org/licenses/.
Type of Term:	element-refinement
Refines:	http://purl.org/dc/elements/1.1/rights
Status:	conforming
Date Issued:	2004-06-14
Term Name: mediator
URI:	http://purl.org/dc/terms/mediator
Label:	Mediator
Definition:	A class of entity that mediates access to the resource and for whom the resource is intended or useful.
Comment:	The audiences for a resource are of two basic classes: (1) an ultimate beneficiary of the resource, and (2) frequently, an entity that mediates access to the resource. The mediator element refinement represents the second of these two classes.
Type of Term:	element-refinement
Refines:	http://purl.org/dc/terms/audience
Status:	recommended
Date Issued:	2001-05-21
Term Name: medium
URI:	http://purl.org/dc/terms/medium
Label:	Medium
Definition:	The material or physical carrier of the resource.
Type of Term:	element-refinement
Refines:	http://purl.org/dc/elements/1.1/format
Status:	recommended
Date Issued:	2000-07-11
Term Name: modified
URI:	http://purl.org/dc/terms/modified
Label:	Modified
Definition:	Date on which the resource was changed.
Type of Term:	element-refinement
Refines:	http://purl.org/dc/elements/1.1/date
Status:	recommended
Date Issued:	2000-07-11
Term Name: provenance
URI:	http://purl.org/dc/terms/provenance
Label:	Provenance
Definition:	A statement of any changes in ownership and custody of the resource since its creation that are significant for its authenticity, integrity and interpretation.
Comment:	The statement may include a description of any changes successive custodians made to the resource.
Type of Term:	element
Status:	conforming
Date Issued:	2004-09-20
Term Name: references
URI:	http://purl.org/dc/terms/references
Label:	References
Definition:	The described resource references, cites, or otherwise points to the referenced resource.
Type of Term:	element-refinement
Refines:	http://purl.org/dc/elements/1.1/relation
Status:	recommended
Date Issued:	2000-07-11
Term Name: replaces
URI:	http://purl.org/dc/terms/replaces
Label:	Replaces
Definition:	The described resource supplants, displaces, or supersedes the referenced resource.
Type of Term:	element-refinement
Refines:	http://purl.org/dc/elements/1.1/relation
Status:	recommended
Date Issued:	2000-07-11
Term Name: requires
URI:	http://purl.org/dc/terms/requires
Label:	Requires
Definition:	The described resource requires the referenced resource to support its function, delivery, or coherence of content.
Type of Term:	element-refinement
Refines:	http://purl.org/dc/elements/1.1/relation
Status:	recommended
Date Issued:	2000-07-11
Term Name: rightsHolder
URI:	http://purl.org/dc/terms/rightsHolder
Label:	Rights Holder
Definition:	A person or organization owning or managing rights over the resource.
Comment:	Recommended best practice is to use the URI or name of the Rights Holder to indicate the entity.
Type of Term:	element
Status:	conforming
Date Issued:	2004-06-14
Term Name: spatial
URI:	http://purl.org/dc/terms/spatial
Label:	Spatial
Definition:	Spatial characteristics of the intellectual content of the resource.
Type of Term:	element-refinement
Refines:	http://purl.org/dc/elements/1.1/coverage
Status:	recommended
Date Issued:	2000-07-11
Term Name: tableOfContents
URI:	http://purl.org/dc/terms/tableOfContents
Label:	Table Of Contents
Definition:	A list of subunits of the content of the resource.
Type of Term:	element-refinement
Refines:	http://purl.org/dc/elements/1.1/description
Status:	recommended
Date Issued:	2000-07-11
Term Name: temporal
URI:	http://purl.org/dc/terms/temporal
Label:	Temporal
Definition:	Temporal characteristics of the intellectual content of the resource.
Type of Term:	element-refinement
Refines:	http://purl.org/dc/elements/1.1/coverage
Status:	recommended
Date Issued:	2000-07-11
Term Name: valid
URI:	http://purl.org/dc/terms/valid
Label:	Valid
Definition:	Date (often a range) of validity of a resource.
Type of Term:	element-refinement
Refines:	http://purl.org/dc/elements/1.1/date
Status:	recommended
Date Issued:	2000-07-11

Section 4: Encoding Schemes

Term Name: Box
URI:	http://purl.org/dc/terms/Box
Label:	DCMI Box
Definition:	The DCMI Box identifies a region of space using its geographic limits.
See:	http://dublincore.org/documents/dcmi-box/
Type of Term:	encoding-scheme
Qualifies:	http://purl.org/dc/terms/spatial
Status:	registered
Date Issued:	2000-07-11
Term Name: DCMIType
URI:	http://purl.org/dc/terms/DCMIType
Label:	DCMI Type Vocabulary
Definition:	A list of types used to categorize the nature or genre of the content of the resource.
See:	http://dublincore.org/documents/dcmi-type-vocabulary/
Type of Term:	encoding-scheme
Qualifies:	http://purl.org/dc/elements/1.1/type
Status:	registered
Date Issued:	2000-07-11
Term Name: DDC
URI:	http://purl.org/dc/terms/DDC
Label:	DDC
Definition:	Dewey Decimal Classification
See:	http://www.oclc.org/dewey/index.htm
Type of Term:	encoding-scheme
Qualifies:	http://purl.org/dc/elements/1.1/subject
Status:	registered
Date Issued:	2000-07-11
Term Name: IMT
URI:	http://purl.org/dc/terms/IMT
Label:	IMT
Definition:	The Internet media type of the resource.
See:	http://www.iana.org/assignments/media-types/
Type of Term:	encoding-scheme
Qualifies:	http://purl.org/dc/elements/1.1/format
Status:	registered
Date Issued:	2000-07-11
Term Name: ISO3166
URI:	http://purl.org/dc/terms/ISO3166
Label:	ISO 3166
Definition:	ISO 3166 Codes for the representation of names of countries
See:	http://www.iso.org/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/list-en1.html
Type of Term:	encoding-scheme
Qualifies:	http://purl.org/dc/terms/spatial
Status:	registered
Date Issued:	2000-07-11
Term Name: ISO639-2
URI:	http://purl.org/dc/terms/ISO639-2
Label:	ISO 639-2
Definition:	ISO 639-2: Codes for the representation of names of languages.
See:	http://lcweb.loc.gov/standards/iso639-2/langhome.html
Type of Term:	encoding-scheme
Qualifies:	http://purl.org/dc/elements/1.1/language
Status:	registered
Date Issued:	2000-07-11
Term Name: LCC
URI:	http://purl.org/dc/terms/LCC
Label:	LCC
Definition:	Library of Congress Classification
See:	http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html
Type of Term:	encoding-scheme
Qualifies:	http://purl.org/dc/elements/1.1/subject
Status:	registered
Date Issued:	2000-07-11
Term Name: LCSH
URI:	http://purl.org/dc/terms/LCSH
Label:	LCSH
Definition:	Library of Congress Subject Headings
Type of Term:	encoding-scheme
Qualifies:	http://purl.org/dc/elements/1.1/subject
Status:	registered
Date Issued:	2000-07-11
Term Name: MESH
URI:	http://purl.org/dc/terms/MESH
Label:	MeSH
Definition:	Medical Subject Headings
See:	http://www.nlm.nih.gov/mesh/meshhome.html
Type of Term:	encoding-scheme
Qualifies:	http://purl.org/dc/elements/1.1/subject
Status:	registered
Date Issued:	2000-07-11
Term Name: NLM
URI:	http://purl.org/dc/terms/NLM
Label:	NLM
Definition:	National Library of Medicine Classification
See:	http://wwwcf.nlm.nih.gov/class/
Type of Term:	encoding-scheme
Qualifies:	http://purl.org/dc/elements/1.1/subject
Status:	registered
Date Issued:	2005-06-13
Term Name: Period
URI:	http://purl.org/dc/terms/Period
Label:	DCMI Period
Definition:	A specification of the limits of a time interval.
See:	http://dublincore.org/documents/dcmi-period/
Type of Term:	encoding-scheme
Qualifies:	http://purl.org/dc/elements/1.1/date
Qualifies:	http://purl.org/dc/terms/temporal
Status:	registered
Date Issued:	2000-07-11
Term Name: Point
URI:	http://purl.org/dc/terms/Point
Label:	DCMI Point
Definition:	The DCMI Point identifies a point in space using its geographic coordinates.
See:	http://dublincore.org/documents/dcmi-point/
Type of Term:	encoding-scheme
Qualifies:	http://purl.org/dc/terms/spatial
Status:	registered
Date Issued:	2000-07-11
Term Name: RFC1766
URI:	http://purl.org/dc/terms/RFC1766
Label:	RFC 1766
Definition:	Internet RFC 1766 'Tags for the identification of Language' specifies a two letter code taken from ISO 639, followed optionally by a two letter country code taken from ISO 3166.
See:	http://www.ietf.org/rfc/rfc1766.txt
Type of Term:	encoding-scheme
Qualifies:	http://purl.org/dc/elements/1.1/language
Status:	registered
Date Issued:	2000-07-11
Term Name: RFC3066
URI:	http://purl.org/dc/terms/RFC3066
Label:	RFC 3066
Definition:	Internet RFC 3066 'Tags for the Identification of Languages' specifies a primary subtag which is a two-letter code taken from ISO 639 part 1 or a three-letter code taken from ISO 639 part 2, followed optionally by a two-letter country code taken from ISO 3166. When a language in ISO 639 has both a two-letter and three-letter code, use the two-letter code; when it has only a three-letter code, use the three-letter code. This RFC replaces RFC 1766.
See:	http://www.ietf.org/rfc/rfc3066.txt
Type of Term:	encoding-scheme
Qualifies:	http://purl.org/dc/elements/1.1/language
Status:	registered
Date Issued:	2002-07-13
Term Name: TGN
URI:	http://purl.org/dc/terms/TGN
Label:	TGN
Definition:	The Getty Thesaurus of Geographic Names
See:	http://www.getty.edu/research/tools/vocabulary/tgn/index.html
Type of Term:	encoding-scheme
Qualifies:	http://purl.org/dc/terms/spatial
Status:	registered
Date Issued:	2000-07-11
Term Name: UDC
URI:	http://purl.org/dc/terms/UDC
Label:	UDC
Definition:	Universal Decimal Classification
See:	http://www.udcc.org/
Type of Term:	encoding-scheme
Qualifies:	http://purl.org/dc/elements/1.1/subject
Status:	registered
Date Issued:	2000-07-11
Term Name: URI
URI:	http://purl.org/dc/terms/URI
Label:	URI
Definition:	A URI Uniform Resource Identifier
See:	http://www.ietf.org/rfc/rfc2396.txt
Type of Term:	encoding-scheme
Qualifies:	http://purl.org/dc/elements/1.1/identifier
Qualifies:	http://purl.org/dc/elements/1.1/source
Qualifies:	http://purl.org/dc/elements/1.1/relation
Status:	registered
Date Issued:	2000-07-11
Term Name: W3CDTF
URI:	http://purl.org/dc/terms/W3CDTF
Label:	W3C-DTF
Definition:	W3C Encoding rules for dates and times - a profile based on ISO 8601
See:	http://www.w3.org/TR/NOTE-datetime
Type of Term:	encoding-scheme
Qualifies:	http://purl.org/dc/elements/1.1/date
Qualifies:	http://purl.org/dc/terms/temporal
Status:	registered
Date Issued:	2000-07-11

Section 5: The DCMI Type Vocabulary

Term Name: Collection
URI:	http://purl.org/dc/dcmitype/Collection
Label:	Collection
Definition:	A collection is an aggregation of items. The term collection means that the resource is described as a group; its parts may be separately described and navigated.
Type of Term:	vocabulary-term
Status:	recommended
Date Issued:	2000-07-11
Term Name: Dataset
URI:	http://purl.org/dc/dcmitype/Dataset
Label:	Dataset
Definition:	A dataset is information encoded in a defined structure (for example, lists, tables, and databases), intended to be useful for direct machine processing.
Type of Term:	vocabulary-term
Status:	recommended
Date Issued:	2000-07-11
Term Name: Event
URI:	http://purl.org/dc/dcmitype/Event
Label:	Event
Definition:	An event is a non-persistent, time-based occurrence. Metadata for an event provides descriptive information that is the basis for discovery of the purpose, location, duration, responsible agents, and links to related events and resources. The resource of type event may not be retrievable if the described instantiation has expired or is yet to occur. Examples - exhibition, web-cast, conference, workshop, open-day, performance, battle, trial, wedding, tea-party, conflagration.
Type of Term:	vocabulary-term
Status:	recommended
Date Issued:	2000-07-11
Term Name: Image
URI:	http://purl.org/dc/dcmitype/Image
Label:	Image
Definition:	An image is a primarily symbolic visual representation other than text. For example - images and photographs of physical objects, paintings, prints, drawings, other images and graphics, animations and moving pictures, film, diagrams, maps, musical notation. Note that image may include both electronic and physical representations.
Type of Term:	vocabulary-term
Broader Than:	http://purl.org/dc/dcmitype/StillImage
Broader Than:	http://purl.org/dc/dcmitype/MovingImage
Status:	recommended
Date Issued:	2000-07-11
Term Name: InteractiveResource
URI:	http://purl.org/dc/dcmitype/InteractiveResource
Label:	Interactive Resource
Definition:	An interactive resource is a resource which requires interaction from the user to be understood, executed, or experienced. For example - forms on web pages, applets, multimedia learning objects, chat services, virtual reality.
Type of Term:	vocabulary-term
Status:	recommended
Date Issued:	2000-07-11
Term Name: MovingImage
URI:	http://purl.org/dc/dcmitype/MovingImage
Label:	Moving Image
Definition:	A series of visual representations that, when shown in succession, impart an impression of motion. Examples of moving images are: animations, movies, television programs, videos, zoetropes, or visual output from a simulation.
Comment:	Instances of the type "Moving Image" must also be describable as instances of the broader type "Image".
Type of Term:	vocabulary-term
Narrower Than:	http://purl.org/dc/dcmitype/Image
Status:	recommended
Date Issued:	2003-11-18
Term Name: PhysicalObject
URI:	http://purl.org/dc/dcmitype/PhysicalObject
Label:	Physical Object
Definition:	An inanimate, three-dimensional object or substance. For example -- a computer, the great pyramid, a sculpture. Note that digital representations of, or surrogates for, these things should use Image, Text or one of the other types.
Type of Term:	vocabulary-term
Status:	recommended
Date Issued:	2002-07-13
Term Name: Service
URI:	http://purl.org/dc/dcmitype/Service
Label:	Service
Definition:	A service is a system that provides one or more functions of value to the end-user. Examples include: a photocopying service, a banking service, an authentication service, interlibrary loans, a Z39.50 or Web server.
Type of Term:	vocabulary-term
Status:	recommended
Date Issued:	2000-07-11
Term Name: Software
URI:	http://purl.org/dc/dcmitype/Software
Label:	Software
Definition:	Software is a computer program in source or compiled form which may be available for installation non-transiently on another machine. For software which exists only to create an interactive environment, use interactive instead.
Type of Term:	vocabulary-term
Status:	recommended
Date Issued:	2000-07-11
Term Name: Sound
URI:	http://purl.org/dc/dcmitype/Sound
Label:	Sound
Definition:	A sound is a resource whose content is primarily intended to be rendered as audio. For example - a music playback file format, an audio compact disc, and recorded speech or sounds.
Type of Term:	vocabulary-term
Status:	recommended
Date Issued:	2000-07-11
Term Name: StillImage
URI:	http://purl.org/dc/dcmitype/StillImage
Label:	Still Image
Definition:	A static visual representation. Examples of still images are: paintings, drawings, graphic designs, plans and maps.
Comment:	Recommended best practice is to assign the type "text" to images of textual materials. Instances of the type "Still Image" must also be describable as instances of the broader type "Image".
Type of Term:	vocabulary-term
Narrower Than:	http://purl.org/dc/dcmitype/Image
Status:	recommended
Date Issued:	2003-11-18
Term Name: Text
URI:	http://purl.org/dc/dcmitype/Text
Label:	Text
Definition:	A text is a resource whose content is primarily words for reading. For example - books, letters, dissertations, poems, newspapers, articles, archives of mailing lists. Note that facsimiles or images of texts are still of the genre text.
Type of Term:	vocabulary-term
Status:	recommended
Date Issued:	2000-07-11

Expressing Dublin Core in HTML/XHTML meta and link elements
... href="http://www.naa.gov.au/recordkeeping/gov_online/agls/1.2" /> <meta
name="DC.title" content="Services to Government" /> <meta name="AGLS.Function" scheme ...
au.dublincore.org/documents/2003/10/31/dcq-html/index.html - 26k - Supplemental Result -

This document describes how a Dublin Core [DCMI] metadata record can be embedded into an HTML/XHTML Web page using HTML/XHTML elements.

It should be noted that several alternative mechanisms are available for associating a DC record with (or embedding a DC record into) an HTML/XHTML [HTML] resource. These include:

Creating a separate RDF/XML [DCRDF, QDCRDF] description and linking to it using the HTML/XHTML <link> element.
Creating a separate XML description [DCXML] and linking to it using the HTML/XHTML <link> element.

These alternative approaches are not described here.

1.1 Terminology

This document uses the following terminology:

Resource: a resource is anything that has identity. Familiar examples include an electronic document, an image, a service (e.g., "today's weather report for Los Angeles"), and a collection of other resources. Not all resources are network "retrievable"; e.g., human beings, corporations, and bound books in a library can also be considered resources.
Property: a property is a specific aspect, characteristic, attribute, or relation used to describe resources.
Record: a record is some structured metadata about a resource, comprising one or more properties and their associated values.

Note that Dublin Core metadata elements are properties (as defined above). Note also that there is potential confusion between the HTML/XHTML usage of the terms 'element' and 'attribute' and the usage of those terms in a more general metadata context.

In the context of this document, it should be noted that the resource being described is an HTML/XHTML Web page and the Dublin Core record describing that resource is embedded into it using HTML/XHTML <meta> elements. It is only possible to describe a single resource (the Web page) using this method. To describe multiple resources (for example, multiple images), link to one or more separate XML or RDF/XML documents containing the multiple Dublin Core records.

2. XHTML encoding

Metadata should be embedded into the <head> section of an XHTML Web page [XHTML11] using the <meta> and <link> elements, as described here.

2.1 Elements and values

Use the 'name' and 'content' attributes of the XHTML <meta> element to encode the DC element (one of the 15 DCMES elements or one of the other elements defined by DCMI, e.g. audience) and its value. Use the following patterns:

<meta name="DC.element" content="Value" />
<meta name="DCTERMS.element" content="Value" />

For example:

<meta name="DC.date" content="2001-07-18" />
<meta name="DCTERMS.audience" content="software developers" />

As a general rule, element names may be mixed-case but should always have a lower-case first letter.

The value in the 'content' attribute is defined to be CDATA, i.e. a sequence of characters from the document character set which may include character entities. Long values may be wrapped across multiple lines as necessary.

2.2 Element refinements

Element refinements are also encoded using the 'name' and 'content' attributes of the XHTML <meta> element. Use the following pattern:

<meta name="DCTERMS.elementRefinement" content="Value" />

For example:

<meta name="DCTERMS.modified" content="2001-07-18" />

Element refinements should use the names specified in the DCMI Metadata Terms recommendation (listed as the 'Name', not as the 'Label'). As a general rule, element refinement names may be mixed-case but should always have a lower-case first letter.

2.3 Encoding schemes

Encoding schemes are encoded using the 'scheme' attribute of the XHTML <meta> element, using the following pattern:

<meta name="DC.element" scheme="DCTERMS.Scheme" content="Value" />

For example:

<meta name="DC.date" scheme="DCTERMS.W3CDTF" content="2001-07-18" />
<meta name="DC.type" scheme="DCTERMS.DCMIType" content="Text" />

Encoding schemes should use the names specified in the DCMI Metadata Terms recommendation (listed as the 'Name', not as the 'Label'). As a general rule, encoding scheme names may be mixed-case but should always start with an upper-case letter. Encoding scheme names are often all upper-case.

2.4 Linking to other resources

Where the value of a property is the URI of another resource (as is typically the case with the DC.relation element for example) an alternative form of encoding using the XHTML <link> element is preferred. Use the following pattern:

<link rel="propertyName" href="resourceURI" />

For example:

<link rel="DC.relation" href="http://www.example.org/" />
<link rel="DCTERMS.references" href="http://www.example.org/publications/2002/176459.pdf" />

In some cases it may be appropriate to encode a list of DCMI and other 'Link types' [XHTMLLINK], for example:

<link rel="DC.rights copyright" href="http://www.example.org/rights.html" />
<link rel="DCTERMS.tableOfContents contents" href="http://www.example.org/toc.html" />

2.5 Language of the value

Where the language of the value is indicated, it should be encoded using the 'xml:lang' attribute of the XHTML <meta> element and/or the 'hreflang' attribute of the XHTML <link> element. For example:

<meta name="DC.subject" xml:lang="en-GB" content="seafood" />
<meta name="DC.subject" xml:lang="fr" content="fruits de mer" />
<link rel="DC.relation" hreflang="en" href="http://www.example.org/en/" />
<link rel="DC.relation" hreflang="de" href="http://www.example.org/de/" />

2.6 Repeated elements and element refinements

Multiple property values should be encoded by repeating the XHTML <meta> element for that property, for example:

<meta name="DC.title" content="First title" />
<meta name="DC.title" content="Second title" />

Note that the order of repeated elements and element refinements is not guaranteed to be preserved across multiple software applications.

2.7 Namespace and profile considerations

The 'DC.' and 'DCTERMS.' prefixes in the property names above are used to indicate the namespace [DCNS] from which the property is taken. The namespace URI should be encoded in the XHTML <link> element [RELSCHEMA], using the following pattern:

<link rel="schema.prefix" href="namespaceURI" />

For example:

<link rel="schema.DC" href="http://purl.org/dc/elements/1.1/" />
<link rel="schema.DCTERMS" href="http://purl.org/dc/terms/" />

While any string is allowable as the prefix, the use of 'DC.' and 'DCTERMS.' is recommended.

In order to give recipient software applications an indication of the XHTML profile that was used to encode the DCMI metadata, the 'profile' attribute of the XHTML <head> element must be used to provide the URI of this DCMI recommendation, as follows:

<head profile="http://dublincore.org/documents/dcq-html/">

3. Compatibility with other DCMI recommendations

Note that previous versions of this document (and other DCMI HTML-encoding documents) made some different recommendations to those found in this document, as follows:

Previous recommendations specified using an uppercase first letter for the names of DCMES elements, for example 'Title' rather than 'title'.
Previous recommendations specified prefixing element refinements by the element being refined, for example 'DC.Date.modified' rather than 'DCTERMS.modified'.
Previous recommendations did not specify using a namespace prefix for encoding scheme names, for example 'URI' rather than 'DCTERMS.URI'.
Previous recommendations did not specify using the HTML/XHTML <link> element to encode properties with values that are the URI for another resource.

These forms of encoding are acceptable but are no longer considered the preferred form.

In general, any software applications that consume DC records embedded into HTML/XHTML Web pages should ignore the case of DC namespace prefixes, element names and element refinement names. I.e. all the following forms should be treated as being equivalent:

<meta name="DC.date" content="2001-07-18" />
<meta name="DC.Date" content="2001-07-18" />
<meta name="dc.date" content="2001-07-18" />

as should:

<meta name="DC.Date.modified" content="2001-07-18" />
<meta name="DCTERMS.modified" content="2001-07-18" />

and:

<meta name="DC.Date" scheme="W3CDTF" content="2001-07-18" />
<meta name="dc.date" scheme="dcterms.W3CDTF" content="2001-07-18" />

All applications must generate metadata according to the recommendations above.

4. Compatibility with older versions of HTML

All the examples in this document conform to XHTML 1.1. The recommendations in this document can be applied to versions of HTML prior to XHTML 1.0 (e.g. HTML 4.01 [HTML401]) but the resulting syntax will be slightly different because older versions of HTML do not require the trailing '/' before the closing '>' in the HTML <meta> and <link> elements. Furthermore, for HTML 4.01 and older versions of HTML, 'lang' should be used to indicate the language of the value, rather than 'xml:lang'. For XHTML 1.0 Transitional (i.e. XHTML designed to be compatible with HTML) both 'lang' and 'xml:lang' should be used, for other version of XHTML (such as 1.1) only xml:lang should be used.

5. Mixing DC metadata with other schemas

DC metadata can be mixed with non-DC metadata in HTML/XHTML <meta> elements. The following example embeds DC, AGLS [AGLS] and unspecified metadata properties in the same HTML/XHTML Web page:

<link rel="schema.DC" href="http://purl.org/dc/elements/1.1/" />
<link rel="schema.AGLS" href="http://www.naa.gov.au/recordkeeping/gov_online/agls/1.2" />

<meta name="DC.title" content="Services to Government" />
<meta name="AGLS.Function" scheme="AGIFT" content="recordkeeping standards" />
<meta name="keywords" content="archives, information management,
public administration" />

Note that DCMI conventions for naming properties and encoding schemes may not apply to non-DC metadata elements.

6. Example

A qualified DC metadata record for this document is shown below. It can also be found embedded into the <head> section of the HTML source of this Web page.

...
<head profile="http://dublincore.org/documents/dcq-html/">
<title>Expressing Dublin Core in HTML/XHTML meta and link elements</title>
<link rel="schema.DC" href="http://purl.org/dc/elements/1.1/" />
<link rel="schema.DCTERMS" href="http://purl.org/dc/terms/" />

<meta name="DC.title" lang="en" content="Expressing Dublin Core
in HTML/XHTML meta and link elements" />
<meta name="DC.creator" content="Andy Powell, UKOLN, University of Bath" />
<meta name="DCTERMS.issued" scheme="DCTERMS.W3CDTF" content="2003-11-01" />
<meta name="DC.identifier" scheme="DCTERMS.URI"
content="http://dublincore.org/documents/dcq-html/" />
<link rel="DCTERMS.replaces" hreflang="en"
href="http://dublincore.org/documents/2000/08/15/dcq-html/" />
<meta name="DCTERMS.abstract" content="This document describes how
qualified Dublin Core metadata can be encoded
in HTML/XHTML &lt;meta&gt; elements" />
<meta name="DC.format" scheme="DCTERMS.IMT" content="text/html" />
<meta name="DC.type" scheme="DCTERMS.DCMIType" content="Text" />
</head>
.

7. Acknowledgements

This document is based on existing recommendations for encoding Dublin Core metadata into HTML [RFC2731], the previous version of this document by Simon Cox, Eric Miller and Andy Powell, current practice on the Web and recent versions of the HTML/XHTML specifications.

8. References

[DCMI]
Dublin Core Metadata Initiative
http://dublincore.org/

[HTML]
HyperText Markup Language (HTML)
http://www.w3.org/MarkUp/

[DCRDF]
Expressing Simple Dublin Core in RDF/XML
Dave Beckett, Eric Miller, Dan Brickley, 2001
http://dublincore.org/documents/dcmes-xml/

[QDCRDF]
Expressing Qualified Dublin Core in RDF / XML
Stefan Kokkelink, Roland Schwdnzl, 2002
http://dublincore.org/documents/dcq-rdf-xml/

[DCXML]
Guidelines for implementing Dublin Core in XML
Andy Powell, Pete Johnston
http://dublincore.org/documents/dc-xml-guidelines/

[DCMES]
Dublin Core Metadata Element Set, Version 1.1: Reference Description
http://dublincore.org/documents/dces/

[DCTERMS]
DCMI Metadata Terms
http://dublincore.org/documents/dcmi-terms/

[XHTML11]
XHTML 1.1: Module-based XHTML
W3C Recommendation, May 2001
http://www.w3.org/TR/xhtml11

[XHTMLLINK]
The 'link'-Element in (X)HTML
http://www.subotnik.net/html/link

[DCNS]
Namespace Policy for the Dublin Core Metadata Initiative (DCMI)
http://dublincore.org/documents/dcmi-namespace/

[RELSCHEMA]
A Proposed Convention for Embedding Metadata in HTML
http://www.w3.org/Search/9605-Indexing-Workshop/ReportOutcomes/S6Group2.html

[HTML401]
HTML 4.01 Specification
Dave Raggett, Arnaud Le Hors, Ian Jacobs, 1999
http://www.w3.org/TR/html40/

[AGLS]
AGLS Metadata Standard
http://www.naa.gov.au/recordkeeping/gov_online/agls/summary.html

[RFC2731]
Encoding Dublin Core metadata in HTML
John Kunze, 1999
http://www.ietf.org/rfc/rfc2731.txt

Sample #4.1 Dep. Consumer Emp. Protection - Alternative Md
... <meta name="AGLS.Function" content="This site provides visitors with information
relating to Consumer and Employment Protection within Western Australia">, ...
www.ami.com.au/~josak/IST4118-assign1/metadata/sample4.alternative.html - 29k - Supplemental Result -

Sample#4 Dep. Consumer Emp. Protection - Alternative Metadata:

Department of Consumer & Employment Protection: Home

~ Kept Original Tags ~

<head>

				

				<title>Department 
				of Consumer and Employment Protection -</title>

~ Kept Original Tag ~

<meta http-equiv="Content-Type"
				content="text/html; 
				charset=iso-8859-1">

This is a standard http coding that is put into the metadata by applications such as dreamweaver. It is used to identify the protocol (HTTP) by which the HTML pages interact with Web Servers.

~ Original Tag ~

<meta name="DC.Identifier"
		scheme="URI"
		content="mailto:online@docep.wa.gov.au">

	The Identifier element is what uniquely identifies the resource. Schemes that can be used include URI, ISBN and ISSN. The mailto: value in the identifier tag above probably adequate, but would be more suited to a AglsAgent scheme, which has an email= value.
	A standard value for a URI scheme is the URL (web address) of the resource.

~ Replacement Tag ~

<meta name="DC.Identifier"
				scheme="URI"
				content="http://www.docep.wa.gove.au">

~ Original Tags ~

<meta name="DC.Creator"
		content="corporateName: 
		Department of Consumer and Employment Protection">

		<meta name="DC.Creator"
		content="corporateName: 
		Strategy Division - Communications">

		<meta name="DC.Creator"
		content="personalName: 
		Patrick Langford">

The author of the resource has written the Creator element three times to allow for three values here. The addition of AglsAgent scheme here, would allow for all three values to be included in one tag-set.

~ Replacement Tag ~

<meta name="DC.Creator"
				scheme="AglsAgent"
				content="corporateName=Department 
				of Consumer and Employment Protection; corporateName=Strategy 
				Division - Communications; personalName=Patrick Langford">

~ Original Tag ~

<meta name="DC.Publisher"
		content="corporateName: 
		Strategy Division - Communications">

The inclusion of the AglsAgent scheme means the corporateName: must change to corporateName=

~ Replacement Tag ~

<meta name="DC.Publisher"
				scheme="AglsAgent"
				content="corporateName=Strategy 
				Division - Communications;">

~ Original Tag ~

<meta name="DC.Rights"
		content="Copyright 
		2002 Department of Consumer and Employment Protection">

The lack of scheme use to ground the metadata elements is the only real weakness in the DoCEPs Website. Using schemes allows the resource to interact more meaningfully with the Indexers used to search them.

~ Replacement Tag ~

<meta name="DC.Rights"
				scheme="URL"
				content="http://www.docep.wa.gov.au/default.asp?id=pages/copyright">

~ Original Tag ~

<meta name="DC.Title"
				content="Department 
				of Consumer and Employment Protection">

~ Original Tag ~

<meta name="DC.Subject"
		content="">

The Subject element - when combined with a good thesaurus - provides good keywords variables with which users can search the resource.

~ Replacement Tag ~

<meta name="DC.Subject"
				scheme="APAIS"
				content="Consumer 
				Protection; Commercial law; Quality 
				control; Product control; 
				Benchmarking; Consumer protection; 
				Standards; Trade regulation; 
				Business regulation; Government 
				regulation of business activity; 
				Labour Relations; Industrial 
				Relations; Enterprise bargaining; 
				Employment law; Industrial 
				arbitration; Industrial law; 
				Negotiation; Worker participation; 
				Working conditions; Work practices; 
				Energy Safety; Energy consumption; 
				Energy resources; Government 
				publications; 
				">

~ Original Tag ~

<meta name="DC.Description"
				content="This 
				site provides visitors with information relating to Consumer and 
				Employment Protection within Western Australia">

~ Original Tag ~

<meta name="DC.Language"
				scheme="RFC1766"
				content="en">

~ Original Tag ~

<meta name="DC.Coverage.spatial"
		content="">

It would seem that the department doesn't quite know what to make of the Coverage element?

~ Replacement Tag ~

<meta name="DC.Coverage.jurisdiction"
				scheme="AglsJuri"
				content="WA">

~ Original Tag ~

<meta name="AGLS.Function"
		content="This 
		site provides visitors with information relating to Consumer and 
		Employment Protection within Western Australia">

The AGLS.Function element - when used with the AGIFT scheme - provides the means for users to search for resources according to services provided.

~ Replacement Tag ~

<meta name="AGLS.Function"
				scheme="AGIFT"
				content="Consumer 
				protection; Fair trading compliance; Employment services; Human 
				resource development; Employment conditions and safety; 
				Recruitment programs; Termination processes; Workers 
				compensation schemes; Workplace discrimination monitoring 
				Workplace equity and justice programs; Income awa

DCMI Metadata Terms

Table of Contents

Section 1: Introduction and Definitions

References

Section 2: The Dublin Core Metadata Element Set

Section 3: Other Elements and Element Refinements

Section 4: Encoding Schemes

Section 5: The DCMI Type Vocabulary

1.1 Terminology

2. XHTML encoding

2.1 Elements and values

2.2 Element refinements

2.3 Encoding schemes

2.4 Linking to other resources

2.5 Language of the value

2.6 Repeated elements and element refinements

2.7 Namespace and profile considerations

3. Compatibility with other DCMI recommendations

4. Compatibility with older versions of HTML

5. Mixing DC metadata with other schemas

6. Example

7. Acknowledgements

8. References

Sample#4 Dep. Consumer Emp. Protection - Alternative Metadata:

Department of Consumer & Employment Protection: Home