Re: qualified name argument to startElement

----- Original Message ----- 
From: "Elliotte Rusty Harold" <[email protected]>
To: "Mikael Ståldal" <[email protected]>
Cc: <[email protected]>
Sent: Wednesday, April 28, 2004 5:07 AM

> Indeed the SAX specification might be clearer if
> we just called that argument "name" rather than
> "qName". As it stands, a document that is
> namespace incompatible due to multiple colons in
> element names can't really be processed by SAX
> because such an element has neither a local part
> nor a qualified name. However, it does have a
> name, and is well-formed though not namespace
> well-formed.

This raises the question: if the namespaces feature
is turned off, is a SAX processor still  in
"namespace processing" mode? That is, should
it report violations of namespace well-formedness?

If not, then the term "qName" really should be
called "name" with the understanding that it
is a qualified name when namespaces are turned on.

Personally, I would have preferred the Expat approach
of passing local name, URI and prefix. Fewer chances
for confusion.

Karl



-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE. 
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
List: sax-devel, [email protected]
See:  http://www.saxproject.org/
https://lists.sourceforge.net/lists/listinfo/sax-devel