- From: Norman Walsh <Norman.Walsh@marklogic.com>
- Date: Tue, 06 Oct 2015 12:22:49 -0500
- To: public-xsl-query@w3.org
- Message-ID: <87h9m3q5cm.fsf@nwalsh.com>
Josh Spiegel <josh.spiegel@oracle.com> writes: > (1) Where it currently says "Each key in the map is unique (there is > no other key to which it is equal) and has associated with it a value > that is a single item or sequence of items.” We need to say somehow > that keys are compared using op:same-key: > https://www.w3.org/XML/Group/qtspecs/specifications/xpath-functions-31/html/Overview-diff.html#func-same-key Ok. Yes, I mentioned that in passing but didn't implement it. I can do that. > (2) Remove this paragraph: "If any date/time values (xs:date, > xs:dateTime, xs:time, xs:gYear, etc.) are used as keys, all such > values must either have a timezone or must not have a timezone. An > error is raised if an attempt is made to mix date/time key values that > have a timezone with values that do not. This constraint applies only > to map keys and applies independently to each map (it is not an error > to have one map that uses date/time keys with timezones and another > which uses values without timezones).” Is that now covered in F&O? I apologize, I haven't looked at a very recent draft. Be seeing you, norm -- Norman Walsh Lead Engineer MarkLogic Corporation Phone: +1 512 761 6676 www.marklogic.com
Received on Tuesday, 6 October 2015 17:23:16 UTC