- From: <bugzilla@jessica.w3.org>
- Date: Wed, 09 Mar 2016 23:27:22 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29526 Bug ID: 29526 Summary: [XQ31] Incompatible change to ExtensionExpr Product: XPath / XQuery / XSLT Version: Candidate Recommendation Hardware: PC OS: All Status: NEW Severity: normal Priority: P2 Component: XQuery 3.1 Assignee: jonathan.robie@gmail.com Reporter: mike@saxonica.com QA Contact: public-qt-comments@w3.org Target Milestone: --- In XQuery 1.0 and 3.0, It was defined that the construct (# pragma #) {} raised a static error if the pragma was not recognized by the query processor. In XQuery 3.1 this now returns an empty sequence when the pragma is not recognized. Although we don't normally treat the abolition of a static error as an incompatibility, I'm worried that we have removed a useful capability here. This construct could be used to make it clear that a query relied on a vendor extension and that no fallback was available. It's a construct that was valid and had a well-defined meaning, and we have changed that meaning. Can we please think again? -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 9 March 2016 23:27:24 UTC