SAX2: Namespace proposal

David Megginson david at
Sun Dec 19 12:20:05 GMT 1999

James Clark writes:

 > The one scenario that bothers me with this is:
 > - the parser always supplies both XML 1.0 names and cooked namespace
 > declarations
 > - the application is namespace-aware and only interested in the cooked
 > namespace information
 > - the application iterates over all attributes using getLocalName(int).

Yes, this is my biggest misgiving as well -- it's the only place where 
a Namespace-aware application is at a disadvantage.

 > Indeed.  Although I think your proposal is quite reasonable, and
 > although I don't have anything better to propose right now, I can't say
 > I feel altogether comfortable with it.  I think we should continue to
 > explore other possible solutions.  If it's possible to have a completely
 > new org.xml.sax2 package, then more radical solutions are possible.  For
 > example, I think there are good arguments for moving to a 
 > interface DocumentHandler {
 >   void startElement(StartElementEvent event)
 >   void endElement(EndElementEvent event)
 >   ...
 > }
 > style interface.  This makes it much easier to evolve the interface in
 > the future.  For example, a SAX3 that added support for XML Schemas
 > could just add additional methods to StartElementEvent and
 > EndElementEvent and thus remain compatible with SAX2.

It's worth considering this approach, but it does create an awful lot
of classes.

All the best,


David Megginson                 david at

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at
Archived as: and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:majordomo at the following message;
unsubscribe xml-dev
To subscribe to the digests, mailto:majordomo at the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at

More information about the Xml-dev mailing list