Standard API to XSL processors

What's really needed is a standard way of binding together XML modules of
all kinds -- parser, DOM, XSL, renderers, etc. But this seems to fall in
the cracks between the various standards groups.

Folks have done conversion objects from DOM to SAX and back. But SAX as it
now stands is missing some items -- comments and entity references are the
ones I know about -- which a fully general XML pipeline would have to
handle. And if you're going between two DOM-based environments, it may not
be maximally efficient to go into and out of SAX; copying via the DOM APIs
would probably be faster. So the pipeline API might have to include some
negotiation to find the best transfer mechanism.

You'd also want to be able to handle sub-sections of documents
(insert/extract).



______________________________________
Joe Kesselman  / IBM Research
Unless stated otherwise, all opinions are solely those of the author.



 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list