Re: Hypertext::non-Hypertext not URL::URN
Al Gilman <asgilman@access.digex.net> Fri, 02 January 1998 22:39 UTC
Delivery-Date: Fri, 02 Jan 1998 17:39:58 -0500
Return-Path: owner-uri@Bunyip.Com
Received: from ns.cnri.reston.va.us (cnri [132.151.1.1]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id RAA07817 for <ietf-archive@ietf.org>; Fri, 2 Jan 1998 17:39:58 -0500 (EST)
Received: from services.bunyip.com (services.Bunyip.Com [192.77.55.2]) by ns.cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id RAA10330; Fri, 2 Jan 1998 17:42:47 -0500 (EST)
Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id RAA20913 for uri-out; Fri, 2 Jan 1998 17:29:32 -0500 (EST)
Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id RAA20904 for uri-in; Fri, 2 Jan 1998 17:29:21 -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 ESMTP id RAA20895 for <uri@services.bunyip.com>; Fri, 2 Jan 1998 17:29:09 -0500 (EST)
Received: (from daemon@localhost) by mocha.bunyip.com (8.8.5/8.8.5) id RAA25420 for uri@services; Fri, 2 Jan 1998 17:29:08 -0500 (EST)
Received: from access2.digex.net (access2.digex.net [205.197.245.193]) by mocha.bunyip.com (8.8.5/8.8.5) with ESMTP id RAA25415; Fri, 2 Jan 1998 17:29:03 -0500 (EST)
Received: (from asgilman@localhost) by access2.digex.net (8.8.4/8.8.4) id RAA00115; Fri, 2 Jan 1998 17:29:29 -0500 (EST)
From: Al Gilman <asgilman@access.digex.net>
Message-Id: <199801022229.RAA00115@access2.digex.net>
Subject: Re: Hypertext::non-Hypertext not URL::URN
To: masinter@parc.xerox.com
Date: Fri, 02 Jan 1998 17:29:29 -0500
Cc: michaelm@rwhois.net, paf@swip.net, fielding@kiwi.ics.uci.edu, harald.t.alvestrand@uninett.no, moore@cs.utk.edu, uri@Bunyip.Com, urn-ietf@Bunyip.Com
In-Reply-To: <34AD297F.15D39C63@parc.xerox.com> from Larry Masinter at "Jan 2, 98 09:53:03 am"
X-Mailer: ELM [version 2.4ME+ PL15 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Sender: owner-uri@Bunyip.Com
Precedence: bulk
to follow up on what Larry Masinter said: > > I think you've made an important point that I don't want to > get lost. The syntax forms that are controversial > (fragment identifiers, relative forms, query syntax) > are part of the application of HYPERTEXT. > > In fact, whether or not you want those forms seems to depend > entirely on whether or not you think you're doing hypertext. > This is an interesting idea to pursue, but not credible in the strong form you stated. If I were on the road wanting to find the nearest IPP accessible Braille embosser with a courier delivery option, I believe this could well wind up as a resource-discovery query involving something much like the ?parm-list familiar in URLs. Not all of the functions you reference are limited to HyperText applications. But one can, for the purpose of analysis and understanding, break out a lattice of classes of [names or identifiers] with longer and shorter sets of "what you can do with it" attached to the class. >From the naming perspective, the paramount characteristic is that the identifier contains a sufficient key (attribute cluster). The ability to abbreviate [for relative forms] in selected contexts [where a document context or other basis for establishing a BASE environment characteristic exists] and to parse by certain methods are introduced lower down in the class web, in more concrete "derived" classes. ["lower" here is dependent on having adopted a "naming perspective."] The difference between an URL view and an URN view of URIs could be summarized in terms of which of the following failure modes you are more concerned to avoid: - The identified resource exists, but you don't get it. -- URL cares first to avoid this - You get a resource, but it is not what you intended. -- URN cares first to avoid this -- Al Gilman
- Hypertext::non-Hypertext not URL::URN Larry Masinter
- Re: Hypertext::non-Hypertext not URL::URN Al Gilman
- Re: Hypertext::non-Hypertext not URL::URN Roy T. Fielding