Re: "Difficult Characters" draft

Larry Masinter <masinter@parc.xerox.com> Tue, 06 May 1997 16:22 UTC

Received: from cnri by ietf.org id aa27686; 6 May 97 12:22 EDT
Received: from services.Bunyip.Com by CNRI.Reston.VA.US id aa13325; 6 May 97 12:22 EDT
Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id LAA15349 for uri-out; Tue, 6 May 1997 11:50:35 -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 ESMTP id LAA15344 for <uri@services.bunyip.com>; Tue, 6 May 1997 11:50:32 -0400 (EDT)
Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by mocha.bunyip.com (8.8.5/8.8.5) with SMTP id LAA26073 for <uri@bunyip.com>; Tue, 6 May 1997 11:50:20 -0400 (EDT)
Received: from casablanca.parc.xerox.com ([13.2.16.111]) by alpha.xerox.com with SMTP id <18014(14)>; Tue, 6 May 1997 08:49:36 PDT
Received: from bronze.parc.xerox.com ([13.1.100.114]) by casablanca.parc.xerox.com with SMTP id <71839>; Tue, 6 May 1997 08:49:27 PDT
Message-ID: <336F5302.64F7@parc.xerox.com>
Date: Tue, 6 May 1997 08:49:22 PDT
From: Larry Masinter <masinter@parc.xerox.com>
Organization: Xerox PARC
X-Mailer: Mozilla 3.01Gold (Win95; I)
MIME-Version: 1.0
To: "Martin J. Duerst" <mduerst@ifi.unizh.ch>
CC: Alain LaBont/e'/ <alb@riq.qc.ca>, URI mailing list <uri@bunyip.com>
Subject: Re: "Difficult Characters" draft
References: <Pine.SUN.3.96.970506111326.245L-100000@enoshima>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-uri@bunyip.com
Precedence: bulk

Martin,

Perhaps you could mention in your draft about the use of
identifiers with characters outside of ASCII that such
use is actually problematic, and that some applications
which use canonical identifiers and exact match as a way
of doing symbol lookup when restricted to ASCII-only symbols
might find that users of languages other than English
will be ill-served by such a design; in some applications
using a careful language-sensitive equivalence lookup
(instead of exact-match) would make the software actually
accomodate the needs and practices of such users.

The mail in the recent week has been full of good examples
of places where canonicalization is either ill-specified
or context-sensitive, and "equivalence matching"
would be far more practical.

Fortunately, it's possible that equivalence-based matching
could be deployed for URLs; other kinds of exact-match
names will require a separate analysis. Both DNS and HTTP-servers
(if not FTP servers) could be coaxed into doing equivalence-matching
instead of exact matching for reference lookup; if they also respond
with the server's view of the "canonical" name, then we
won't be asking clients to do what it seems like is nearly
impossible.

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