XML Component API

[Tyler Baker]

Michael.Kay at icl.com wrote:

> > From: Oren Ben-Kiki [mailto:oren at capella.co.il]
> >
> > I raised the question of a standard API to XSL processors in
> > the XSL mailing
> > list. This question has quickly touched on general issues of
> > how to combine
> > XML processing modules, since there are two incompatible ways
> > to pass XML
> > data - as an in-memory DOM tree or as "parsing" events.
> >
>
> SAXON (http://home.iclweb.com/icl2/mhkay/saxon.html) provides a higher-level
> API that can be used to process XML documents on top of either SAX or DOM.
> It provides a useful model where most of your processing is sequential but
> you might occasionally (or in the future) want to navigate from a node that
> you reached serially, e.g. to follow an IDREF.
>
> I've recently been trying to implement an XSL subset using SAXON and have
> realised that the XSL processing model requires the document to be built in
> memory, even though 90% of useful applications don't. For an XSL API,
> therefore, I think you can forget any idea of an event-based approach.
>
> Mike Kay

That has not been my experience.  I have not had any problem with spitting out
processed XSL Output to SAX events.  Things could change, but for now I have not
found any reason why you can't use DocumentHandler as an interface for delegating
processing of XSL output.

Tyler


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)