Re: VOTE - Move XML Commons to Xerces

+1 from me. Great to see this move near-completion, under discussion as it's been since long before I went AWOL. Cheers! Neil Neil Graham Manager, C++ Compiler Front-End and Runtime Development IBM Toronto Lab Phone: 905-413-3519, T/L 969-3519 E-mail: [EMAIL PROTECTED] Gareth R

Re: [VOTE]: Fw: XML commons release

Here's my +1 as well; it's been far too long without a release of these two important building blocks. Cheers, Neil Neil Graham Manager, C++ Compiler Front-End and Runtime Development IBM Toronto Lab Phone: 905-413-3519, T/L 969-3519 E-mail: [EMAIL PROTECTED] Michael Glavassevi

Re: [VOTE] Migrate xml-commons from CVS to SVN

Hi Jeremias, +1 from me. SVN has cewrtainly proved useful and dependable in Xerces-C land. Cheers, Neil Neil Graham Manager, XML Parser Development IBM Toronto Lab Phone: 905-413-3519, T/L 969-3519 E-mail: [EMAIL PROTECTED] Jeremias Maerki <[EMAIL PROTECTED]> 06/21/2005 02:52

Re: Remaining work for JAXP 1.3 APIs

Hi Michael, Too bad all these fixes didn't make it into the JAXP APIs that were recently added to the main trunk. But definitely +1 to updating the trunk appropriately. Cheers, Neil Neil Graham Manager, XML Parser Development IBM Toronto Lab Phone: 905-413-3519, T/L 969-3519 E-mail: [

Re: CVS Resolver supports XML Catalogs 1.1

Thanks David, This looks to me exactly like the right thing to do. Cheers! Neil Neil Graham Manager, XML Parser Development IBM Toronto Lab Phone: 905-413-3519, T/L 969-3519 E-mail: [EMAIL PROTECTED] David Crossley <[EMAIL PROTECTED]> 05/06/2005 01:13 AM To Norman Walsh &

Re: CVS Resolver supports XML Catalogs 1.1

f you only need XML-APIS, for instance, you should not need to carry around a NOTICES file about public-domain material from Arbortext. So I'd suggest we establish separate NOTIZCES files for each of the subcomponents from the start. Cheers, Neil Neil Graham Manager, XML Parser Devel

Re: Donation of JAXP 1.3 Sources to Apache

ut on a branch in Xerces. Cheers, Neil Neil Graham Manager, XML Parser Development IBM Toronto Lab Phone: 905-413-3519, T/L 969-3519 E-mail: [EMAIL PROTECTED] Neeraj Bajaj <[EMAIL PROTECTED]> 04/04/2005 01:07 AM Please respond to xerces-j-dev To xalan-dev@xml.apache.org cc

Re: Donation of JAXP 1.3 Sources to Apache

folks at Sun for having surmounted all obstacles and got this done! Cheers, Neil Neil Graham Manager, XML Parser Development IBM Toronto Lab Phone: 905-413-3519, T/L 969-3519 E-mail: [EMAIL PROTECTED] Eduardo Pelegri-Llopart <[EMAIL PROTECTED]> 03/31/2005 11:41 AM Please respon

Re: SVN migration (Was: Donation of JAXP 1.3 Sources to Apache)

Hi David, David Crossley <[EMAIL PROTECTED]> wrote on 10/20/2004 03:20:26 AM: > Neil Graham wrote: > > > > > > So would this be an appropriate time to move the > > > xml-commons repository to SVN? > > > > Well, I don't know about you,

Re: Donation of JAXP 1.3 Sources to Apache

rtion of Apache projects have migrated to SVN so far? There would be a significantly higher amount of churn caused to the community by an SVN migration than was caused by our earlier Jira migration; so I'd prefer to go down a well-trod path than be on the bleeding edge in this particular

Re: Donation of JAXP 1.3 Sources to Apache

Hi all, Berin Lautenbach <[EMAIL PROTECTED]> wrote on 10/13/2004 06:59:22 PM: > I'm assuming that this is something that XML-Commons/Xerces/Xalan wish > to do? Here's a +1 from someone who's committed to Xerces-J and xml-commons. If either project didn't want to move up to the latest standa

Re: [PROPOSAL] javax.xml and javax.xml.namespace package to xml commons

ons to a version of what's *stable*; the DOM level 3 API's are not there yet for this reason. Since these classes were used in JSR's that have gone final, it makes sense to include them; but I don't believe we should be using commons to track where we think specs are likely to go

Re: [ANN] XInclude processor for xml-commons

such a thing, but I'm not sure many exist ATM. Anyway, before responding any further on these threads, I need to spend some quality time with XInclude, and hopefully also have a look at Joerg's code. Cheers! Neil Neil Graham XML Parser Development IBM Toronto Lab Phone

Re: [ANN] XInclude processor for xml-commons

its development lists, but they've been pretty much dead for quite some time... But I'll leave the hard job of selling XNI to Andy; it works well for us, but perhaps SAX is good enough for what you need it to do. Cocoon being the huge project it is, I certainly wouldn't blame you

Re: [ANN] XInclude processor for xml-commons

ting SAX, you're not in the Xerces pipeline world anymore; so this guy is only useful at the end of such a pipeline (whatever XNI components that pipeline has in it). So there's no way of putting a Xerces validator after that component, for instance (to do so would kind of defeat the po

Re: [ANN] XInclude processor for xml-commons

op a full PSVI API at this stage. > BTW the XInclude spec is one of the more sick of the canon. :) Oh well; such is life. Again, I'm not saying that Xerces is the only possible home for such a project--just want to make sure that what's done makes sense for as wide a user-base as pos

Re: [ANN] XInclude processor for xml-commons

is mean it supports text parsing? What would that mean in terms of the XInclude spec? Cheers! Neil Neil Graham XML Parser Development IBM Toronto Lab Phone: 905-413-3519, T/L 969-3519 E-mail: [EMAIL PROTECTED] |-+> | | "