Uniform Resource Name
From Wikipedia, the free encyclopedia
A Uniform Resource Name (URN) is a Uniform Resource Identifier (URI) that uses the urn scheme, and does not imply availability of the identified resource. Both URNs (names) and URLs (locators) are URIs, and a particular URI may be a name and a locator at the same time.
The Functional Requirements for Uniform Resource Names are described in RFC 1737. The URNs are part of a larger Internet information architecture which is composed of URNs, Uniform Resource Characteristics (URCs), and Uniform Resource Locators (URLs). Each plays a specific role:
- URNs are used for identification,
- URCs for including meta-information.
- URLs for locating or finding resources.
- URCs for including meta-information.
RFC 2141 says:
- Uniform Resource Names (URNs) are intended to serve as persistent, location-independent resource identifiers and are designed to make it easy to map other namespaces (that share the properties of URNs) into URN-space. Therefore, the URN syntax provides a means to encode character data in a form that can be sent in existing protocols, transcribed on most keyboards, etc.
Contents |
[edit] URN Syntax
RFC 2141 (dated May 1997 and still classified as needing requests discussion and suggestions for improvements) describe in BCNF the syntax of URNs as:
<URN> ::= "urn:" <NID> ":" <NSS>
where <NID> is the Namespace Identifier, and <NSS> is the Namespace Specific String. Phrases enclosed in quotes are REQUIRED. The leading "urn:" sequence is case-insensitive. The Namespace ID determines the syntactic interpretation of the Namespace Specific String.
[edit] Comparison with URLs
A URN is like a person's name, while a URL is like their street address. The URN defines something's identity, while the URL provides a method for finding something. Essentially, "what" vs. "where".
URNs are often compared to the ISBN system for uniquely identifying books (and in fact you can encode an ISBN as a URN). Having a book's unique identifier lets you discuss the book, such as whether you've read it, enjoyed it, etc. To actually read the book, however, you need its location (e.g. "on the bedside table"). So URNs and URLs are often complementary; for example, you might discuss an RFC using both concepts: "you can find urn:ietf:rfc:3187 (URN) over at http://www.faqs.org/rfcs/rfc3187.html (URL)."
[edit] Examples
[edit] See also
- DOI (digital object identifier)
- PURL
- XRI - Extensible Resource Identifier
- Internet Assigned Numbers Authority
- Life Science Identifiers
[edit] External links
- Uniform Resource Names Charter — The IETF's Uniform Resource Names working group
- IANA URN namespace assignmentsde:Uniform Resource Name
