RE: Response to comment on Namespaces in XML 1.1

I somehow don't think you've captured the spirit of the
suggestion. Whether you want to "disallow" or "strongly
discourage" may in fact be a matter for backward compatibility,
but the point is that if you use hex escapes in a namespace
name URI, you will risk confusion if there is an equivalent,
non-escaped IRI.

So the "good practice" is not just to avoid use of
'confusingly similar IRIs as namespace names', but to
avoid use of URIs which have equivalent IRIs.

("equivalent" in previous paragraphs taken to be:
  there is a commonly used equivalence relationship
  for which the two RIs are equivalent.)


Larry


> -----Original Message-----
> From: xml-names-editor@w3.org [mailto:xml-names-editor@w3.org] 
> Sent: Tuesday, April 22, 2003 8:08 AM
> To: Larry Masinter
> Cc: xml-names-editor@w3.org
> Subject: Response to comment on Namespaces in XML 1.1
> 
> 
> This is the XML Core Working Group's formal response to your comment
> on the CR draft of Namespaces in XML 1.1.  If you sent more than one
> comment, you will receive a reply for each.  Your comment is 
> archived at 
> 
  http://lists.w3.org/Archives/Public/xml-names-editor/2003Feb/0000.html

Please let us know whether you accept our resolution of our comment,
or wish to have an objection formally recorded.  If we do not hear
from you within 10 days we will assume that you accept our response.

Re: comparing IRI references

We will add a "good practice" note to the spec advising against the
use of confusingly similar IRIs as namespace names.  We will also
advise against using spaces in namespace names, because of the
problems with space-delimited lists (in particular, schemaLocation).
On the other hand, outlawing hex escapes completely would introduce an
incompatibility with 1.0 (which allows them) and we believe it is too
drastic a change.

Received on Friday, 25 April 2003 02:35:46 UTC