XOM API for Processing XML with Java

[Elliotte Harold <elharo AT metalab.unc.edu>]

Regier Avery J wrote:


> I'd be disappointed in seeing anything less than 100% conformance.  In that your goals 
> are expressly "correctness, simplicity, and performance, in that order", I 
> would assume correctness to include completeness.  Practically, I'm working on an 
> internal company messaging spec that may include the use of XPath and XPointer.  If I 
> have to write into the spec limitiations on the use of XPath because there are no 
> libraries that support the whole spec, it would be a major pain and negate a lot of the 
> benefit of pointing people to an existing open spec rather than writing our own and the 
> implementations that go with it.  (With that in mind, I'm all for seeing XPointer 
> support as well. :)

Saxon and NUX already give you close to 100% compliance to XPath. 
(Apparently there are some holes around the edges, but you're unlikely 
to fall into them unless you go looking for them.) I'm just trying for 
the right 80/20 split that will earn the biggest payback with the least 
effort and complexity. Integrating full XPath into XOM would require a 
much more complex API.


--
Elliotte Rusty Harold  elharo AT metalab.unc.edu
XML in a Nutshell 3rd Edition Just Published!
http://www.cafeconleche.org/books/xian3/
http://www.amazon.com/exec/obidos/ISBN=0596007647/cafeaulaitA/ref=nosim