From: "us4rmc::raisch@internet.com"@boco.enet.dec.com
Message-Id: <9406082323.AA03986@enet-gw.pa.dec.com>
Date: Wed, 8 Jun 94 16:23:42 PDT
To: mike@boco.enet ("carifio <mike@boco.enet>")
Subject: Re: some questions on the March 94 Masinter&Sollins URN reqs draft spec
On Wed, 8 Jun 1994, Mike Carifio wrote:
> 2) Suppose a naming authority resolves a URN to have two (or more)
> URLs. Is it implied that each of the resources are an ``equally good''
> resource for this URN? For example URN u1 might map to <url:http://foo.com>
> and <url:ftp://foo.com>, indicating that the user can choose with
> scheme to go with. Am I reading too much into this?
Define "equally good", please?
This speaks to a truely enormous issue I have been screaming myself blue
in the face about for over a year now: What questions do we need to ask to
be able to make an informed retrieval decision?
The issues at hand include those surrounding the usability of the
retrieved resource from the customer's viewpoint, the best use of the
server from which the resource is retrieved and the best use of the
networks between the producer/repository and the consumer/customer.
So, when you come up with a definition for the aforementioned term, I
would be very interested in hearing about it. Thanks.
-- </rr> Rob Raisch, The Internet Company
% ====== Internet headers and postmarks (see DECWRL::GATEWAY.DOC) ======
% Received: from inet-gw-3.pa.dec.com by us4rmc.pko.dec.com (5.65/rmc-22feb94) id AA11425; Wed, 8 Jun 94 19:26:42 -040
% Received: from internet.com by inet-gw-3.pa.dec.com (5.65/27May94) id AA25749; Wed, 8 Jun 94 15:08:26 -070
% Received: by internet.com (5.65c/Spike-2.1) id AA27913; Wed, 8 Jun 1994 14:59:06 -070
% Date: Wed, 8 Jun 1994 14:52:04 -0700 (PDT)
% From: "Rob Raisch, The Internet Company" <raisch@internet.com>
% Subject: Re: some questions on the March 94 Masinter&Sollins URN reqs draft spec
% To: Mike Carifio <boco::carifio>
% Cc: boco::url
% In-Reply-To: <9406081910.AA29120@enet-gw.pa.dec.com>
% Message-Id: <Pine.3.85.9406081404.A10791-0100000@hmmm>
% Mime-Version: 1.0
% Content-Type: TEXT/PLAIN; charset=US-ASCII