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

Re: XML Component API

• From: "Bill la Forge" <b.laforge@j...>
• To: "Oren Ben-Kiki" <oren@c...>
• Date: Sun, 17 Jan 1999 12:40:33 -0500

Oren,

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.)

http://www.jxml.com/mdsax/mdsaxintro.html

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.

Bill


-----Original Message-----
From: Oren Ben-Kiki <oren@c...>
To: XML List <xml-dev@i...>
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
>efficiency.
>
>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
>it.
>
>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: DTD vs DCD vs Schema
• Next by Date: Re: specs for Coins 3.1 ?
• Previous by thread: Re: XML Component API
• Next by thread: RE: XML Component API
• Index(es):
  • Date
  • Thread