The Dublin Core Element Set v1.1
type: Schema
publisher: The Dublin Core Metadata Initiative
description: The Dublin Core metadata vocabulary is a simple vocabulary intended to facilitate discovery of resources.
language: English
Relation: dces
date: 2000-07-02

Title
type: Property
comment: A name given to the resource.
comment: Typically, a Title will be a name by which the resource is formally known.

Contributor
type: Property
comment: An entity responsible for making contributions to the content of the resource.
comment: Examples of a Contributor include a person, an organisation, or a service. Typically, the name of a Contributor should be used to indicate the entity.

Author/Creator
type: Property
comment: An entity primarily responsible for making the content of the resource.
comment: Examples of a Creator include a person, an organisation, or a service. Typically, the name of a Creator should be used to indicate the entity.

Publisher
type: Property
comment: An entity responsible for making the resource available.
comment: Examples of a Publisher include a person, an organisation, or a service. Typically, the name of a Publisher should be used to indicate the entity.

Subject
type: Property
comment: The topic of the content of the resource.
comment: Typically, a Subject will be expressed as keywords, key phrases or classification codes that describe a topic of the resource. Recommended best practice is to select a value from a controlled vocabulary or formal classification scheme.

Description
type: Property
comment: An account of the content of the resource.

Date
type: Property
comment: A date associated with an event in the life cycle of the resource.
comment: Typically, Date will be associated with the creation or availability of the resource. Recommended best practice for encoding the date value is defined in a profile of ISO 8601 [W3CDTF] and follows the YYYY-MM-DD format.

Resource Type
type: Property
comment: The nature or genre of the content of the resource.

Format
type: Property
comment: The physical or digital manifestation of the resource.
comment: Typically, Format may include the media-type or dimensions of the resource. Format may be used to determine the software, hardware or other equipment needed to display or operate the resource. Examples of dimensions include size and duration. 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).

Resource Identifier
type: Property
comment: An unambiguous reference to the resource within a given context.
comment: Recommended best practice is to identify the resource by means of a string or number conforming to a formal identification system. Example formal identification systems include the Uniform Resource Identifier (URI) (including the Uniform Resource Locator (URL)), the Digital Object Identifier (DOI) and the International Standard Book Number (ISBN).

Language
type: Property
comment: A language of the intellectual content of the resource.
comment: Recommended best practice for the values of the Language element is defined by RFC 1766 [RFC1766] which includes a two-letter Language Code (taken from the ISO 639 standard [ISO639]), followed optionally, by a two-letter Country Code (taken from the ISO 3166 standard [ISO3166]). For example, 'en' for English, 'fr' for French, or 'en-uk' for English used in the United Kingdom.

Relation
type: Property
comment: A reference to a related resource.
comment: Recommended best practice is to reference the resource by means of a string or number conforming to a formal identification system.

Source
type: Property
comment: A Reference to a resource from which the present resource is derived.
comment: The present resource may be derived from the Source resource in whole or in part. Recommended best practice is to reference the resource by means of a string or number conforming to a formal identification system.

Coverage
type: Property
comment: The extent or scope of the content of the resource.
comment: Coverage will typically include spatial location (a place name or geographic coordinates), temporal period (a period label, date, or date range) or jurisdiction (such as a named administrative entity). Recommended best practice is to select a value from a controlled vocabulary (for example, the Thesaurus of Geographic Names [TGN]) and that, where appropriate, named places or time periods be used in preference to numeric identifiers such as sets of coordinates or date ranges.

Rights
type: Property
comment: Information about rights held in and over the resource.
comment: Typically, a Rights element will contain a rights management statement for the resource, or reference a service providing such information. Rights information often encompasses Intellectual Property Rights (IPR), Copyright, and various Property Rights. If the Rights element is absent, no assumptions can be made about the status of these and other rights with respect to the resource.