Re: Another doc issue

OK. I looked at it again and there is a conflict. On 
http://sax.sourceforge.net/?selected=namespaces we find

Code using element names would normally match first for a null URI, and 
if it's null then use qName otherwise use localName.

and a little later we see:

If the URI were the emtpy string, you would normally use the qName to 
identify attributes. So code looking at those attributes would normally 
match first for a null URI, and if it's null then use qName otherwise 
use the localName.


The problem is the suggestion to match for a null URI. This contradicts 
the JavaDoc for startElement which says unequivocally that the uri 
argument is "The Namespace URI, or the empty string if the element has 
no Namespace URI or if Namespace processing is not being performed." I 
think this is how all current parsers behave.


I think these sentences in 
http://sax.sourceforge.net/?selected=namespaces should simply be 
deleted. I don't think they're reliable or accurate. The empty string 
could mean namespace processing is not being performed, or it could mean 
the namespace URI is the empty string. I suspect at one point in the 
past. somebody was planning on the empty string only being used when 
namespace processing is performed but this is not the case now.

-- 
Elliotte Rusty Harold  [email protected]
XML in a Nutshell 3rd Edition Just Published!
http://www.cafeconleche.org/books/xian3/
http://www.amazon.com/exec/obidos/ISBN=0596007647/cafeaulaitA/ref=nosim


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
List: sax-devel, [email protected]
See:  http://www.saxproject.org/
https://lists.sourceforge.net/lists/listinfo/sax-devel