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: Sun, 28 Oct 2012 21:14:59 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-19671-523-g2e7oxEIKq@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19671

Andrew Eisenberg <andrew.eisenberg@us.ibm.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |andrew.eisenberg@us.ibm.com

--- Comment #1 from Andrew Eisenberg <andrew.eisenberg@us.ibm.com> ---
I'm not sure that I understand your concern. We say, "If an XQuery 3.0
processor processes a module labeled with a version of "1.0", it must either
raise a static error [err:XQST0031], or attempt to process the module with an
XQuery 1.0 processor."

An XQuery 3.0 processor can also be an XQuery 1.0 processor if it recognizes
XQuery 1.0 syntax and provides XQuery 1.0 semantics.

An XQuery 3.0 processor might be given:

xquery version "1.0"; count(./products/product)

and return 12.

It might be given:

xquery version "1.0";
for $p in ./products/product
group by $cat := $p/category
return <products category="{$cat}" count="{count($p)}" />

and return XPST0003.

This allows an author to use some XQuery 3.0 processors to write XQuery 1.0
modules that will work with other XQuery 1.0 processors.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Sunday, 28 October 2012 21:15:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 28 October 2012 21:15:01 GMT