> > Again, due to statement#1, there is no real reason to move the generic DOM > above the xerces package, but there are motivations to separate it into its > own package. > > -Ralf
Correction: One reason to move a generic DOM out above Xerces is so that you don't need the xerces jar simply to use the DOM. Of course we could provide a "jar-stripper" tool, which allows you to select the items you want. This will probably come up again, as xerces provides more functionality (like multiple DOMs), or even some DOM Level2 functionality which a specific client may not need.
