Relevance based on ref in deselected case.

Hi,

I have a question about the relevance of UI controls in relation with 
erratum 31.4 Non-Relevance and the switch Element 
(http://www.w3.org/2006/03/REC-xforms-20060314-errata.html#E31d).

Use case 1
1) If you have a trigger that has a ref, and is in a case with id 'a'.
2) assume that case 'a' is selected
3) change 'the' value of a control so that the result of the ref on the 
trigger becomes an empty nodeset
--> the trigger becomes non-relevant
This use case I understand and is easy to implement due to the fact that 
the trigger is dependant to the node in the instance data that changes and 
gets event informing him that a value has changed

Use case 2
1) If you have a trigger that has a ref, and is in a case with id 'a'.
2) assume that case 'a' is not selected and another case is selected
3) change 'the' value of a control so that the result of the ref on the 
trigger becomes an empty nodeset (the trigger gets no events due to 
erratum 31.4)
4) toggle to case 'a' 
--> should there be 'special' code that forces the trigger to become 
non-relevant? If so is it just in the processor or does the '
xforms-disabled' gets send to the control?What about other events?

Attached you can find a testcase that tests this 'issue', if the input 
contains '1' the trigger 'Optional trigger' becomes relevant, if it 
contains any other value the trigger becomes non-relevant.

Regards,

Nick Van den Bleeken  -  Research & Development
Inventive Designers
Phone: +32 - 3 - 8210170
Fax: +32 - 3 - 8210171
Email: Nick_Van_den_Bleeken@inventivedesigners.com



--------------------------------------------------

Inventive Designers' Email Disclaimer:

http://www.inventivedesigners.com/email-disclaimer