xml-dev - RE: Who will maintain SAX?

[Bill dehOra <wdehora@cromwellmedia.co.uk>]

>Because an event-based callback parser is a 
>requirement.  It could have come from anywhere, 
>but getting it here saved a lot of hassle.  Your 
>perspective may be based on that.

If it's such a requirement, why aren't there a rash of callback APIs? There
are more DOMs that SAXs (SAXophones?), despite DOM being a ratified API.


>When something is first offered and easy to adopt, they 
>adopt it.  It's cheaper to let this list 
>do that work and it is the right thing to do because 
>it is experimental.  But not when it comes time to 
>extend it. That is when each decision has the most 
>impact on the codebase and responsible vendors 
>protect their customers.  Otherwise, we are back 
>to Sun Owns Java, Adobe Owns PDF and so on.  You 
>get a PAS (publicly accessible specification) instead 
>of an openly developed specification.  

A standards body isn't going to protect you from this. Not even ANSI.
Vendors do as vendors will.

-Bill de hÓra