From: ccoprmm@oit.gatech.edu (Michael Mealling)
Message-Id: <199310281626.AA22468@oit.oit.gatech.edu>
Subject: Re: options, not nesting?
To: M.T.Hamilton@lut.ac.uk (Martin Hamilton)
Date: Thu, 28 Oct 93 12:26:02 EDT
In-Reply-To: <199310281013.KAA11027@lust.lut.ac.uk>; from "Martin Hamilton" at Oct 28, 93 10:13 am
Martin Hamilton said this:
> / Rather than making URNs and URLs and URCs and URMs all different
> / things, one of which contains the other all nested, how about just
> / allowing various information to be optional?
> / [...]
>
> This sounds rather like an IETF resource template, let's say with
> references to URNs, URLs, and future URIs being by means of the
> fabled "URI:" attribute. Is anyone unhappy with this scenario?
Yes. I even wrote a paper about it:
<http://www.gatech.edu/urm.paper>
> If a search returns a template with URLs in, they may be used
> directly to gain access to the resource. URNs would lead to a
> template which connects them with URLs.
>
> I think this means the whole URM, URC, ... shebang is rendered
> unnecessary, but am willing to be convinced otherwise!
In my paper I call that template a URTemplate. I added URMs as an allowed
data element in the Template because that allows you to send around
your meta-information and other stuff with the URNs and URLs.
-MM
-- ------------------------------------------------------------------------------ Michael Mealling ! Hypermedia WWW, WAIS, and gopher will be Georgia Institute of Technology ! here soon via MIME. Your view of the Michael.Mealling@oit.gatech.edu ! internet is about to change completely!