- From: <bugzilla@jessica.w3.org>
- Date: Wed, 15 Apr 2015 11:03:45 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28494
Michael Kay <mike@saxonica.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mike@saxonica.com
--- Comment #1 from Michael Kay <mike@saxonica.com> ---
For reference this test is in prod/FLWORExpr.xml
The essence of the test is
let $baseElement as empty-sequence() := $extended/baseElement
return $baseElement
where $extended/baseElement actually selects something.
By XPTY0005 I think you mean XPST0005. I agree that XPST0005 is a reasonably
result.
I'm not happy with the idea that the query can validly return an empty
sequence. I know that almost anything can be justified under "errors and
optimizations", but this seems a bit extreme. I would argue that it violates at
least the spirit of the rule "If a processor evaluates an operand E (wholly or
in part), then it is required to establish that the actual value of the operand
E does not violate any constraints on its cardinality." - the intended effect
of this rule is that you can short-cut evaluation of a sequence, but not in
such a way that you fail to detect cardinality errors.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 15 April 2015 11:03:47 UTC