- From: John Boyer <boyerj@ca.ibm.com>
- Date: Mon, 15 Jun 2009 13:32:27 -0700
- To: "www-forms@w3.org" <www-forms@w3.org>
- Message-ID: <OFB8599A5B.E42932D1-ON882575D6.006FC72B-882575D6.0070D63F@ca.ibm.com>
On May 27, the working group decided to update a few more XForms 1.1 tests [1]. [1] http://lists.w3.org/Archives/Public/public-forms/2009May/att-0059/2009-05-27.html The changes were made before the end of May. The following tests now use the output control rather than upload to bind to datatypes hexBinary and base64Binary in order to receive xforms-valid and xforms-invalid events: 5.1.a, 5.1.c, 5.2.1.a and 5.2.1.c Test 6.1.6.a needed to have the number() function added to a constraint XPath in order to be a correct test. Three tests related to xforms-binding-exception were amended in Ch. 7 (see [1] for details). The xforms-link-error test was removed, to match the change to Ch. 10 of the spec. Test 11.1.u was corrected to reflect the submission separator attribute default of ampersand, not semicolon. Test 11.9.8.a was modified to match the specification. The test required a trailing semicolon separator on the end of the url-encoded submission serialization, but the separator default is ampersand and in any case the trailing character should not be there because it is not *separating* tag-value pairs. The working group does not believe any of these changes affect the implementability of features. In a number of the cases, we believe implementers amended the tests to produce their implementation reports but that the amendments did not make their way back to the test suite, and these changes are helping to fix that. 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 Monday, 15 June 2009 20:33:12 UTC