- From: Chris Lilley <chris@w3.org>
- Date: Tue, 4 Feb 2003 01:49:41 +0100
- To: Dan Connolly <connolly@w3.org>
- CC: www-international@w3.org, Martin Duerst <duerst@w3.org>, "Ian B. Jacobs" <ij@w3.org>, <www-tag@w3.org>, Max Froumentin <mf@w3.org>, Michel Suignard <michelsu@microsoft.com>
On Monday, February 3, 2003, 11:00:52 PM, Dan wrote: DC> On Mon, 2003-02-03 at 15:51, Chris Lilley wrote: DC> [...] >> 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 .... DC> Either that or everybody has to follow the convention to use DC> upper-case in %xx escapes. Surely we could get that consistently DC> deployed in the IRI-grokking world. So everyone has to use upper case, but lower case is still accepted and sometimes means the same thing (if you go back to IRI first) and sometimes not (if you dont). Doesn't sound very clean to me. High chance of surprises. DC> Sender-makes-right is *much* cheaper here. Not necessarily. -- Chris mailto:chris@w3.org
Received on Monday, 3 February 2003 19:53:50 UTC