> ResourceIdentifierGuidelines

The following 468 words could not be found in the dictionary of 550 words (including 550 LocalSpellingWords) and are highlighted below:

654xz321   about   above   Abstract   abstract   ac   accept   access   accordance   adopted   agents   all   All   allocation   also   an   An   and   Andy   another   applicable   applications   appropriate   Architecture   architecturewiki   Archival   are   ark   articles   as   Assets   assets   assigned   Assigning   assigning   assignments   at   attributes   Authority   Barker   based   bath   be   Because   been   before   being   below   benefit   best   block   Book   building   but   By   by   C3044   C3187   C69   called   Campbell   can   case   cases   citable   cite   clarification   Clarifications   code   collaborating   common   commonly   communities   comparing   component   components   comprehensive   conform   conforming   conforms   connects   consume   contained   contains   content   context   Contribution   contributions   copies   Core   creation   Creator   Date   dc   dces   dcmes   dcmi   dcq   dcterms   decision   defined   defines   Definitions   defintion   deployed   Description   descriptions   designed   developed   digit   Digital   digital   directly   distinguish   distributed   Do   Document   document   documents   doi   draft   Draft   drafts   Dublin   dublincore   dx   E2   each   Edition   edition   Eduserv   eight   electronic   element   Element   elements   else   elsewhere   embodies   encoding   Encoding   ensure   entities   example   Example   exception   existing   expedite   Expressing   expressions   extensible   facilitate   ffffcc   Finished   First   five   following   For   for   form   formal   forms   Foundation   Framework   from   Functionally   fundamental   General   Generic   given   goes   gov   guidelines   Guidelines   had   Handbook   handle   Handle   handles   Handles   has   have   hb   hdl   helps   here   high   Hostport   how   However   href   hyphens   iana   identification   identified   identifier   Identifier   Identifiers   identifiers   identifies   identify   identifying   ietf   if   If   implementing   in   In   include   including   increase   indicated   information   Information   Initiative   insensitive   instead   intellectual   intended   intermediate   International   Introduction   is   Is   issn   Issued   issues   it   Item   items   its   Johnston   Key   kind   known   Ks   kunze   label   Latest   length   library   link   list   loc   location   Locator   Lorna   Ls   maintained   managing   Map   mapped   mapping   Mapping   materials   mean   means   mechanism   meta   Metadata   metadata   Model   model   monographic   most   mutable   name   Name   named   Names   namespace   Namespace   namespaces   Namespaces   naming   net   network   No   no   Not   not   Note   note   Ns   number   Number   Numbers   Object   object   objects   oclc   ocm41020136   of   on   optional   or   other   part   periodical   persistence   Persistent   persistent   Pete   Phil   phrase   poi   pointing   points   possibly   Powell   practice   prefix   primary   principle   promise   property   provide   provider   provides   providing   Public   public   publications   published   publishing   purl   purposes   put   Qualifier   qualifiers   Qualifiers   quality   rather   rdf   recognised   Recommendations   Recommended   Reference   reference   References   referencing   registered   registry   rel   Relation   relation   removed   Replaced   Replaces   representation   required   resolution   resolving   resource   Resource   resources   rfc   rfc3044   rfc3187   rfc3986   rights   Rights   Scheme   scheme   schemes   scope   sections   see   Self   semantic   Semantic   Serial   serial   serials   service   Set   should   show   shown   sici   Simple   simple   simply   since   site   software   some   Source   source   spaces   special   Specific   specific   specification   specified   Standard   standard   statement   Status   string   sub   supported   supports   sw   Syntax   system   System   systems   tablebgcolor   tablewidth   than   that   The   the   These   they   things   this   This   though   three   through   Thus   time   title   to   To   tree   two   type   typically   uk   ukoln   unambiguous   understand   Uniform   unique   unmodified   unregistered   uri   urn   use   used   users   uses   Using   using   value   variable   Version   via   w3   way   Web   webarch   what   which   Wide   widely   will   with   within   work   World   writing   xsi   xtcat   Z39  

Clear message

Guidelines for using resource identifiers in Dublin Core metadata

This document is part of the [Self]DC Architecture Wiki.

IMPORTANT: Do not cite materials in this Wiki other than for the purposes of collaborating on document creation. This Wiki is intended to be used to work on draft copies of documents. Finished documents will be published, in a persistent and citable form, on the dublincore.org Web site (or elsewhere in some cases).

Creator: Andy Powell, Eduserv Foundation
Creator: Pete Johnston, Eduserv Foundation
Creator: Lorna Campbell, CETIS
Creator: Phil Barker, CETIS
Date Issued: 2006-06-21
Identifier: http://dublincore.org/architecturewiki/ResourceIdentifierGuidelines
Replaces: http://www.ukoln.ac.uk/metadata/dcmi/identifiers/
Is Replaced By: Not applicable
Latest Version:
Status of Document: DRAFT DCMI Recommended Resource
Description of Document: This document provides guidelines for using a number of widely adopted identification systems in Dublin Core (DC) metadata descriptions.

1. Introduction

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

2. Definitions

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

and goes on to note that:

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 Uniform Resource Identifier (URI): Generic Syntax Internet-Draft [URI] defines an identifier as:

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:

3. General guidelines

All formal identifiers used in DC metadata 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]. For example: [DC/XHTML-ENCODING] 

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

[DC/XML-ENCODING] 

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

[DC/RDF-ENCODING] 

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

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

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. An example of each is shown, using the DC/XHTML 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: 

<link rel="DC.relation"
      href="http://loc.gov/ark:/12025/654xz321" />

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: 

<link rel="DC.relation" href="http://dx.doi.org/10.1000/182" />

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: 

<link rel="DC.relation" href="http://hdl.handle.net/4263537/4069" />

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: 

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

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: 

<link rel="DC.relation" href="urn:ISSN:1361-3200" />

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. For example: 

<link rel="DC.relation"
      href="http://purl.org/net/ukoln" />
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. For example: 

<link rel="DC.relation"
      content="http://purl.org/poi/xtcat.oclc.org/OCLCNo/ocm41020136" />

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: 

<link rel="DC.relation"
      href="info:sici/1046-8188(199501)13:1%3C69:FTTHBI%3E2.0.TX;2-4" />

References

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

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

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