Question about precedence in calculate

Dear Working Group,

I have a question about what happens when two calculates apply to the 
same value. We apply one calculate to an element and another calculate 
to the first textnode of the element hence from the rule 'writing 
simpleContent' both calculates operates on the same value. This is legal 
in XForms as it states 'If the node already contains a model item 
property of the same name, XForms processing for this containing 
document halts with an exception (4.5.1 The xforms-binding-exception 
Event)'. And the text and element node are two different nodes e.g. it 
should be legal.

Please see the attached testcase.

On a side note I was a bit surprised to find the wording which disallows 
two MIPs of the same type on the same node in the xforms-model-construct 
section. Does this mean that bind/@nodeset which a dynamic predicate 
does not reapply in the processing of rebuild but only initially and for 
submission (and what happens for insert and delete then)?

Best regards,
David

-- 
--------------------------------------------
David Landwehr (david.landwehr@solidapp.com)
Chief Executive Officer, SolidApp
Web: http://www.solidapp.com
Office: +45 48268212
Mobile: +45 24275518
--------------------------------------------