SAX dot NET - Unifying Extension interfaces: second thoughts

After having gotten some positive feedback (mostly off-list)
about unifying the "version 2" extension interfaces with the
original ones, I am having second thoughts, mostly because of this:

As far as I can tell, the SAX extensions are meant to
include interfaces for reporting parts of an XML document
that the XML spec does not explicitly require to be reported.

Unifying these interfaces - IAttributes(2), ILocator(2) and
IEntityResolver(2) - would break the semantics behind this
separation of modules/namespaces.

Another option could be to simply pack everything into one
namespace - without any separation on the definition level - and
document which parts an XML processor is required to support and
which ones are optional.

Not sure, currently.

Karl


-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
List: sax-devel, [email protected]
See:  http://www.saxproject.org/
https://lists.sourceforge.net/lists/listinfo/sax-devel