Not sure of any future boost plans for an XML library - seems a little specific to me though.

Aren't there already more specific libraries in boost? Like Python and Spirit? Anyway, it seems quite useful to me.

You can always try apache xerces-c: http://xerces.apache.org/xerces-c/

On first sight it looks a bit heavyweight. But I'll take a closer look later. Thanks. (Zeljko as well.) -- Michiel Helvensteijn

Hi there, regarding POCO: I was wondering whether it wouldn't make sense for the POCO and Boost groups to cooperate more closely ? Some of the work done for both library collections is redundant - e.g. both have smart pointers and threads. And some of the other libraries complement each other. Plus, POCO is also delivered under the Boost license and is portable. Are there contacts between the core development groups ? Well, ob course the above is just my "user's perspective". I realise that actually merging two long-standing projects will be a bit of a problem. Best, Ruediger Peter Klotz wrote:

...

In the meantime, can anyone recommend another open source C++ XML library I can use (with DOM parser)?

I recommend using POCO (Portable Components). It is a portable and very powerful open source C++ library that includes an XML DOM parser.

You can find it here:

http://pocoproject.org/

Best regards, Peter.

Kind Regards / Mit freundlichen Gruessen, Ruediger Berlich /*************************************************************************/ The Steinbuch Centre for Computing of Karlsruhe Institute of Technology (the Cooperation of Forschungszentrum Karlsruhe GmbH and Universitaet Karlsruhe TH) will run its annual GridKa School from September 8th to 12th, 2008. Please find further information at http://www.fzk.de/gks08 . /*************************************************************************/

Andy wrote:

Not sure of any future boost plans for an XML library - seems a little specific to me though.

An XML parsing library is needed in boost it's got my vote. I have and currently using xerces and looked at extending boost::serialization to provide xml with DTD validation. Not something serialization does. I found boost::serialization to be somewhat difficult to extend and asked that a clear path to extending serialization be provided. I think a front end / back end approach to these and other libraries (xerces, libxml, rapidXML) should be supported in boost allowing the developer to choose which implementation is used on the back end. This will mean that the front end interface will have to provide all features and notifications of what features are and are not provided by the back end. I used xerces and boost::function boost::bind to allow callbacks from Xerces and tried to hide as much of the implementation of xerces from the interface. I was using SAX2 not DOM, but xerces supports both. Light weight and XML should not be used in the same sentence. There is no light weight XML implementation that is standards conforming. If it is light weight it lacks features, if it does not lack features it is heavy weight. These two are inversely proportional when talking about XML. And once we get XML then we will want the holy grail of XML which is an XSLT transformer. Heck at least I want one. Get ready to have boat loads of fun with wide char conversions and Unicode! Brian