Request for Discussion: SAX 1.0 in C++

[uche.ogbuji at fourthought.com]

> > What in SAX2 is most urgently needed for DOM and XSLT?  I know that
> > DOM level one *can* support some things that SAX doesn't report (such
> > as comments and CDATA section boundaries), but there is nothing in DOM
> > level one that says those have to be included, and I've heard of
> > relatively few real-world applications that need that information.
> 
> How about focusing on SAX/2, and making the first C/C++ SAX interface
> actually SAX 2 so we kill two birds with one stone ?

This to me seems the most sensible approach.  Especially when SAX2 has had so 
much discussion and is potentially so close to completion.  The C++/SAX 
discussion is just starting and could go on for months.  It might as well be 
built around an up-to-date standard.

-- 
Uche Ogbuji
FourThought LLC, IT Consultants
uche.ogbuji at fourthought.com	(970)481-0805
Software engineering, project management, Intranets and Extranets
http://FourThought.com		http://OpenTechnology.org



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