Dublin Core

Last updated
Logo image of DCMI, which formulates Dublin Core DCMI-logo.svg
Logo image of DCMI, which formulates Dublin Core

The Dublin Core Schema is a small set of vocabulary terms that can be used to describe digital 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 (DCMES), [4] is endorsed in the following standards documents:

Contents

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, [8] hosted by the OCLC (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". [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 the 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, 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. [12]

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. [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

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

  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 JTC1 SC36.

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

Encoding examples

<metaname="DC.Format"content="video/mpeg; 10 minutes"/>
<metaname="DC.Language"content="en"/>
<metaname="DC.Publisher"content="publisher-name"/>
<metaname="DC.Title"content="HYP"/>

Example of use [and mention] by WebCite

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

Qualified Dublin Core

(Superseded in 2008 by the DCMI Metadata Terms. [18] ) 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, [19] 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. [16]

DCMI Metadata Terms

The DCMI Metadata Terms lists the current set of the Dublin Core vocabulary. [13] 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[ clarification needed ] 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 [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 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. [21] 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. [22] 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. [23]

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

See also

Related Research Articles

XML Markup language developed by the W3C for encoding of data

Extensible Markup Language (XML) is a markup language that defines a set of rules for encoding documents in a format that is both human-readable and machine-readable. The World Wide Web Consortium's XML 1.0 Specification of 1998 and several other related specifications—all of them free open standards—define XML.

The Resource Description Framework (RDF) is a family of World Wide Web Consortium (W3C) specifications originally designed as a metadata data model. It has come to be used as a general method for conceptual description or modeling of information that is implemented in web resources, using a variety of syntax notations and data serialization formats. It is also used in knowledge management applications.

Geography Markup Language used to describe geographical features

The Geography Markup Language (GML) is the XML grammar defined by the Open Geospatial Consortium (OGC) to express geographical features. GML serves as a modeling language for geographic systems as well as an open interchange format for geographic transactions on the Internet. Key to GML's utility is its ability to integrate all forms of geographic information, including not only conventional "vector" or discrete objects, but coverages and sensor data.

MARCstandards are a set of digital formats for the description of items catalogued by libraries, such as books. Working with the Library of Congress, American computer scientist Henriette Avram developed MARC in the 1960s to create records that could be read by computers and shared among libraries. By 1971, MARC formats had become the US national standard for dissemination of bibliographic data. Two years later, they became the international standard. There are several versions of MARC in use around the world, the most predominant being MARC 21, created in 1999 as a result of the harmonization of U.S. and Canadian MARC formats, and UNIMARC. UNIMARC is maintained by the Permanent UNIMARC Committee of the International Federation of Library Associations and Institutions (IFLA), and is widely used in Europe. The MARC 21 family of standards now includes formats for authority records, holdings records, classification schedules, and community information, in addition to the format for bibliographic records.

The PBCore metadata standard was created by the public broadcasting community in the United States of America for use by public broadcasters and related communities that manage audiovisual assets, including libraries, archives, independent producers, etc. PBCore is organized as a set of specified fields that can be used in database applications, and it can be used as a data model for media cataloging and asset management systems. As an XML schema, PBCore enables data exchange between media collections, systems and organizations.

Learning object metadata Data model

Learning Object Metadata is a data model, usually encoded in XML, used to describe a learning object and similar digital resources used to support learning. The purpose of learning object metadata is to support the reusability of learning objects, to aid discoverability, and to facilitate their interoperability, usually in the context of online learning management systems (LMS).

RDF Schema is a set of classes with certain properties using the RDF extensible knowledge representation data model, providing basic elements for the description of ontologies, otherwise called RDF vocabularies, intended to structure RDF resources. These resources can be saved in a triplestore to reach them with the query language SPARQL.

Extensible Metadata Platform ISO standard

The Extensible Metadata Platform (XMP) is an ISO standard, originally created by Adobe Systems Inc., for the creation, processing and interchange of standardized and custom metadata for digital documents and data sets.

The e-Government Metadata Standard, e-GMS, is the UK e-Government Metadata Standard. It defines how UK public sector bodies should label content such as web pages and documents to make such information more easily managed, found and shared.

RDFa is a W3C Recommendation that adds a set of attribute-level extensions to HTML, XHTML and various XML-based document types for embedding rich metadata within Web documents. The RDF data-model mapping enables its use for embedding RDF subject-predicate-object expressions within XHTML documents. It also enables the extraction of RDF model triples by compliant user agents.

Simple Knowledge Organization System (SKOS) is a W3C recommendation designed for representation of thesauri, classification schemes, taxonomies, subject-heading systems, or any other type of structured controlled vocabulary. SKOS is part of the Semantic Web family of standards built upon RDF and RDFS, and its main objective is to enable easy publication and use of such vocabularies as linked data.

The AgMES initiative was developed by the Food and Agriculture Organization (FAO) of the United Nations and aims to encompass issues of semantic standards in the domain of agriculture with respect to description, resource discovery, interoperability and data exchange for different types of information resources.

Agricultural Information Management Standards, abbreviated to AIMS is a space for accessing and discussing agricultural information management standards, tools and methodologies connecting information workers worldwide to build a global community of practice. Information management standards, tools and good practices can be found on AIMS:

A schema crosswalk is a table that shows equivalent elements in more than one database schema. It maps the elements in one schema to the equivalent elements in another schema.

Metadata Data about data

Metadata is "data that provides information about other data". In other words, it is "data about data." Many distinct types of metadata exist, including descriptive metadata, structural metadata, administrative metadata, reference metadata and statistical metadata.

A metadata standard is a requirement which is intended to establish a common understanding of the meaning or semantics of the data, to ensure correct and proper use and interpretation of the data by its owners and users. To achieve this common understanding, a number of characteristics, or attributes of the data have to be defined, also known as metadata.

The Office Open XML file formats are a set of file formats that can be used to represent electronic office documents. There are formats for word processing documents, spreadsheets and presentations as well as specific formats for material such as mathematical formulae, graphics, bibliographies etc.

The Publishing Requirements for Industry Standard Metadata (PRISM) specification defines a set of XML metadata vocabularies for syndicating, aggregating, post-processing and multi-purposing content. PRISM provides a framework for the interchange and preservation of content and metadata, a collection of elements to describe that content, and a set of controlled vocabularies listing the values for those elements. PRISM can be XML, RDF/XML, or XMP and incorporates Dublin Core elements. PRISM can be thought of as a set of XML tags used to contain the metadata of articles and even tag article content.

ISO/IEC 19788Information technology – Learning, education and training – Metadata for learning resources is a multi-part standard prepared by subcommittee SC36 of the Joint Technical Committee ISO/IEC JTC1, Information Technology for Learning, Education and Training. This committee was created to deal with the consequences of substantial overlap in areas of standardization done at the International Organization for Standardization (ISO) and the International Electrotechnical Commission.

Asset Description Metadata Schema

The Asset Description Metadata Schema (ADMS) is a common metadata vocabulary to describe standards, so-called interoperability assets, on the Web.

References

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

Further reading