Re: URI-protocol mapping
Dan Connolly <connolly@w3.org> Fri, 21 February 1997 18:54 UTC
Received: from cnri by ietf.org id aa16403; 21 Feb 97 13:54 EST
Received: from services.Bunyip.Com by CNRI.Reston.VA.US id aa19792; 21 Feb 97 13:54 EST
Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id NAA04884 for uri-out; Fri, 21 Feb 1997 13:15:19 -0500 (EST)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.8.5/8.8.5) with SMTP id NAA04879 for <uri@services.bunyip.com>; Fri, 21 Feb 1997 13:15:16 -0500 (EST)
Received: from mintaka.lcs.mit.edu by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA04625 (mail destined for uri@services.bunyip.com); Fri, 21 Feb 97 13:15:15 -0500
Received: from beach.w3.org by MINTAKA.LCS.MIT.EDU id aa04727; 21 Feb 97 12:56 EST
Message-Id: <330DE1C5.13593C7F@w3.org>
Date: Fri, 21 Feb 1997 11:56:21 -0600
From: Dan Connolly <connolly@w3.org>
Organization: World Wide Web Consortium
X-Mailer: Mozilla 3.01 (X11; I; Linux 2.0.18 i586)
Mime-Version: 1.0
To: Daniel LaLiberte <liberte@ncsa.uiuc.edu>
Cc: touch@isi.edu, uri@bunyip.com
Subject: Re: URI-protocol mapping
References: <199702201904.AA04605@ash.isi.edu> <199702211616.KAA18104@void.ncsa.uiuc.edu>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-uri@bunyip.com
Precedence: bulk
Daniel LaLiberte wrote: > BTW, people interested in this subject should read: > > Decoupling the URL Scheme from the Transport Protocol > http://www.ansa.co.uk/ANSA/ISF/decoupling.html Yes, that's an excellent reference. Note that it echoes the original design principles of the web: ------------- http://www.w3.org/pub/WWW/DesignIssues/DosDonts.html timbl, circa 1990 Short UDIs UDIs should be kept short and devoid of information that indicates the mechanism by which the document is retrieved. (in the theoretically clean implementation, the ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ protocol information should not be present). ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The motivation is that when a document changes implementation (e.g. from being a file to being part of a data base, or by moving to a different location, the anchors pointing to it should not have to change. ------------- Dan
- URI-protocol mapping (was Re: How to add new "pro… Daniel LaLiberte
- Re: URI-protocol mapping (was Re: How to add new … touch
- Re: URI-protocol mapping (was Re: How to add new … Daniel LaLiberte
- Re: URI-protocol mapping (was Re: How to add new … touch
- Re: URI-protocol mapping (was Re: How to add new … Daniel LaLiberte
- Re: URI-protocol mapping (was Re: How to add new … touch
- Re: URI-protocol mapping (was Re: How to add new … Roy T. Fielding
- Re: URI-protocol mapping (was Re: How to add new … Dan Connolly
- Re: URI-protocol mapping (was Re: How to add new … Ron Daniel Jr.
- Re: URI-protocol mapping (was Re: How to add new … Dan Connolly
- Re: URI-protocol mapping (was Re: How to add new … touch
- Re: URI-protocol mapping (was Re: How to add new … Ron Daniel Jr.
- Re: URI-protocol mapping Dan Connolly
- Re: URI-protocol mapping (was Re: How to add new … Dan Connolly
- Re: URI-protocol mapping Daniel LaLiberte
- Re: URI-protocol mapping (was Re: How to add new … Ron Daniel Jr.