[Bug 26958] On not precluding updates in XQuery 3.1

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

--- Comment #30 from Jonathan Robie <jonathan.robie@gmail.com> ---
I just added the text to the internal working draft so we can discuss this more
concretely.  I am using <add></add> to indicate new material.

For map constructors:

<quote section="3.10.1 Maps">
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.
<add>Unlike element constructors, if the MapValueExpr evaluates to a node, the
associated value is the node itself, not a new node with the same values. If
the MapValueExpr evaluates to a map or array, the associated value is a new map
or array 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. However, we need to be clear about the data
model instance that is constructed so that future versions of the XQuery Update
Facility update the instances defined in this specification.</add>
</quote>

For array constructors:

<quote section="3.10.2.1 Array Constructors">
<add>
In both forms of an ArrayConstructor, if a member expression evaluates to a
node, the associated value is the node itself, not a new node with the same
values. If the member expression evaluates to a map or array, the associated
value is a new map or array 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. However, we need to be clear about the data
model instance that is constructed so that future versions of the XQuery Update
Facility update the instances defined in this specification.
</add>
</quote>

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

Received on Tuesday, 11 November 2014 14:43:25 UTC