Lists Home |
Date Index |
"Simon St.Laurent" wrote:
> I've been thinking about this unfortunate situation and think I may have a
> proposal which will let us steer through the disconnect between
> namespaces-on and namespace-off approaches as people like Glenn seem to see
> How about:
> 1) The qName parameter is renamed "rawName", and documentation explains
> that this is both the Qualified Name in namespace-aware processing and the
> Name in namespace-unaware processing.
-1. rawName doesn't mean anything. qName does.
> 2) A filter which copies rawName to localName in the event that localName
> is empty or null is included in the org.xml.sax.helpers package. This way,
> developers can adapt filters and applications which work using
> namespace-aware expectations to namespace-unaware processing without having
> to retrofit their code.
But why would we want to do this? So far, nobody has reported a parser
that doesn't report the element type name in localName when namespace
processing is turned off, and everybody (admittedly a small sample) is
writing code that relies on the value in localName. The change you
suggest would break existing applications.
I vote that we change the docs to align with current practice and remove
the ambiguity. This would be backwards incompatible in the theoretical
world but backwards compatible in the real world.