[Bug 16089] New: [QT3] FunctionCall-015


           Summary: [QT3] FunctionCall-015
           Product: XPath / XQuery / XSLT
           Version: Member-only Editors Drafts
          Platform: PC
        OS/Version: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XQuery 3 & XPath 3 Test Suite
        AssignedTo: benjie.nguyen@gmail.com
        ReportedBy: tim@cbcl.co.uk
         QAContact: public-qt-comments@w3.org

I'm unable to spot the type check error in this test case.  From the comment, I
suspect it relatese to 


Applying Function Conversion Rules, 

1. Atomization is applied to the given value, resulting in a sequence of atomic

   This gives xs:QName(xs:untypedAtomic("local:f")

2. Expected type of constructor function xs:QName in xs:anyAtomicType?.  This
is not namespace-sensitive.  Therefore XPTY0117 is not raised.

3. Result is xs:QName(xs:untypedAtomic("local:f")) (not an error in XQ30).

Am I missing something?

BTW, I'm not sure this test really depends on schema validation.

   <test-case name="FunctionCall-015">
      <description>Test that arguments are atomized - but not the argument of
casting to QName</description>
      <created by="Michael Kay" on="2011-10-31"/>
      <dependency type="spec" value="XQ30+"/>
      <dependency type="feature" value="schemaValidation"/>
         declare function local:f($in as xs:integer) as xs:integer { $in + 1 };
         let $f := function-lookup(xs:QName(<f>local:f</f>), 1)
         return $f(12)]]></test>
        <error code="XPTY0004"/>

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 Thursday, 23 February 2012 10:33:20 UTC