Re: UTF-8 and URLs

Francois Yergeau <yergeau@alis.com> Fri, 25 April 1997 15:57 UTC

Received: from cnri by ietf.org id aa28500; 25 Apr 97 11:57 EDT
Received: from services.Bunyip.Com by CNRI.Reston.VA.US id aa12725; 25 Apr 97 11:57 EDT
Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id KAA14445 for uri-out; Fri, 25 Apr 1997 10:22:38 -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 KAA14438 for <uri@services.bunyip.com>; Fri, 25 Apr 1997 10:22:36 -0400 (EDT)
Received: from ns.alis.com by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA28061 (mail destined for uri@services.bunyip.com); Fri, 25 Apr 97 10:22:34 -0400
Received: from fyergeau.alis.com ([207.81.28.17]) by genstar.alis.ca (8.7.5/8.7.3) with SMTP id KAA29370 for <uri@Bunyip.Com>; Fri, 25 Apr 1997 10:21:53 -0400 (EDT)
Message-Id: <3.0.1.32.19970425102234.00d53550@genstar.alis.ca>
X-Sender: yergeau@genstar.alis.ca
X-Mailer: Windows Eudora Pro Version 3.0.1 (32)
Date: Fri, 25 Apr 1997 10:22:34 -0400
To: uri@bunyip.com
From: Francois Yergeau <yergeau@alis.com>
Subject: Re: UTF-8 and URLs
In-Reply-To: <33604065.2C69100A@w3.org>
References: <SIMEON.9704240851.W@tp7.Jck.com> <3.0.1.32.19970424225624.00d6262c@genstar.alis.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-MIME-Autoconverted: from quoted-printable to 8bit by services.bunyip.com id KAA14440
Sender: owner-uri@bunyip.com
Precedence: bulk
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by services.bunyip.com id KAA14445

À 00:25 25-04-97 -0500, Dan Connolly a écrit :
>> Let's see: we would have an i18n RFC that would allow URLs to contain most
>> any characters, and a (possibly Draft) standard that would say "All URLs
>> consist of a restricted set of characters..." (we know which): clear
>> contradiction.
>
>Please don't cite out of context or paraphrase wildly. The _existing_
>RFC limits the characters in URLs. In fact, the UTF-8-in-%XX encoding
>propsal doesn't even change that: it just adds semantics to the syntax.

I'm sorry, but I see it differently: the UTF-8-in-%XX proposal doesn't add
octet values on-the-wire, but it adds, and correctly maps, thousands of
characters.

>>From what I can see, Larry is the only guy around here volunteering
>to be editor; as such, it's up to him to decide whether it's more
>convenient to present the ideas in one document or two.

Well, I think Martin has volunteered too, at least to some extent.  And I
wouldn't mind if it were purely a presentation issue, as you imply, but I
don't think it is.  The issue is what will be standardized as *the* URL
syntax.

Regards,


-- 
François Yergeau <yergeau@alis.com>
Alis Technologies Inc., Montréal
Tél : +1 (514) 747-2547
Fax : +1 (514) 747-2561