- From: <bugzilla@wiggum.w3.org>
- Date: Tue, 06 Oct 2009 10:27:50 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7163
Jonathan Robie <jonathan.robie@redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
--- Comment #6 from Jonathan Robie <jonathan.robie@redhat.com> 2009-10-06 10:27:49 ---
I propose to fix this with the following text in XQuery 1.1:
<quote="XQuery 1.1">
XQuery Version 1.1 is an extension of XPath Version 2.1. In general, any
expression that is syntactically valid and executes successfully in both XPath
2.0 and XQuery 1.0 will return the same result in both languages. There are a
few exceptions to this rule:
* Because XQuery expands character entity references and XPath does not,
expressions containing character entitities produce different results in the
two languages. For instance, the value of the string literal "&" is & in
XQuery, and & in XPath. (XPath is often embedded in other languages, which
may expand character entitities before the XPath expression is evaluated.)
* The namespace axis, which was deprecated in XPath 2.0, is not supported in
XQuery.
* If XPath 1.0 compatibility mode is enabled, XPath behaves differently from
XQuery in a number of ways, which are discussed in [XPath 1.0].
</quote>
In XPath 2.1, the last bullet point is replaced with the following:
<quote="XPath 2.1">
* If XPath 1.0 compatibility mode is enabled, XPath behaves differently from
XQuery in a number of ways, which are noted throughout this document, and
listed in "I.2 Incompatibilities when Compatibility Mode is false".
</quote>
I am marking this as fixed, feel free to reopen if I got this wrong.
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 6 October 2009 10:27:51 UTC