OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   xmlns-uris and namespaces.html

[ Lists Home | Date Index | Thread Index ]

It loks like the namespaces.html document was patched, but there is still
one line that is possibly incorrect: it is in the bullet list "If namespaces
is true and namespace-prefixes is true, then a SAX2 XML reader will report
the following:"

an attribute with no Namespace URI (empty string), no local name (empty
string), and the qName "xmlns:h";

Clearly this was written before xmlns-uris was added. Also, this page makes
no mention of xmlns-uris in the properties table. My question is:

(a) should I do a low impact change and only call out the new property in
this one bullet point (with link)? or

(b) should I insert a sub section in the introduction and insert it into the
table?

I posted this question about a week and a half ago, but it seemed to be
lost:

>>
I was looking for wording related to the xmlns-uris feature. My question is
whether or not the xmlns-uris feature can be true while namespaces is false
and namespace-prefixes is true-- or namespaces is true and
namespace-prefixes
is false Obviously this would make little sense but
nothing in the specs (that I could find) forbids it. Should it be forbidden?
If so what is the correct action? A SAXNotSupported exception? Or having the
side-affect of changing the associated features? I suppose that this
question applies similarly to the namespaces and namespace-prefixes
features.
<<

In the table, "Illegal Combination" gives no indication what will happen if
you try to set a parser in such a state.

Thanks,
Jeff Rafter





 

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS