Home> Documents > DCLOMidentifiers >

IMPORTANT: The guidelines presented in this document do not reflect concensus within the elearning and IEEE LOM community. Therefore a revised version of this document is available that only provides guidance for using resource identifiers in Dublin Core metadata.

Guidelines for using resource identifiers in Dublin Core metadata and IEEE LOM

1. Introduction

This document provides guidelines for using a number of widely adopted identification systems in Dublin Core (DC) metadata [DCMI] and IEEE Learning Object Metadata (LOM) [LOM].

2. Definitions

In the Dublin Core Metadata Element Set defintion [DCMES], the Dublin Core Metadata Initiative (DCMI) defines an identifier as:

An unambiguous reference to [a] resource within a given context.

and goes on to note that:

Recommended best practice is to identify the resource by means of a string or number conforming to a formal identification system. Example formal identification systems include the Uniform Resource Identifier (URI) (including the Uniform Resource Locator (URL)), the Digital Object Identifier (DOI) and the International Standard Book Number (ISBN).

In DC metadata, identifiers are typically used with the Identifier, Source and Relation elements, though they may also be used elsewhere, for example with the Rights element as a reference to a service providing a rights statement.

The IEEE LOM standard defines an identifier as:

A globally unique label that identifies [a] learning object.

Within LOM, identifiers are used as values for the 1.1:General.Identifier, 3.1:Meta-Metadata.Identifier and 7.2.1:Relation.Resource.Identifier data elements. The LOM data model associates two data elements with each of these, called 'Catalog' and 'Entry'. These are defined as:

The name or designator of the identification or cataloguing scheme for this entry. A namespace scheme.

and

The value of the identifier within the identification or cataloguing scheme that designates or identifies this learning object. A namespace specific string.

respectively. For example 1.1.1:General.Identifier.Catalog and 1.1.2:General.Identifier.Entry.

The Uniform Resource Identifier (URI): Generic Syntax Internet-Draft [URI] defines an identifier as:

An identifier embodies the information required to distinguish what is being identified from all other things within its scope of identification.

URIs are a fundamental building block of the semantic Web [SW], the Resource Description Framework [RDF] and the Dublin Core Abstract Model [DCAM]. The Architecture of the World Wide Web [WEBARCH] contains the following principle:

To benefit from and increase the value of the World Wide Web, agents should provide URIs as identifiers for resources.

3. General guidelines

All formal identifiers used in DC metadata and LOM should be URIs. The phrase 'formal identifier' is used here to mean an identifier that conforms to a widely recognised identifier scheme. URIs provide a simple, extensible and widely deployed mechanism for identifying resources that supports the use (through mapping) of existing identification schemes including the common Uniform Resource Locator (URL) [URI-CLARIFICATION]. In DC metadata (with the exception of simple DC), the 'URI' encoding scheme should be indicated if appropriate, in accordance with the DCMI encoding guidelines [DCMI-ENCODINGS]. In LOM, the 'catalog' should be set to 'URI'. For example:

<meta name="DC.identifier" scheme="DCTERMS.URI" content="http://www.ukoln.ac.uk/" />
<link rel="DC.relation" href="http://www.bath.ac.uk/" />
...

<metadata ...>
  <dc:identifier xsi:type="dcterms:URI">http://www.ukoln.ac.uk/</dc:identifier>
  <dc:relation xsi:type="dcterms:URI">http://www.bath.ac.uk/</dc:relation>
  ...
</metadata>

<rdf:RDF ...>
  <rdf:Description rdf:about="http://www.ukoln.ac.uk/">
    <dc:relation rdf:resource="http://www.bath.ac.uk/" />
    ...
  </rdf:Description>
</rdf:RDF>

<lom ...>
  <general>
    <identifier>
      <catalog>URI</catalog> 
      <entry>http://www.ukoln.ac.uk/</entry> 
    </identifier>
    ...
  </general>
  ...
  <relation>
    <resource>
      <identifier>
        <catalog>URI</catalog> 
        <entry>http://www.bath.ac.uk/</entry> 
      </identifier>
    </resource>
  </relation>
  ...
</lom>

Recommended best practice is to use URIs that conform to a registered URI scheme, since this helps to ensure that the URIs are unique. A list of registered URI schemes is maintained by IANA [URI-SCHEMES].

A URL is simply a type of URI that identifies a resource via a representation of its primary access mechanism (e.g., its network "location"), rather than by some other attributes it may have. Thus, an 'http' URL is a URI (or to put it another way, 'http' is a URI scheme).

A Uniform Resource Name (URN) is a URI that uses the 'urn' URI scheme and that is intended to 'name' a resource in a persistent way. The URN defines sub-spaces, called 'namespaces', which are assigned namespace identifiers. Thus, 'ISBN' is a URN namespace identifier (see below):

<link rel="DC.source" href="urn:ISBN:1-56592-149-6" />

<lom ...>
  ...
  <relation>
    <kind>isBasedOn</kind>
    <resource>
      <identifier>
        <catalog>URI</catalog> 
        <entry>urn:ISBN:1-56592-149-6</entry>
      </identifier>
    </resource>
  </relation>
  ...
</lom>

A list of registered URN namespace identifiers is maintained by IANA [URN-NIDS].

The 'info' URI scheme [INFO-URI] [INFO-REG] has been developed from within the library and publishing communities to expedite the referencing by URIs of information assets that have identifiers in public namespaces but have no representation within the URI allocation. However, at the time of writing, the 'info' URI scheme had not been registered with IANA.

4. Specific identifier scheme guidelines

The following sections show how identifiers from specific identification systems can be used. Two examples of each are shown, using the DC/XHTML encoding and the LOM/XML encoding.

These guidelines are based on the following decision tree:

1. If the identifier is an 'http' URI, use it as is
2. else, if the identifier is, or can be mapped to, a URI using a registered URI scheme, use that
3. else, if the identifier is, or can be mapped to, a URI using a registered URN namespace, use that
4. else, if the identifier is, or can be mapped to, an unregistered URI scheme or an unregistered URN namespace use that.

4.1 ARK

The ARK (Archival Resource Key) naming scheme is designed to facilitate the high-quality and persistent identification of information objects [ARK]. An ARK is a special kind of URL that connects users to three things: the named object, its metadata, and the provider's promise about its persistence. An ARK has five components: an optional and mutable Name Mapping Authority Hostport, the "ark:" label, the Name Assigning Authority Number (NAAN), the assigned Name, and an optional and possibly mutable Qualifier supported by the NMA.

Map ARKs to 'http' URIs, using the Name Mapping Authority Hostport component. For example:

<meta name="DC.identifier" scheme="DCTERMS.URI"
      content="http://loc.gov/ark:/12025/654xz321" />

<identifier>
  <catalog>URI</catalog> 
  <entry>http://loc.gov/ark:/12025/654xz321</entry> 
</identifier>

4.2 DOI

The Digital Object Identifier [DOI] is a persistent identifier of intellectual property entities. DOIs are most commonly mapped to 'http' URIs using the http://dx.doi.org/ prefix or to URIs using the 'doi' URI scheme [DOI-HANDBOOK]. For example:

http://dx.doi.org/10.1000/182
doi:10.1000/182

However, they may also be mapped to 'info' URIs [INFO-URI] [INFO-REG]. For example:

info:doi/10.1000/182

Note: at the time of writing, the 'doi' and 'info' URI schemes had not been registered with IANA.

For example:

<meta name="DC.identifier" scheme="DCTERMS.URI" content="http://dx.doi.org/10.1000/182" />

<identifier>
  <catalog>URI</catalog> 
  <entry>http://dx.doi.org/10.1000/182</entry> 
</identifier>

Note: software applications that consume metadata should accept and understand the other forms of DOIs shown above.

4.3 Handle

The Handle System [HANDLE] is a comprehensive system for assigning, managing, and resolving persistent identifiers, known as "handles," for digital objects and other resources on the Internet. Handles are most commonly mapped to 'http' URIs using the http://hdl.handle.net/ prefix or to URIs using the 'hdl' URI scheme. For example:

http://hdl.handle.net/4263537/4069
hdl:4263537/4069

Note: at the time of writing, the 'hdl' URI scheme had not been registered with IANA.

For example:

<meta name="DC.identifier" scheme="DCTERMS.URI" content="http://hdl.handle.net/4263537/4069" />

<identifier>
  <catalog>URI</catalog> 
  <entry>http://hdl.handle.net/4263537/4069</entry> 
</identifier>

Note: software applications that consume metadata should accept and understand the 'hdl' URI form of Handles shown above.

4.4 ISBN

An International Standard Book Number (ISBN) identifies an edition of a monographic work and is defined by the standard NISO/ANSI/ISO 2108:1992. RFC-3187 [RFC3187] defines the mechanism for mapping an ISBN to a URN.

Map ISBNs to URNs, using the 'ISBN' URN namespace identifier. For example:

<meta name="DC.identifier" scheme="DCTERMS.URI" content="urn:ISBN:1-56592-149-6" />

<identifier>
  <catalog>URI</catalog> 
  <entry>urn:ISBN:1-56592-149-6</entry> 
</identifier>

Note that the hyphens in the ISBN are optional (and should be removed before comparing two ISBN URNs) and that the 'ISBN' URN namespace identifier is case-insensitive.

4.5 ISSN

The International Standard Serial Number (ISSN) is an eight-digit number which identifies periodical publications, including electronic serials [ISSN]. RFC-3044 [RFC3044] defines the mechanism for mapping an ISSN to a URN.

Map ISSNs to URNs, using the 'ISSN' URN namespace identifier. For example:

<meta name="DC.identifier" scheme="DCTERMS.URI" content="urn:ISSN:1361-3200" />

<identifier>
  <catalog>URI</catalog> 
  <entry>urn:ISSN:1361-3200</entry> 
</identifier>

Note that the hyphens in the ISSN are optional (and should be removed before comparing two ISSN URNs) and that the 'ISSN' URN namespace identifier is case-insensitive.

4.6 PURL

A PURL is a Persistent Uniform Resource Locator [PURL]. Functionally, a PURL is a URL. However, instead of pointing directly to the location of an Internet resource, a PURL points to an intermediate resolution service. Because PURLs conform to the URI specification, they can be used unmodified in DC metadata and LOM. For example:

<meta name="DC.identifier" scheme="DCTERMS.URI"
      content="http://purl.org/net/ukoln" />

<identifier>
  <catalog>URI</catalog> 
  <entry>http://purl.org/net/ukoln</entry> 
</identifier>

4.6.1 POI

The PURL-based Object Identifier (POI) provides a simple specification for resource identifiers based on the PURL system [POI]. Because POIs conform to the URI specification, they can be used unmodified in DC metadata and LOM. For example:

<meta name="DC.identifier" scheme="DCTERMS.URI"
      content="http://purl.org/poi/xtcat.oclc.org/OCLCNo/ocm41020136" />

<identifier>
  <catalog>URI</catalog> 
  <entry>http://purl.org/poi/xtcat.oclc.org/OCLCNo/ocm41020136</entry> 
</identifier>

4.7 SICI

The Serial Item and Contribution Identifier (SICI) standard defines a variable length code that provides unique identification of serial items (e.g., issues) and the contributions (e.g., articles) contained in a serial title. SICI is specified in NISO/ANSI Z39.56-1996. The 'info' URI Scheme Internet-Draft [INFO-URI] provides a mechanism for mapping a SICI to an 'info' URI.

Note: at the time of writing, the 'info' URI scheme had not been registered with IANA.

Map SICIs to 'info' URIs. For example:

<meta name="DC.identifier" scheme="DCTERMS.URI"
      content="info:sici/1046-8188(199501)13:1%3C69:FTTHBI%3E2.0.TX;2-4" />

<identifier>
  <catalog>URI</catalog> 
  <entry>info:sici/1046-8188(199501)13:1%3C69:FTTHBI%3E2.0.TX;2-4</entry> 
</identifier>

References

[DCMI] Dublin Core Metadata Initiative
http://dublincore.org/

[LOM] IEEE Learning Object Metadata
http://ltsc.ieee.org/wg12/

[DCMES] Dublin Core Metadata Element Set, Version 1.1: Reference Description
http://dublincore.org/documents/dces/

[DCQ] Dublin Core Qualifiers
http://dublincore.org/documents/dcmes-qualifiers/

[URI] Uniform Resource Identifiers (URI): Generic Syntax
http://www.ietf.org/rfc/rfc3986.txt

[SW] Semantic Web
http://www.w3.org/2001/sw/

[RDF] Resource Description Framework
http://www.w3.org/RDF/

[DCAM] Dublin Core Abstract Model
http://dublincore.org/documents/abstract-model/

[WEBARCH] Architecture of the World Wide Web, First Edition
http://www.w3.org/TR/webarch/

[URI-CLARIFICATION] URIs, URLs, and URNs: Clarifications and Recommendations 1.0
http://www.w3.org/TR/uri-clarification/

[DCMI-ENCODINGS] DCMI Encoding Guidelines
http://dublincore.org/resources/expressions/

[DC/XHTML-ENCODING] Expressing Dublin Core in HTML/XHTML meta and link elements
http://dublincore.org/documents/dcq-html/

[DC/XML-ENCODING] Guidelines for implementing Dublin Core in XML
http://dublincore.org/documents/dc-xml-guidelines/

[DC/RDF-ENCODING] Expressing Simple Dublin Core in RDF/XML
http://dublincore.org/documents/dcmes-xml/

[LOM/XML-ENCODING] LOM XML Schema definitions
http://ltsc.ieee.org/xsd/lomv1.0/

[URI-SCHEMES] Uniform Resource Identifier (URI) SCHEMES
http://www.iana.org/assignments/uri-schemes

[URN-NIDS] URN Namespaces
http://www.iana.org/assignments/urn-namespaces

[ARK] The ARK Persistent Identifier Scheme
http://www.ietf.org/internet-drafts/draft-kunze-ark-09.txt

[DOI] The Digital Object Identifier System
http://www.doi.org/

[DOI-HANDBOOK] DOI Handbook
http://www.doi.org/hb.html

[INFO-URI] The "info" URI Scheme for Information Assets with Identifiers in Public Namespaces
http://info-uri.info/registry/drafts.html

[INFO-REG] "info" URI scheme registry
http://info-uri.info/registry/

[HANDLE] The Handle System
http://www.handle.net/>

[RFC3187] RFC-3187: Using International Standard Book Numbers as Uniform Resource Names
http://www.ietf.org/rfc/rfc3187.txt

[ISSN] International Standard Serial Number
http://www.issn.org/

[RFC3044] RFC-3044: Using The ISSN (International Serial Standard Number) as URN (Uniform Resource Names) within an ISSN-URN Namespace
http://www.ietf.org/rfc/rfc3044.txt

[PURL] Persistent Uniform Resource Locator
http://purl.org/

[POI] The PURL-based Object Identifier (POI)
http://www.ukoln.ac.uk/distributed-systems/poi/