[jdom-interest] What do we want JDOM to be?
kesavk at voquette.com
Wed Dec 6 10:21:24 PST 2000
Yes, We all want to hear from Jason & Brett whats the future of JDOM how
will it going to maintain the 80% or 20% difference from DOM. As one can
see DOM is now getting close to its version3.0 they are able to add lots of
features. To maintain what ever difference JDOM also should be having more
functionalities otherwise the 20 will eventually become 50. I enjoyed using
JDOM in my project and I got lots of benifits by using JDOM but at the same
time I had to use again DOM for XPathe XSL etc. I used to convert JDOM
objects to DOM to get the functionality. I am expecting this kind of
converting from JDOM to DOM and reverse should get decreased in future. I
expect we can develop full featured XML based applications with JDOM
650 356 3740
mailto:kesavk at voquette.com
From: Guy Nirpaz [mailto:guyn at tantian.com]
Sent: Tuesday, December 05, 2000 10:27 PM
To: jdom-interest at jdom.org
Subject: [jdom-interest] What do we want JDOM to be?
Recent discussions on this mailing list clearly show that not everybody
understands the same way what is 80% (or 95%) and what isn't, and belongs to
20% (or 5%). The project initiators (Brett and Jason) stated that JDOM isn't
going to encapsulate everything that can be done with XML API .The big
question is what goes in and what stays out?
Most people really like JDOM the first time they lay their hands on it. And
the excitement even increases when they do actual coding using JDOM (at
least me and my team have). But, after a while people start looking for more
advanced features - like XPath, XSLT, etc... . Some of them are inside JDOM
some aren't yet and some will never be.
I think it is a good point in the JDOM lifecycle to have a discussion on
what eventually will get into JDOM and what will stay out.
For example - is JDOM going to support XPath? (I know bob is working on
that) If so, what are the features that we need to add to the API for XPath
support? The same question is valid for XLink, XInclude, XSLT and others.
I believe that if we get to agree on the functional spec. we will be able to
clearly identify the design choices. People will be able to find out if JDOM
is right for them (or will be in the future) or not - and yes, there are
cases when it isn't ;-)
guyn at tantian.com
To control your jdom-interest membership:
More information about the jdom-interest