cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Turner <j...@socialchange.net.au>
Subject Re: cvs commit: xml-cocoon2 LISCENSE.resolver
Date Sat, 13 Oct 2001 08:10:19 GMT
On Wed, Oct 10, 2001 at 02:03:22PM +0200, Stefano Mazzocchi wrote:
[..]
> > I think the only way to avoid devloving into an IANAL discussion is to ask
> > Sun. Does any of you have the authority to talk to Sun on behalf of ASF?
> 
> I do and I did some days ago: Norman and I are already talking about
> having Sun donate the resolver.jar code to the ASF. The Apache XML PMC
> suggested to talk about the integration in a public forum and I was
> going to start the discussion on the Xerces-J list to know if the
> community believes it's better to have a separate project for entity
> resolution or ship it with xerces.
> 
> Norman like the first solution more (making a different project since it
> provides more flexibility and componentization even for other
> parsers/tools), I'm more or less neutral and I'd like to choose the
> solution that makes it easier for everybody (devs and users) to
> bootstrap that code.
[..]
> 
> So, let's talk about it here to start: assuming the code gets donated,
> where would you like it to go?
> 
> The options I see (but maybe you have others) are:
> 
>  1) integrate with Xerces
>  2) create another project under Apache XML

I'd prefer a separate project. The catalog code has nothing to do with
Xerces, and "integrating" it seems to imply breaking parser-neutrality.

Perhaps there could be an xml-commons, like jakarta-commons, for this sort of
reusable stuff?

--Jeff

> In all cases, next step will be talking to the Xerces community to see
> what they think about it.
> 
> Stefano.

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message