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:28:13 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-26958-523-hM3AEQXkWP@http.www.w3.org/Bugs/Public/>

--- Comment #28 from Michael Kay <mike@saxonica.com> ---
>There is no ambiguity as long as we
preclude updates on the instances that are created. 

Perhaps we have a different understanding of the word preclude?

My understanding is it means "to make impossible". The requirement is that we
shall not do anything that makes updates impossible. I think we can achieve
this by doing nothing. Your objection, going back to the original comment in
this bug entry, is that doing nothing "results in two sets of behavior that can
be distinguished only when updates are implemented". I don't think that's a
problem; the time to define the detail of how updates work is when we design
the update facility, not now. Many people (for example, most XPath/XSLT
implementors) will never implement in-situ update, and it would be entirely
wrong for specs other than the Update spec to attempt to dictate choices that
have no effect on non-Update programs.

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

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:51 UTC