1

Dublin Core & DCMI– an introduction

Some slides are from DCMI Training Resources at: http://dublincore.org/resources/training/

2

1. The original Dublin Core: the idea A basic description mechanism that:

can be used in all domains can be used for any type of resource is simple, yet powerful can be extended and can work with specific

solutions

Making it easier to find information wherever located (Internet/Intranets)

3

2. The Dublin Core Metadata Element Set （ DCMES ） dc:

Metadata elements The Dublin Core Metadata Element Set

http://dublincore.org/documents/dces/or: http://dublincore.org/documents/dcmi-terms/#H2

“Core” set, simple enough for non-experts to understand and create

A “library catalog card” for Web objects Based on consensus across domains

Elements1. Identifier2. Title3. Creator4. Contributor5. Publisher6. Subject7. Description8. Coverage9. Format10. Type11. Date12. Relation13. Source14. Rights15. Language

4

The Dublin Core Metadata Element Set （ DCMES ）

15 elementsall optionalall repeatable

5Compiled based on Compiled according to DCMI Metadata Terms, 2008-01-14 , ©mzeng

6Compiled based on Compiled according to DCMI Metadata Terms, 2008-01-14 , ©mzeng

Cont. DC Version 1.1 Elements with Refinements and Encoding Schemes

7

Elements* requiring using Encoding Schemes

Content Intellectual Property

Instantiation Coverage * Contributor Date *Description Creator Format *Type * Publisher Identifier

Relation Rights Language * Source

Subject *Title

Values assigned in some spaces should follow certain encoding schemes.

An encoding scheme usually appears as a list of name tokens or terms from which values can be selected for the associated metadata elements.

8

Value space that should apply controlled vocabularies / value encoding schemes : LANGUAGE

Examples from values associated with LANGUAGE elementfound in the research samples because of failing to follow the recommendation en eng en-GB en-US English

engfre new Korean Deutsch German LOCLANGUAGE:: German

9

Value space that should follow syntax encoding schemes : DATE

Examples from values associated with DATE element 1979 2000-03 2000-03-01 2001-01-02T21:48.00Z 200003 C1999, 2000 January, 1919 May, 1919

1987, c2000 ?1999 1952 (issued) (1982) 1930? 1823-1845 Between 1680 and 1896? 5/1/01 01 May 2008

10

3. Growing the vocabulary to become DCMI Metadata Terms (dcterms:)

AbstractAccess rightsAlternativeAudienceAvailableBibliographic citationConforms toCreatedDate acceptedDate copyrightedDate submittedEducation levelExtentHas formatHas partHas versionIs format ofIs part of

Is referenced byIs replaced byIs required byIssuedIs version ofLicenseMediatorMediumModifiedProvenanceReferencesReplacesRequiresRights holderSpatialTable of contentsTemporalValid

RefinementsBoxDCMITypeDDCIMTISO3166ISO639-2LCCLCSHMeSHPeriodPointRFC1766RFC3066TGNUDCURIW3CTDF

EncodingsCollectionDatasetEventImageInteractive ResourceMoving ImagePhysical ObjectServiceSoftwareSoundStill ImageText

Types

11

Note: all refinements are now also 'properties' in DCMI Terms

DCMI Metadata Termsdcterms: or dct:

12

5. DCMI namespaces

All DCMI Metadata Terms are given a unique identity within DCMI namespaces:• http://purl.org/dc/elements/1.1/ (for the legacy DC-15 elements)• http://purl.org/dc/terms/ (for all elements and element refinements)• http://purl.org/dc/dcmitype/ (for the DCMI Type vocabulary)

13

http://purl.org/dc/elements/1.1/creator “dc:creator” http://purl.org/dc/terms/title "dct:title"

E.g., “title” is identified by its Uniform Resource Identifier (URI):

“http://purl.org/dc/elements/1.1/title” in legacy “dc” or "http://purl.org/dc/terms/title" in “dcterms”

Term URI QName (XML qualified name)

Term constraints: Range and Domain

14

Constraints indicate•where it applies (Has Domain: “Collection”)

• what values to be used in the metadata statement, non-literal or literal (constant values represented by character strings).

•what kind of values its instances should be (Has Range: “Frequency”).

Literal and non-literal values

15

The values

are literals*

The values

are literals*

The values are non-literals(URIs)

The values are non-literals(URIs)

*literal (constant values represented by character strings)

16

6. The Dublin Core in context: Application profiles (will be discussed later)

In practice, metadata implementers combine elements from different sources (e.g. DC plus

elements from other schemas, “local” elements) refine definitions of elements constrain use of elements

Application profiles (will be discussed later) element set plus policies, guidelines some DCMI WGs developing application profiles for specific

domains

17

References

Dublin Core Metadata Initiative: http://dublincore.org/DCMI Metadata Terms http://dublincore.org/documents/dcmi-terms/ Dekkers, Makx. (2010). Dublin Core in the Early Web Revolution. http://dublincore.org/resources/training/Baker, Thomas. (2009) The "metadata record" and DCMI Abstract Model. http://dublincore.org/resources/training/Dempsey, Lorcan. “Scientific, Industrial, and Cultural Heritage: a shared approach” http://www.ariadne.ac.uk/issue22/dempsey/Johnston, Pete. (2002). An introduction to the Dublin Core and the DCMI. www.ukoln.ac.uk/interop-focus/presentations/gateway/gateway.pptBaker, Thomas. (2005) Diverse vocabulariesin a common model: Dublin Core at 10 years. http://dc2005.uc3m.es/program/presentations/2005-09-12.plenary.baker-keynote.ppt