Jeremias Maerki <[EMAIL PROTECTED]> wrote on 11/19/2006 04:13:49 AM: > But couldn't the stable parts be merged into Trunk and released from > there? With the separate JAR it shouldn't get in the way of the TCK, > would it?
Do you mean the SAC, SMIL and SVG bindings? I agree that those could be merged onto the trunk. > On 19.11.2006 05:19:59 Michael Glavassevich wrote: > > Hi Cameron, > > > > Cameron McCormack <[EMAIL PROTECTED]> wrote on 11/18/2006 07:45:49 PM: > > > > > Hi commonsers. > > > > > > Earlier this year, Jeremias took the initiative[1] to make a branch of > > > XML Commons to include DOM Level 3 (and SVG 1.1) interfaces. Batik is > > > looking at making a release soon (in the next couple of months) and so > > > I?d like to reuse as much external code as possible from Commons rather > > > than including it in Batik?s repository. > > > > > > Are there any plans on merging this branch into the trunk any time soon > > > (and having another release)? > > > > Oddly enough, I was just about to propose a release for this Wednesday so > > that Xalan-J 2.7.1 can pick up the latest APIs in their release [2] on > > Friday. > > > > I don't think we can move DOM Level 3 Events onto the trunk yet. JAXP 1.3 > > (which is currently on the trunk) includes DOM Level 2 Events. Since DOM > > Level 3 Events adds methods to existing interfaces it's probably not going > > to get by the JAXP 1.3 TCK's signature tests. This TCK issue [3] is what > > led to having a branch in the first place. > > > > > I note that DOM Level 3 Events is still a > > > Working Draft (and I?m not sure what the current timeline is) and DOM 3 > > > XPath is a Note (but will be returned to WD status soon), so that may > > > affect whether you want these interfaces to go in a release at this > > > stage. > > > > > > Including only the stable DOM Level 3 interfaces in a Commons release, > > > and having the unstable ones in Batik?s tree, would be a good compromise > > > for now I think. If a release isn?t going to be made soon, is it > > > ?wrong? to make a jar from code that?s in the branch and include it in > > > Batik?s distribution? > > > > Historically that's what had been happening with Xerces and Xalan > > releases. Really there should have been official releases of the APIs. In > > the future (hopefully in the next few days) there will be. I think we > > should do the same for Batik and have a release of the external-extended > > branch. > > > > > (By the way, should discussion remain on this list, or move to a xerces > > > list?) > > > > This is still the right list. > > > > > Thanks, > > > > > > Cameron > > > > > > [1] http://www.mail-archive.com/[email protected]/msg00560.html > > > > > > -- > > > Cameron McCormack, http://mcc.id.au/ > > > xmpp:[EMAIL PROTECTED] ? ICQ 26955922 ? MSN [EMAIL PROTECTED] > > > > [2] http://marc.theaimsgroup.com/?l=xalan-dev&m=116384070614284&w=2 > > [3] http://marc.theaimsgroup.com/?l=xml-commons-dev&m=113889540731107&w=2 > > > > Michael Glavassevich > > XML Parser Development > > IBM Toronto Lab > > E-mail: [EMAIL PROTECTED] > > E-mail: [EMAIL PROTECTED] > > > > Jeremias Maerki Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: [EMAIL PROTECTED] E-mail: [EMAIL PROTECTED]
