|Domain||World Wide Web|
A Uniform Resource Identifier (URI) is a string of characters that unambiguously identifies a particular resource. To guarantee uniformity, all URIs follow a predefined set of syntax rules, but also maintain extensibility through a separately defined hierarchical naming scheme (e.g.
Such identification enables interaction with representations of the resource over a network, typically the World Wide Web, using specific protocols. Schemes specifying a concrete syntax and associated protocols define each URI. The most common form of URI is the Uniform Resource Locator (URL), frequently referred to informally as a web address. More rarely seen in usage is the Uniform Resource Name (URN), which was designed to complement URLs by providing a mechanism for the identification of resources in particular namespaces.
URLs and URNs
A Uniform Resource Name (URN) is a URI that identifies a resource by name in a particular namespace. A URN may be used to talk about a resource without implying its location or how to access it. For example, in the International Standard Book Number (ISBN) system, ISBN 0-486-27557-4 identifies a specific edition of Shakespeare's play Romeo and Juliet. The URN for that edition would be urn:isbn:0-486-27557-4. However, it gives no information as to where to find a copy of that book.
A Uniform Resource Locator (URL) is a URI that specifies the means of acting upon or obtaining the representation of a resource, i.e. specifying both its primary access mechanism and network location. For example, the URL
http://example.org/wiki/Main_Page refers to a resource identified as
/wiki/Main_Page, whose representation, in the form of HTML and related code, is obtainable via the Hypertext Transfer Protocol (http:) from a network host whose domain name is
A URN may be compared to a person's name, while a URL may be compared to their street address. In other words, a URN identifies an item and a URL provides a method for finding it.
Technical publications, especially standards produced by the IETF and by the W3C, normally reflect a view outlined in a W3C Recommendation of 2001, which acknowledges the precedence of the term URI rather than endorsing any formal subdivision into URL and URN.
URL is a useful but informal concept: a URL is 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.
As such, a URL is simply a URI that happens to point to a resource over a network.[a] However, in non-technical contexts and in software for the World Wide Web, the term "URL" remains widely used. Additionally, the term "web address" (which has no formal definition) often occurs in non-technical publications as a synonym for a URI that uses the http or https schemes. Such assumptions can lead to confusion, for example, in the case of XML namespaces that have a visual similarity to resolvable URIs.
Standardize on the term URL. URI and IRI [Internationalized Resource Identifier] are just confusing. In practice a single algorithm is used for both so keeping them distinct is not helping anyone. URL also easily wins the search result popularity contest.
While most URI schemes were originally designed to be used with a particular protocol, and often have the same name, they are semantically different from protocols. For example, the scheme http is generally used for interacting with web resources using HTTP, but the scheme file has no protocol.
Each URI begins with a scheme name that refers to a specification for assigning identifiers within that scheme. As such, the URI syntax is a federated and extensible naming system wherein each scheme's specification may further restrict the syntax and semantics of identifiers using that scheme. The URI generic syntax is a superset of the syntax of all URI schemes. It was first defined in RFC 2396, published in August 1998, and finalized in RFC 3986, published in January 2005.
The URI generic syntax consists of a hierarchical sequence of five components:
URI = scheme:[//authority]path[?query][#fragment]
where the authority component divides into three subcomponents:
authority = [[email protected]]host[:port]
This is represented in a syntax diagram as:
The URI comprises:
- A non-empty scheme component followed by a colon (
:), consisting of a sequence of characters beginning with a letter and followed by any combination of letters, digits, plus (
+), period (
.), or hyphen (
-). Although schemes are case-insensitive, the canonical form is lowercase and documents that specify schemes must do so with lowercase letters. Examples of popular schemes include
irc. URI schemes should be registered with the Internet Assigned Numbers Authority (IANA), although non-registered schemes are used in practice.[b]
- An optional
component preceded by two slashes (
- An optional userinfo subcomponent that may consist of a user name and an optional password preceded by a colon (
:), followed by an at symbol (
@). Use of the format
username:passwordin the userinfo subcomponent is deprecated for security reasons. Applications should not render as clear text any data after the first colon (
:) found within a userinfo subcomponent unless the data after the colon is the empty string (indicating no password).
- A host subcomponent, consisting of either a registered name (including but not limited to a hostname), or an IP address. IPv4 addresses must be in dot-decimal notation, and IPv6 addresses must be enclosed in brackets (
- An optional port subcomponent preceded by a colon (
- An optional userinfo subcomponent that may consist of a user name and an optional password preceded by a colon (
- A path component, consisting of a sequence of path segments separated by a slash (
/). A path is always defined for a URI, though the defined path may be empty (zero length). A segment may also be empty, resulting in two consecutive slashes (
//) in the path component. A path component may resemble or map exactly to a file system path, but does not always imply a relation to one. If an authority component is present, then the path component must either be empty or begin with a slash (
/). If an authority component is absent, then the path cannot begin with an empty segment, that is with two slashes (
//), as the following characters would be interpreted as an authority component. The final segment of the path may be referred to as a 'slug'.
- An optional query component preceded by a question mark (
?), containing a query string of non-hierarchical data. Its syntax is not well defined, but by convention is most often a sequence of attribute–value pairs separated by a delimiter.
- An optional fragment component preceded by a hash (
#). The fragment contains a fragment identifier providing direction to a secondary resource, such as a section heading in an article identified by the remainder of the URI. When the primary resource is an HTML document, the fragment is often an
idattribute of a specific element, and web browsers will scroll this element into view.
Strings of data octets within a URI are represented as characters. Permitted characters within a URI are the ASCII characters for the lowercase and uppercase letters of the modern English alphabet, the Arabic numerals, hyphen, period, underscore, and tilde. Octets represented by any other character must be percent-encoded.
Of the ASCII character set, the characters
: / ? # [ ] @ are reserved for use as delimiters of the generic URI components and must be percent-encoded – for example,
%3F for a question mark. The characters
! $ & ' ( ) * + , ; = are permitted by generic URI syntax to be used unencoded in the user information, host, and path as delimiters. Additionally,
@ may appear unencoded within the path, query, and fragment; and
/ may appear unencoded as data within the query or fragment.
The following figure displays example URIs and their component parts.
userinfo host port ┌──┴───┐ ┌──────┴──────┐ ┌┴┐ https://[email protected]:123/forum/questions/?tag=networking&order=newest#top └─┬─┘ └───────────┬──────────────┘└───────┬───────┘ └───────────┬─────────────┘ └┬┘ scheme authority path query fragment ldap://[2001:db8::7]/c=GB?objectClass?one └┬─┘ └─────┬─────┘└─┬─┘ └──────┬──────┘ scheme authority path query mailto:[email protected] └─┬──┘ └────┬─────────────┘ scheme path news:comp.infosystems.www.servers.unix └┬─┘ └─────────────┬─────────────────┘ scheme path tel:+1-816-555-1212 └┬┘ └──────┬──────┘ scheme path telnet://192.0.2.16:80/ └─┬──┘ └─────┬─────┘│ scheme authority path urn:oasis:names:specification:docbook:dtd:xml:4.1.2 └┬┘ └──────────────────────┬──────────────────────┘ scheme path
A URI reference is either a URI, or a relative reference when it does not begin with a scheme component followed by a colon (
:). A path segment that contains a colon character (e.g.,
foo:bar) cannot be used as the first path segment of a relative reference if its path component does not begin with a slash (
/), as it would be mistaken for a scheme component. Such a path segment must be preceded by a dot path segment (e.g.,
- in HTML, the value of the
srcattribute of the
imgelement provides a URI reference, as does the value of the
hrefattribute of the
- in XML, the system identifier appearing after the
SYSTEMkeyword in a DTD is a fragmentless URI reference;
- in XSLT, the value of the
hrefattribute of the
xsl:importelement/instruction is a URI reference; likewise the first argument to the
https://example.com/path/resource.txt#fragment //example.com/path/resource.txt /path/resource.txt path/resource.txt ../resource.txt ./resource.txt resource.txt #fragment
An absolute URI is a URI with no fragment component.
Resolving a URI reference against a base URI results in a target URI. This implies that the base URI exists and is an absolute URI. The base URI can be obtained, in order of precedence, from:
- the reference URI itself if it is a URI;
- the content of the representation;
- the entity encapsulating the representation;
- the URI used for the actual retrieval of the representation;
- the context of the application.
Within a representation with a well defined base URI of
a relative reference is resolved to its target URI as follows:
"g:h" -> "g:h" "g" -> "http://a/b/c/g" "./g" -> "http://a/b/c/g" "g/" -> "http://a/b/c/g/" "/g" -> "http://a/g" "//g" -> "http://g" "?y" -> "http://a/b/c/d;p?y" "g?y" -> "http://a/b/c/g?y" "#s" -> "http://a/b/c/d;p?q#s" "g#s" -> "http://a/b/c/g#s" "g?y#s" -> "http://a/b/c/g?y#s" ";x" -> "http://a/b/c/;x" "g;x" -> "http://a/b/c/g;x" "g;x?y#s" -> "http://a/b/c/g;x?y#s" "" -> "http://a/b/c/d;p?q" "." -> "http://a/b/c/" "./" -> "http://a/b/c/" ".." -> "http://a/b/" "../" -> "http://a/b/" "../g" -> "http://a/b/g" "../.." -> "http://a/" "../../" -> "http://a/" "../../g" -> "http://a/g"
Naming, addressing, and identifying resources
URIs and URLs have a shared history. In 1994, Tim Berners-Lee's proposals for hypertext implicitly introduced the idea of a URL as a short string representing a resource that is the target of a hyperlink. At the time, people referred to it as a "hypertext name" or "document name".
Over the next three and a half years, as the World Wide Web's core technologies of HTML, HTTP, and web browsers developed, a need to distinguish a string that provided an address for a resource from a string that merely named a resource emerged. Although not yet formally defined, the term Uniform Resource Locator came to represent the former, and the more contentious Uniform Resource Name came to represent the latter.
During the debate over defining URLs and URNs, it became evident that the concepts embodied by the two (2) terms were merely aspects of the fundamental, overarching, notion of resource identification. In June 1994, the IETF published Berners-Lee's RFC 1630, the first Request for Comments that acknowledged the existence of URLs and URNs. Most importantly, it defined a formal syntax for Universal Resource Identifiers (i.e. URL-like strings whose precise syntaxes and semantics depended on their schemes). In addition, the RFC attempted to summarize the syntaxes of URL schemes in use at the time. It acknowledged -- but did not standardize -- the existence of relative URLs and fragment identifiers.
Refinement of specifications
In December 1994, RFC 1738 formally defined relative and absolute URLs, refined the general URL syntax, defined how to resolve relative URLs to absolute form, and better enumerated the URL schemes then in use. The agreed definition and syntax of URNs had to wait until the publication of RFC 2141 in May 1997.
The publication of RFC 2396 in August 1998 saw the URI syntax become a separate specification and most of the parts of RFCs 1630 and 1738 relating to URIs and URLs in general were revised and expanded by the IETF. The new RFC changed the meaning of "U" in "URI" to "Uniform" from "Universal".
In December 1999, RFC 2732 provided a minor update to RFC 2396, allowing URIs to accommodate IPv6 addresses. A number of shortcomings discovered in the two specifications led to a community effort, coordinated by RFC 2396 co-author Roy Fielding, that culminated in the publication of RFC 3986 in January 2005. While obsoleting the prior standard, it did not render the details of existing URL schemes obsolete; RFC 1738 continues to govern such schemes except where otherwise superseded. RFC 2616 for example, refines the
http scheme. Simultaneously, the IETF published the content of RFC 3986 as the full standard STD 66, reflecting the establishment of the URI generic syntax as an official Internet protocol.
In 2001, the W3C's Technical Architecture Group (TAG) published a guide to best practices and canonical URIs for publishing multiple versions of a given resource. For example, content might differ by language or by size to adjust for capacity or settings of the device used to access that content.
In August 2002, RFC 3305 pointed out that the term "URL" had, despite widespread public use, faded into near obsolescence, and serves only as a reminder that some URIs act as addresses by having schemes implying network accessibility, regardless of any such actual use. As URI-based standards such as Resource Description Framework make evident, resource identification need not suggest the retrieval of resource representations over the Internet, nor need they imply network-based resources at all.
The Semantic Web uses the HTTP URI scheme to identify both documents and concepts in the real world, a distinction which has caused confusion as to how to distinguish the two. The TAG published an e-mail in 2005 on how to solve the problem, which became known as the httpRange-14 resolution. The W3C subsequently published an Interest Group Note titled Cool URIs for the Semantic Web, which explained the use of content negotiation and the HTTP 303 response code for redirections in more detail.
Relation to XML namespaces
In XML, a namespace is an abstract domain to which a collection of element and attribute names can be assigned. The namespace name is a character string which must adhere to the generic URI syntax. However, the name is generally not considered to be a URI, because the URI specification bases the decision not only on lexical components, but also on their intended use. A namespace name does not necessarily imply any of the semantics of URI schemes; for example, a namespace name beginning with http: may have no connotation to the use of the HTTP.
Originally, the namespace name could match the syntax of any non-empty URI reference, but the use of relative URI references was deprecated by the W3C. A separate W3C specification for namespaces in XML 1.1 permits internationalized resource identifier (IRI) references to serve as the basis for namespace names in addition to URI references.
- CURIE – defines a generic, abbreviated syntax for expressing URIs
- Dereferenceable Uniform Resource Identifier – a resource retrieval mechanism that uses any of the internet protocols (e.g. HTTP) to obtain a copy or representation of the resource it identifies
- Extensible Resource Identifier – a scheme and resolution protocol for abstract identifiers compatible with URIs
- Internationalized Resource Identifier (IRI) – a generalization of URIs allowing the use of Unicode
- Internet Resource Locator (IRL) – described in RFC 1736, conveys location and access information for resources
- Persistent uniform resource locator (PURL) – a URI that is used to redirect to the location of the requested web resource
- Uniform Naming Convention – a common syntax used by Microsoft to describe the location of a network resource, such as a shared file, directory, or printer
- Resource Directory Description Language – a descriptive language to provide machine- and human-readable information about a particular namespace and about the XML documents that use it
- List of URI schemes – Official IANA-registered schemes
- A report published in 2002 by a joint W3C/IETF working group aimed to normalize the divergent views held within the IETF and W3C over the relationship between the various 'UR*' terms and standards. While not published as a full standard by either organization, it has become the basis for the above common understanding and has informed many standards since then.
- The procedures for registering new URI schemes were originally defined in 1999 by RFC 2717, and are now defined by RFC 7595, published in June 2015.
- For URIs relating to resources on the World Wide Web, some web browsers allow
.0portions of dot-decimal notation to be dropped or raw integer IP addresses to be used.
- Historic RFC 1866 (obsoleted by RFC 2854) encourages CGI authors to support ';' in addition to '&'.
- RFC 3986 (2005), §3.0.
- Joint W3C/IETF URI Planning Interest Group (2001).
- Joint W3C/IETF URI Planning Interest Group (2002).
- "URL Standard: 6.3. URL APIs elsewhere".
- "URL Standard: Goals".
- RFC 2396 (1998).
- RFC 3986 (2005).
- RFC 3986, section 3 (2005).
- IETF (2015).
- RFC 3986 (2005), §3.2.2.
- Lawrence (2014).
- RFC 2396 (1998), §3.3.
- RFC 1866 (1995), §8.2.1.
- RFC 3986 (2005), §2.
- RFC 3986 (2005), §2.2.
- RFC 3986 (2005), §3.3.
- RFC 3986 (2005), §3.4.
- RFC 3986 (2005), §4.1.
- RFC 3986 (2005), §4.2.
- RFC 3986 (2005), §4.4.
- RFC 3986 (2005), §5.1.
- RFC 3986 (2005), §5.4.
- Palmer (2001).
- W3C (1992).
- RFC 1630
- W3C (2001).
- Fielding (2005).
- W3C (2008).
- Morrison (2006).
- Harold (2004).
- W3C (2009).
- W3C (2006).
- Fielding, Roy T. (2005-06-18). "[httpRange-14] Resolved". Retrieved 2009-07-24.
- Harold, Elliotte Rusty (2004). XML 1.1 Bible (Third ed.). Wiley Publishing. p. 291. ISBN 978-0-7645-4986-1.
- Joint W3C/IETF URI Planning Interest Group (2001-09-21). "URIs, URLs, and URNs: Clarifications and Recommendations 1.0". Retrieved 2009-07-27.
- Mealling, Michael; Denenberg, Ray, eds. (August 2002). "Report from the Joint W3C/IETF URI Planning Interest Group: Uniform Resource Identifiers (URIs), URLs, and Uniform Resource Names (URNs): Clarifications and Recommendations". World Wide Web Consortium. Retrieved 2015-09-13.
- Hansen, Tony; Hardie, Ted (June 2015). Thaler, Dave (ed.). "Guidelines and Registration Procedures for URI Schemes". Internet Engineering Task Force. ISSN 2070-1721.
- Morrison, Michael Wayne (2006). "Hour 5: Putting Namespaces to Use". Sams Teach Yourself XML. Sams Publishing. p. 91.
- Palmer, Sean B. (2001). "The Early History of HTML". Retrieved 2009-04-30.
- URI Planning Interest Group, W3C/IETF (2001-09-21). "URIs, URLs, and URNs: Clarifications and Recommendations 1.0". Retrieved 2009-07-27.
- "W3 Naming Schemes". World Wide Web Consortium. 1992. Retrieved 2009-07-24.
- "On Linking Alternative Representations To Enable Discovery And Publishing". World Wide Web Consortium. 2006 . Retrieved 2012-04-03.
- Bray, Tim; Hollander, Dave; Layman, Andrew; Tobin, Richard, eds. (2006-08-16). "Namespaces in XML 1.1 (Second Edition)". World Wide Web Consortium. 2.2 Use of URIs as Namespace Names. Retrieved 2015-08-31.
- Ayers, Danny; Völkel, Max (2008-12-03). Sauermann, Leo; Cyganiak, Richard (eds.). "Cool URIs for the Semantic Web". World Wide Web Consortium. Retrieved 2012-04-03.
- Bray, Tim; Hollander, Dave; Layman, Andrew; Tobin, Richard; Thompson, Henry S., eds. (2009-12-08). "Namespaces in XML 1.0 (Third Edition)". World Wide Web Consortium. 2.2 Use of URIs as Namespace Names. Retrieved 2015-08-31.
- Berners-Lee, Tim; Connolly, Daniel "Dan" (November 1995). "Hypertext Markup Language – 2.0". Internet Engineering Task Force. Retrieved 2015-09-13.
- Berners-Lee, Tim; Fielding, Roy T.; Masinter, Larry (August 1998). Uniform Resource Identifiers (URI): Generic Syntax. Internet Engineering Task Force. doi:10.17487/RFC2396. RFC 2396. Retrieved 2015-08-31.
- Berners-Lee, Tim; Fielding, Roy T.; Masinter, Larry (January 2005). Uniform Resource Identifiers (URI): Generic Syntax. Internet Engineering Task Force. doi:10.17487/RFC3986. RFC 3986. Retrieved 2015-08-31.
- Berners-Lee, Tim; Fielding, Roy T.; Masinter, Larry (January 2005). Uniform Resource Identifiers (URI): Generic Syntax, section 3, Syntax Components. Internet Engineering Task Force. doi:10.17487/RFC3986. RFC 3986. Retrieved 2015-08-31.
- Lawrence, Eric (2014-03-06). "Browser Arcana: IP Literals in URLs". IEInternals. Microsoft. Retrieved 2016-04-25.
- URI Schemes – IANA-maintained registry of URI Schemes
- URI schemes on the W3C wiki
- Architecture of the World Wide Web, Volume One, §2: Identification – by W3C
- W3C URI Clarification