Hello Jeremy, The seriousness of the defects depend on what you use.
The XML Schema API [1] spec was published fairly recently. We want to reduce the impact on users of this API by releasing a fix for it now instead of waiting several months while new developers run into this problem (especially anyone else who might choose to implement it). Deprecating the HTML/XHTML serializers now instead of later should give people time to change their code while we work towards picking up Xalan's serialization code. The serializer bug injected into 2.6.1 might have delayed that release had we learned about it before it went out. The SAX bugs seem to be giving some users of Castor [2] a headache. [1] http://www.w3.org/Submission/2004/SUBM-xmlschema-api-20040122/ [2] http://www.mail-archive.com/castor-dev%40exolab.org/msg15353.html On Mon, 16 Feb 2004, Jeremy Carroll wrote: > I am having difficulty assessing the significance of your proposal to do a > further point release so quickly: are the defects with Xerces 2.6.1 really > that serious? should we (the Jena team) effectively do a recall on Jena 2.1 > and release a Jena 2.1.1 with Xerces 2.6.2? (A fairly small minority of > Jena users will be using the Xerces APIs directly). > > > Jena URL > http://jena.sourceforge.net > > > Jeremy Carroll --------------------------- Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: [EMAIL PROTECTED] E-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
