W3C home > Mailing lists > Public > uri@w3.org > October 2004

RE: TAG scheme - some comments

From: McDonald, Ira <imcdonald@sharplabs.com>
Date: Fri, 22 Oct 2004 09:50:23 -0700
Message-ID: <CFEE79A465B35C4385389BA5866BEDF00C792A@mailsrvnt02.enet.sharplabs.com>
To: "'Tim Kindberg'" <timothy@hpl.hp.com>, "Hammond, Tony" <T.Hammond@nature.com>
Cc: uri@w3.org, sandro hawke <sandro@w3.org>

Hi,

>><Tony Hammond wrote...>
>> 6. Note that normalization issues are ducked. :) Probably wisely too. Not
>> sure what the ramifications of this might be especially wrt TAG
processors
>> and %-encoding.

><Tim Kindberg replied...>
>Yes, we decided that tags that are different as strings (with same 
>character encoding) are different, full stop. It's nice and easy to 
>understand and there's no compelling need for a more sophisticated 
>criterion for equality.

While neither RFC 2717 nor draft RFC 2717bis address it,
most existing URI scheme RFCs actually do identify rules for
"comparison of two XXX URIs".  Since TAG values can be UTF-8
(percent-encoded), there are certainly string comparison
issues to be addressed (like underlying UTF-8 normalization
to NFC or NFKC forms).  Using a Stringprep profile (RFC 3454) 
is a good approach (RFC 3454).  I suggest looking at:

"Nameprep: A Stringprep Profile for Internationalized Domain Names"
RFC 3491, March 2003


Cheers,
- Ira

Ira McDonald (Musician / Software Architect)
Blue Roof Music / High North Inc
PO Box 221  Grand Marais, MI  49839
phone: +1-906-494-2434
email: imcdonald@sharplabs.com
Received on Friday, 22 October 2004 16:58:34 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 13 January 2011 12:15:34 GMT