[brailleblaster] Re: XOM XPath Support
- From: "John J. Boyer" <john.boyer@xxxxxxxxxxxxxxxxx>
- To: brailleblaster@xxxxxxxxxxxxx
- Date: Fri, 11 Jan 2013 16:28:11 -0600
Thanks. This is a handy reference.
John
On Fri, Jan 11, 2013 at 06:11:50PM +0000, Keith Creasy wrote:
> Here is a pretty good explanation of XOM XPath support. Note that it looks
> like simple location paths do return a node set in document order:
>
> http://www.xom.nu/xpath.xhtml
>
> Document Order
>
> XPath node-sets are unordered (like any set) and do not contain duplicates.
> The Nodes object returned by the query method also does not contain
> duplicates.However, it orders all nodes in document
> order<http://www.w3.org/TR/xpath#dt-document-order>. Generally this is the
> order in which nodes would be encountered in a depth first traversal of the
> tree. Attributes and namespaces appear after their parent element in this
> order and before any child elements. However, otherwise their order is not
> guaranteed.
>
> (Refering to the order of attributes.)
>
>
>
>
>
> The main limitations eems to be this:
>
>
>
>
> Expressions that return non node-sets
>
> XOM only supports expressions that return node-sets as queries. Expressions
> that return numbers, booleans, or strings throw an XPathException. Examples
> of such expressions include count(//), 1 + 2 + 3,name(/*), and @id='p12'.
> Note that all of these expressions can be used in location path predicates.
> They just can't be the final result of evaluating an XPath expression.
>
>
> Keith Creasy
> Software Developer
> American Printing House for the Blind
> KCreasy@xxxxxxx
> Phone: 502.895.2405
> Skype: keith537
>
--
John J. Boyer; President, Chief Software Developer
Abilitiessoft, Inc.
http://www.abilitiessoft.com
Madison, Wisconsin USA
Developing software for people with disabilities
Other related posts:
