> ... isn't this just the kind of thing API versioning is for? Sometimes. Folk talk about both "major versions" and "minor versions". Incompatible changes, as a rule, only show up in "major versions" which are widely advertised as breaking things, and forcing rewrites of applications.
There have to be very strong reasons for the user community to adopt such incompatible changes. Coping with a W3C inconsistency-du-jour seems to be at best a weak reason to start defining a SAX3 that's incompatible with SAX2 ... :) - Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
