- From: <bugzilla@jessica.w3.org>
- Date: Tue, 10 Apr 2012 13:05:09 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16681
Summary: [XP30] err:XPDY0129
Product: XPath / XQuery / XSLT
Version: Member-only Editors Drafts
Platform: PC
URL: https://www.w3.org/XML/Group/qtspecs/specifications/xq
uery-30/html/xpath-30.html#id-cast
OS/Version: Windows NT
Status: NEW
Severity: normal
Priority: P2
Component: XPath 3.0
AssignedTo: jonathan.robie@gmail.com
ReportedBy: tim@cbcl.co.uk
QAContact: public-qt-comments@w3.org
In section 3.13.2 Cast of XPath 3.0, a new error is introduced.
err:XPDY0129
The cast failed because the input value is not in the lexical space of the
target type (after whitespace normalization as required by the target type).
Yet the text also states that:
"If casting from the input type to the target type is supported but
nevertheless it is not possible to cast the input value into the value space of
the target type, a dynamic error is raised. [err:FORG0001] This includes the
case when any facet of the target type is not satisfied. For example, the
expression "2003-02-31" cast as xs:date would raise a dynamic error."
What conditions does XPDY0129 catch which are not already caught by FORG0001
(Invalid value for cast/constructor.) or indeed err:FOCA0002 (Invalid lexical
value).
Note that XPDY0129 is not mentioned in section 18 Casting of F&0 3.0.
--
Configure bugmail: https://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, 10 April 2012 13:05:20 UTC