This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 16681 - [XP30] err:XPDY0129
Summary: [XP30] err:XPDY0129
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XPath 3.0 (show other bugs)
Version: Member-only Editors Drafts
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Jonathan Robie
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
Depends on:
Reported: 2012-04-10 13:05 UTC by Tim Mills
Modified: 2012-05-22 16:33 UTC (History)
0 users

See Also:


Description Tim Mills 2012-04-10 13:05:07 UTC
In section 3.13.2 Cast of XPath 3.0, a new error is introduced.


    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.
Comment 1 Jonathan Robie 2012-05-22 16:33:44 UTC
I will replace XPDY0129 with FORG0001.