RE: [libxml++] libxml++ future

[Murray Cumming <murrayc usa net>]

On Fri, 2003-09-26 at 17:39, Dan Dennedy wrote:
> On Fri, 2003-09-26 at 11:15, Murray Cumming Comneon com wrote:
> > > From: Dan Dennedy [mailto:dan dennedy org] 
> > > I am also personally interested in entity-support in the near term.
> > 
> > As you know, I'm willfully ignorant. Could you tell us more about what you
> > would like the API to do for this?
> 
> For now, I just need to be able to manually add them from the sax parser
> in my custom DOM

By the way, let's get that custom_dom example into libxml++. But I'd
prefer to call it derived_dom_parser, because I think that's what it is.

>  --it always goes back to that! So, I would need the SAX
> event exposed, and a very simple node subclass.

So I think a large part of this is: Adding 
class Entity : public Node
and telling libxml to give us Entities instead of substituting them. I
think there's some libxml function for that. (We should add the option
to libxml++ as well).

> Basically, in a custom DOM derived from libxml++ DOM, I need to preserve
> any node I do not know about (xml passthrough). Hopefully, you can
> envision how this whole thing ties in well with namespaces support. A
> custom DOM implementation is only concerned with things in selective
> namespaces; foreign namespace nodes simply pass-through. Now, combine
> this concept with chains of SAX parsers/serializers and you have a
> framework for simple, modular xml processors. This concept can then be
> distributed using xml-rpc or that network adapter thingee for libsigc++.
> 
> You may wonder what my motivation is... I work very much in the video
> space where things are time-based and there is heavy processing. I want
> to load xml into a DOM, manipulate the DOM over time (SMIL animation),
> and for each iteration/frame, serialize signals out to, for example, an
> SVG processor (i.e., the expat-based librsvg).
> 
> I am not very concerned about DTD nodes, however.
> 
> I am curious, has there been any discussion of W3C DOM API conformance?

Do you mean the thing that the Xerces-C++ people proposed?

-- 
Murray Cumming
murrayc usa net
www.murrayc.com