XOM API for Processing XML with Java

[Wolfgang Hoschek <whoschek AT lbl.gov>]

nux-1.0rc3 has been uploaded to http://dsd.lbl.gov/nux/

Changelog:
	• 	XOM nomore requires Jaxen jar file unless really needed (soft  
dependency).
	• 	XQuery/XPath: Added explain() method returning a description of the  
compiled and optimized expression tree; useful for advanced performance  
diagnostics only.
	• 	XQuery/XPath: By default the doc() function now uses a  
DocumentURIResolver that uses a non-validating XOM Builder to parse  
documents.  This can be overriden by passing in your custom  
DocumentURIResolver.
	• 	XQuery/XPath: By default a top-level atomic value in the result  
sequence is converted to an Element named "atomic-value" with a child  
Text  node holding the atomic value's standard XPath 2.0 string  
representation. An "atomic-value" element is decorated with a namespace  
and a W3C XML Schema type attribute.  The XPath 2.0 string  
representation continues to be accessible via Node.getValue().  Because  
XOM has no concept of a namespace node, the same conversion occurs for  
XPath namespace nodes in the result sequence.  (The standard XPath 2.0  
string representation of a namespace node is its URI).  "Normal" nodes  
and anything not at top-level continue to be returned "as is", without  
conversion.


Examples for xs:integer, xs:string and xs:date:

<atomic-value xsi:type="xs:integer" xmlns="http://dsd.lbl.gov/nux";
    
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>1</atomic-value>
<atomic-value xsi:type="xs:string" xmlns="http://dsd.lbl.gov/nux";
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>hello  
world</atomic-value>
<atomic-value xsi:type="xs:date" xmlns="http://dsd.lbl.gov/nux";
    
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>2004-12-31</ 
atomic-value>