To: moore@cs.utk.edu
In-Reply-To: moore@cs.utk.edu's message of Fri, 15 Apr 1994 02:06:46 -0700 <94Apr15.020702pdt.2767@golden.parc.xerox.com>
Subject: Re: URN and citations
From: Larry Masinter <masinter@parc.xerox.com>
Message-Id: <94Apr15.031524pdt.2760@golden.parc.xerox.com>
Date: Fri, 15 Apr 1994 03:15:11 PDT
Keith, thanks for the lucid analysis of the issue of "sameness" and
the requirements for LIFNs. At this point, to make progress, let me
ask which alternatives you think we should follow:
1) We (Karen and I) should modify `URN Requirements' document to
reflect your concerns. If you think we should do this, please
identify how it should change.
2) You produce an alternative requirements document for URNs. Using
some or most of our wording, but modified to meet your concerns.
3) We call the thing you want to use something other than a URN. I
don't like this much. At some point, I liked the idea of just having
something ELSE which we called a `LIFN', but that seems silly to me at
the moment.
4) we call the whole thing off and wait for some grand architectural
vision. I'm not serious about this one, or, to put it more strongly,
I would be seriously opposed to this.
I thin we need to focus our discussion and produce requirement and
design documents. I definitely don't want to get into a mode where we
abandon the URN requirements and design while waiting for a grander
set of architectural requirements, even though the naming scheme
should serve that grander scheme.
I'd suggest 2; if the URI working group likes your counter-proposal
better, we can abandon the Sollins/Masinter version and go with the
Moore version.