W3C home > Mailing lists > Public > public-xformsusers@w3.org > April 2019

Re: ACTION-2244: Remove the term deep copy

From: Erik Bruchez <ebruchez@orbeon.com>
Date: Mon, 1 Apr 2019 11:13:00 -0700
Message-ID: <CAAc0PEUEmJdZp8bpsgf9qt6tn_CxF9OB3NT-5cGrtrFdwabT2A@mail.gmail.com>
To: Steven Pemberton <steven.pemberton@cwi.nl>
Cc: XForms <public-xformsusers@w3.org>, XForms Users Community Group Issue Tracker <sysbot+tracker@w3.org>
>
> Insert talks all the time about a node that is cloned. Should that be an
> *item* that is cloned?


I don't think it makes sense to "clone" items since the "identity of atomic
values, by contrast, is determined solely by their intrinsic properties. No
two distinct integers, for example, have the same value; every instance of
the value “5” as an integer is identical to every other instance of the
value “5” as an integer.".

However, we do need to say what `<insert>` does with atomic values. They
are eventually converted to text nodes. For example:

    <insert context="foo" origin="5"/>

should yield:

    <foo>5</foo>

The following:

    <insert context="foo" origin="1 to 5"/>

might yield, as would `<xsl:value-of>`:

    <foo>1 2 3 4 5</foo>

XSLT has a whole section on how sequences are produced. See [1] and [2].
When combining items in a sequence, the default separator is the single
space, but XSLT makes this configurable with a `separator` attribute.

-Erik

[1] https://www.w3.org/TR/xslt-30/#element-value-of
[2] https://www.w3.org/TR/xslt-30/#constructing-simple-content
Received on Monday, 1 April 2019 18:13:35 UTC

This archive was generated by hypermail 2.3.1 : Monday, 1 April 2019 18:13:36 UTC