>From RFC 2396
A URI can be further classified as a locator, a name, or both. The term
Uniform Resource Locator (URL) refers to the subset of URI that identify
resources via a representation of their primary access mechanism (e.g.,
their network "location"), rather than identifying the resource by name or
by some other attribute(s) of that resource. The term Uniform Resource Name
(URN) refers to the subset of URI that are required to remain globally
unique and persistent even when the resource ceases to exist or becomes
unavailable.
The following examples illustrate URI that are in common use.
ftp://ftp.is.co.za/rfc/rfc1808.txt
-- ftp scheme for File Transfer Protocol services
gopher://spinaltap.micro.umn.edu/00/Weather/California/Los%20Angeles
-- gopher scheme for Gopher and Gopher+ Protocol services
http://www.math.uio.no/faq/compression-faq/part1.html
-- http scheme for Hypertext Transfer Protocol services
mailto:[EMAIL PROTECTED]
-- mailto scheme for electronic mail addresses
news:comp.infosystems.www.servers.unix
-- news scheme for USENET news groups and articles
telnet://melvyl.ucop.edu/
-- telnet scheme for interactive services via the TELNET Protocol
The URL syntax was designed for unambiguous reference to network resources
and extensibility via the URL scheme. However, as URL identification and
usage have become commonplace, traditional media (television, radio,
newspapers, billboards, etc.) have increasingly used abbreviated URL
references. That is, a reference consisting of only the authority and path
portions of the identified resource, such as
www.w3.org/Addressing/
or simply the DNS hostname on its own. Such references are primarily
intended for human interpretation rather than machine, with the assumption
that context-based heuristics are sufficient to complete the URL (e.g., most
hostnames beginning with www are likely to have a URL prefix of http://).
Although there is no standard set of heuristics for disambiguating
abbreviated URL references, many client implementations allow them to be
entered by the user and heuristically resolved. It should be noted that such
heuristics may change over time, particularly when new URL schemes are
introduced.
PACS
------Original Message------
From: "C.S.Sriram" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Sent: January 28, 2000 4:37:41 AM GMT
Subject: Re: URI versus URL
If you could go to http://whatis.com u can find the definition of URI
URI is Universal Resource Identifier.
A URI (Uniform Resource Identifier; pronounced YEW-AHR-EYE) is the way you
identify any of those points of content, whether it be a page of text, a
video or sound clip, a still or animated image, or a program.The most common
form of URI is the Web page address, which is a particular form or subset of
URI called a Uniform Resource Locator (URL).
Thanks and Regards,
Sriram.C.S
Associate Consultant
HCL Infosystems Ltd.
43/44, Thapar House,
Montieth Road
Egmore
Chennai - 600008
> -----Original Message-----
> From: A mailing list for discussion about Sun Microsystem's Java Servlet
> API Technology. [mailto:[EMAIL PROTECTED]]On Behalf Of Milt
> Epstein
> Sent: Thursday, January 27, 2000 12:56 PM
> To: [EMAIL PROTECTED]
> Subject: Re: URI versus URL
>
>
> On Wed, 26 Jan 2000, Maxime Poulin wrote:
>
> > Hi all,
> >
> > I've been seeing in some servlet books the term URI which
> > was not to be misinterpreted as URL... Could someone explain me what
> > is a URI, and the difference between a URI and a URL ?
>
> Reading the comments in the JSDK source files (or their javadocs), it
> looks like the way they use it, URL is the entire thing with scheme,
> server, and port, while URI is only the stuff after that.
>
> IIRC, "URL" is "Uniform Resource Locator". Not sure what the 'I' in
> "URI" is.
>
> Milt Epstein
> Research Programmer
> Software/Systems Development Group
> Computing and Communications Services Office (CCSO)
> University of Illinois at Urbana-Champaign (UIUC)
> [EMAIL PROTECTED]
>
> __________________________________________________________________
> _________
> To unsubscribe, send email to [EMAIL PROTECTED] and include
> in the body
> of the message "signoff SERVLET-INTEREST".
>
> Archives: http://archives.java.sun.com/archives/servlet-interest.html
> Resources: http://java.sun.com/products/servlet/external-resources.html
> LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
>
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
.................................................................................
iWon.com http://www.iwon.com why wouldn't you?
.................................................................................
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
