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


Help: OASIS Mailing Lists Help | MarkMail Help



   Consensus? expected local name for non-namespace qualifiedelements

[ Lists Home | Date Index | Thread Index ]

I've just returned from Kentucky and read through the messages of the 
last few days. There's clearly a significant amount of disagreement 
on what does and what should happen when namespace processing is 
turned *off*. However, there seems to be nearly unanimous agreement 
on what happens when namespace processing is turned *on*. In 
particular, I am prepared to offer the following tentative consensus:

When the feature http://xml.org/sax/features/namespaces has the value 
true (as it does by default), SAX 2.0 parsers *must* report a 
non-empty local name for all elements and attributes, whether 
namespace qualified or not. A parser that reports the local name as 
the empty string when http://xml.org/sax/features/namespaces is true 
is simply not compliant with the SAX 2.0 specification.

Does anyone want to stick their hand up and disagree with this statement?

| Elliotte Rusty Harold | elharo@metalab.unc.edu | Writer/Programmer |
|          The XML Bible, 2nd Edition (Hungry Minds, 2001)           |
|             http://www.cafeconleche.org/books/bible2/              |
|   http://www.amazon.com/exec/obidos/ISBN=0764547607/cafeaulaitA/   |
|  Read Cafe au Lait for Java News:  http://www.cafeaulait.org/      |
|  Read Cafe con Leche for XML News: http://www.cafeconleche.org/    |


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

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