Naming and Addressing: URLs

This is the overview materials related to the W3C Addressing Activity, one of the activities of the W3C Architecture domain.

Learning About URIs

URIs, or Uniform Resouce Identifiers, are the technology for naming and addressing resources (pages, services, documents, etc.) on the web. It is an extensible technology: there are a number of existing addressing schemes, and more may be incorporated over time.

A Beginner's Guide to URLs
The classic intro to URLs, by The NCSA Mosaic team
Schemes
http:, ftp:, irc:, etc. Need to look one up? Thinking of suggesting a new one?

UR* Terms

The basic picture looks like this:

	 _______________________________________________________
	|	 _________________                              |
	|	|  ftp:		 |                              |
	|	|  gopher:	 |                              |
	|	|  http:       _______________                  |
	|	|  etc	      |  |  urn:      |                 |
	|	|_____________|__|  fpi: ?    |                 |
	|		URLs  |               |                 |
	|		      |_______________|                 |
	|                             URNs                      |
	|_______________________________________________________|
                               URIs
URI
Uniform Resource Idenifier. The generic set of all names/addresses that are short strings that refer to resources. Full definition is given in the URI spec.
URL
Uniform Resource Locator. The set of URI schemes that have explicit instructions on how to access the resource on the internet. Full definition is given in the URL specification.
URN
Uniform Resource Name.
  1. An URI that has an institutional commitment to persistence, availability, etc. Note that this sort of URI may also be a URL. See, for example, PURLs.
  2. A particular scheme which is currently (1991,2,3,4,5,6,7) under development in the IETF (see discussion forums below), which should provide for the resolution using internet protocols of names which have a greater persistence than that currently assiated with internet host names or organizations. When defined, a URN(2) will be an example of a URI.
URC
Uniform Resource Citation, or Uniform Resource Characteristics. A set of attribute/value pairs describing a resource. Some of the values may be URIs of various kinds. Others may include, for example, authorship, publisher, datatype, date, copyright status and shoe size. Not normally discussed as a short string, but a set of fields and values with some defined free formatting.

W3C has developed the PICS technology for resource description.

See also: an index of web architecture terms, a glossary of web terms.

Timeline: News, Events, Publications, and History

This is a publication history, or bibliography collected from IETF documents and W3C Technical Reports as well as a record of events.

April 1997
38th IETF: URN WG meeting (research notes)
January 1997
W3C Addressing Activity Statement updated for W3C Advisory Committee meeting [members only]
December 1996
San Jose IETF -- URL BOF
Spring 1996
2nd issue of W3J, Key Specifications of the World Wide Web includes URI specs.
July 1995
IETF URI Working Group is closed.
June 1995
RFC 1808 released as Proposed Standard

Relative Uniform Resource Locators R. Fielding

Abstract:

... When embedded within a base document, a URL in its absolute form may contain a great deal of information which is already known from the context of that base document's retrieval, including the scheme, network location, and parts of the url-path. In situations where the base URL is well-defined and known to the parser (human or machine), it is useful to be able to embed URL references which inherit that context rather than re-specifying it in every instance.

This one is both authoritative (i.e. it's been through the IETF proposed standard process) and accurate on the matter of the syntax of URLs. Its grammar is complete and consistent, and there are several clarifying examples.

On the other hand, it does not discuss any of the actual URL schemes (such as HTTP, FTP, ...)

December 1994
(RFC 1738) released as Proposed Standard:

Uniform Resource Locators (URL) T. Berners-Lee, L. Masinter, M. McCahill

Abstract:

This document specifies a Uniform Resource Locator (URL), the syntax and semantics of formalized information for location and access of resources via the Internet.

This one is ratified as an IETF proposed standard, and it discusses each of the URL schemes (known at that time), but its grammar has some mistakes, and it doesn't cover several aspects of URL syntax, such as relative URLs and fragment identifiers

December 1994
RFC 1737, Informational

Functional Requirements for Uniform Resource Names , K. Sollins, L. Masinter

Abstract:

This document specifies a minimum set of requirements for a kind of Internet resource identifier known as Uniform Resource Names (URNs). ...
June 1994
RFC 1630, Informational, is released:

Universal Resource Identifiers in WWW: A Unifying Syntax for the Expression of Names and Addresses of Objects on the Network as used in the World-Wide Web T. Berners-Lee.

This documents the designer's intent, before it was revised by the standards process. It was written by Tim Berners-Lee, but has only informational status in the IETF. It discusses all aspects of URLs (relative, etc.) though it has some mistakes in the grammar etc.
March 94
IETF URI working group is formed
1991
Tim Berners-Lee's original writings on Document Naming, part of Design Issues for the Web

See also:

Discussion Forums: How Do I Get Involved?

www-talk
A mailing list for technical discussion of web architecture and technology, with a hypertext archive (now searchable! Thanks EIT guys!)
IETF Working Group
This is where URL standardization used to takes place.

The area director for the IETF Applications Area maintains some notes on URL schemes

Roy Fielding maintains a URI WG Archive, and there is an archive of the uri mailing list.

URN WG
archive

You might also be interested in the discussion of extended fragement identifiers for XML and the issue of internationalization of URLs.

If you are new to the IETF, you should probably do some background reading. I recommend:

Research Notebook: Recommended Reading

IETF - Uniform Resource Identifiers (URI) Working Group
by Roy Fielding.
BIBLINK - Work Package 2 - Other Resources
Decoupling the URL Scheme from the Transport Protocol
an idea from TimBL's design issues, independently discovered?
Hypernews on URNs
By Daniel LaLiberte at NCSA. Also, hypernews on URCs.
The Augmented Knowledge Workshop, Engelbart et. al., 1973
URI background
by Ron Daniel
Stable Network File URLs as a Mechanism for Uniform Naming
by Terry Winograd

I found a draft of this dated Dec 1993, but it has since (Apr 97) gone.

Research Notebook: Works In Progress

DesignIssues: more on Axioms of Web Architecture, Myth of Naming and Addressing, etc.
Automated Link Maintenance
Catalog Numbers
URIs for publishing: URNs, Catalog numbers, citations...
Catalogs: Resource Description and Discovery
notes on PICS metadata infrastructure for resource description and catalogs
Quality of Service
on the tension between reliability and scalability
the "me llamo" link
idea: a link type where a document says "I call myself X". In combination with a back-link service, it's a nifty URN idea.


Dan Connolly
last revised $Author: connolly $ on $Date $
Created 1993 by TimBL