Re: UTF-8 URL for testing

Larry Masinter <masinter@parc.xerox.com> Sat, 12 April 1997 01:01 UTC

Received: from cnri by ietf.org id aa23882; 11 Apr 97 21:01 EDT
Received: from services.Bunyip.Com by CNRI.Reston.VA.US id aa23702; 11 Apr 97 21:01 EDT
Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id UAA23200 for uri-out; Fri, 11 Apr 1997 20:33:20 -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 UAA23193 for <uri@services.bunyip.com>; Fri, 11 Apr 1997 20:33:14 -0400 (EDT)
Received: from alpha.Xerox.COM by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA20624 (mail destined for uri@services.bunyip.com); Fri, 11 Apr 97 20:33:11 -0400
Received: from bronze ([13.2.17.209]) by alpha.xerox.com with SMTP id <15509(1)>; Fri, 11 Apr 1997 17:33:09 PDT
Message-Id: <334EC975.586@parc.xerox.com>
Date: Fri, 11 Apr 1997 16:29:57 -0700
From: Larry Masinter <masinter@parc.xerox.com>
Reply-To: masinter@parc.xerox.com
Organization: PARC
X-Mailer: Mozilla 3.01Gold (Win95; I)
Mime-Version: 1.0
To: Dan Connolly <connolly@w3.org>
Cc: Francois Yergeau <yergeau@alis.com>, uri@bunyip.com
Subject: Re: UTF-8 URL for testing
References: <3.0.1.32.19970410171259.0075760c@genstar.alis.com> <334E7F88.4703@w3.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-uri@bunyip.com
Precedence: bulk

Just because a problem is important doesn't
mean that we should recommend something that has not yet
been demonstrated to actually solve the problem.

The proposal of hex-encoded UTF-8-encoded Unicode
has not been demonstrated to actually solve the problem
of letting people in Japan use URLs in Japan and people
in Israel use URLs in Hebrew. In fact, it hasn't yet
been demonstrated, as far as I can tell, to let Franc,ois
use the correct spelling of his own name in his own URLs.

Instead of trying to convince me about how easy this is
to demonstrate, or to claim that there is "wide consensus"
that someone else should implement this, we need to actually
have a demonstration of the technology. If Amaya or Jigsaw
were to include support for this method of encoding
of URLs, for example, it would go a long way, but they don't,
at least not in a way that demonstrates that the proposal
actually solves the problem that the proponents of the proposal
are claiming are so important that we solve. They don't let
people type in URLs in any syntax other than ASCII, they don't
display URLs in any form other than their %A0%0E%FE%B0 form,
and as such it makes no sense for us to continue to discuss.

If this is were to be a W3C recommendation, it should be
supported by the W3C software.
--
http://www.parc.xerox.com/masinter