At 12:39 PM 2/17/99 -0600, Paul Presod wrote:
>
>It seems to me that an XSL processor is just a SAX filter that takes a
>stylesheet as an argument. The "simple API for XSL" is the SAX filter API.
>

For once, I agree 100% with Paul.  I'm quite happy with SAX as an API for
transmitting all kinds of XML information, including XSL information.
Tools for converting SAX to a DOM tree (Docuverse DOM -
http://www.docuverse.com/domsdk/index.html) and back again (DOM parser, at
http://www.ccil.org/~cowan/XML/) are readily available.  

The SAX filter model is a great way (I think) to make changes to XML
documents using  modular tools (including XSL tools, like XT) at low cost.

Folks may want to take a look at the SAX 1.1 (now called ModSAX?)
discussions on the xml-dev list, if you have a case for additional needed
functionality.

Simon St.Laurent
XML: A Primer / Building XML Applications (April)
Sharing Bandwidth / Cookies
http://www.simonstl.com


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