Edit filter log

'{{Redirect|URI}} {{good article}} In [[information technology]], a '''Uniform Resource Identifier''' ('''URI''') is a [[character string (computer science)|string]] of [[character (computing)|character]]s used to [[identifier|identify]] a [[resource (computer science)|resource]]. Such identification enables interaction with representations of the resource over a network, typically the [[World Wide Web]], using specific [[protocol (computing)|protocol]]s. Schemes specifying a concrete [[syntax]] and associated protocols define each URI. The most common form of URI is the [[Uniform Resource Locator|Uniform Resource Locator (URL)]], frequently referred to informally as a ''web address.'' More rarely seen in usage is the [[Uniform Resource Name|Uniform Resource Name (URN)]], which was designed to complement URLs by providing a mechanism for the identification of resources in particular [[namespace]]s. ==Relationship between URIs, URLs, and URNs== A Uniform Resource Name (URN) can be compared to a person's name, while a Uniform Resource Locator (URL) can be compared to their street address. In other words, a URN identifies an item and a URL provides a method for finding it. ===URLs=== {{Main article|Uniform Resource Locator}} A URL is a URI that, in addition to identifying a web resource, specifies the means of acting upon or obtaining the representation of it, i.e. specifying both its primary access mechanism and network location. For example, the URL <tt><nowiki>http://example.org/wiki/Main_Page</nowiki></tt> refers to a resource identified as <tt><nowiki>/wiki/Main_Page</nowiki></tt> whose representation, in the form of [[HTML]] and related code, is obtainable via [[Hypertext Transfer Protocol]] (<tt>http</tt>) from a network host whose [[domain name]] is <tt><nowiki>example.org</nowiki></tt>. ===URNs=== {{Main article|Uniform Resource Name}} A 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|International Standard Book Number (ISBN)]] system, <code><nowiki>ISBN</nowiki> 0-486-27557-4</code> identifies a specific edition of Shakespeare's play ''[[Romeo and Juliet]]''. The URN for that edition would be <code><nowiki>urn:isbn:0-486-27557-4</nowiki></code>. To gain access to the book, its location is needed, for which a URL would have to be specified. ===Conceptual distinctions=== Technical publications, especially standards produced by the [[Internet Engineering Task Force|IETF]] and by the [[World Wide Web Consortium|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. {{quotation|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.{{sfnp|Joint W3C/IETF URI Planning Interest Group|2001}}}} A URL is simply a URI that happens to point to a resource over a network. {{efn|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.{{sfnp|Joint W3C/IETF URI Planning Interest Group|2002}}}} 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 <code>http</code> or <code>https</code> scheme. Such assumptions can lead to confusion, for example in the case of XML namespaces, which have a [[#Relation to XML namespaces|visual similarity to resolvable URIs]]. While most URI schemes were originally designed to be used with a particular [[protocol (computing)|protocol]], and often have the same name (such as the <code>http</code> scheme, which is generally used for interacting with [[web resource]]s using HTTP), they should not be referred to as ''protocols''. Some URI schemes are not associated with any specific protocol (e.g. <code>[[file URI scheme|file]]</code>) and many others do not use the name of a protocol as their prefix (e.g. <code>[[Usenet newsgroup|news]]</code>). ==Syntax== The syntax of generic URIs and absolute URI references was first defined in [[Request for Comments|Request for Comments (RFC)]] 2396, published in August 1998,{{sfnp|RFC 2396|1998}} and finalized in <nowiki>RFC</nowiki> 3986, published in January 2005.{{sfnp|RFC 3986|2005}} <section begin=syntax /><!-- This section is transcluded in other articles. See Help:Labeled section transclusion --> A generic URI is of the form: '''scheme''':['''//'''['''user:password@''']'''host'''[''':port''']]['''/''']'''path'''[?'''query'''][#'''fragment'''] It comprises: * The '''scheme''', consisting of a sequence of characters beginning with a letter and followed by any combination of letters, digits, plus (<code>+</code>), period (<code>.</code>), or hyphen (<code>-</code>). Although schemes are case-insensitive, the canonical form is lowercase and documents that specify schemes must do so with lowercase letters. It is followed by a colon (<code>:</code>). Examples of popular schemes include <code>[[Hypertext Transfer Protocol|http]]</code>, <code>[[File Transfer Protocol|ftp]]</code>, <code>[[Mailto|mailto]]</code>, <code>[[File URI scheme|file]]</code>, <code>[[Data URI scheme|data]]</code>, and [[Internet Relay Chat#URI scheme|irc]]. URI schemes should be registered with the [[Internet Assigned Numbers Authority|Internet Assigned Numbers Authority (IANA)]], although non-registered schemes are used in practice.{{efn|The procedures for registering new URI schemes were originally defined in 1999 by <nowiki>RFC 2717</nowiki>, and are now defined by <nowiki>RFC 7595</nowiki>, published in June 2015.{{sfnp|IETF|2015}}}} * Two slashes (<code>//</code>): This is required by some schemes and not required by some others. When the authority component (explained below) is absent, the path component cannot begin with two slashes.{{sfnp|RFC 3986|2005|loc=§3}} * An '''authority part''', comprising: ** An optional [[authentication]] section of a [[user name]] and [[password]], separated by a colon, followed by an at symbol (<code>@</code>) ** A "'''host'''", 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 (<code>[&nbsp;]</code>).{{sfnp|RFC 3986|2005|loc=§3.2.2}}{{efn|For URIs relating to resources on the World Wide Web, some web browsers allow {{code|.0}} portions of dot-decimal notation to be dropped or raw integer IP addresses to be used.{{sfnp|Lawrence|2014}}}} ** An optional [[Port (computer networking)|port number]], separated from the hostname by a colon * A '''path''', which contains data, usually organized in hierarchical form, that appears as a sequence of segments separated by slashes. Such a sequence may resemble or map exactly to a [[Path (computing)|file system path]], but does not always imply a relation to one.{{sfnp|RFC 2396|1998|loc=§3.3}} The path must begin with a single slash (<code>/</code>) if an authority part was present, and may also if one was not, but must not begin with a double slash. The path is always defined, though the defined path may be empty (zero length) {| class="wikitable" style="float: right; font-size: 0.9em; margin-left: 1em" |- ! Query delimiter ! Example |- | Ampersand (<code>&amp;</code>) | <code>key1=value1&key2=value2</code> |- | Semicolon (<code>;</code>){{efn|Historic <nowiki>RFC 1866</nowiki> (obsoleted by <nowiki>RFC 2854</nowiki>) encourages CGI authors to support ';' in addition to '&'.{{sfnp|RFC 1866|1995|loc=§8.2.1}}}}{{Incomplete short citation|date=August 2016}} | <code>key1=value1;key2=value2</code> |} * An optional '''query''', separated from the preceding part by a question mark (<code>?</code>), 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 pair]]s separated by a [[delimiter]]. * An optional '''fragment''', separated from the preceding part by a [[Number sign|hash]] (<code>#</code>). 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 [[HTML#Attributes|<code>id</code> attribute]] of a specific element, and web browsers will scroll this element into view.<section end=syntax /> Strings of data [[Octet (computing)|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]], [[Full stop|period]], [[underscore]], and [[tilde]].{{sfnp|RFC 3986|2005|loc=§2}} Octets represented by any other character must be [[percent-encoding|percent-encoded]]. Of the ASCII character set, the characters <code>: / ? # [ ] @</code> are reserved for use as delimiters of the generic URI components and must be percent-encoded&nbsp;— for example, <code>%3F</code> for a question mark.{{sfnp|RFC 3986|2005|loc=§2.2}} The characters <code>! $ & ' ( ) * + , ; =</code> are permitted by generic URI syntax to be used unencoded in the user information, host, and path as delimiters.{{sfnp|RFC 3986|2005|loc=§3.2.2}}{{sfnp|RFC 3986|2005|loc=§3.3}} Additionally, <code>:</code> and <code>@</code> may appear unencoded within the path, query, and fragment; and <code>?</code> and <code>/</code> may appear unencoded as data within the query or fragment.{{sfnp|RFC 3986|2005|loc=§3.3}}{{sfnp|RFC 3986|2005|loc=§3.4}} ===Examples=== The following figure displays two example URIs and their component parts. <!-- based on format of examples in RFC 3986 --> <pre> hierarchical part ┌───────────────────┴─────────────────────┐ authority path ┌───────────────┴───────────────┐┌───┴────┐ abc://username:password@example.com:123/path/data?key=value&key2=value2#fragid1 └┬┘ └───────┬───────┘ └────┬────┘ └┬┘ └─────────┬─────────┘ └──┬──┘ scheme user information host port query fragment urn:example:mammal:monotreme:echidna └┬┘ └──────────────┬───────────────┘ scheme path</pre> ==URI references== A URI reference may take the form of a full URI, the scheme-specific portion of a full URI, a trailing component of a full URI, or the empty string.{{sfnp|RFC 3986|2005|loc=§4.1}} An optional ''fragment identifier'', preceded by <code>#</code>, may be present at the end of a URI reference. The part of the reference before the <code>#</code> indirectly identifies a resource, and the fragment identifier identifies some portion of that resource.{{sfnp|RFC 3986|2005|loc=§4.2}} To derive a URI from a URI reference, software converts the URI reference to ''absolute'' form by merging it with a ''base'' URI according to a fixed algorithm.{{sfnp|RFC 3986|2005|loc=§5.1}} The system treats the URI reference as relative to the base URI, although in the case of an absolute reference, the base has no relevance. If the base URI includes a fragment identifier, it is ignored during the merging process.{{sfnp|RFC 3986|2005|loc=§5.1}} If a fragment identifier is present in the URI reference, it is preserved during the merging process.{{sfnp|RFC 3986|2005|loc=§5.2.2}} Web document [[markup language]]s frequently use URI references to point to other resources, such as external documents or specific portions of the same logical document.{{sfnp|RFC 3986|2005|loc=§4.4}} ===Examples in markup languages=== * In [[HTML]], the value of the <code>src</code> attribute of the <code>img</code> element provides a URI reference, as does the value of the <code>href</code> attribute of the <code>a</code> or <code>link</code> element. * In [[XML]], the [[system identifier]] appearing after the <code>SYSTEM</code> keyword in a [[Document Type Definition|DTD]] is a fragmentless URI reference. * In [[XSLT]], the value of the <code>href</code> attribute of the <code>xsl:import</code> element/instruction is a URI reference; likewise the first argument to the <code>document()</code> function. ===Examples of absolute URIs=== * <tt><nowiki>https://example.org/absolute/URI/with/absolute/path/to/resource.txt</nowiki></tt> * <tt><nowiki>ftp://example.org/resource.txt</nowiki></tt> * <tt><nowiki>urn:</nowiki>[[International Standard Serial Number#Use in URNs|ISSN]]<nowiki>:1535–3613</nowiki></tt> ===Examples of URI references=== * <tt><nowiki>https://example.org/absolute/URI/with/absolute/path/to/resource.txt</nowiki></tt> * <tt><nowiki>//example.org/scheme-relative/URI/with/absolute/path/to/resource.txt</nowiki></tt> * <tt>/relative/URI/with/absolute/path/to/resource.txt</tt> * <tt>relative/path/to/resource.txt</tt> * <tt>../../../resource.txt</tt> * <tt>./resource.txt#frag01</tt> * <tt>resource.txt</tt> * <tt>#frag01</tt> ==URI resolution== To ''resolve'' a URI means either to convert a relative URI reference to absolute form, or to ''dereference'' a URI or URI reference, by attempting to obtain a representation of the resource that it identifies. A ''same-document reference'' is a URI reference to a document containing the URI reference itself. A URI reference is defined as a same-document reference if, when resolved to absolute form, it equates exactly to the base URI in effect for the reference.{{sfnp|RFC 3986|2005|loc=§4.4}} When encountering a same-document reference, document processing software, for example a web browser, to efficiently use its current representation of a document to satisfy the resolution of a reference to that document without fetching a new representation. ''URI equivalence'' is defined as when a URI reference, while not identical to the base URI, still represents the same resource.{{sfnp|RFC 3986|2005|loc=§4.4}} ==History== ===Naming, addressing, and identifying resources=== URIs and URLs have a shared history. In 1994, [[Tim Berners-Lee|Tim Berners-Lee's]] proposals for [[hypertext]]{{sfnp|Palmer|2001}} 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"{{sfnp|W3C|1992}} 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 two concepts embodied by the terms were merely aspects of the fundamental, overarching notion of resource ''identification''. In June 1994, the IETF published Berners-Lee's <nowiki>RFC 1630</nowiki>: the first Request for Comments that acknowledged the existence of URLs and URNs, and, more importantly, defined a formal syntax for ''Universal Resource Identifiers''&nbsp;— URL-like strings whose precise syntaxes and semantics depended on their schemes. In addition, this RFC attempted to summarize the syntaxes of URL schemes in use at the time. It also acknowledged, but did not standardize, the existence of relative URLs and fragment identifiers. ===Refinement of specifications=== In December 1994, <nowiki>RFC 1738</nowiki> 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 <nowiki>RFC 2141</nowiki> in May 1997. The publication of <nowiki>RFC 2396</nowiki> in August 1998 saw the URI syntax become a separate specification{{sfnp|RFC 2396|1998}} 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, <nowiki>RFC 2732</nowiki> provided a minor update to <nowiki>RFC 2396</nowiki>, allowing URIs to accommodate [[IPv6]] addresses. A number of shortcomings discovered in the two specifications led to a community effort, coordinated by <nowiki>RFC 2396</nowiki> co-author [[Roy Fielding]], that culminated in the publication of <nowiki>RFC 3986</nowiki> in January 2005. While obsoleting the prior standard, it did not render the details of existing URL schemes obsolete; <nowiki>RFC 1738</nowiki> continues to govern such schemes except where otherwise superseded. <nowiki>RFC 2616</nowiki> for example, refines the <code>http</code> scheme. Simultaneously, the IETF published the content of <nowiki>RFC 3986</nowiki> 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.{{sfnp|W3C|2001}} 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, <nowiki>RFC 3305</nowiki> 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''.{{sfnp|Fielding|2005}} The W3C subsequently published an Interest Group Note titled ''Cool URIs for the Semantic Web'',{{sfnp|W3C|2008}} 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 [[XML namespace|namespace]] is an abstract domain to which a collection of element and attribute names can be assigned.<!-- who or what can do such assignation? --> The namespace name is a character string which must adhere to the generic URI syntax.{{sfnp|Morrison|2006}} However, the name is generally not considered to be a URI,{{sfnp|Harold|2004}} 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.{{sfnp|W3C|2009}} A separate W3C specification for namespaces in XML 1.1 permits [[Internationalized resource identifier|internationalized resource identifier (IRI)]] references to serve as the basis for namespace names in addition to URI references.{{sfnp|W3C|2006}} ==See also== * [[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 * [[Persistent uniform resource locator]] – 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 * [[Universally unique identifier|UUID]] ==Notes== {{div col|colwidth=39em}} {{notelist}} {{div col end}} ==References== {{reflist|30em}} ===Cited works=== {{refbegin|30em}} * {{cite web|first=Roy T.|last=Fielding|authorlink=Roy Fielding|title=[httpRange-14] Resolved|url =http://lists.w3.org/Archives/Public/www-tag/2005Jun/0039.html|date=18 June 2005|accessdate=24 July 2009|ref=harv}} * {{cite book|first=Elliotte Rusty|last=Harold|authorlink=Elliotte Rusty Harold|year=2004|title=XML 1.1 Bible|edition=Third|publisher=[[Wiley Publishing]]|page=291|isbn=0-7645-4986-3|ref=harv}} * {{cite web|url=http://www.w3.org/TR/uri-clarification/|author=Joint W3C/IETF URI Planning Interest Group|title=URIs, URLs, and URNs: Clarifications and Recommendations 1.0|date=21 September 2001|accessdate=2009-07-27|ref={{SfnRef|Joint W3C/IETF URI Planning Interest Group|2001}}}} * {{cite web|url=https://tools.ietf.org/html/rfc3305|title=Report from the Joint W3C/IETF URI Planning Interest Group: Uniform Resource Identifiers (URIs), URLs, and Uniform Resource Names (URNs): Clarifications and Recommendations|editor1-first=M.|editor1-last=Mealling|editor2-first=R.|editor2-last=Denenberg|publisher=[[World Wide Web Consortium]]|date=August 2002|accessdate=13 September 2015|ref={{SfnRef|Joint W3C/IETF URI Planning Interest Group|2002}}}} * {{cite web|url=https://tools.ietf.org/html/rfc7595|title=Guidelines and Registration Procedures for URI Schemes|editor-first=D.|editor-last=Thaler|author1-first=T.|author1-last=Hansen|author2-first=T.|author2-last=Hardie|publisher=[[Internet Engineering Task Force]]|date=June 2015|issn=2070-1721|ref={{SfnRef|IETF|2015}}}} * {{cite book|last=Morrison|first=Michael|year=2006|title=Sams Teach Yourself XML|publisher=[[Sams Publishing]]|chapter=Hour 5: ''Putting Namespaces to Use''|page=91|ref=harv}} * {{cite web|first=Sean B.|last=Palmer|title=The Early History of HTML|url=http://infomesh.net/html/history/early/|year=2001|accessdate=2009-04-30|ref=harv}} * {{cite web|author = URI Planning Interest Group, W3C/IETF|title= URIs, URLs, and URNs: Clarifications and Recommendations 1.0|url= http://www.w3.org/TR/uri-clarification/ | date = 21 September 2001|accessdate=2009-07-27|ref={{SfnRef|URI Planning Interest Group|2009}} }} * {{cite web|url= http://www.w3.org/History/19921103-hypertext/hypertext/WWW/Addressing/Addressing.html|title=W3 Naming Schemes|publisher=[[World Wide Web Consortium]]|year=1992|accessdate=2009-07-24|ref={{SfnRef|W3C|1992}}}} * {{cite web|url=http://www.w3.org/2001/tag/doc/alternatives-discovery.html |title=On Linking Alternative Representations To Enable Discovery And Publishing|publisher=[[World Wide Web Consortium]]|year=2006|orig-year=2001|accessdate=2012-04-03|ref={{SfnRef|W3C|2001}}}} * {{cite web|url=http://www.w3.org/TR/REC-xml-names/#iri-use|title=Namespaces in XML 1.1 (Second Edition)|date=16 August 2006|at=2.2 Use of URIs as Namespace Names|editor1-first=Tim|editor1-last=Bray|editor1-link=Tim Bray|editor2-first=Dave|editor2-last=Hollander|editor3-first=Andrew|editor3-last=Layman|editor4-first=Richard|editor4-last=Tobin|publisher=[[World Wide Web Consortium]]|accessdate=31 August 2015|ref={{SfnRef|W3C|2006}}}} * {{cite web|url=http://www.w3.org/TR/cooluris/|title=Cool URIs for the Semantic Web|editor1-first=Leo|editor1-last=Sauermann|editor2-first=Richard|editor2-last=Cyganiak|author1-first=Danny|author1-last=Ayers|author2-first=Max|author2-last=Völkel|publisher=[[World Wide Web Consortium]]|date=3 December 2008|accessdate=2012-04-03|ref={{SfnRef|W3C|2008}}}} * {{cite web|url=http://www.w3.org/TR/REC-xml-names/#iri-use|title=Namespaces in XML 1.0 (Third Edition)|date=8 December 2009|at=2.2 Use of URIs as Namespace Names|editor1-first=Tim|editor1-last=Bray|editor1-link=Tim Bray|editor2-first=Dave|editor2-last=Hollander|editor3-first=Andrew|editor3-last=Layman|editor4-first=Richard|editor4-last=Tobin|editor5-first=Henry S.|editor5-last=Thompson|publisher=[[World Wide Web Consortium]]|accessdate=31 August 2015|ref={{SfnRef|W3C|2009}}}} * {{cite web|url=https://tools.ietf.org/html/rfc1866#section-8.2.1|title=Hypertext Markup Language - 2.0|author1-first=Tim|author1-last=Berners-Lee|author1-link=Tim Berners-Lee|author2-first=Dan|author2-last=Connolly|publisher=[[Internet Engineering Task Force]]|date=November 1995|accessdate=13 September 2015}} * {{cite web|url=http://tools.ietf.org/html/rfc2396|title=Uniform Resource Identifiers (URI): Generic Syntax|author1-first=Tim|author1-last=Berners-Lee|author1-link=Tim Berners-Lee|author2-first=Roy|author2-last=Fielding|author2-link=Roy Fielding|author3-first=Larry|author3-last=Masinter|publisher=[[Internet Engineering Task Force]]|date=August 1998|accessdate=31 August 2015|ref={{SfnRef|RFC 2396|1998}}}} * {{cite web|url=http://tools.ietf.org/html/rfc3986|title=Uniform Resource Identifiers (URI): Generic Syntax|author1-first=Tim|author1-last=Berners-Lee|author1-link=Tim Berners-Lee|author2-first=Roy|author2-last=Fielding|author2-link=Roy Fielding|author3-first=Larry|author3-last=Masinter|publisher=[[Internet Engineering Task Force]]|date=January 2005|accessdate=31 August 2015|ref={{SfnRef|RFC 3986|2005}}}} * {{cite web|last1=Lawrence|first1=Eric|title=Browser Arcana: IP Literals in URLs|url=http://blogs.msdn.com/b/ieinternals/archive/2014/03/06/browser-arcana-ipv4-ipv6-literal-urls-dotted-va-dotless.aspx|website=IEInternals|publisher=[[Microsoft]]|date=6 March 2014|accessdate=2016-04-25|ref=harv}} {{refend}} ==External links== * [http://www.iana.org/assignments/uri-schemes.html URI Schemes]&nbsp;– [[Internet Assigned Numbers Authority|IANA]]-maintained registry of URI Schemes * [http://www.w3.org/wiki/UriSchemes URI schemes on the W3C wiki] * [http://www.w3.org/TR/webarch/#identification Architecture of the World Wide Web, Volume One, §2: Identification]&nbsp;– by W3C * [http://www.w3.org/TR/uri-clarification/ W3C URI Clarification] {{Semantic Web|state=collapsed}} {{URI scheme}} {{Hypermedia}} {{Authority control}} [[Category:Application layer protocols]] [[Category:Internet protocols]] [[Category:Internet Standards]] [[Category:URI schemes]] [[Category:Semantic Web| ]]'