i followed your discussion after my return from the hollidays. IMHO, the
most import thing that had to be noticed under all circumstances is that
a JDOMv2 must be able to process not only xml documents but xml fragments.
If the public api will be changed anyway, we should take the chance for
adjusting JDOMv2 to the process modell of the new XPath/XQuery datamodel.
I know, this means a lot of conceiving changes, but this will be worthwhile.
So, what did you all say about a XDM-compliant JDOMv2? I've spended some
thoughts about that in a private project, but at least i didn't have had
the time to perform changes in that way.
To control your jdom-interest membership: