- From: John Boyer <boyerj@ca.ibm.com>
- Date: Sun, 15 Mar 2009 16:00:35 -0700
- To: public-forms@w3.org
- Message-ID: <OFA9DE9A4B.12069816-ON8825757A.007DA50B-8825757A.007E5480@ca.ibm.com>
B9 copies an attribute list into an element, so it needs to use context rather than nodeset. B11 does a replace attribute. This should be a setvalue, not an insert. Note that B4 already does a "set attribute" (i.e. create if not exist, reset value if exists), so B11 is only different if it has the behavior of replacing the value of an existing attribute. The most efficient way to do this is with a setvalue whose ref and value have the nodeset and origin values in the current appendix. The title of the appendix will have to change to "Data Mutation Patterns with insert, delete and setvalue" B14 does a move attribute operation, and the element receiving the attribute is identified in the nodeset, so again that is supposed to be context rather than nodeset. 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, 15 March 2009 23:00:40 UTC