Re: revised "generic syntax" internet draft

"Martin J. Duerst" <> Sat, 19 April 1997 16:50 UTC

Received: from cnri by id aa12622; 19 Apr 97 12:50 EDT
Received: from services.Bunyip.Com by CNRI.Reston.VA.US id aa08386; 19 Apr 97 12:50 EDT
Received: (from daemon@localhost) by (8.8.5/8.8.5) id MAA23397 for uri-out; Sat, 19 Apr 1997 12:31:59 -0400 (EDT)
Received: from (mocha.Bunyip.Com []) by (8.8.5/8.8.5) with SMTP id MAA23391 for <>; Sat, 19 Apr 1997 12:31:52 -0400 (EDT)
Received: from by with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA14020 (mail destined for; Sat, 19 Apr 97 12:31:49 -0400
Received: from by with SMTP (PP) id <>; Sat, 19 Apr 1997 18:31:22 +0200
Date: Sat, 19 Apr 1997 18:31:13 +0200
From: "Martin J. Duerst" <>
To: Larry Masinter <>
Cc: Gary Adams - Sun Microsystems Labs BOS <>,,
Subject: Re: revised "generic syntax" internet draft
In-Reply-To: <>
Message-Id: <Pine.SUN.3.96.970419181442.708b-100000@enoshima>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Precedence: bulk

On Wed, 16 Apr 1997, Larry Masinter wrote:

> > 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 process draft definitely covers the case of new schemes well.

- It does not cover new versions of existing schemes.

- It does not cover schemes that came newly into existence before
	the process draft will actually be in force (for example
	the imap URL scheme, which is very eager to follow the
	designation of a recommended character encoding scheme
	for URLs as soon as there is one).

- It does not address the fact that for most cases, the updating
	of an URL scheme happens for reasons orthogonal to
	character encoding, and that UTF-8 can be adopted in
	existing schemes without changing their definition.

Regards,	Martin.