[Bug 26958] On not precluding updates in XQuery 3.1

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26958

--- Comment #32 from Jonathan Robie <jonathan.robie@gmail.com> ---
For maps, I changed the text to this:

<add>
Each MapKeyExpr expression is evaluated and atomized; a type error
[err:XPTY0004] occurs if the result is not a single atomic value. The
associated value is the result of evaluating the corresponding MapValueExpr. If
the MapValueExpr evaluates to a node, the associated value is the node itself,
not a new node with the same values.

Note:

XQuery 3.1 has no operators that can distinguish a map or array from another
map or array with the same values. Future versions of the XQuery Update
Facility, on the other hand, will expose this difference, and need to be clear
about the data model instance that is constructed.

In some existing implementations that support updates via proprietary
extensions, if the MapValueExpr evaluates to a map or array, the associated
value is a new or array with the same values.
</add>

For arrays, I changed it to this:

<add>
If a member of an array is a node, its node identity is preserved.

Note:

XQuery 3.1 has no operators that can distinguish a map or array from another
map or array with the same values. Future versions of the XQuery Update
Facility, on the other hand, will expose this difference, and need to be clear
about the data model instance that is constructed.

In some existing implementations that support updates via proprietary
extensions, if a member expression evaluates to a map or array, the member is a
new map or array with the same values.
</add>

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Friday, 5 December 2014 22:19:32 UTC