Logo image of DCMI, which formulates Dublin Core

The Dublin Core, also known as the Dublin Core Metadata Element Set (DCMES), is a set of fifteen main metadata items for describing digital or physical resources. The Dublin Core Metadata Initiative (DCMI) is responsible for formulating the Dublin Core; DCMI is a project of the Association for Information Science and Technology (ASIS&T), a non-profit organization.

Dublin Core has been formally standardized internationally as ISO 15836 by the International Organization for Standardization (ISO)[1] and as IETF RFC 5013 by the Internet Engineering Task Force (IETF),[2] as well as in the U.S. as ANSI/NISO Z39.85 by the National Information Standards Organization (NISO).[3]

The core properties are part of a larger set of DCMI Metadata Terms. "Dublin Core" is also used as an adjective for Dublin Core metadata, a style of metadata that draws on multiple Resource Description Framework (RDF) vocabularies, packaged and constrained in Dublin Core application profiles.[4]

The resources described using the Dublin Core may be digital resources (video, images, web pages, etc.) as well as physical resources such as books or works of art. 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

"Dublin" refers to Dublin, Ohio, USA where the schema originated during the 1995 invitational OCLC/NCSA Metadata Workshop,[5] hosted by the OCLC (known at that time as Online Computer Library Center), 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".[6] 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.

In 1999, the first Dublin Core encoding standard was expressed in terms of HTML 'meta' tagging.[7] 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 the most popular vocabularies for use with RDF, more recently in the context of the linked data movement.[8]

The Dublin Core Metadata Initiative (DCMI)[9] 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.[10]

Currently, any and all changes that are made to the Dublin Core standard, are 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.[11]

Levels of the standard

The Dublin Core standard originally included 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 RDF data model.[12] 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/.[13]

Dublin Core Metadata Element Set

The original DCMES Version 1.1 consists of 15 metadata elements, defined this way in the original specification:[6][14]

  1. Contributor – "An entity responsible for making contributions to the resource".
  2. Coverage – "The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant".
  3. Creator – "An entity primarily responsible for making the resource".
  4. Date – "A point or period of time associated with an event in the lifecycle of the resource".
  5. Description – "An account of the resource".
  6. Format – "The file format, physical medium, or dimensions of the resource".
  7. Identifier – "An unambiguous reference to the resource within a given context".
  8. Language – "A language of the resource".
  9. Publisher – "An entity responsible for making the resource available".
  10. Relation – "A related resource".
  11. Rights – "Information about rights held in and over the resource".
  12. Source – "A related resource from which the described resource is derived".
  13. Subject – "The topic of the resource".
  14. Title – "A name given to the resource".
  15. Type – "The nature or genre of the resource".

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 a NISO standards, Z39.85, and IETF RFC 5013 in 2007, ISO 15836 standard in 2009 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 JTC 1/SC 36.

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

Encoding examples

<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" />

Example of use [and mention] by WebCite

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

Qualified Dublin Core

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

Element 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 a 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

The DCMI Metadata Terms lists the current set of the Dublin Core vocabulary.[12] This set includes the fifteen terms of the DCMES (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

Syntax choices for metadata expressed with the Dublin Core elements depend on context. Dublin Core concepts and semantics are designed to be syntax independent and apply to a variety of contexts, as long as the metadata is in a form suitable for interpretation by both machines and people.

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

Notable applications

One Document Type Definition based on Dublin Core is the Open Source Metadata Framework (OMF) specification.[20] 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.[21] The Zope CMF's Metadata products, used by the Plone, ERP5, the Nuxeo CPS Content management systems, SimpleDL, and Fedora Commons also implement Dublin Core. The EPUB e-book format uses Dublin Core metadata in the OPF file.[22]

The Australian Government Locator Service (AGLS) metadata standard is an application profile of Dublin Core.[23]: 5 

See also

References

  1. ↑ "ISO 15836-1:2017 – Information and documentation – The Dublin Core metadata element set – Part 1: Core elements". International Organization for Standardization. May 2017. Retrieved 2 October 2018.
  2. ↑ The Dublin Core Metadata Element Set, Dublin Core Metadata Initiative, August 2007
  3. ↑ "NISO Standards – National Information Standards Organization". Niso.org. 22 May 2007. Archived from the original on 16 November 2011. Retrieved 5 April 2013.
  4. ↑ "Dublin Core". Dublin Core Metadata Initiative. 22 December 2011.
  5. ↑ "DCMI: The OCLC/NCSA Metadata Workshop: The Essential Elements of Network Object Description". dublincore.org. March 1995. Retrieved 13 October 2019.
  6. 1 2 "Dublin Core Metadata Element Set, Version 1.1". dublincore.org. Retrieved 11 November 2017.
  7. ↑ Kunze, John A. (December 1999). "Encoding Dublin Core Metadata in HTML". IETF.org. Retrieved 17 June 2021.
  8. ↑ "Metadata Basics". DCMI. 15 December 2018. Retrieved 19 February 2019.
  9. ↑ "DCMI Home: Dublin Core® Metadata Initiative (DCMI)". Dublincore.org. Retrieved 4 December 2015.
  10. ↑ "OCLC Research and the Dublin Core Metadata Initiative". Retrieved 21 April 2010.
  11. ↑ "Dublin Core Metadata Element Set, Version 1.1". Dublincore.org. Retrieved 4 December 2015.
  12. 1 2 "DCMI Metadata Terms". Dublincore.org. Retrieved 4 December 2015.
  13. ↑ "DCMI: Dublin Core Metadata Element Set, Version 1.1: Reference Description". dublincore.org. Retrieved 3 April 2018.
  14. ↑ Section 3: Properties of DCMI Metadata Terms at dublincore.org
  15. 1 2 "Dublin Core Metadata Registry". Archived from the original on 7 May 2017. Retrieved 18 March 2008.
  16. ↑ "WebCite archive form". WebCite. These are Dublin Core elements. Entering these will help you to correctly cite the URL. [...]
  17. ↑ "Dublin Core Qualifiers". Dublincore.org. Retrieved 27 May 2017.
  18. ↑ "DCMI: DCMI Grammatical Principles". dublincore.org. Retrieved 3 April 2018.
  19. ↑ "DCMI: DCMI Abstract Model". dublincore.org. Retrieved 3 April 2018.
  20. ↑ "m e t a l a b open source metadata framework". ibiblio.org. Retrieved 3 April 2018.
  21. ↑ "PBCore Schema – PBCore". pbcore.org. Retrieved 19 January 2018. PBCore is built on the foundation of the Dublin Core (ISO 15836), an international standard for resource discovery.
  22. ↑ "Open Packaging Format (OPF) § Publication Metadata". International Digital Publishing Forum. Retrieved 11 November 2017.
  23. ↑ "AGLS Metadata Standard Part 1 – Reference Description" (PDF). National Archives of Australia. 30 June 2010. Retrieved 28 November 2019.
  24. ↑ "ADMS-AP for Joinup version 2.0". Joinup. December 2015.

Further reading

Wikiversity has learning resources about Digital Libraries/Metadata
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.