Lists Home |
Date Index |
- From: "Bill la Forge" <email@example.com>
- To: "Oren Ben-Kiki" <firstname.lastname@example.org>
- Date: Sun, 17 Jan 1999 12:40:33 -0500
This looks like you are treating SAX events and documents something like
Java bean events, and I wonder if it would be appropriate to conform to a greater
degree to the event method signature patterns.
I would also like to refer you to MDSAX, which you may find somewhat complimentary.
(It also provides an open-archecture for supporting alternatives to things like
namespaces, if that is the issue of the moment.)
We are now viewing the current release as just one possible implementation of a
multi-document SAX-based framework. The next step will be to seperate and simplify
the api, while still providing a sample implementation.
It is open source software (BSD licence), but more than that, we really want to throw this
effort open to the entire XML development community.
Again, the work you are doing appears to be complimentary to ours, with the
producer/consumer interfaces providing an api for connecting various processes,
while MDSAX provides a means for defining a SAX-event process.
From: Oren Ben-Kiki <email@example.com>
To: XML List <firstname.lastname@example.org>
Date: Sunday, January 17, 1999 4:46 AM
Subject: XML Component API
>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.
>I came up with the attached scheme. It allows writing all sorts of XML
>related components, using either of the APIs, and still easily combine them
>together to obtain complex XML processing goals, with little or no loss of
>I understand that a new version of SAX interface is being considered, making
>it more like an implementation of the visitor pattern for DOM trees then a
>simple parser interface. This is a chance to add something along the
>attached API directly to the SAX interface, if that's the right place for
>Share & Enjoy,
> Oren Ben-Kiki
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)