W3C home > Mailing lists > Public > public-xformsusers@w3.org > June 2018

12.2.2 References to Elements within a bind Element

From: Steven Pemberton <steven.pemberton@cwi.nl>
Date: Thu, 28 Jun 2018 15:53:58 +0200
To: " XForms" <public-xformsusers@w3.org>
Message-ID: <op.zlbnj8rasmjzpq@steven-xps>
https://www.w3.org/community/xformsusers/wiki/XForms_2.0#References_to_Elements_within_a_bind_Element

"However, if the target bind element has one or more bind element  
ancestors, then the identified bind may be a target element that is  
associated with more than one target bind object.

If a target bind element is outermost, or if all of its ancestor bind  
elements have ref attributes that select only one node, then the target  
bind only has one associated bind object, so this is the desired target  
bind object whose sequence is used in the source binding. Otherwise, the  
in-scope evaluation context item of the source object containing the bind  
attribute is used to help select the appropriate target bind object from  
among those associated with the target bind element.

 From among the bind objects associated with the target bind element, if  
there exists a bind object created with the same in-scope evaluation  
context item as the source object, then that bind object is the desired  
target bind object. Otherwise, the IDREF resolution produced a null search  
result."

So what gets output in the following?


<instance>
    <dates xmlns="">
       <date value="2018-06-28"/>
       <date value="2018-06-27"/>
       <date value="2018-06-26"/>
       <date value="2018-06-25"/>
    </dates>
</instance>

<bind ref="date">
    <bind ref="@value" type="date" id="DATE"/>
</bind>
...

<repeat bind="DATE">
    <output ref="."/>
</repeat>

Steven
Received on Thursday, 28 June 2018 13:54:23 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 28 June 2018 13:54:23 UTC