This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Assertion <not><assert-type>function(xs:anyAtomicType) as xs:integer?</assert-type></not> will need to be negated if the changes to the judgement subtype-itemtype(Ai, Bi) in Bug 29586 are adopted. It might be necessary regardless of Bug 29586 if we take the view that it's acceptable to return a subtype. I suggest changing this to <assert-type>function(xs:anyAtomicType) as item()*</assert-type> at the very least.
Test map-put-003-hof is similarly affected.
Now fixed.
I am seeing three tests that appear to be still incorrect: map-merge-003-hof has <assert-type>function(xs:anyURI) as xs:integer*</assert-type> map-put-003-hof has <assert-type>function(xs:string) as xs:integer*</assert-type> map-entry-001-hof has <assert-type>function(xs:anyAtomicType) as xs:integer?</assert-type> I thought the idea/agreement was to change all of these to say "as item()*".
See rule 35 in 2.5.6.2 The judgement subtype-itemtype(Ai, Bi). Ai is map(K, V), and Bi is function(xs:anyAtomicType) as V?. The test asserts <assert-type>map(xs:string, xs:integer+)</assert-type> so we know that <assert-type>function(xs:anyAtomicType) as xs:integer*</assert-type> should hold, and therefore by rule 26, <assert-type>function(xs:anyURI) as xs:integer*</assert-type> should hold.
My re-opening in comment 3 is withdrawn.