# Re: URLs, URIs, and references

Mitra (mitra@pandora.sf.ca.us)
Wed, 26 May 1993 08:56:45 PDT

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Dirk Herr-Hoyman: "Re: URLs, URIs, and references"
- Previous message: Peter Deutsch: "Re: URLs, URIs, and references"

    From: mitra@pandora.sf.ca.us (Mitra)

    Date: Wed, 26 May 1993 08:56:45 PDT

    In-Reply-To:  "Chris Weider" <clw@merit.edu>

    To: clw@merit.edu, uri@bunyip.com

    Subject: Re: URLs, URIs, and references

    Message-Id:  <9305260856.aa27918@pandora.sf.ca.us>

Agreed Chris, I still have lots of questions about how a URN scheme is going
to work in practice. For example is a WWW anchor, or a gopher SelectString going
to give you a URN and a URL for every pointer? Will there be a deterministic
and not too slow way of turning a URN into a URL. For example if the URN
is URN:ISOC:12345::6789::: then I presume there is either the approach
of query 1 -> ISOC returning the addresses of a server for ISOC registered
publisher 12345 and then a query to that address for the URL of 6789 and
then a query to fetch that URL. That could get very slow, and liable to
reliability problems (if any of the servers are down the query fails).

Dont get me wrong, I'm totally in favour of the URN/URL/URC structure being
proposed, just worried that "rough consensus" isnt enough, we need "working
code".

Do you think that now would be a good time to start work on how these things
get passed around together, in order to test out URL's I need a way to
pass a Type with them?

- Mitra

- Next message: Dirk Herr-Hoyman: "Re: URLs, URIs, and references"
- Previous message: Peter Deutsch: "Re: URLs, URIs, and references"