W3C home > Mailing lists > Public > xml-names-editor@w3.org > November 2003


From: Julian Reschke <julian.reschke@gmx.de>
Date: Thu, 06 Nov 2003 13:31:42 +0100
Message-ID: <3FAA3F2E.90501@gmx.de>
To: xml-names-editor@w3.org


as many have said before, it's really really a bad idea to normatively 
refer to other specs that haven't been finished. Here in particular I 
must note that the appendix points to IRI draft 03, which not only has 
been updated twice since, but also substantially differs from draft 03.

Also note that the IRI draft in turn has a normative reference to 
RFC2396bis (thie URI draft update), for which the release date is also 

So here are my suggestions, sorted by preference:

- do not allow IRIs as namespace names (if only for the simple reason 
that this change wasn't on the requirements list, see 

- do not publish XML-NAMES 1.1 before the IRI draft becomes an IETF 
standard (and when it does and happens to allow SP as IRI character 
again as it did in draft 03, forbid them explicitly in namespace names; 
see for instance 

Regards, Julian

<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Thursday, 6 November 2003 07:31:46 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:13:30 UTC