SAX: Status Report

Peter Murray-Rust peter at
Wed Jan 7 23:14:44 GMT 1998

Hi Alex,

At 16:41 07/01/98 -0600, Alex Milowski wrote:
>...on a similar note, having been too busy lately to keep up.
>What is the different between SAX and XAPI-J.  Where did SAX come from?
>What are the requirements, design patterns, etc?
>...a URL for the above, maybe?
>Obviously, I'm confused!  ;-)
Like you, I was sad that XAPI-J didn't get adopted more widely, because a
lot of hard thought had gone into it. The "general consensus" - and I am
only guessing this through discussions on this list and a few RL encounters
- seems to be that XAPI-J is too close to the DOM and perhaps too involved
for many applications.

I therefore thought it was worth raising this again - about a month ago -
and there was a lot of general enthusiasm. David Megginson and Tim Bray
offered to pursue a "simple API" - hence SAX, and we have generated at lot
of valuable input on this list. In my opinion we have homed in on something
valuable, but simpler that XAPI-J.  DavidM and I are jointly producing some
(slightly retrofitted) goals  to measure our current position against. 

David devised 10 questions which he requested comments on, and we have been
analysing these over the last few days. You are welcome to submit comments
- you'll find the Q's on this list

Do not feel that the XAPI-J effort was 'wasted' - perhaps it wasn't exactly
right for that particular time, but it had an important effect on the
construction of interfaces.


Peter Murray-Rust, Director Virtual School of Molecular Sciences, domestic
net connection
VSMS, Virtual Hyperglossary

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at
Archived as:
To (un)subscribe, mailto:majordomo at the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at

More information about the Xml-dev mailing list