- From: John Boyer <boyerj@ca.ibm.com>
- Date: Fri, 22 Jan 2010 16:35:50 -0800
- To: "Klotz, Leigh" <Leigh.Klotz@xerox.com>
- Cc: "Owen Newnan" <onewnan@gmail.com>, "Forms WG" <public-forms@w3.org>
Received on Saturday, 23 January 2010 00:58:10 UTC
As with the soap:encodingStyle attr in test 11.11.1.a, the xsi:type on output makes no sense in this test. I removed the bogus attributes in test 8.1.5.c and 11.11.1.a and checked in the updates, including an updated zip file. Cheers, John M. Boyer, Ph.D. STSM, Lotus Forms 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 From: "Klotz, Leigh" <Leigh.Klotz@xerox.com> To: "Forms WG" <public-forms@w3.org> Cc: "Owen Newnan" <onewnan@gmail.com> Date: 01/21/2010 06:00 PM Subject: XForms 1.1 test suite 8.1.5.c has extraneous xsi:type on xf:output Owen Newnan reports an extraneous xsi:type on xf:output in 8.1.5.c. The test label says "UI Common added to output element" and so perhaps it was thought to be a foreign attribute. However, xsi:type MAY be specially treated by XSD validators so it's not a good choice for a foreign attribute. The bulk of the test, though, is about the UI Common elements hint, help, and alert. Leigh.
Received on Saturday, 23 January 2010 00:58:10 UTC