W3C home > Mailing lists > Public > public-qt-comments@w3.org > October 2012

[Bug 19671] [XQ3.0] Backwards compatibility and the version declaration

From: <bugzilla@jessica.w3.org>
Date: Tue, 30 Oct 2012 12:45:04 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-19671-523-AKdNErCSUo@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19671

--- Comment #5 from Jonathan Robie <jonathan.robie@gmail.com> ---
> The Editor will wordsmith this policy properly.

Here's my first attempt.

[Definition: A version declaration can identify the applicable XQuery syntax
and semantics for a module, as well as its encoding.] The version number "1.0"
indicates a requirement that the module must be processed by an XQuery 1.0
processor; the version number "3.0" indicates a requirement that the module
must be processed by an XQuery 3.0 processor. If the version declaration is not
present or the version is not included in the declaration, an XQuery 3.0
processor assumes a version of "3.0".

If an XQuery 3.0 processor processes a module labeled with a version other than
"3.0", it must do one of the following:

* Evaluate the query using the semantics of the XQuery version specified in the
version declaration.

* Evaluate the query using the semantics of XQuery 3.0.
  Note: An implementation may issue a warning in this case. 

* Raise a static error [err:XQST0031].

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 30 October 2012 12:45:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 30 October 2012 12:45:14 GMT