Re: URI-protocol mapping (was Re: How to add new "protocols" ?)
touch@isi.edu Thu, 20 February 1997 19:33 UTC
Received: from cnri by ietf.org id aa23010; 20 Feb 97 14:33 EST
Received: from services.Bunyip.Com by CNRI.Reston.VA.US id aa19276; 20 Feb 97 14:33 EST
Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id OAA09961 for uri-out; Thu, 20 Feb 1997 14:04:47 -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 OAA09956 for <uri@services.bunyip.com>; Thu, 20 Feb 1997 14:04:44 -0500 (EST)
From: touch@isi.edu
Received: from zephyr.isi.edu by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA25261 (mail destined for uri@services.bunyip.com); Thu, 20 Feb 97 14:04:42 -0500
Received: from ash.isi.edu by zephyr.isi.edu (5.65c/5.61+local-23) id <AA25655>; Thu, 20 Feb 1997 11:04:41 -0800
Date: Thu, 20 Feb 1997 11:04:39 -0800
Posted-Date: Thu, 20 Feb 1997 11:04:39 -0800
Message-Id: <199702201904.AA04605@ash.isi.edu>
Received: by ash.isi.edu (5.65c/4.0.3-6) id <AA04605>; Thu, 20 Feb 1997 11:04:39 -0800
To: touch@isi.edu, liberte@ncsa.uiuc.edu
Subject: Re: URI-protocol mapping (was Re: How to add new "protocols" ?)
Cc: uri@bunyip.com
X-Auto-Sig-Adder-By: faber@isi.edu
Sender: owner-uri@bunyip.com
Precedence: bulk
> > I've been using URL as the last step in that chain. > > So for you a URN necessarily maps to a URL or perhaps another URN or a > description of the resource, but never to the resource itself. I > don't think that restriction is necessary. At some point you must know who you're talking with what protocol to use If you return that in a record from a URN server, that's OK too, but that's what I've been calling a URL. A URL is a context-independent absolute identifier. > Indirection is necessary to get the mobility that names allow, but > indirection is possible also for URLs. A URL is symbolic too. We just disagree on this. I consider a URL a collapsed version of a URN-DNS response. Everything else is a URN to me. The value in stating it this way is that, in the end, you must know the two things above. > Certainly one must eventually get down to lower level primitives. > But both URNs and URLs can do that, unless you restrict that URNs > can not do that. That's what I've been doing - the point is that, at some level, you need the lowest level primitives. What do you call them, if not URLs? Joe ---------------------------------------------------------------------- Joe Touch - touch@isi.edu http://www.isi.edu/~touch/ ISI / Project Leader, ATOMIC-2, LSAM http://www.isi.edu/atomic2/ USC / Research Assistant Prof. http://www.isi.edu/lsam/
- 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.