RE: Feedback on 1.1: Case element content model and attributes

In this case, we should define the behaviour in cases such as having the ref
pointing to a non-existant node or a non-relevant node. Then, if the user
toggles to that case or selected is "true", what is the behaviour?
 
I think this relates to the previous posts about having selected as a
boolean xpath expression or allowing AVT for the selected attribute. I think
we must clarify wchich direction are we taking in these issues and solve all
the implications before adding anything to the standard.
 
Regards,
 
Rafael Benito
SATEC


  _____  

De: www-forms-request@w3.org [mailto:www-forms-request@w3.org] En nombre de
John Boyer
Enviado el: lunes, 11 de septiembre de 2006 12:33
Para: www-forms@w3.org; www-forms-editor@w3.org
Asunto: Feedback on 1.1: Case element content model and attributes



The case element is meant to be "like a group" that can be selected by a
switch. 

For consistency, then, the case element should be allowed to have an
optional single-node binding, and its content model should include UICommon.


John M. Boyer, Ph.D.
Senior Product Architect/Research Scientist
Co-Chair, W3C XForms Working Group
Workplace, Portal and Collaboration Software
IBM Victoria Software Lab
E-Mail: boyerj@ca.ibm.com  http://www.ibm.com/software/

Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer