W3C home > Mailing lists > Public > www-tag@w3.org > February 2003

Re: [Minutes] 27 Jan 2003 TAG teleconf (httpRange-14, arch doc, IRIEverywhere-27, binaryXML-30, xmlProfiles-29)

From: Martin Duerst <duerst@w3.org>
Date: Tue, 04 Feb 2003 20:24:56 -0500
Message-Id: <4.2.0.58.J.20030204202207.033f0730@localhost>
To: Dan Connolly <connolly@w3.org>, Chris Lilley <chris@w3.org>
Cc: www-international@w3.org, "Ian B. Jacobs" <ij@w3.org>, www-tag@w3.org, Max Froumentin <mf@w3.org>, Michel Suignard <michelsu@microsoft.com>

At 16:00 03/02/03 -0600, Dan Connolly wrote:

>On Mon, 2003-02-03 at 15:51, Chris Lilley wrote:
>[...]
> > It would be highly desirable for FOO used in an IRI and the hexified
> > version of FOO used in a URI to compare the same when comparing two
> > URIs. If this is not done, then IRI-URI is a one-way street.
> >
> > For this to work in any sensible manner, then clearly it is not enough
> > for FOO to compare the same as %ab%cd%ef. It also has to compare the
> > same as %AB%CD%EF and %Ab%cd%eF and ....
>
>Either that or everybody has to follow the convention to use
>upper-case in %xx escapes. Surely we could get that consistently
>deployed in the IRI-grokking world.
>
>Sender-makes-right is *much* cheaper here.

Hello Dan,

I think that if we decide that we want to force things such as
namespaces to do FOO == %AB%CD%EF, then it would be easy to at
the same time also teach them that %AB%CD%EF == %Ab%cd%eF, and
so on. So for namespace purposes, 'always escape to upper case'
doesn't really cut it.

Regards,    Martin.
Received on Tuesday, 4 February 2003 20:25:34 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:47:16 GMT