W3C home > Mailing lists > Public > public-forms@w3.org > March 2012

Missing details about "11.21 The iterate attribute"

From: Erik Bruchez <ebruchez@orbeon.com>
Date: Fri, 30 Mar 2012 11:40:17 -0700
Message-ID: <CAAc0PEXNb0fdrvbS7s2zAG7O8G8YEi9=jG=T49aMCG1Wg9G6=g@mail.gmail.com>
To: public-forms@w3.org
All,

Looking at section "11.21 The iterate attribute": we need to say what
happens when both `iterate` and `context` are used. I am not sure if
we discussed this point during the call (I remember discussing whether
while and iterate could be used together).

I realize that "context everywhere" is not in the spec yet, but even
so this applies to `insert` and `delete` already. For example, what
should be the behavior of:

    <xforms:insert iterate="" context="" ref="..." origin="..."/>

Attribute order not being significant, of course, the following is
exactly the same:

    <xforms:insert context="" iterate="" ref="..." origin="..."/>

Our own implementation implements `context` first, then `iterate`.
However, we are not particularly happy about this, as it prevents
doing something like:

  <xforms:insert xxforms:iterate="1 to 10" context="instance()"
ref="*" origin="element('foo')"/>

This might be less of a problem if `insert` is modified to support an
`into` attribute:

  <xforms:insert xxforms:iterate="1 to 10" into="instance()" ref="*"
origin="element('foo')"/>

But still, we probably have to say something about `iterate` and
`context` since we are stuck with `context` for a while.

-Erik
Received on Friday, 30 March 2012 18:41:06 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 October 2013 22:06:56 UTC