Hi Michael, Thanks for sharing the release update for next version of Xerces.
I am quite excited to seeing the new Xerces-J release, available to the community :) The timing of the release, as you wrote, looks great to me :) On Wed, Oct 14, 2009 at 11:25 AM, Michael Glavassevich <[email protected]> wrote: > Hi all, > > I think it's about time we had a release. It's been over two years since the > last one and during that time we've made significant progress in a number of > areas: > > * XML Schema 1.1 > * JAXP 1.4 > * StAX event API (javax.xml.stream.events) > * Element Traversal API [1] (org.w3c.dom.ElementTraversal) > * Unicode normalization and normalization checking > > among other enhancements. > > Before we can do the Xerces release, we're first going to need to get out an > official release of the JAXP 1.4 APIs from XML Commons. The coding has been > done for awhile now. Just needs some documentation updates and a release > candidate to vote on. If anyone would like to help out with that it would be > appreciated. Hoping we could wrap that up and roll out releases from the > other branches of XML Commons over the next month. > > Then we could start preparing the Xerces-J release. There's been a bit of > chatter about having one in December. How does Friday, December 18th sound? > Just before the end of the year. > > I'm thinking that we'd release two sets of binaries for 2.10.0, one built > from the trunk and an experimental one from the XML Schema 1.1 branch so > that the community could start to try out the new features: assertions, > conditional type assessment, etc... with an understanding that things could > change in the future along with the spec which isn't final yet. > > What do folks think? > > Thanks. > > [1] http://www.w3.org/TR/ElementTraversal/ > > Michael Glavassevich > XML Parser Development > IBM Toronto Lab > E-mail: [email protected] > E-mail: [email protected] -- Regards, Mukul Gandhi --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
