Re: revised "generic syntax" internet draft

Larry Masinter <masinter@parc.xerox.com> Thu, 17 April 1997 04:25 UTC

Received: from cnri by ietf.org id aa15622; 17 Apr 97 0:25 EDT
Received: from services.Bunyip.Com by CNRI.Reston.VA.US id aa01555; 17 Apr 97 0:25 EDT
Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id AAA05212 for uri-out; Thu, 17 Apr 1997 00:14:26 -0400 (EDT)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.8.5/8.8.5) with SMTP id AAA05207 for <uri@services.bunyip.com>; Thu, 17 Apr 1997 00:14:24 -0400 (EDT)
Received: from alpha.Xerox.COM by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA27603 (mail destined for uri@services.bunyip.com); Thu, 17 Apr 97 00:14:21 -0400
Received: from casablanca.parc.xerox.com ([13.2.16.111]) by alpha.xerox.com with SMTP id <14783(6)>; Wed, 16 Apr 1997 21:14:19 PDT
Received: from bronze ([13.2.17.210]) by casablanca.parc.xerox.com with SMTP id <71898>; Wed, 16 Apr 1997 21:14:08 PDT
Message-Id: <3355987B.4D76@parc.xerox.com>
Date: Wed, 16 Apr 1997 20:26:51 -0700
From: Larry Masinter <masinter@parc.xerox.com>
Organization: Xerox PARC
X-Mailer: Mozilla 3.01Gold (Win95; I)
Mime-Version: 1.0
To: Gary Adams - Sun Microsystems Labs BOS <Gary.Adams@east.sun.com>
Cc: fielding@kiwi.ics.uci.edu, uri@bunyip.com
Subject: Re: revised "generic syntax" internet draft
References: <199704161444.KAA03396@zeppo.East.Sun.COM>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-uri@bunyip.com
Precedence: bulk

> So, since I'm looking for a solution to the end to end problem, here's 
> a proposal that I think you might see as a viable solution.
> ...
> Without changing the definition of URLs, we simply define the next version
> of a particular URL scheme (or a new scheme) which includes the constraint
> or feature that the %HH escaped characters were generated by a UTF8 aware
> service. Clients could then take advantage of this updated information in
> determining how to present the URL or in the ways it would accept URL 
> inputs.

I think the language to this effect is already in 
  draft-masinter-url-process

That is, I think we've already adopted this. The bruhaha has
been over the desire to make recommendations about existing
URL schemes in the "draft standard".

Larry

--
http://www.parc.xerox.com/masinter