[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: XML Component API

• From: "Oren Ben-Kiki" <oren@c...>
• To: "XML List" <xml-dev@i...>
• Date: Mon, 18 Jan 1999 21:57:37 +0200

Michael.Kay@i... wrote:

>> From: Oren Ben-Kiki [mailto:oren@c...]
>> 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.


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.
SAXON does make one wonder what would have become of XSL if it was designed
as a procedural instead of declerative language...

Share & Enjoy,

    Oren Ben-Kiki


xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• Prev by Date: RE: Template System Using XML
• Next by Date: Re: XML Component API
• Previous by thread: Re: XML Component API
• Next by thread: RE: XML Component API
• Index(es):
  • Date
  • Thread