Uniform Resource Name
URIs, URNs, and URLs
URNs were originally conceived to be part of a three-part information architecture for the Internet, along with Uniform Resource Locators (URLs) and Uniform Resource Characteristics (URCs), a metadata framework. As described in the 1994 RFC 1737,, and later in the 1997 RFC 2141 , URNs were distinguished from URLs, which identify resources by specifying their locations in the context of a particular access protocol, such as HTTP or FTP. In contrast, URNs were conceived as persistent, location-independent identifiers assigned within defined namespaces, typically by an authority responsible for the namespace, so that they are globally unique and persistent over long periods of time, even after the resource which they identify ceases to exist or becomes unavailable.
URCs never progressed past the conceptual stage, and other technologies such as the Resource Description Framework later took their place. Since RFC 3986 in 2005, use of the terms "Uniform Resource Name" and "Uniform Resource Locator" has been deprecated in technical standards in favor of the term Uniform Resource Identifier (URI), which encompasses both, a view proposed in 2001 by a joint working group between the World Wide Web Consortium (W3C) and Internet Engineering Task Force (IETF).
A URI is a string of characters used to identify a name or resource. URIs are used in many Internet protocols to refer to and access information resources. URI schemes include the familiar
http, as well as hundreds of others.
In the "contemporary view", as it is called, all URIs identify or name resources, perhaps uniquely and persistently, with some of them also being "locators" which are resolvable in conjunction with a specified protocol to a representation of the resources.
Other URIs are not locators and are not necessarily resolvable within the bounds of the systems where they are found. These URIs may serve as names or identifiers of resources. Since resources can move, opaque identifiers which are not locators and are not bound to particular locations are arguably more likely than identifiers which are locators to remain unique and persistent over time. But whether a URI is resolvable depends on many operational and practical details, irrespective of whether it is called a "name" or a "locator". In the contemporary view, there is no bright line between "names" and "locators".
In accord with this way of thinking, the distinction between Uniform Resource Names and Uniform Resource Locators is now no longer used in formal Internet Engineering Task Force technical standards, though the latter term, URL, is still in wide informal use.
The term "URN" continues now as one of more than a hundred URI "schemes",
ftp:, and so forth. URIs of the
urn: scheme are not locators, are not required to be associated with a particular protocol or access method, and need not be resolvable. They should be assigned by a procedure which provides some assurance that they will remain unique and identify the same resource persistently over a prolonged period. Some namespaces under the
urn: scheme, such as
urn:uuid: assign identifiers in a manner which does not require a registration authority, but most of them do. A typical URN namespace is
urn:isbn, for International Standard Book Numbers. This view is continued in the 2017 RFC 8141 .
namestring = assigned-name [ rq-components ] [ "#" f-component ] assigned-name = "urn" ":" NID ":" NSS NID = (alphanum) 0*30(ldh) (alphanum) ldh = alphanum / "-" NSS = pchar *(pchar / "/") rq-components = [ "?+" r-component ] [ "?=" q-component ] r-component = pchar *( pchar / "/" / "?" ) q-component = pchar *( pchar / "/" / "?" ) f-component = fragment
- The leading scheme (
urn:) is case-insensitive.
<NID>is the namespace identifier, and may include letters, digits, and
- The NID is followed by the namespace-specific string
<NSS>, the interpretation of which depends on the specified namespace. The NSS may contain ASCII letters and digits, and many punctuation and special characters. Disallowed ASCII and Unicode characters may be included if percent-encoded.
In 2017 the syntax for URNs was updated as follows:
- The slash character (
/) is now allowed in the NSS to represent names containing slashes from non-URN identifier systems.
- The q-component was added to enable passing of parameters to named resources.
- The r-component was added to enable passing of parameters to resolvers. However, the updated specification notes that the r-component should not be used until its semantics are defined via further standardization.
In order to ensure the global uniqueness of URN namespaces, their identifiers (NIDs) are required to be registered with the IANA. Registered namespaces may be "formal" or "informal". An exception to the registration requirement was formerly made for "experimental namespaces", since rescinded by RFC 8141.
Approximately sixty formal URN namespace identifiers have been registered. These are namespaces where Internet users are expected to benefit from their publication, and are subject to several restrictions. They must:
- Not be an already-registered NID
- Not start with
- Be more than two letters long
- Not start with
XY-, where XY is any combination of two ASCII letters
- Not start with
x-(see "Experimental namespaces", below)
Informal namespaces are registered with IANA and assigned a number sequence (chosen by IANA on a first-come-first-served basis) as an identifier, in the format
Informal namespaces are fully fledged URN namespaces and can be registered in global registration services.
An exception to the registration requirement was formerly made for "experimental namespaces". However, following the deprecation of the "X-" notation for new identifier names , RFC 8141  did away with experimental URN namespaces, indicating a preference for use of the
urn:example namespace where appropriate.
||The 1968 book The Last Unicorn, identified by its book number.|
||The 2002 film Spider-Man, identified by its audiovisual number.|
||The scientific journal Science of Computer Programming, identified by its serial number.|
||The IETF's RFC 2648.|
||The default namespace rules for MPEG-7 video metadata.|
||The OID for the United States.|
||A version 1 UUID.|
||A National Bibliography Number for a document, indicating country (
||A directive of the European Union, using the proposed Lex URN namespace.|
||A directive of the Life Science Identifiers may be resolved to http://zoobank.org/urn:lsid:zoobank.org:pub:CDC8D258-8F57-41DC-B560-247E17D3DC8C .|
- Archival Resource Key (ARK)
- .arpa – urn.arpa is for dynamic discovery
- Extensible resource identifier (XRI)
- Handle System
- Info URI scheme
- Life Science Identifiers (LSID)
- The Magnet URI scheme, which uses URNs
- Persistent Uniform Resource Locator (PURL)
- Tag URI scheme
- Digital Object Identifier (DOI)
- Sollins, Karen; Masinter, Larry (December 1994). "Request for Comments: 1737: Functional Requirements for Uniform Resource Names". IETF. Retrieved 2012-12-07.
- Moats, Ryan (May 1997). "Request for Comments: 2141: URN Syntax". IETF. Retrieved 2012-12-07.
- Daigle, Leslie L.; van Gulik, Dirk-Willem; Faltstrom, Patrik (October 2002). "Request for Comments: 3406: Uniform Resource Names (URN) Namespace Definition Mechanisms". IETF. Retrieved 2012-12-07.
- Berners-Lee, Tim; Fielding, Roy; Masinter, Larry (January 2005). "Request for Comments: 3986: Uniform Resource Identifier (URI): Generic Syntax". IETF. Retrieved 2012-12-07.
- Saint-Andre, Peter (April 2013). "Request for Comments: 6963: A Uniform Resource Name (URN) Namespace for Examples". IETF. Retrieved 2017-04-28.
- Saint-Andre, Peter; Klensin, John (April 2017). "Request for Comments: 8141: Uniform Resource Names (URNs)". IETF. Retrieved 2017-04-28.
- "Factsheet: DOI System and Internet Identifier Specifications". International DOI Foundation. October 2012. Retrieved 2012-12-06.
- W3C/IETF URI Planning Interest Group (21 September 2001). "URIs, URLs, and URNs: Clarifications and Recommendations 1.0". W3C. Retrieved 2012-12-07.