Re: XForms 1.1 - target of the xforms-delete event

Another possible fix is to have xforms delete ignore nodes which are not 
in the same instances as the first node, or to no-op entirely.

Insert can only insert nodes into one instance, so it is reasonable to 
have consistency with delete.   When delete was changed from one node to 
many nodes, the most urgent requirement we had in mind to satisfy was 
deletion of a set of children of a given node.  This can reasonably expand 
to nodes having a common ancestor, but crossing DOMs just seems a little 
much, esp. without the analogous insert ability.

John M. Boyer, Ph.D.
STSM, Interactive Documents and Web 2.0 Applications
Chair, W3C Forms Working Group
Workplace, Portal and Collaboration Software
IBM Victoria Software Lab

Blog RSS feed:

Erik Bruchez <>
Forms WG <>
xforms <>,
05/27/2009 10:47 AM
Re: XForms 1.1 - target of the xforms-delete event

Good point. I guess you have something like this in mind:

<xforms:delete nodeset="instance('foo')/foo | instance('bar')/bar"/>

I think that the right fix is to dispatch xforms-delete to all the 
instances from which nodes are removed. Context information must be 
adjusted appropriately for each event dispatch.


On May 27, 2009, at 7:54 AM, Vlad Trakhtenberg wrote:

> Dear WG,
> According to the current XForms 1.1 spec the delete action can 
> delete nodes from more than one XForms instance (if no delete 
> location specified - as in 10.4 step 4 ). If so, which instance the 
> corresponding xforms-delete event must target?
> Regards,
> Vlad Trakhtenberg,
> IBM, Victoria Lab.

Orbeon Forms - Web Forms for the Enterprise Done the Right Way

Received on Wednesday, 27 May 2009 17:53:08 UTC