The "Common formats" include simple representations like JSON, XML, or CSV, but also include database writing/retrieval formats. For example, one "format" interfaces with MySQL databases. The premise behind the library is not just data conversions, but basically an ETL implementation that provides analysis filters on the data as well. If the internal representation is not used, there is practically no limit to the size of data being converted or analyzed. This is a major difference from Boost.Serialization. On 01/09/2018 12:45 PM, Edward Diener via Boost wrote:

On 1/9/2018 12:36 PM, Oliver Adams via Boost wrote:

...

Hi all,

I was wondering if a library I'm developing would be of value to the Boost community. It is basically an event-driven parsing/serialization library for common formats using a standard internal representation or simple pass-through conversions. Would anyone be interested in something like this being added to Boost?

Thanks.

"Common formats" needs to be specified. Boost already has a serialization library so you might also want to explain how your library is different from that. It is always a good idea to be as specific as possible when querying about the interest in a new library.

_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

Stefan,

As you are mentioning SAX, do you have XML in mind ?

The library supports a version of XML (at least for writing, right now), but is not limited to that.

(I started a couple of discussions on this list, and do have some working code here: https://github.com/stefanseefeld/boost.xml) How does your library compare to that ?

The goals of the library are to be fast, generic, and easy to use. The focus of the library is on data, not on arbitrary structure, so it just supports a hierarchy or list of values, no graphs right now. You can check it out here: https://github.com/owacoder/cppdatalib. The readme referenced in the link provides a bit more of an overview of what the library is like. On 01/09/2018 01:18 PM, Stefan Seefeld via Boost wrote:

On 09.01.2018 12:36, Oliver Adams via Boost wrote:

...

Hi all,

I was wondering if a library I'm developing would be of value to the Boost community. It is basically an event-driven parsing/serialization library for common formats using a standard internal representation or simple pass-through conversions. Would anyone be interested in something like this being added to Boost? As you are mentioning SAX, do you have XML in mind ? I once developed a C++ wrapper around existing XML C APIs (both, DOM and SAX), with the intent of eventually submitting it to Boost, but never found the energy to finish this. (I started a couple of discussions on this list, and do have some working code here: https://github.com/stefanseefeld/boost.xml) How does your library compare to that ? I'm not sure there would still be any interest in XML APIs in Boost at this point in time. But if so, I believe it's best to start with something like that rather than invent yet another "XML-like" tool.

Best,

Stefan

2018-01-09 15:18 GMT-03:00 Stefan Seefeld via Boost mailto:boost@lists.boost.org>:

I'm not sure there would still be any interest in XML APIs in Boost at this point in time.

I'd like to see a XML library in Boost. I'd love to see anyone pursuing this effort. Then have a look at https://github.com/stefanseefeld/boost.xml. It's an API, with existing bindings to libxml2, and the original intent to add support for other backends (e.g. xerces). If there is enough interest I'd be happy to revive / continue the

On 09.01.2018 20:14, Vinícius dos Santos Oliveira wrote: project. (Please submit issues and feature requests to that project, so we can discuss more technical details there.) Stefan -- ...ich hab' noch einen Koffer in Berlin...