Re: UR Accessors

Paul Hoffman <ietf-lists@proper.com> Thu, 15 June 1995 05:08 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa20293; 15 Jun 95 1:08 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa20289; 15 Jun 95 1:08 EDT
Received: from services.Bunyip.COM by CNRI.Reston.VA.US id aa25742; 15 Jun 95 1:08 EDT
Received: (from daemon@localhost) by services.bunyip.com (8.6.10/8.6.9) id XAA26691 for uri-out; Wed, 14 Jun 1995 23:32:38 -0400
Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.6.10/8.6.9) with SMTP id XAA26685 for <uri@services.bunyip.com>; Wed, 14 Jun 1995 23:32:36 -0400
Received: from proper.proper.com by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA13477 (mail destined for uri@services.bunyip.com); Wed, 14 Jun 95 23:33:23 -0400
Received: from [165.227.40.35] (user12.znet.com [165.227.40.12]) by proper.proper.com (8.6.11/8.6.5) with SMTP id UAA00732; Wed, 14 Jun 1995 20:33:04 -0700
X-Sender: ietflist@proper.com
Message-Id: <v02120c23ac05540df039@[165.227.40.35]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Wed, 14 Jun 1995 20:35:52 -0700
To: Daniel LaLiberte <liberte@ncsa.uiuc.edu>
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Paul Hoffman <ietf-lists@proper.com>
Subject: Re: UR Accessors
Cc: uri@bunyip.com
X-Orig-Sender: owner-uri@bunyip.com
Precedence: bulk

At 7:06 AM 6/14/95, Daniel LaLiberte wrote:
>We need a new name for a URI concept that has been bouncing around
>under the name "URC0".  A URC0 has been thought of as a set of URLs
>(previously called a list of URLs) where any one of the URLs would do
>as the identifier of the resource.  I want to generalize this further,
>and distinguish it from the other URC issues.

Please note that the URC0 draft (draft-ietf-uri-urc-trivial-00) describes a
URC0 response as a list of URLs, *each of which can have metainformation*.
That's much more than "a set of URLs".

Further, the URLs are not equivalent: they would not all "do as the
identifier of the resource." A URC can be for a multi-volume work. For
example, one URC0-style URC for an encyclopedia could contain one URL for
each volume. In this case, the metainformation for each URL would become
quite important, no?

>So in conclusion, I am suggesting we need a new name for the concept
>of accessing resources.  This is not a URN, and not necessarily a
>single URL, and not as much as general metadata.

I'm not sure why it is "not as much as general metadata". If the metadata
is easy to ignore, why not include it for those who want to see it? Many
people (myself included) find metainformation very valuable when deciding
whether or not to access a resource (particularly one that may cost money
or time). It sounds like you're proposing a "list of URLs" kind of idea,
but I see no reason not to let publishers add metadata to such a list if it
doesn't get in the way of the people who only want the location-type
information.

--Paul Hoffman
--Proper Publishing