W3C home > Mailing lists > Public > public-qt-comments@w3.org > November 2015

[Bug 29220] map-merge-003-hof, map-entry-001-hof, map-put-003-hof

From: <bugzilla@jessica.w3.org>
Date: Tue, 03 Nov 2015 19:04:36 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29220-523-HtdA1aYtr8@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29220

--- Comment #2 from Christian Gruen <christian.gruen@gmail.com> ---
(In reply to Michael Kay from comment #1)
> §§This means that a function item type with a more specific return type,
> such as function(xs:anyAtomicType) as xs:integer, does not match a map
> in the sense required to satisfy the instance of operator.§§
> [...]
> I think that if you are challenging this test case then you are challenging
> this statement in the spec, especially the sentence I have marked with
> §§..§§.
Yes, it may well be that the spec needs to be revised as well. – In the
discussed test, it is assumed that 

  map { "foo", 1 to 5 } instance of function(xs:anyURI) as xs:integer*

yields false, but I believe it should yield true.

However, the result should not be true for the example return type in the spec
(xs:integer), because the returned result of a map can always be the empty
sequence.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 3 November 2015 19:04:38 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 3 November 2015 19:04:38 UTC