7/29/2019 DCMI3

1/20

Dublin Core Metadata

Introduction

The name "Dublin" is due to its origin at a 1995 invitational workshopin Dublin, Ohio; USA; "core" because its elements are broad andgeneric, usable for describing a wide range of resources. The DublinCore Metadata Initiative Limited is registered in Singapore.

The Dublin Coremetadata terms are a set of vocabulary of fifteenterms which can be used to describe resources for the purposes ofdiscovery. The terms can be used to describe a full range of webresources: video, images, web pages etc. and physical resources suchas books and objects like artworks.

Since 2001, the event includes a Tutorial track, a peer-reviewedConference track, Special Sessions and Working Group meetingsattended by hundreds of experts in the field from many countriesaround the world.

http://en.wikipedia.org/wiki/Metadatahttp://en.wikipedia.org/wiki/Metadata

7/29/2019 DCMI3

2/20

All changes made to terms of the Dublin Core Metadata Element Set since 2001have been reviewed by a Dublin Core Metadata Initiatives (DCMI) Usage Boardin the context of a DCMI Namespace Policy [DCMI-NAMESPACE]. Thenamespace policy describes how DCMI terms are assigned Uniform Resource

Identifiers (URIs) and sets limits on the range of editorial changes that mayallowably be made to the labels, definitions, and usage comments associatedwith existing DCMI terms.

The Dublin Core Metadata Initiative Conference and Workshop Series gathersexperts from various areas in the private and public sectors, including the libraryworld, the networking and digital library research communities, corporateknowledge management, e-government and public sector information.

Initially organized as a series of invitational workshops with a main focus at thedefinition and finalization of the Dublin Core metadata standards, this has

developed into an annual get-together of people involved in the work of DCMIand other metadata activities.

Since January 2008, therefore, DCMI includes formal domains and ranges in thedefinitions of its properties.

7/29/2019 DCMI3

3/20

The Dublin Core element set was originally developed in English, but versions are

being created in many other languages

The Dublin Core standard includes two levels:

(1) Simple (2) Qualified

Simple Dublin Core comprises fifteen elements.

Qualified Dublin Core includes three additional elements

(1) Audience (2) Provenance (3) Rights Holder

The semantics of Dublin Core have been established by an international, cross-disciplinary group of professionals from librarianship, computer science, text

encoding, the museum community, and other related fields of scholarship and

practice.

Note: Semantics Web is collaborative movement led by the international standards

body, the world wide web consortium(W3C)

7/29/2019 DCMI3

4/20

Mission and Principles

Providing open access to education, training and documentation resources

related to innovative design and metadata best practices.

Supporting a worldwide community of people working with metadata to

share experiences and find common solutions through collaborative tools,

publications and meetings.

Promoting co-operation, and interoperability across standards and

vocabularies, by engaging with other organizations and communities.

Developing and maintaining the DCMI metadata vocabularies andpromoting their use in conjunction with other vocabularies for describing

resources.

7/29/2019 DCMI3

5/20

Dublin Core Elements

1.Creator

2.Contributor

3.Coverage

4.Date5.Description

6.Format

7. Identifier

8.Language

9. Publisher

10.Title

11.Type

12.Subject13.Source

14.Rights

15.Relation

7/29/2019 DCMI3

6/20

Label: Creator

Element Description: An entity primarily responsible for making

the resource.

Comment: Examples of a Creator include a person, anorganization, or a service. Typically, the name of a creator shouldbe used to indicate the entity.

Examples:

Creator="Shakespeare, William"

Creator="Hubble Telescope"Creator="Internal Revenue Service. Customer Complaints Unit

URI: http://purl.org/dc/elements/1.1/creator

http://purl.org/dc/elements/1.1/creatorhttp://purl.org/dc/elements/1.1/creatorhttp://purl.org/dc/elements/1.1/creator

7/29/2019 DCMI3

7/20

Label: Contributor

Element Description: An entity responsible for making contributions to the content of the resource.

Examplesof a contributor include a person, an organization or a service. Typically, the name of a

contributor should be used to indicate the entity.Contributor is the most general of the elements used for "agents" responsible for the resource, so should

be used when primary responsibility is unknown or irrelevant.

URI: http://purl.org/dc/elements/1.1/contributor

Label: Coverage

Element Description: The spatial or temporal topic of the resource, the spatial applicability of the

resource, or the jurisdiction under which the resource is relevant.

Examples:

Coverage="1995-1996"

Coverage="Boston, MA"

Coverage="17th century"

Coverage="Upstate New York

URI: http://purl.org/dc/elements/1.1/coverage

http://purl.org/dc/elements/1.1/contributorhttp://purl.org/dc/elements/1.1/coveragehttp://purl.org/dc/elements/1.1/coveragehttp://purl.org/dc/elements/1.1/coveragehttp://purl.org/dc/elements/1.1/coveragehttp://purl.org/dc/elements/1.1/contributorhttp://purl.org/dc/elements/1.1/contributor

7/29/2019 DCMI3

8/20

Date

Element Description:A point or period of time associated with

an event in the lifecycle of the resource.

Comment:Date may be used to express temporal information atany level of granularity. Recommended best practice is to use anencoding scheme, such as the W3CDTF and follows the YYYY-

MM-DD format.

Examples:

Date="1998-02-16"Date="1998-02"Date="1998

URI: http://purl.org/dc/elements/1.1/date

http://purl.org/dc/elements/1.1/datehttp://purl.org/dc/elements/1.1/datehttp://purl.org/dc/elements/1.1/date

7/29/2019 DCMI3

9/20

Label: Description

Definition: An account of the resource.

Comment: 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.

Examples:

Description="Illustrated guide to airport markings and lighting signals, with

particular reference to SMGCS (Surface Movement Guidance and Control

System) for airports with low visibility conditions."

URI: http://purl.org/dc/elements/1.1/description

http://purl.org/dc/elements/1.1/descriptionhttp://purl.org/dc/elements/1.1/descriptionhttp://purl.org/dc/elements/1.1/description

7/29/2019 DCMI3

10/20

Label: Format

Definition: The file format, physical medium, or dimensions of the resource.

Comment: 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] defining computer media formats).

Examples:

Title="Dublin Core icon"

Identifier="http://purl.org/metadata/dublin_core/images/dc2.gif& quot;

Type="Image"

Format="image/gif"

Format="4 kB"

URI: http://purl.org/dc/elements/1.1/format

http://purl.org/dc/elements/1.1/formathttp://purl.org/dc/elements/1.1/formathttp://purl.org/dc/elements/1.1/format

7/29/2019 DCMI3

11/20

Resource Identifier

Definition: An unambiguous reference to the resource within a given context.

Comment: Recommended best practice is to identify the resource by meansof a string conforming to a formal identification system.

Examples:

Examples of formal identification systems include the Uniform ResourceIdentifier (URI) (including the Uniform Resource Locator (URL), the DigitalObject Identifier (DOI) and the International Standard Book Number(ISBN).

Identifier="http://purl.oclc.org/metadata/dublincore/& quot;

Identifier="ISBN:0385424728"Identifier="H-A-X 5690B" [publisher number]

URI: http://purl.org/dc/elements/1.1/identifier

http://purl.org/dc/elements/1.1/identifierhttp://purl.org/dc/elements/1.1/identifierhttp://purl.org/dc/elements/1.1/identifier

7/29/2019 DCMI3

12/20

Language

Definition: A language of the intellectual content of the resource.

Comment: Recommended best practice is to use a controlledvocabulary such as RFC 4646 [RFC4646]. Examples include "en" or"eng" for English, "akk" for Akkadian, and "en-GB" for English used inthe United Kingdom.

Examples:

Language="en"Language="fr"Language="Primarily English, with some abstracts also in French."

Language="en-US"

URI: http://purl.org/dc/elements/1.1/language

http://purl.org/dc/elements/1.1/languagehttp://purl.org/dc/elements/1.1/languagehttp://purl.org/dc/elements/1.1/language

7/29/2019 DCMI3

13/20

Publisher

Definition: An entity responsible for making the resource available.

Comment: Examples of a Publisher include a person, an organization,or a service. Typically, the name of a Publisher should be used toindicate the entity.

Examples:

Publisher="University of South Where"Publisher="Funky Websites, Inc."Publisher="Carmen Miranda"

URI: http://purl.org/dc/elements/1.1/publisher

http://purl.org/dc/elements/1.1/publisherhttp://purl.org/dc/elements/1.1/publisherhttp://purl.org/dc/elements/1.1/publisher

7/29/2019 DCMI3

14/20

Source

Definition: A related resource from which the described resource is derived.

Comment: The described resource may be derived from the related resourcein whole or in part. Recommended best practice is to identify the relatedresource by means of a string conforming to a formal identification system.

Examples:

Source="RC607.A26W574 1996" [where "RC607.A26W574 1996" is thecall number of the print version of the resource, from which the presentversion was scanned]

Source="Image from page 54 of the 1922 edition of Romeo and Juliet"

URI: http://purl.org/dc/elements/1.1/source

http://purl.org/dc/elements/1.1/sourcehttp://purl.org/dc/elements/1.1/sourcehttp://purl.org/dc/elements/1.1/source

7/29/2019 DCMI3

15/20

Subject and Keywords

Definition: The topic of the resource.

Comment: The topic of the content of the resource. Typically, a

Subject will be expressed as keywords or key phrases or classification

codes that describe the topic of the resource. Recommended best

practice is to select a value from a controlled vocabulary or formalclassification scheme.

Examples:

Subject="Aircraft leasing and renting"Subject="Dogs"

URI: http://purl.org/dc/elements/1.1/subject

7/29/2019 DCMI3

16/20

Title

Definition: A name given to the resource.

Comment: Typically, a Title will be a name by which theresource is formally known.

Examples:

Title="A Pilot's Guide to Aircraft Insurance"Title="The Sound of Music"

Title="Green on Greens"

URI: http://purl.org/dc/elements/1.1/title

http://purl.org/dc/elements/1.1/titlehttp://purl.org/dc/elements/1.1/titlehttp://purl.org/dc/elements/1.1/title

7/29/2019 DCMI3

17/20

Resource Type

Definition: The nature or genre of the content of the resource.

Comment: Recommended best practice is to use a controlled vocabularysuch as the DCMI Type Vocabulary [DCMITYPE]. To describe the file format,physical medium, or dimensions of the resource, use the Format element.

Examples:

Type="Image"Type="Sound"Type="Text"Type= ="Exhibition catalog"

Note: The first three values are taken from the DCMI Type Vocabulary, andfollow the capitalization conventions for that vocabulary. The last value isa term from an unspecified source.

URI: http://purl.org/dc/elements/1.1/type

http://purl.org/dc/elements/1.1/typehttp://purl.org/dc/elements/1.1/typehttp://purl.org/dc/elements/1.1/type

7/29/2019 DCMI3

18/20

Relation

Definition: A reference to a related resource.

Comment: Recommended best practice is to identify the relatedresource by means of a string conforming to a formal identificationsystem.

Examples:

Title="Candle in the Wind"Subject="Diana, Princess of Wales"Date="1997"Creator="John, Elton"

Type="sound"Description="Tribute to a dead princess."Relation="Elton John's 1976 song Candle in the Wind"

URI: http://purl.org/dc/elements/1.1/relation

http://purl.org/dc/elements/1.1/relationhttp://purl.org/dc/elements/1.1/relation

7/29/2019 DCMI3

19/20

Rights Management

Definition: Information about rights held in and over the resource.

Comment: Typically a Rights element will contain a rights managementstatement 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, noassumptions can be made about the status of these and other rights withrespect to the resource.

Examples:

Rights="Access limited to members"Rights="http://cs-tr.cs.cornell.edu/Dienst/Repository/2.0/Terms& quot;

URI: http://purl.org/dc/elements/1.1/rights

http://purl.org/dc/elements/1.1/rightshttp://purl.org/dc/elements/1.1/rightshttp://purl.org/dc/elements/1.1/rights

7/29/2019 DCMI3

20/20

Qualified Dublin Core includes three additional elements.

Audience: A class of entity for whom the resource is intended or useful. A classof entity may be determined by the creator or the publisher or by a third party.

Examples:Audience="elementary school studentsAudience="ESL teachersAudience="deafadults

Provenance:A statement of any changes in ownership and custody of theresource since its creation that are significant for its authenticity, integrity andinterpretation.

Example:

Provenance="Stolen in 1999; recovered by the Museum in 2003.

RightsHolder:A person or organization owning or managing rights over theresource.

Example:

RightsHolder="University ofBath or "Stuart Weibel