Dublin Core is an international ISO standard with 15 metadata elements for describing sources, both on the web and physically. Apart from the simple description by means of 15 metadata fields, the standard can also be used to combine different metadata standards in order to promote interoperability.
The DCMI Metadata Terms is an extension with ‘qualified’ terms that refine the 15 basic elements. There are also specific elements for documenting relationships between sources. The possibilities for documenting technical properties are limited because the data structure aims for the widest possible use.
Dublin Core Elements Set is a minimum standard.
Table 1 – The Dublin Core metadata element set
Content | Intellectual property | Instantiation |
Coverage | Contributor | Date |
Description | Creator | Format |
Type | Publisher | Identifier |
Relation | Rights | Language |
Source | ||
Subject | ||
Title |
From: dublincore.org
The standard is sometimes regarded as poorly organised because of the difficulty of finding definitions for the individual metadata elements. A major difference with other metadata standards for documents is that there is no predefined order in which the elements should be used. In the list above, the element ‘Title’ is listed first and ‘Rights’ last. But it could just as well be the other way round or in alphabetical order.
There are two ways to use the elements: with or without extensions. If you use them without extensions then you use “Simple Dublin Core” or simplified Dublin Core. If you use the elements with extensions then you use Qualified Dublin Core. The extensions are called refinements or qualifiers. For example, ‘created’, ‘valid’, ‘issued’ and ‘modified’ are the recommended refinements of the ‘Date’ element.
So, dc.date.created would be the name for the creation date element of a document in Qualified DC. Qualified DC also adds three more metadata elements: Audience, Provenance and RightsHolder.
Contributor
Label | Contributor |
URL | contributor |
Definitie | An entity responsible for making contributions to the resource. |
Commentaar | Examples of a Contributor include a person, an organization, or a service. Typically, the name of a Contributor should be used to indicate the entity. |
Coverage
Label | Coverage |
URL | coverage |
Definitie | The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant. |
Commentaar | Spatial topic and spatial applicability may be a named place or a location specified by its geographic coordinates. Temporal topic may be a named period, date, or date range. A jurisdiction may be a named administrative entity or a geographic place to which the resource applies. Recommended best practice is to use a controlled vocabulary such as the Thesaurus of Geographic Names [TGN]. Where appropriate, named places or time periods can be used in preference to numeric identifiers such as sets of coordinates or date ranges. |
Creator
Label | Creator |
URL | creator |
Definitie | An entity primarily responsible for making the resource. |
Commentaar | Examples of a Creator include a person, an organization, or a service. Typically, the name of a Creator should be used to indicate the entity. |
Date
Label | Date |
URL | date |
Definitie | A point or period of time associated with an event in the lifecycle of the resource. |
Commentaar | Date may be used to express temporal information at any level of granularity. Recommended best practice is to use an encoding scheme, such as the W3CDTF profile of ISO 8601 [W3CDTF]. |
Description
Label | Description |
URL | description |
Definitie | An account of the resource. |
Commentaar | Description may include but is not limited to: an abstract, a table of contents, a graphical representation, or a free-text account of the resource. |
Format
Label | Format |
URL | format |
Definitie | The file format, physical medium, or dimensions of the resource. |
Commentaar | Examples of dimensions include size and duration. Recommended best practice is to use a controlled vocabulary such as the list of Internet Media Types [MIME]. |
Identifier
Label | Identifier |
URL | identifier |
Definitie | An unambiguous reference to the resource within a given context. |
Commentaar | Recommended best practice is to identify the resource by means of a string conforming to a formal identification system. |
Language
Label | Language |
URL | language |
Definitie | A language of the resource. |
Commentaar | Recommended best practice is to use a controlled vocabulary such as RFC 4646 [RFC4646]. |
Publisher
Label | Publisher |
URL | publisher |
Definitie | An entity responsible for making the resource available. |
Commentaar | Examples of a Publisher include a person, an organization, or a service. Typically, the name of a Publisher should be used to indicate the entity. |
Relation
Label | Relation |
URL | relation |
Definitie | A related resource. |
Commentaar | Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system. |
Rights
Label | Rights |
URL | rights |
Definitie | Information about rights held in and over the resource. |
Commentaar | Typically, rights information includes a statement about various property rights associated with the resource, including intellectual property rights. |
Source
Label | Source |
URL | source |
Definitie | A related resource from which the described resource is derived. |
Commentaar | The described resource may be derived from the related resource in whole or in part. Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system. |
Subject
Label | Subject |
URL | subject |
Definitie | The topic of the resource. |
Commentaar | Typically, the subject will be represented using keywords, key phrases, or classification codes. Recommended best practice is to use a controlled vocabulary. |
Title
Label | Title |
URL | title |
Definitie | A name given to the resource. |
Commentaar | Typically, a Title will be a name by which the resource is formally known. |
Type
Label | Type |
URL | Type |
Definitie | The nature or genre of the resource. |
Commentaar | Recommended best practice is to use a controlled vocabulary such as the DCMI Type Vocabulary [DCMITYPE]. To describe the file format, physical medium, or dimensions of the resource, use the Format element. |