- From: <bugzilla@jessica.w3.org>
- Date: Fri, 19 Sep 2014 09:17:34 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21893
Tim Mills <tim@cbcl.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CLOSED |REOPENED
CC| |tim@cbcl.co.uk
Component|XPath 3.0 |XPath 3.1
Resolution|FIXED |---
--- Comment #2 from Tim Mills <tim@cbcl.co.uk> ---
I'm reopening this because the text of XPTY0117 says:
"In a cast expression, if an item is of type xs:untypedAtomic and the expected
type is namespace-sensitive, a type error [err:XPTY0117] is raised."
yet the error is only raised in function conversion (3.1.5.2 Function
Conversion Rules), and NOT casting.
Also in that section we read
"Each item in the atomic sequence that is of type xs:untypedAtomic is cast to
the expected generalized atomic type. For built-in functions where the expected
type is specified as numeric, arguments of type xs:untypedAtomic are cast to
xs:double. If the item is of type xs:untypedAtomic and the expected type is
namespace-sensitive, a type error [err:XPTY0117] is raised."
The text "If the item is of type xs:untypedAtomic and the expected type is
namespace-sensitive, a type error [err:XPTY0117] is raised." should probably
come first here to indicate that a cast is NOT attempted.
Although this is a bug in 3.0, I'll hope it can be fixed in 3.1 and have marked
it as a bug against 3.1.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 19 September 2014 09:17:37 UTC