Re: Changes to test suite

John,

I am reviewing the Test Suite to check  your questions, but here's the
quick view answers:

1) the definition of "valid" now includes not(required and empty) [Section
4.3.3, 4.4.5]   Test case 11.2.d covers this.

2) the definition of the function is-card-number() and the card-number
datatype now allow any number of digits. [Section 5.2.7,   Test case
5.2.7.a.xhtml covers this.

3) The text for the bind element now clearly specifies behavior when the
nodeset attribute is omitted. [Section 3.3.4]  This is not explicitly
tested at this time.

4) The examples in 5.2.4 and 5.2.5 contained cut-paste typos that hopefully
do not exist in the test suite.  These typos do not exist in the test
suite.

5) Section 10.3 makes yet another clarification that the context node for
the origin expression is affected by the context attribute, if present.
Test case b.4.a.xhtml covers this.

6) The effect of the encoding attribute, or its default value, on the
charset MIME parameter added to the Accept parameter for method="get" SOAP
submissions and the Content-type header in method="post" SOAP submissions.
[Section 11.11.3]  Test cases 11.11.2.a.xhtml, 11.11.3.a.xhtml,
11.11.3.b.xhtml and 11.11.3.c.xhtml cover this.

Keith


                                                                           
             John Boyer                                                    
             <boyerj@ca.ibm.co                                             
             m>                                                         To 
             Sent by:                  Keith Wells/Raleigh/IBM@IBMUS       
             public-forms-requ                                          cc 
             est@w3.org                public-forms <public-forms@w3.org>  
                                                                   Subject 
                                       Changes to test suite               
             08/12/2008 02:43                                              
             PM                                                            
                                                                           
                                                                           
                                                                           
                                                                           





Please see the current editor's draft of XForms 1.1:
http://www.w3.org/MarkUp/Forms/specs/XForms1.1/index-diff.html

I'd like to have confirmation please, in the test suite and also by
implementers, that some of the changes made to XForms 1.1 since CR have in
fact been reflected:

1) the definition of "valid" now includes not(required and empty) [Section
4.3.3, 4.4.5]

2) the definition of the function is-card-number() and the card-number
datatype now allow any number of digits. [Section 5.2.7,

3) The text for the bind element now clearly specifies behavior when the
nodeset attribute is omitted. [Section 3.3.4]

4) The examples in 5.2.4 and 5.2.5 contained cut-paste typos that hopefully
do not exist in the test suite

5) Section 10.3 makes yet another clarification that the context node for
the origin expression is affected by the context attribute, if present.

6) The effect of the encoding attribute, or its default value, on the
charset MIME parameter added to the Accept parameter for method="get" SOAP
submissions and the Content-type header in method="post" SOAP submissions.
[Section 11.11.3]

Thanks,
John M. Boyer, Ph.D.
Senior Technical Staff Member
Lotus Forms Architect and Researcher
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