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:05:03 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-26958-523-k736WgfPZl@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26958

--- Comment #26 from Jonathan Robie <jonathan.robie@gmail.com> ---
(In reply to Michael Kay from comment #25)
> >If they ever plan to update that, there's a big gotcha due to an ambiguity in our specification. The Working Group has agreed, at least twice, to fix that gotcha.
> 
> I don't believe there is any ambiguity in our specification, and I beleive
> that the only thing we have agreed regarding updating of maps and arrays is
> that we will not do anything that prevents us deciding to do this in the
> future.

Comment #13 is the last Working Group decision on this, is there new
information that should require us to revisit that decision?

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.

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

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