- From: Thierry Michel <tmichel@w3.org>
- Date: Tue, 16 Apr 2002 12:15:25 +0200
- To: <tw176@columbia.edu>
- Cc: <www-forms-editor@w3.org>
Your issue concerning the XForms Working draft raised during Last Call http://lists.w3.org/Archives/Public/www-forms-editor/2002Feb/0002.html was processed by the XForms Working Group. XForms WG Response: Hi Thomas, The Working Group has solicited input from a number of experts in the areas of research and professional survey/polling areas. The general direction we've taken is for a general-purpose solution that can be used to build more specialized tools. As a specific example, I believe the scenario you outlined below could be constructed out of the existing components in XForms. For instance, the XML instance data to capture the input data could have separate 'slots' for the user choice-from-the-list and reported answer... <research> ... <question number="4"> <userChoice/> <reportedAnswer>N/A</reportedAnswer> </question> ... </research> This represents a question where the user didn't select a predefined choice, but rather chose the option "not applicable". Thus, an element <userChoice>, mapped directly to a list, is not required, but all the elements <reportedAnswer> are required. This could be done with a single line... <bind ref="//reportedAnswer" required="true"/> Another option is to use an XML Schema union, as you suggested. For the user interface, a form control <selectOne> could present the specific choices for that question, while other user interface, say <button> with a <setValue> XForms Action attached, could ensure the reportedAnswer gets populated. Please answer to www-forms-editor@w3.org to state that you are/are not satisfied
Received on Tuesday, 16 April 2002 06:15:25 UTC