Message-Id: <9305252106.AA05265@expresso.bunyip.com>
From: Peter Deutsch <peterd@bunyip.com>
Date: Tue, 25 May 1993 17:06:50 -0400
In-Reply-To: Peter Svanberg's message as of May 25, 20:32
To: Peter Svanberg <psv@nada.kth.se>, "Chris Weider" <clw@merit.edu>
Subject: Re: URN contents
To continue on my URL crusade...
[ You wrote: ]
. . .
> (In URLs, on the other hand, it must - in some way - be possible to
> use *any* character used in a culture if it should have any chance of
> being used - internally - in that culture. I'll return to that.)
Actually, this is an arguement for allowing only the
server which must respond to a URL to generate it, and for
treating it as an opaque 7 bit (no, 8 aiiiieeeeeee! <plop>) string.
I am really starting to think of these things as much like
those Gopher selector strings. Such strings _can_ be file
pathnames, but they could just as easily (to the user) be
randomly generated hash values. I think this is important.
Now, we can have structure to them, but should the user have
to know what it is?
Dunno...
- peterd
--
------------------------------------------------------------------------------
Peter Deutsch, (514) 875-8611 (phone)
Bunyip Information Systems Inc. (514) 875-8134 (fax)
<peterd@bunyip.com>
"Charging for information is not a crime, any more than charging for food is
a crime. On the other hand, I agree that letting people _starve_ is a crime."
------------------------------------------------------------------------------