W3C home > Mailing lists > Public > public-qt-comments@w3.org > March 2017

Re: [FO31] map:entry superfluous?

From: Michael Kay <mike@saxonica.com>
Date: Thu, 16 Mar 2017 09:53:59 +0000
Cc: public-qt-comments <public-qt-comments@w3.org>, Andrew Coleman <andrew_coleman@uk.ibm.com>
Message-Id: <2BA103F5-54A9-4162-8A7E-DB3A6B4CD2F3@saxonica.com>
To: Thomas Fischer <fischer.th@gmail.com>
Just for the record: this comment was captured at


where you can find the record of the Working Group's deliberations.

Many thanks for taking the time to comment on the specification.

Michael Kay
for the XSL and XQuery Working Groups

> On 30 Nov 2016, at 14:38, Thomas Fischer <fischer.th@gmail.com> wrote:
> Hi,
> the documentation for map:entry <https://www.w3.org/XML/Group/qtspecs/specifications/xpath-functions-31/html/#func-map-entry> says:
> Unlike the map expression (map{...}), this technique can be used to construct a map with a variable number of entries, for example:
>     map:merge(for $b in //book return map:entry($b/isbn, $b))
> At least with Saxon-HE you can achieve the same result with a simple map constructor
>     map:merge(for $b in //book return map{$b/isbn: $b})
> I wonder, if this is just a "special feature" of Saxon or if there is any other reason to keep map:entry in the proposal
> salute
> Th. Fischer

Received on Thursday, 16 March 2017 09:54:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:58:03 UTC