- From: John Boyer <boyerj@ca.ibm.com>
- Date: Sat, 28 Feb 2009 22:22:49 -0800
- To: public-forms@w3.org
- Message-ID: <OFDB7AD0CE.8348B630-ON8825756C.0022274B-8825756C.0022FBE5@ca.ibm.com>
A "typo" of sorts was introduced into the last call working draft of XForms 1.1 regarding the evaluation context of the "at" attribute. There was an overhaul of the whole section, and the error got in then. If you read the description of the "at" attribute, it says it is evaluated using the inscope evaluation context. It is supposed to say that it is evaluated using the nodeset binding for the evaluation context. If you check the processing details of the insert action, specifically in step 4, you will see that it correctly describes the use of the nodeset binding for the evaluation context. The more detailed description is the correct version, and here is the corroborating evidence: 1) The at attribute is specified as having no meaning when the nodeset binding is not expressed. 2) The delete action also has an at attribute, and it is evaluated based on the nodeset binding. 3) In XForms 1.0, the "at" attribute of insert was evaluated relative to the nodeset binding. In XForms 1.0, there was no default for "at", so if you wanted to insert at the end of the list you had to say at="last()". Such forms would stop working in 1.1. We need to double-check the test suite to ensure that the interpretation of the "at" attribute is based on the detailed processing method, not the attribute overview. Cheers, John M. Boyer, Ph.D. STSM, Interactive Documents and Web 2.0 Applications Chair, W3C Forms Working Group Workplace, Portal and Collaboration Software IBM Victoria Software Lab E-Mail: boyerj@ca.ibm.com Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer Blog RSS feed: http://www.ibm.com/developerworks/blogs/rss/JohnBoyer?flavor=rssdw
Received on Sunday, 1 March 2009 06:22:46 UTC