It also seems that some XPath 3.1 language features like the string concatenation operator "||" work nevertheless, so that seems to indicate that under the hood you use a version of Saxon that supports XPath 3.1 and not 3.0.
When I use other features like the XPath 3.1 map or array types, for instance
Code: Select all
array { //*[not(*)]/string() }
This feature request is to allow the use of full XPath 3.1 and some way to allow an XPath query to return maps and/or arrays.