Re: What URIs are and are not.

John C Klensin <KLENSIN@infoods.mit.edu>
Date: Tue, 09 Nov 1993 08:18:41 -0500 (EST)
From: John C Klensin <KLENSIN@infoods.mit.edu>
Subject: Re: What URIs are and are not.
In-reply-to: <9311091028.AA08692@www3.cern.ch>
To: timbl@nxoc01.cern.ch
Cc: Erik.Huizer@surfnet.nl, uri@bunyip.com, www-talk@nxoc01.cern.ch
Message-id: <752851121.120215.KLENSIN@INFOODS.UNU.EDU>
X-Envelope-To: timbl@NXOC01.CERN.CH, www-talk@NXOC01.CERN.CH
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT
Mail-System-Version: <MultiNet-MM(330)+TOPSLIB(156)+PMDF(4.2)@INFOODS.UNU.EDU>
Tim,
   In the hope that adding another AD to this discussion will clarify,
rather than further muddy the waters, let me try to briefly summarize
what I (we) said in Houston.

To advance the URL document, we  are going to need  a clear statement of
what the WG intends it to be used for, ideally stated in terms of
functional requirements.  My personal preference is that we end up  with
two documents, so that the functional requirements/rationale  can remain
very stable while the URL doc evolves as it passes along the standards
track.  But that is just a preference; the WG should do what it thinks
best.  

I expect that this document will be somewhat different than it would
have been a year or 18 months ago: we've all learned things from the
last months of discussions and examination of different requirements.

   john