Simon St.Laurent wrote: > If "namespace processing is off and we've never heard of namespaces", then > we've never heard of QNames either. If you insist on going this route, > you'd better change the API to remove the notion of QName when namespace > processing is off. "Local name" might at least mean "the name local to the > element" in cases without any understanding of namespaces.
I understand it the same way. The confusion in this thread really is: if NS processing is off, then which should really represent the element name - qName or localName? I agree with you that localName is the more natural candidate. > >Those are both categories of implementation variance that the current > >SAX spec allows, though which (thankfully) not many implementors have > >taken advantage of. In the interest of application portability, I'd > >be glad to see them removed in a SAX 2.1 release. > > In the interest of application portability, I'd recommend requiring > reporting the name of the element as localName when namespace processing is > turned off. In order to satisfy everybody, I would say, qName = localName when NS processing is off. Karl --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
