Breeze looks like a Java/XML databinding solution? Lots more of those about
- Castor et al. I'd have thought either that these would be seen as falling
into a different category (apples and oranges) or that they'd need fuller
representation.
Out of SAX, DOM, JDOM and dom4j I'd predict the same winner for most
use-cases - and it isn't DOM! James - is it just a financial restriction
upon your attending?
- Thomas.
At 10:11 29/06/2001 +0100, James Strachan wrote:
>Does anyone fancy taking part in a Town Hall meeting at XML 2001 Conference
>(in Florida this December) to compare XML APIs, highlighting dom4j's
>advantages over the alternatives? Details are below - though the deadlines
>are wrong apparently, there's much more time.
>
>I'd love to go, it could be fun but I don't think I'll be able to make it.
>(And my bank balance hasn't recovered after JavaOne :-).
>
>James
>
>From: "Philippe Le Hegaret" <[EMAIL PROTECTED]>
>To: "James Strachan" <[EMAIL PROTECTED]>
> > Here is a proposal for a Town Hall meeting during the XML 2001 Conference
> > http://www.gca.org/attend/2001_conferences/xml_2001/.
> >
> > The purpose is to compare JDOM [1], DOM4J [2], DOM [3], ElectricXML [4],
>Breeze
> > [5], and SAX [6] during the meeting. The attendee must be able to
>understand
> > the differences between the APIs, their performances, and their advantages
>and
> > disadvantages.
> >
> > Being able to compare APIs is not easy:
> > - they can be implementation independent
> > - their scopes might be different,
> > - DTD/Schema datatypes specific,
> > - etc.
> >
> > In order to compare them fairly, the idea is to come up with a set of use
>cases
> > (4 seems a reasonable number) and try to resolve them using each API. Each
>use
> > case should try to give a favor to one of the API but must be a user
>common use
> > case. Each use case should be approachable by all APIs (otherwise we can't
> > really compare them). The scope of the expected solutions will be clearly
> > defined (loading, error handling, valid/invalid XML documents, ...).
> >
> > I need at least one expert to defend each API using the _Java_ language. 2
>is a
> > maximun. Each expert will be in charge of proposing a solution for each
>use
> > case using his API and can also try with others APIs. He must be able to
> > present the advantage of his solutions, including the time spent to
>develop
> > them. If some important points regarding your API will be not be covered
>by the
> > use case, you will be able to mention them, as long as they are
>technicals.
> >
> > Since I'm planning to chair the Town Hall, I will stay neutral and won't
>be
> > able to defend the DOM API. Keep in mind that my goal is not encourage the
> > public to only use the DOM API but to give them directions to choose
>between
> > the current APIs. If you plan to show performance comparaisons during the
> > discussion, please give the results and code used to test the APIs at
>least one
> > month before the conference. This is an open-mike forum so attendees will
>be
> > able to ask questions or argue with the experts.
> >
> > I guess that, if the participants are acting in a fairly manner, the
>attendees
> > will have an interesting discussion.
> >
> > If you accept to represent one of the APIs, please let me know asap
>(deadline
> > is June 24, 2001 - 5 days _before_ the XML 2001 deadline). If you don't
>want to
> > represent your API, let me know asap, I will need to find someone else. If
>you
> > can't participate but have someone to replace you, let me know. Feel free
>to
> > forward to any appropriate person. If I'm not able to find enough experts
>for
> > each API before the June 24, I'll cancel this proposal.
> >
> > If you don't want to participate in this town hall meeting, please let me
>know
> > and I'll try to find someone to replace you.
> >
> > Regarding the choice of use cases, I'll propose them before August 31,
>2001. We
> > must be able to reach a consensus on them before October 9, 2001. It will
>give
> > you two months to implement the solutions. Of course, if you have a
>proposal
> > for a use case, feel free to propose it.
> >
> > Regards,
> >
> > Philippe
> >
> > [1] http://www.w3.org/DOM/
> > [2] http://jdom.org/
> > [3] http://dom4j.org/
> > [4] http://www.themindelectric.com/products/xml/xml.html
> > [5] http://www.breezefactor.com/
> > [6] http://www.megginson.com/SAX/
> > --
> > Philippe Le Hegaret - http://www.w3.org/People/LeHegaret/
> > World Wide Web Consortium (W3C), DOM Activity Lead
> >
>
>
>_________________________________________________________
>Do You Yahoo!?
>Get your free @yahoo.com address at http://mail.yahoo.com
>
>
>_______________________________________________
>dom4j-dev mailing list
>[EMAIL PROTECTED]
>http://lists.sourceforge.net/lists/listinfo/dom4j-dev
_______________________________________________
dom4j-dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dom4j-dev
