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

[Bug 26958] On not precluding updates in XQuery 3.1

From: <bugzilla@jessica.w3.org>
Date: Thu, 06 Nov 2014 18:14:18 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-26958-523-2fTzyu3zLh@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26958

--- Comment #27 from Michael Kay <mike@saxonica.com> ---

> We have discussed and agreed to this requirement at least a handful of
> times, starting with the requirements document. There is no ambiguity as
> long as we preclude updates on the instances that are created.  But if we do
> allow any kind of in-situ updates analogous to the current XQuery Update
> Facility, we face the ambiguity mentioned in the original description of
> this issue.

The decision recorded in comment #13 appears to be a provisional decision
affecting the design of a future version of XQuery Update. It doesn't affect
our current specs. It says (I think) that map and array constructors should
"copy" any maps and arrays supplied as input, but since "copying" a map or
array is an undefined and meaningless operation until we introduce updates,
that's not a meaningful thing to say in our current specs.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 6 November 2014 18:14:20 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:59 UTC