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

[Bug 29959] [xq31] fn:put()

From: <bugzilla@jessica.w3.org>
Date: Mon, 14 Nov 2016 23:15:31 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29959-523-HMJkj1dzic@http.www.w3.org/Bugs/Public/>

--- Comment #11 from Jonathan Robie <jonathan.robie@gmail.com> ---
I think we need to do *something*.  fn:put() was available with XQuery Update
1.0, and we don't have XQuery Update 3.1 yet.  And the ability to create
multiple files as the result of a query is a rather fundamental one.  We
shouldn't tell people they have to use XSLT if they want to do that.

Here are the possible choices that I see:

1. Eliminate fn:put() from XQuery 3.1.  As I indicate above, I don't think this
is acceptable.

2. Add fn:put() to F&O 3.1, indicating that implementations SHOULD treat it as
though it contributes to the result of the query even though it does not return
a value.  This kind of special casing is not usually a great idea, but it may
be the simplest way to provide the desired functionality.  This probably
corresponds to what implementers will do if we do nothing.

3. Modify the signature of fn:put() so that it actually does return a value
that changes the query result in addition to the side effect.  This is
undesirable because (a) it differs from the definition of fn:put() in XQuery
Update 1.0, and (b) it requires the ability to return a value and a pending
update from the same function, something we will probably have in XQuery Update
3.1, but which never made it into the XQuery 1.0 specification.

None of these are great options, but I think special casing the function as in
#2 makes the most sense, and corresponds to the semantics we would want in the
XQuery Update 3.1 specification when it is finished.

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 14 November 2016 23:15:39 UTC

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