| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Uniform Resource Identifiers, Locators and Names (URIs, URLs and URNs): Overview, History, Significance and Standards (Page 2 of 3) URI Categories URIs are in fact a general purpose method for referring to many kinds of TCP/IP resources. They are currently divided into two primary categories based on how they describe a resource:
The difference between a URL and a URN is that the former is much more specific and oriented around how to access a resource, while the latter is more abstract and designed more to identify what the resource is than describe how to get it. Giving someone a URL is like giving them directions to find a book, as follows: Take the train to Albuquerque, then Bus #11 to 41 Albert Street, a red brick house owned by Joanne Johnson. The book you want is the third from the right on the bottom of the bookshelf on the second floor. A URN is more like referring to a book using its International Standard Book Number (ISBN); it uniquely identifies the book regardless of where the book may be located, and doesn't tell you how to access it. (In fact, ISBNs are one of the identification systems used with URNs.) While URLs and URNs are theoretical peers, in practice, URLs are used far more than URNs. In fact, URLs are so dominant that most people have never even heard of URIs or URNs. The reason is that even though the example above suggests that URNs are more natural than URLs, URLs are easier to use in practicethey provide the information needed to access a resource, and without being able to access a resource, simply knowing how to identify it is of limited value. URNs are an attractive concept because they identify a resource without tying it to a specific access mechanism or location. However, the implementation of URNs requires some means of tying the permanent identifier of a resource to where it is at any given moment, which is not a simple task. For this reason, URNs and the methods for using them have been in development for a number of years, while URLs have been in active use all that time. While URLs began with the Web and most URLs are still used with HTTP, they can and do refer to resources that are accessed using many other protocols, such as FTP and Telnet. Again here, the compactness of URIs makes them very powerful; with a URL, we can use one string to tell a program to retrieve a file using FTP. This replaces the complete FTP process of starting an FTP client, establishing a session, logging in and issuing commands.
Home - Table Of Contents - Contact Us The TCP/IP Guide (http://www.TCPIPGuide.com) Version 3.0 - Version Date: September 20, 2005 © Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved. Not responsible for any loss resulting from the use of this site. |