In computing Information technology is "the study, design, development, implementation, support or management of computer-based information systems, particularly software applications and computer hardware", according to the Information Technology Association of America (ITAA). IT deals with the use of electronic computers and computer software to, a Uniform Resource Identifier (URI) is a string In mathematical logic, more precisely in the theory of formal languages, and in computer science, a string is a sequence of symbols that are chosen from a set or alphabet.[citation needed] of characters In computer and machine-based telecommunications terminology, a character is a unit of information that roughly corresponds to a grapheme, grapheme-like unit, or symbol, such as in an alphabet or syllabary in the written form of a natural language used to identify An identifier is a unique expression in a written format either by a code, by numbers or by the combination of both to distinguish variations from one to another among a class of substances, items, or objects. For living organisms and the structural identifications of objects, identifiers could be more complicated a name or a resource The concept of resource is primitive in the Web architecture, and is used in the definition of its fundamental elements. The term was first introduced to refer to targets of Uniform Resource Locators , but its definition has been further extended to include the referent of any Uniform Resource Identifier (RFC 3986), or Internationalized Resource on the Internet The Internet is a global system of interconnected computer networks that use the standard Internet Protocol Suite to serve billions of users worldwide. It is a network of networks that consists of millions of private, public, academic, business, and government networks of local to global scope that are linked by a broad array of electronic and. Such identification enables interaction with representations of the resource over a network (typically the World Wide Web The World Wide Web, abbreviated as WWW and commonly known as the Web, is a system of interlinked hypertext documents accessed via the Internet. With a web browser, one can view web pages that may contain text, images, videos, and other multimedia and navigate between them by using hyperlinks. Using concepts from earlier hypertext systems, British) using specific protocols In computing and telecommunications, a protocol or communications protocol is a formal description of message formats and the rules for exchanging those messages. Protocols may include signaling, authentication and error detection and correction capabilities. In its simplest form, a protocol can be defined as the rules governing the syntax,. Schemes specifying a concrete syntax In linguistics, syntax is the study of the principles and rules for constructing sentences in natural languages and associated protocols define each URI.

Relationship to URL and URN

A URI may be classified as a locator (URL), or a name (URN), or both. A Uniform Resource Name A Uniform Resource Name 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 (URN) functions like a person's name, while a Uniform Resource Locator In computing, a Uniform Resource Locator is a Uniform Resource Identifier (URI) that specifies where an identified resource is available and the mechanism for retrieving it. In popular usage and in many technical documents and verbal discussions it is often incorrectly used as a synonym for URI,. The best-known example of a URL is the " (URL) resembles that person's street address. In other words: the URN defines an item's identity, while the URL provides a method for finding it.

The ISBN The International Standard Book Number is a unique numeric commercial book identifier based upon the 9-digit Standard Book Numbering (SBN) code created by Gordon Foster, now Emeritus Professor of Statistics at Trinity College, Dublin, for the booksellers and stationers W.H. Smith and others in 1966 system for uniquely identifying books provides a typical example of the use of URNs. ISBN 0486275574 (urn:isbn:0-486-27557-4) cites unambiguously a specific edition of Shakespeare's play Romeo and Juliet Romeo and Juliet is a tragedy written early in the career of playwright William Shakespeare about two young "star-cross'd lovers" whose deaths ultimately unite their feuding families. It was among Shakespeare's most popular plays during his lifetime and, along with Hamlet and Macbeth, is one of his most frequently performed plays. Today,. To gain access to this object and read the book, one needs its location: a URL address. A typical URL for this book on a Unix-like A Unix-like operating system is one that behaves in a manner similar to a Unix system, while not necessarily conforming to or being certified to any version of the Single UNIX Specification operating system would be a file path A path, the general form of a filename or of a directory name, specifies a unique location in a file system. A path points to a file system location by following the directory tree hierarchy expressed in a string of characters in which path components, separated by a delimiting character, represent each directory. The delimiting character is most such as file:///home/username/RomeoAndJuliet.pdf, identifying the electronic book saved in a file on a local hard disk. So URNs and URLs have complementary purposes.

Technical view

A URL is a URI that, in addition to identifying a network-homed resource The concept of resource is primitive in the Web architecture, and is used in the definition of its fundamental elements. The term was first introduced to refer to targets of Uniform Resource Locators , but its definition has been further extended to include the referent of any Uniform Resource Identifier (RFC 3986), or Internationalized Resource, specifies the means of acting upon or obtaining the representation: either through description of the primary access mechanism, or through network "location". For example, the URL http://www.wikipedia.org/ identifies a resource (Wikipedia's Wikipedia is a free, web-based, collaborative, multilingual encyclopedia project supported by the non-profit Wikimedia Foundation. Its 15 million articles have been written collaboratively by volunteers around the world, and almost all of its articles can be edited by anyone with access to the site. Wikipedia was launched in 2001 by Jimmy Wales home page The home page is the URL or local file that automatically loads when a web browser starts or when the browser's "home" button is pressed. One can turn this feature off and on, as well as specify a URL for the page to be loaded) and implies that a representation of that resource (such as the home page's current HTML HTML, which stands for HyperText Markup Language, is the predominant markup language for web pages. It provides a means to create structured documents by denoting structural semantics for text such as headings, paragraphs, lists, links, quotes and other items. It allows images and objects to be embedded and can be used to create interactive forms code, as encoded characters A character encoding system consists of a code that pairs each character from a given repertoire with something else, such as a sequence of natural numbers, octets or electrical pulses, in order to facilitate the transmission of data through telecommunication networks or storage of text in computers) is obtainable via HTTP The Hypertext Transfer Protocol is an Application Layer protocol for distributed, collaborative, hypermedia information systems from a network host named www.wikipedia.org. A Uniform Resource Name A Uniform Resource Name 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 (URN) is a URI that identifies a resource by name, in a particular namespace A namespace is an abstract container or environment created to hold a logical grouping of unique identifiers or symbols . An identifier defined in a namespace is associated with that namespace. The same identifier can be independently defined in multiple namespaces. That is, the meaning associated with an identifier defined in one namespace may or. One can use a URN to talk about a resource without implying its location or how to access it. The resource does not need to necessarily be network homed. For example, the URN urn:isbn:0-395-36341-1 is a URI that specifies the identifier system, i.e. International Standard Book Number (ISBN The International Standard Book Number is a unique numeric commercial book identifier based upon the 9-digit Standard Book Numbering (SBN) code created by Gordon Foster, now Emeritus Professor of Statistics at Trinity College, Dublin, for the booksellers and stationers W.H. Smith and others in 1966), as well as the unique reference within that system and allows one to talk about a book, but doesn't suggest where and how to obtain an actual copy of it.

Technical publications, especially standards produced by the IETF The Internet Engineering Task Force develops and promotes Internet standards, cooperating closely with the W3C and ISO/IEC standards bodies and dealing in particular with standards of the TCP/IP and Internet protocol suite. It is an open standards organization, with no formal membership or membership requirements. All participants and managers are and by the W3C The World Wide Web Consortium is the main international standards organization for the World Wide Web (abbreviated WWW or W3), normally no longer^[when?] use the term URL, as the need to distinguish between URLs and URIs rarely arises.^[1] 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 URL or URI, although it generally refers only to the 'http' and 'https' URL schemes.

RFC 3305

Much of this discussion comes from RFC3305, titled 'Report from the Joint W3C/IETF URI Planning Interest Group: Uniform Resource Identifiers (URIs), URLs, and Uniform Resource Names (URNs): Clarifications and Recommendations'. This RFC In computer network engineering, a Request for Comments is a memorandum published by the Internet Engineering Task Force (IETF) describing methods, behaviors, research, or innovations applicable to the working of the Internet and Internet-connected systems outlines the work of a joint W3C/IETF working group set up specifically 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.

Syntax

The URI syntax consists of a URI scheme In the field of computer networking, a URI scheme is the top level of the Uniform Resource Identifier naming structure. All URIs and absolute URI references are formed with a scheme name, followed by a colon character (":"), and the remainder of the URI called (in the outdated RFCs 1738 and 2396, but not the current STD 66/RFC 3986) the name (such as "http The Hypertext Transfer Protocol is an Application Layer protocol for distributed, collaborative, hypermedia information systems", "ftp File Transfer Protocol is a standard network protocol used to copy a file from one host to another over a TCP/IP-based network, such as the Internet. FTP is built on a client-server architecture and utilizes separate control and data connections between the client and server applications, which solves the problem of different end host", "mailto Electronic mail, commonly called email or e-mail, is a method of exchanging digital messages across the Internet or other computer networks. Email systems are based on a store-and-forward model in which email server computer systems accept, forward, deliver and store messages on behalf of users, who only need to connect to the email infrastructure," or "file") followed by a colon As with many other punctuation marks, the usage of colon varies among languages and, for a given language, among historical periods. As a rule, however, a colon informs the reader that what follows proves and explains, or simply provides elements of, what is referred to before character, and then by a scheme-specific part. The specifications that govern the schemes determine the syntax and semantics Semantics is the study of meaning, usually in language. The word "semantics" itself denotes a range of ideas, from the popular to the highly technical. It is often used in ordinary language to denote a problem of understanding that comes down to word selection or connotation. This problem of understanding has been the subject of many of the scheme-specific part, although the URI syntax does force all schemes to adhere to a certain generic syntax that, among other things, reserves certain characters for special purposes (without always identifying those purposes). The URI syntax also enforces restrictions on the scheme-specific part to, for example, provide for a degree of consistency when the part has a hierarchical structure. Percent encoding Percent-encoding, also known as URL encoding, is a mechanism for encoding information in a Uniform Resource Identifier under certain circumstances. Although it is known as URL encoding it is, in fact, used more generally within the main Uniform Resource Identifier (URI) set, which includes both Uniform Resource Locator (URL) and Uniform Resource can add extra information to a URI.

History

Naming, addressing, and identifying resources

URIs and URLs have a shared history. In 1990, Tim Berners-Lee’s Sir Timothy John "Tim" Berners-Lee, OM, KBE, FRS, FREng, FRSA , is a British engineer and computer scientist and MIT professor credited with inventing the World Wide Web, making the first proposal for it in March 1989. On 25 December 1990, with the help of Robert Cailliau and a young student at CERN, he implemented the first successful proposals for HyperText Hypertext is text displayed on a computer or other electronic device with references to other text that the reader can immediately access, usually by a mouse click or keypress sequence. Apart from running text, hypertext may contain tables, images and other presentational devices. Hypertext is the underlying concept defining the structure of the^[2] implicitly introduced the idea of a URL as a short string representing a resource that is the target of a hyperlink In computing, a hyperlink is a reference to a document that the reader can directly follow, or that is followed automatically[citation needed]. The reference points to a whole document or to a specific element within a document. Hypertext is text with hyperlinks. Such text is usually viewed with a computer. A software system for viewing and. At the time, people referred to it as a 'hypertext name'^[3] or 'document name'.

Over the next 3.5 years, as the World Wide Web's core technologies of HTML HTML, which stands for HyperText Markup Language, is the predominant markup language for web pages. It provides a means to create structured documents by denoting structural semantics for text such as headings, paragraphs, lists, links, quotes and other items. It allows images and objects to be embedded and can be used to create interactive forms (the HyperText Markup Language A markup language is a modern system for annotating a text in a way that is syntactically distinguishable from that text. The idea and terminology evolved from the "marking up" of manuscripts, i.e. the revision instructions by editors, traditionally written with a blue pencil on authors' manuscripts. Examples are typesetting instructions), HTTP The Hypertext Transfer Protocol is an Application Layer protocol for distributed, collaborative, hypermedia information systems, and web browsers A web browser is a software application for retrieving, presenting, and traversing information resources on the World Wide Web. An information resource is identified by a Uniform Resource Identifier and may be a web page, image, video, or other piece of content. Hyperlinks present in resources enable users to easily navigate their browsers to 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 The Internet Engineering Task Force develops and promotes Internet standards, cooperating closely with the W3C and ISO/IEC standards bodies and dealing in particular with standards of the TCP/IP and Internet protocol suite. It is an open standards organization, with no formal membership or membership requirements. All participants and managers are published Berners-Lee's RFC 1630: the first RFC In computer network engineering, a Request for Comments is a memorandum published by the Internet Engineering Task Force (IETF) describing methods, behaviors, research, or innovations applicable to the working of the Internet and Internet-connected systems that (in its non-normative text) acknowledged the existence of URLs and URNs, and, more importantly, defined a formal syntax for Universal Resource Identifiers — 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 In computer hypertext, a fragment identifier is a short string of characters that refers to a resource that is subordinate to another, primary resource. The primary resource is identified by a Uniform Resource Identifier , and the fragment identifier points to the subordinate resource. Typically, the fragment identifier is appended to the Uniform.

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^[4] and most of the parts of RFCs 1630 and 1738 relating to URIs and URLs in general were revised and expanded^{[by whom?]}. The new RFC changed the significance of the "U" in "URI": it came to represent "Uniform" rather than "Universal". The sections of RFC 1738 that summarized existing URL schemes migrated into a separate document.^[5] IANA The Internet Assigned Numbers Authority is the entity that oversees global IP address allocation, root zone management for the Domain Name System (DNS), media types, and other Internet Protocol related assignments. It is operated by the Internet Corporation for Assigned Names and Numbers, better known as ICANN keeps a registry of those schemes^[6]; RFC 2717 first described the procedure to register them.

In December 1999, RFC 2732 provided a minor update to RFC 2396, allowing URIs to accommodate IPv6 Internet Protocol version 6 is an Internet Protocol version which is designed to succeed IPv4, the first implementation which is still in dominant use currently[update]. It is an Internet Layer protocol for packet-switched internetworks. The main driving force for the redesign of Internet Protocol is the foreseeable IPv4 address exhaustion. IPv6 addresses. Some time later, a number of shortcomings discovered in the two specifications led to the development of a number of draft revisions under the title rfc2396bis. This community effort, coordinated by RFC 2396 co-author Roy Fielding Roy Thomas Fielding is an American computer scientist. He is one of the principal authors of the HTTP specification (RFC 2616), and a frequently-cited authority on computer network architecture, culminated in the publication of RFC 3986 in January 2005. This RFC, as of 2009^[update] the current version of the URI syntax recommended for use on the Internet, renders RFC 2396 obsolete. It does not, however, 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 August 2002, RFC 3305 pointed out that the term 'URL' has, despite its widespread use in the vernacular of the Internet-aware public at large, faded into near obsolescence. It now serves only as a reminder that some URIs act as addresses because they have schemes that imply some kind of network accessibility, regardless of whether systems actually use them for that purpose. 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.

On November 1, 2006, the W3C Technical Architecture Group published 'On Linking Alternative Representations To Enable Discovery And Publishing', 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.

The Semantic Web uses the HTTP URI scheme to identify both documents and concepts in the real world: this has caused confusion as to how to distinguish the two. The Technical Architecture Group of W3C (TAG) published an e-mail in June 2005 on how to solve this problem. The e-mail became known as the httpRange-14 resolution.^[7] To expand on this (rather brief) email, W3C published in March 2008 the Interest Group Note Cool URIs for the Semantic Web^[8]. This explains the use of content negotiation and the 303-redirect code in more detail.

URI reference

A URI reference is another type of string that represents a URI, and (in turn) represents the resource identified by that URI. Informal usage does not often maintain the distinction between a URI and a URI reference, but protocol documents should not allow for ambiguity.

A URI reference may take the form of a full URI, or just the scheme-specific portion of one, or even some trailing component thereof – even the empty string. An optional fragment identifier, preceded by #, may be present at the end of a URI reference. The part of the reference before the # indirectly identifies a resource, and the fragment identifier identifies some portion of that resource.

To derive a URI from a URI reference, software converts the URI reference to 'absolute' form by merging it with an absolute 'base' URI according to a fixed algorithm. 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. The base URI typically identifies the document containing the URI reference, although this can be overridden by declarations made within the document or as part of an external data transmission protocol. If the base URI includes a fragment identifier, it is ignored during the merging process. If a fragment identifier is present in the URI reference, it is preserved during the merging process.

Web document markup languages frequently use URI references to point to other resources, such as external documents or specific portions of the same logical document.

Uses of URI references in markup languages

• In HTML, the value of the src attribute of the img element is a URI reference, as is the value of the href attribute of the a or link element.
• In XML, the system identifier appearing after the SYSTEM keyword in a DTD is a fragmentless URI reference.
• In XSLT, the value of the href attribute of the xsl:import element/instruction is a URI reference; likewise the first argument to the document() function.

Examples of absolute URIs

• http://example.org/absolute/URI/with/absolute/path/to/resource.txt
• ftp://example.org/resource.txt
• urn:issn:1535-3613

Examples of URI references

• http://en.wikipedia.org/wiki/URI#Examples_of_URI_references ("http" specifies the 'scheme' name, "en.wikipedia.org" is the 'authority', "/wiki/URI" the 'path' pointing to this article, and "#Examples_of_URI_references" is a 'fragment' pointing to this section.)
• http://example.org/absolute/URI/with/absolute/path/to/resource.txt
• //example.org/scheme-relative/URI/with/absolute/path/to/resource.txt
• /relative/URI/with/absolute/path/to/resource.txt
• relative/path/to/resource.txt
• ../../../resource.txt
• ./resource.txt#frag01
• resource.txt
• #frag01
• (empty string)

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. The 'resolver' component in document processing software generally provides both services.

One can regard a URI reference as a same document reference: a reference to the document containing the URI reference itself. Document processing software can efficiently use its current representation of the document to satisfy the resolution of a same document reference without fetching a new representation. This is only a recommendation, and document processing software can alternatively use other mechanisms to determine whether to obtain a new representation.

The current URI specification as of 2009^[update], RFC 3986, defines a URI reference as a same document reference if, when resolved to absolute form, it equates exactly to the base URI in effect for the reference. Typically, the base URI is the URI of the document containing the reference. XSLT 1.0, for example, has a document() function that, in effect, implements this functionality. RFC 3986 also formally defines URI equivalence, which can be used^{[by whom?]} to determine that a URI reference, while not identical to the base URI, still represents the same resource and thus can be considered to be a same document reference.

RFC 2396 prescribed a different method for determining same document references; RFC 3986 made RFC 2396 obsolete, but RFC 2396 still serves as the basis of many specifications and implementations. This specification defines a URI reference as a same document reference if it is an empty string or consists of only the # character followed by an optional fragment.

Relation to XML namespaces

XML has a concept of a namespace, an abstract domain to which a collection of element and attribute names can be assigned. An XML namespace is identified by a name in the form of character string, which must adhere to the generic URI syntax. However, the namespace name is generally not considered^{[by whom?]} to be a URI because the 'URI-ness' of strings is, according to the URI specification, based on their intended use, not just their lexical components. A namespace name also does not necessarily imply any of the semantics of URI schemes; a namespace name beginning with 'http:', for example, likely has nothing to do with the HTTP protocol. XML professionals have debated this intensively on the xml dev electronic mailing list; some feel that a namespace name could be a URI, since the collection of names comprising a particular namespace could be considered^{[by whom?]} to be a resource that is being identified^{[by whom?]}, and since a version of the 'Namespaces in XML' specification says that the namespace name is a URI reference.^[9] But the consensus seems to suggest that a namespace name is just a string that happens to look like a URI, nothing more.

Initially, the namespace name could match the syntax of any non-empty URI reference, but an erratum to the 'Namespaces In XML Recommendation' later deprecated the use of relative URI references. A separate specification, issued for namespaces for XML 1.1, allows IRI references, not just URI references, to serve as the basis for namespace names.

To mitigate confusion that began to arise among newcomers to XML from the use of URIs (particularly HTTP URLs) for namespaces, a descriptive language called RDDL (Resource Directory Description Language) developed, though the specification of RDDL (http://www.rddl.org/) has no official standing and no relevant organization (such as W3C) has considered or approved it. An RDDL document can provide machine- and human-readable information about a particular namespace and about the XML documents that use it. Authors of XML documents were encouraged^{[by whom?]} to put RDDL documents in locations such that if a namespace name in their document somehow becomes de-referenced, then an RDDL document would be obtained, thus satisfying the desire among many developers for a namespace name to point to a network-accessible resource.

See also

References

1. ^ URI Planning Interest Group, W3C/IETF (21 September 2001). "URIs, URLs, and URNs: Clarifications and Recommendations 1.0". http://www.w3.org/TR/uri-clarification/. Retrieved 2009-07-27.
2. ^ Palmer, Sean B.. "The Early History of HTML". http://infomesh.net/html/history/early/. Retrieved 2009-04-30.
3. ^ "W3 Naming Schemes". W3. http://www.w3.org/History/19921103-hypertext/hypertext/WWW/Addressing/Addressing.html. Retrieved 2009-07-24. "The format of a hypertext name consists of the name of the naming sub-scheme to be used, then a name in a format particular to that sub-scheme, then an optional anchor identifier within the document. For example, the format is for all internet-based access methods: scheme : // host.domain:port / path / path # anchor"
4. ^ http://www.faqs.org/rfcs/rfc2396.html
5. ^ This separate document is not explicitly linked^{[by whom?]}, RFC 2717 and RFC 4395 point to the IANA registry as the official URI scheme registry.
6. ^ IANA registry of URI schemes
7. ^ The httpRange-14 resolution consists of three bullet points: see Fielding, Roy T. (2005-06-18). "[httpRange-14 Resolved"]. http://lists.w3.org/Archives/Public/www-tag/2005Jun/0039.html. Retrieved 2009-07-24. , and did not help much to reduce the confusion.
8. ^ http://www.w3.org/TR/cooluris/
9. ^ World Wide Web Consortium (1999-01-14). "Namespaces in XML" (PDF). W3C. http://www.aifb.uni-karlsruhe.de/Lehre/Sommer2004/ISWWW/w3c/xml_namespace_1_on_1.pdf. Retrieved 2009-09-14. "[Definition:] The attribute's value, a URI reference, is the namespace name identifying the namespace."

External links

• RFC 3986 / STD 66 (2005) – the current^[update] generic URI syntax specification
• RFC 2396 (1998) and RFC 2732 (1999) – obsolete, but widely implemented, version of the generic URI syntax
• RFC 1808 (1995) – obsolete companion to RFC 1738 covering relative URL processing
• RFC 1738 (1994) – mostly obsolete definition of URL schemes and generic URI syntax
• RFC 1630 (1994) – the first generic URI syntax specification; first acknowledgement of URLs in an Internet standard
• URI Schemes – IANA-maintained registry of URI Schemes
• URI Working Group – coordination center for development of URI standards
• Architecture of the World Wide Web, Volume One, §2: Identification – by W3C
• Example of discussion about names and addresses
• W3C materials related to addressing
• W3C URI Clarification
• What's a URI and why does it matter? (2008) - from W3C
• The Self-Describing Web (2008) - from W3C

Categories: Semantic Web | URI scheme

See Also:

What Links Here:

• Home

Recently Viewed Pages:

• Home
• Web Browser: Blogs
• Computers: Software: Internet: Clients: WWW: Browsers: Firefox: Directory
• Universal Edit Button: Blogs
• Cascading Style Sheets: News
• Encyclopedia: Konqueror
• Computers: Software: Internet: Clients: WWW: Browsers: Internet Explorer: Directory
• World Wide Web: Encyclopedia
• Web Page: Encyclopedia
• Safari (Web Browser): Encyclopedia

Most Popular Pages:

• Cascading Style Sheets: News
• Web Browser: Blogs
• Encyclopedia: Konqueror
• NPAPI
• Referrers
• Midori (Browser)
• Uniform Resource Identifier: Web Search
• File Fippo Download: Videos
• Downloads
• Midori (Browser): Videos

Related 'Uniform Resource Identifier' Searches: