29937 2016-10-13 15:23:27 +0000 [QT3TS] fn-load-xquery-module-060 2016-10-19 12:51:56 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XQuery 3 & XPath 3 Test Suite Candidate Recommendation PC Windows NT CLOSED FIXED P2 normal --- 1 tim oneil mike public-qt-comments oldest_to_newest 127766 0 tim 2016-10-13 15:23:27 +0000 I disagree with the expected result of the test, and don't think the description matches the test. The loaded module has no context item declaration, therefore doesn't place any restrictions on the context item type. When the module is compiled, the compiler introduces dynamic type checking for the assignment declare variable $cim:context as node() := .; which will trigger an XPTY0004 if $cim:context happens to be evaluated. <test-case name="fn-load-xquery-module-060"> <description>Checks for an error when calling fn:load-xquery-module and providing the wrong type of value for the context item.</description> <created by="Debbie Lockett" on="2015-06-01"/> <module uri="http://www.w3.org/fots/fn/load-xquery-module/context-item/module" file="load-xquery-module/context-item2-module.xqm"/> <test>fn:load-xquery-module("http://www.w3.org/fots/fn/load-xquery-module/context-item/module", map{"context-item" : "item"})</test> <result> <error code="FOQM0005"/> </result> </test-case> xquery version "3.1"; module namespace cim = "http://www.w3.org/fots/fn/load-xquery-module/context-item/module"; declare variable $cim:context as node() := .; declare function cim:get-context-child() as node()* { $cim:context/child::node() }; 127768 1 mike 2016-10-13 15:39:58 +0000 I agree. (We're passing this one because we redirect XPTY0004 to FOQM0005 rather indiscriminately, which is going to catch quite a few cases that shouldn't be caught). 127850 2 tim 2016-10-19 12:51:29 +0000 Now fixed.