Re: revised "generic syntax" and "data:" internet drafts

Larry Masinter (masinter@parc.xerox.com)
Fri, 4 Apr 1997 15:57:59 PST


Message-Id: <33459587.2FD0@parc.xerox.com>
Date: Fri, 4 Apr 1997 15:57:59 PST
From: Larry Masinter <masinter@parc.xerox.com>
To: Edward Cherlin <cherlin@newbie.net>
Cc: uri@bunyip.com
Subject: Re: revised "generic syntax" and "data:" internet drafts

I'm surprised I have to spell this out. 

Martin has proposed that we add to the "Draft Standard" the following
wording:

>    URL creation mechanisms that generate the URL from a source which
>    is not restricted to a single character->octet encoding are
>    encouraged, but not required, to transition resource names toward
>    using UTF-8 exclusively.

I will point out that of all of the implementors of all of the software
that I'm aware of that contain "URL creation mechanisms", including
the software products from Alis, Accent, Netscape and Microsoft -- 
even in the latest versions which purport to support UTF-8 in the
representation of text--  I have yet to see any product that is a
"URL creation mechanism" that actually does what Martin is proposing
we encourage them to do ("transition resource names toward using
UTF-8 exclusively"). Not only aren't they transitioning toward
using UTF-8 exclusively, I've yet to see one that actually uses
UTF-8 in resource names at all. When I asked for instances of some
actual
practice, I got sent two examples of URLs on Martin's own site
in which the "URL creation mechanism" was careful hand crafting
of the URLs themselves. Furthermore, none of the implementors
of the "URL creation mechanisms" have stepped forward to endorse
this proposal. The only voices for it are those who are not actually
producing "URL creation mechanisms". Even the most ferverent
believer in UTF-8 would not be so foolish as to create a product
that 'transitioned' toward 'using UTF-8 exclusively'.  Certainly, 99.99%
of the installed "URL creation mechanisms that generate a URL from a
source that is restricted to a single character->octet encoding"
do *NOT* "use UTF-8 exclusively".

It would be irresponsible and ridiculous to insert a recommendation
into a Draft Standard of a practice that not only did not occur
in the Proposed Standard but also is not the result of implementation
experience of the community.

Regards,

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