Hi Christian,
The spec offers three alternatives:
* Process the module using the specification of the XQuery version
identified in the version declaration.
* Process the module using the specification of XQuery 3.0. (→ 3.1)
* Raise a static error [err:XQST0031]
But these are the alternatives for
> If an XQuery 3.0 processor processes a module labeled with a version
of "1.0", it must do one of the following:
How do we know that they also apply to an XQuery 3.1 processor ?
Bye,
Benito
On 10/26/2014 07:59 PM, Christian Grün wrote:
Is xquery version "3.1"; valid?
I think it should be (although it seems not to be mentioned in the
current version of the spec [1]).
What should a XQuery processor that understands 3.1 do, if the query starts
with xquery version "3.0";
but contains expressions that are only valid in 3.1 and not in 3.0?
The spec offers three alternatives:
* Process the module using the specification of the XQuery version
identified in the version declaration.
* Process the module using the specification of XQuery 3.0. (→ 3.1)
* Raise a static error [err:XQST0031]
Hope this helps,
Christian
[1] http://www.w3.org/TR/2014/WD-xquery-31-20141007/#id-version-declaration
_______________________________________________
[email protected]
http://x-query.com/mailman/listinfo/talk
