xml-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arved Sandstrom" <Arved...@chebucto.ns.ca>
Subject Re: [vote] Accepting Entity Resolver Donation
Date Mon, 03 Dec 2001 13:07:09 GMT
+1.

----- Original Message -----
From: "Davanum Srinivas" <dims@yahoo.com>
To: <general@xml.apache.org>
Sent: Monday, December 03, 2001 8:43 AM
Subject: Re: [vote] Accepting Entity Resolver Donation


> Team,
>
> Since Avalon and Cocoon2 are interested, there are no other conditions
that i see at will
> disqualify Entity Resolver from xml-commons: See
>
http://cvs.apache.org/viewcvs.cgi/~checkout~/xml-commons/README.html?rev=1.1
&content-type=text/html
> for more information.
>
> So Here's my VOTE for adding Entity Resolver to xml-commons:
> - Davanum Srinivas [+1]
>
> Please add yours....
>
> Thanks,
> dims
>
> --- David Crossley <crossley@indexgeo.com.au> wrote:
> > Stefano Mazzocchi wrote:
> > > A while back, I talked to Norman Walsh (of Docbook fame, if you don't
> > > know him) about making his entity resolver (or entity catalog)
> > > implementation a full open source project, given the incredible need
for
> > > such a thing on XML-based applications (see recent talks on xml-dev
> > > about XML portability, for example).
> > >
> > > Cocoon already uses such an entity resolver and since we were thinking
> > > about moving the most general XML-based components back into Avalon
> > > (so that they are available to all the rest of Avalon-aware
applications),
> > > it would be extremely beneficial for us to have the ability to
influence
> > > directly the code in order to make it easier to deploy and use such
> > > important tool.
> > >
> > > Norman wrote this code while working at Sun, but it's already licensed
> > > with a BSD-like license, so there are no legal obstacles whatsoever.
> > >
> > > What I proposed Norman is to bootstrap a community around this code
here
> > > under Apache and he liked the concept.
> > >
> > > I see several possible solutions:
> > >
> > > 1) merge the donated code with an existing subproject (Xerces would be
> > > my choice)
> >
> > The entity resolver can be attached to any SAX parser and stylesheet
> > processor. So it would not be appropriate to be under Xerces. Also,
> > the entity resolver needs high exposure, as it is a facilty that needs
> > to be widely used.
> >
> > > 2) create a new subproject (but there might not be enough community
> > > diversity for this to happen)
> > >
> > > 3) place it under xml-commons, following the same charter and
community
> > > restrictions of jakarta-commons.
> >
> > This sounds like an appropriate place.
> >
> > > 4) ???
> > There is another option ...
> >
> > 4) Avalon Excalibur
> > The Excalibur people expressed interest back in September.
> > http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=100303902726035&w=2
> >
> > 5) ???
> >
> > > Norman suggested to make the code available separately from an
existing
> > > product in order to increase usability and modularity, since entity
> > > resolution using SAX2 doesn't require the presence of an XML parser.
> > >
> > > So, there are a few votes:
> > >
> > > a) would you like to accept this code donation?
> >
> > +1
> >
> > > b) if so, where do you think it should be located?
> >
> > I see that there are two options:
> > 3) xml-commons
> > 4) Avalon Excalibur
> >
> > I do not know on what grounds to decide. I lean towards
> > Excalibur because avalon-dev have expressed interest.
> > However, xml-commons might ensure that the resolver
> > remained independent. An Excalibur component would
> > simply have the classes to implement the resolver - this
> > is what would be moved from the current Cocoon.
> >
> > After expressing that, i seem to have found my stance:
> > xml-commons is the home for the entity resolver donation
> > and subsequent project.
> > Excalibur has a new component that hooks up the resolver
> > to any parser that gets used by the Avalon framework.
> > --David Crossley
> >
> > > Please place a vote.
> > >
> > > [Norm, sorry for having taken so long for this but I had to wait for
the
> > > other code donations to happen or being resolved]
> > >
> > > Thanks.
> > >
> > > --
> > > Stefano Mazzocchi      One must still have chaos in oneself to be
> > >                           able to give birth to a dancing star.
> > > <stefano@apache.org>                             Friedrich Nietzsche
> > > --------------------------------------------------------------------
> > àßß@
> >
> > ---------------------------------------------------------------------
> > In case of troubles, e-mail:     webmaster@xml.apache.org
> > To unsubscribe, e-mail:          general-unsubscribe@xml.apache.org
> > For additional commands, e-mail: general-help@xml.apache.org
> >
>
>
> =====
> Davanum Srinivas - http://jguru.com/dims/
>
> __________________________________________________
> Do You Yahoo!?
> Buy the perfect holiday gifts at Yahoo! Shopping.
> http://shopping.yahoo.com
>
> ---------------------------------------------------------------------
> In case of troubles, e-mail:     webmaster@xml.apache.org
> To unsubscribe, e-mail:          general-unsubscribe@xml.apache.org
> For additional commands, e-mail: general-help@xml.apache.org
>


---------------------------------------------------------------------
In case of troubles, e-mail:     webmaster@xml.apache.org
To unsubscribe, e-mail:          general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org


Mime
View raw message