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 17250 - fn-filter-012
Summary: fn-filter-012
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XQuery 3 & XPath 3 Test Suite (show other bugs)
Version: Last Call drafts
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Tim Mills
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-30 17:32 UTC by Michael Kay
Modified: 2012-05-31 09:55 UTC (History)
0 users

See Also:

Attachments

Description Michael Kay 2012-05-30 17:32:09 UTC 
This test does

fn:filter( fn:string#1, () )

and expects the result ().

I think it is legitimate to raise XPTY0004, on the grounds that the supplied function is the wrong type: it returns a string rather than a boolean.

Under Errors and Optimization it is also legitimate to return ()
Comment 1 O'Neil Delpratt 2012-05-31 08:20:17 UTC 
Hi Tim, this seems right to me, however would you be able to resolve this bug issue. Thanks.
Comment 2 Tim Mills 2012-05-31 08:47:36 UTC 
Agreed.  For the record, it is the text

"If the result of invoking the new function would necessarily result in a type error, that error may be raised during function coercion. It is implementation dependent whether this happens or not."

that permits XPTY0004.
Comment 3 Tim Mills 2012-05-31 09:19:05 UTC 
Fixed in CVS.  

Please mark the bug as CLOSED if you agree with the resolution.  Otherwise, REOPEN.