Dublin Core

From Wikipedia, the free encyclopedia
  (Redirected from Dublin core)
Jump to: navigation, search

The Dublin Core Schema is a small set of vocabulary terms that can be used to describe web resources (video, images, web pages, etc.), as well as physical resources such as books or CDs, and objects like artworks.[1] The full set of Dublin Core metadata terms can be found on the Dublin Core Metadata Initiative (DCMI) website.[2] The original set of 15 classic[3] metadata terms, known as the Dublin Core Metadata Element Set[4] are endorsed in the following standards documents:

Dublin Core Metadata may be used for multiple purposes, from simple resource description, to combining metadata vocabularies of different metadata standards, to providing interoperability for metadata vocabularies in the Linked Data cloud and Semantic Web implementations.

Background[edit]

"Dublin" refers to Dublin, Ohio, USA where the schema originated during the 1995 invitational OCLC/NCSA Metadata Workshop,[8] hosted by the Online Computer Library Center (OCLC), a library consortium based in Dublin, and the National Center for Supercomputing Applications (NCSA). "Core" refers to the metadata terms as "broad and generic being usable for describing a wide range of resources".[4] The semantics of Dublin Core were established and are maintained by an international, cross-disciplinary group of professionals from librarianship, computer science, text encoding, museums, and other related fields of scholarship and practice.

Starting in 2000, the Dublin Core community focused on "application profiles" – the idea that metadata records would use Dublin Core together with other specialized vocabularies to meet particular implementation requirements. During that time, the World Wide Web Consortium's work on a generic data model for metadata, the Resource Description Framework (RDF), was maturing. As part of an extended set of DCMI Metadata Terms, Dublin Core became one of most popular vocabularies for use with RDF, more recently in the context of the Linked Data movement.[9]

The Dublin Core Metadata Initiative (DCMI)[10] provides an open forum for the development of interoperable online metadata standards for a broad range of purposes and of business models. DCMI's activities include consensus-driven working groups, global conferences and workshops, standards liaison, and educational efforts to promote widespread acceptance of metadata standards and practices. In 2008, DCMI separated from OCLC and incorporated as an independent entity.[11]

Currently, any and all changes that are made to the Dublin Core standard as reviewed by a DCMI Usage Board within the context of a DCMI Namespace Policy (DCMI-NAMESPACE). This policy describes how terms are assigned and also sets limits on the amount of editorial changes allowed to the labels, definitions, and usage comments.[12]

Levels of the standard[edit]

The Dublin Core standard originally includes two levels: Simple and Qualified. Simple Dublin Core comprised 15 elements; Qualified Dublin Core included three additional elements (Audience, Provenance and RightsHolder), as well as a group of element refinements (also called qualifiers) that could refine the semantics of the elements in ways that may be useful in resource discovery.

Since 2012 the two have been incorporated into the DCMI Metadata Terms as a single set of terms using the Resource Description Framework (RDF).[13] The full set of elements is found under the namespace http://purl.org/dc/terms/. Because the definition of the terms often contains domains and ranges, which may not be compatible with the pre-RDF definitions used for the original 15 Dublin Core elements, there is a separate namespace for the original 15 elements as previously defined: http://purl.org/dc/elements/1.1/.[14]

Dublin Core Metadata Element Set Version 1.1[edit]

The original Dublin Core Metadata Element Set consists of 15 metadata elements:[4]

  1. Title
  2. Creator
  3. Subject
  4. Description
  5. Publisher
  6. Contributor
  7. Date
  8. Type
  9. Format
  10. Identifier
  11. Source
  12. Language
  13. Relation
  14. Coverage
  15. Rights

Each Dublin Core element is optional and may be repeated. The DCMI has established standard ways to refine elements and encourage the use of encoding and vocabulary schemes. There is no prescribed order in Dublin Core for presenting or using the elements. The Dublin Core became ISO 15836 standard in 2006 and is used as a base-level data element set for the description of learning resources in the ISO/IEC 19788-2 Metadata for learning resources (MLR) – Part 2: Dublin Core elements, prepared by the ISO/IEC JTC1 SC36.

Full information on element definitions and term relationships can be found in the Dublin Core Metadata Registry.[15]

Example of code[edit]

<meta name="DC.Format" content="video/mpeg; 10 minutes">

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

<meta name="DC.Publisher" content="publisher-name" > <meta name="DC.Title" content="HYP" >

An example of use [and mention] of D.C. (by WebCite)[edit]

At the web page which serves as the "archive" form for WebCite,[16] it says, in part: "Metadata (optional)         These are Dublin Core elements. [...]".

Qualified Dublin Core (deprecated in 2012[17])[edit]

Subsequent to the specification of the original 15 elements, an ongoing process to develop exemplary terms extending or refining the Dublin Core Metadata Element Set (DCMES) was begun. The additional terms were identified, generally in working groups of the Dublin Core Metadata Initiative, and judged by the DCMI Usage Board to be in conformance with principles of good practice for the qualification of Dublin Core metadata elements.

Elements refinements make the meaning of an element narrower or more specific. A refined element shares the meaning of the unqualified element, but with a more restricted scope. The guiding principle for the qualification of Dublin Core elements, colloquially known as the Dumb-Down Principle,[18] states that an application that does not understand a specific element refinement term should be able to ignore the qualifier and treat the metadata value as if it were an unqualified (broader) element. While this may result in some loss of specificity, the remaining element value (without the qualifier) should continue to be generally correct and useful for discovery.

In addition to element refinements, Qualified Dublin Core includes a set of recommended encoding schemes, designed to aid in the interpretation of an element value. These schemes include controlled vocabularies and formal notations or parsing rules. A value expressed using an encoding scheme may thus be a token selected from a controlled vocabulary (for example, a term from a classification system or set of subject headings) or a string formatted in accordance with a formal notation, for example, "2000-12-31" as the ISO standard expression of a date. If an encoding scheme is not understood by an application, the value may still be useful to human reader.

Audience, Provenance and RightsHolder are elements, but not part of the Simple Dublin Core 15 elements. Use Audience, Provenance and RightsHolder only when using Qualified Dublin Core. DCMI also maintains a small, general vocabulary recommended for use within the element Type. This vocabulary currently consists of 12 terms.[15]

DCMI Metadata Terms[edit]

The Dublin Core Metadata Initiative (DCMI) Metadata Terms is the current set of the Dublin Core vocabulary.[19] This set includes the fifteen terms of the Dublin Core Metadata Element Set (in italic), as well as the qualified terms. Each term has a unique URI in the namespace http://purl.org/dc/terms, and all are defined as RDF properties.

  • abstract
  • accessRights
  • accrualMethod
  • accrualPeriodicity
  • accrualPolicy
  • alternative
  • audience
  • available
  • bibliographicCitation
  • conformsTo
  • contributor
  • coverage
  • created
  • creator
  • date
  • dateAccepted
  • dateCopyrighted
  • dateSubmitted
  • description
  • educationLevel
  • extent
  • format
  • hasFormat
  • hasPart
  • hasVersion
  • identifier
  • instructionalMethod
  • isFormatOf
  • isPartOf
  • isReferencedBy
  • isReplacedBy
  • isRequiredBy
  • issued
  • isVersionOf
  • language
  • license
  • mediator
  • medium
  • modified
  • provenance
  • publisher
  • references
  • relation
  • replaces
  • requires
  • rights
  • rightsHolder
  • source
  • spatial
  • subject
  • tableOfContents
  • temporal
  • title
  • type
  • valid

Syntax[edit]

Syntax choices for Dublin Core metadata depends on a number of variables, and "one size fits all" prescriptions rarely apply. When considering an appropriate syntax, it is important to note that Dublin Core concepts and semantics are designed to be syntax independent and are equally applicable in a variety of contexts, as long as the metadata is in a form suitable for interpretation both by machines and by human beings.

The Dublin Core Abstract Model[20] provides a reference model against which particular Dublin Core encoding guidelines can be compared, independent of any particular encoding syntax. Such a reference model allows implementers to gain a better understanding of the kinds of descriptions they are trying to encode and facilitates the development of better mappings and translations between different syntax.

Some applications[edit]

One Document Type Definition based on Dublin Core is the Open Source Metadata Framework (OMF) specification. OMF is in turn used by Rarian (superseding ScrollKeeper), which is used by the GNOME desktop and KDE help browsers and the ScrollServer documentation server. PBCore is also based on Dublin Core. The Zope CMF's Metadata products, used by the Plone, ERP5, the Nuxeo CPS Content management systems, SimpleDL, and FedoraCommons also implement Dublin Core. The EPUB e-book format uses Dublin Core metadata in the OPF file.[21] eXo Platform also implements Dublin Core.

DCMI also maintains a list of projects using Dublin Core[22] on its website.

See also[edit]

Related software[edit]

  • Dublin Core Meta Toolkit (Conversion of Access, MySQL, or CSV data to DublinCore metadata)
  • Fedora repository architecture and Project (An open-source software system capable of implementing OAI-PMH (and thus Dublin Core).
  • Omeka, A free, open-source, unqualified Dublin-Core compliant web-publishing system for digital archives.
  • The Archivist's Toolkit is a self-described as an "Archival Data Management system" able to work with the Dublin Core format. It will soon be merged with Archon, which is ambiguous as to its OAI support.
  • ICA-AtoM, a web-based archival description/publication software that can serve as an OAI-PMH repository and uses OAI-PMH as the main language for remote data exchange

References[edit]

  1. ^ "DCMI Metadata Terms". Dublincore.org. Retrieved 5 April 2013. 
  2. ^ "DCMI Metadata Terms". Dublincore.org. Retrieved 5 April 2013. 
  3. ^ "DCMI Specifications". Dublincore.org. 14 December 2009. Retrieved 5 April 2013. 
  4. ^ a b c "Dublin Core Metadata Element Set, Version 1.1". Dublincore.org. Retrieved 5 April 2013. 
  5. ^ The Dublin Core Metadata Element Set, Dublin Core Metadata Initiative, August 2007
  6. ^ "ISO 15836:2009 - Information and documentation - The Dublin Core metadata element set". Iso.org. 18 February 2009. Retrieved 5 April 2013. 
  7. ^ "NISO Standards - National Information Standards Organization". Niso.org. 22 May 2007. Retrieved 5 April 2013. 
  8. ^ OCLC/NCSA Metadata Workshop
  9. ^ "DCMI Metadata Basics". http://dublincore.org/metadata-basics/. 
  10. ^ http://dublincore.org/
  11. ^ "OCLC Research and the Dublin Core Metadata Initiative". Retrieved 21 April 2010. 
  12. ^ http://dublincore.org/documents/dces/
  13. ^ http://dublincore.org/documents/dcmi-terms/
  14. ^ Dublin Core Metadata Element Set, version 1.1
  15. ^ a b Dublin Core Metadata Registry
  16. ^ "WebCite® archive form". WebCite. "Metadata (optional)         These are Dublin Core elements. [...]" 
  17. ^ http://dublincore.org/documents/2000/07/11/dcmes-qualifiers/
  18. ^ Dumb-Down Principle for qualifiers
  19. ^ dublincore.org/documents/dcmi-terms/
  20. ^ Dublin Core Abstract Model
  21. ^ "Open Packaging Format (OPF) 2.0.1 – 2.2: Publication Metadata". International Digital Publishing Forum. Retrieved 12 September 2013. 
  22. ^ "DCMI Projects - Alphabetical". DCMI. Retrieved 15 March 2013. 

Further reading[edit]

External links[edit]