W3C home > Mailing lists > Public > public-iri@w3.org > July 2007

Re: SVG12: IRI Processing rules and xlink:href

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Mon, 02 Jul 2007 10:52:07 +0200
To: Martin Duerst <duerst@it.aoyama.ac.jp>
Cc: public-i18n-core@w3.org, public-iri@w3.org
Message-ID: <nteh83lr59104h19lnkugfeh4bq4mtd3t7@hive.bjoern.hoehrmann.de>

* Martin Duerst wrote:
>I have assigned this issue the following id: transcodeNFC-103
>(http://www.w3.org/International/iri-edit/#transcodeNFC-103).
>
>I have changed the wording in step 1.b. of Section
>3.1.  Mapping of IRIs to URIs from:
>
>            b. If the IRI is in some digital representation (e.g., an
>               octet stream) in some known non-Unicode character
>               encoding, convert the IRI to a sequence of characters
>               from the UCS normalized according to NFC.
>
>to:
>
>            b. If the IRI is in some digital representation (e.g., an
>               octet stream) in some known non-Unicode character
>               encoding, convert the IRI to a sequence of characters
>               from the UCS. The resulting sequence of characters
>               SHOULD be normalized using NFC.
>
>Any comments welcome!

There should be no SHOULD, it's critical that applications get this
right. Where normalization is necessary or beneficial, it should be
applied to the text content before any IRI processing takes place.
Besides, this does not resolve disputes as to when step b) would apply
at all.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de
68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Monday, 2 July 2007 08:52:17 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 30 April 2012 19:51:53 GMT