XML Component API

[Michael.Kay at icl.com]

> The SAXON framework seems well suited for doing XSL-like 
> transformations,
> but doesn't solve the problem of combining different XML processing
> components into a single computation - at least, it doesn't 
> seem to have
> have any advantage over the SAX interfaces in this very 
> specific regard.

You're right: I've been struggling this week trying to implement stylesheets
using SAXON, which requires multiple XML processing components, and it's not
easy. SAXON is good at producing multiple outputs from one input, but
multiple inputs (files or views) is more difficult. If anyone has any
suggestions, please let me know! I've started looking at MDSAX to see if
that offers any inspiration: perhaps it will, when I understand it better.

Mike Kay

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/
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe 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)