W3C home > Mailing lists > Public > xml-names-editor@w3.org > September 2002

last call comments, usage of IRI rather than URI

From: Julian Reschke <julian.reschke@greenbytes.de>
Date: Thu, 26 Sep 2002 23:57:26 +0200
To: <xml-names-editor@w3.org>
Message-ID: <JIEGINCHMLABHJBIGKBCIEADFHAA.julian.reschke@greenbytes.de>


Looking at it -- I'm not convinced that allowing IRI references is a good
idea. There is existing code out there that assumes that every namespace
name in an XML document can be represented as a URI. With a IRI containing
non-ASCII characters, this is not true anymore. Translating to a URI will
not work because

- namespace identity is defined on a char-by-char basis, so the resulting
URI does *not* identify the same namespace and
- for a recipient of a "down-transformed" IRI there's no way to know it
originally used IRI syntax (so there'll be problems round-tripping them).

This is *not* an academic argument -- our WebDAV server implementation
relies on the fact that WebDAV properties are identified by URIs, and will
reject those which do not conform to the URI syntax. So when at some point
of time the WebDAV WG will have to decide about what do to with XML 1.1, it
may have to restrict the set a legal namespace names to URIs.

To satisfy I18N requirements (which I *do* understand), wouldn't it make
more sense to state that the characters in a namespace URI, when un-escaped,
SHOULD map to valid UTF-8 octet sequences (possibly normalized)?

Julian

--
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760

>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Thursday, 26 September 2002 17:58:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:43 GMT