W3C home > Mailing lists > Public > public-forms@w3.org > February 2009

Implementation/test case triage (latest)

From: Keith Wells <wellsk@us.ibm.com>
Date: Tue, 17 Feb 2009 14:15:25 -0500
To: Forms WG <public-forms@w3.org>
Message-ID: <OF90A2697B.6A5E1C1C-ON87257560.00696DF6-85257560.0069C81D@us.ibm.com>


* This is the most recent triage list, mostly unchanged from our F2F last
week.
Implementation Summary (02/10/2009): Firefox, EMC, and Chiba(partial)
XForms 1.1 implementation reports

Action: Analyze the Firefox and EMC implementation reports to find the test
cases which have zero or one successful passes.
Note: Even though the Ubiquity-XForms project [1] has not officially
submitted a formal implementation report for XForms 1.1, these reports are
available and some test cases with successful passes were used in this
summary.

Note: MUST/Required, SHOULD/Recommendation and MAY/Optional were derived
from [2].
Note: The implementation in parenthesis after the test case indicates the
implementation where the test case passes.

Test Suite Location [3].

>From chapter 3:
0 Passes (need 2 implementation passes):

Required (has 1 implementation, needs 1 implementation):

>From chapter 4:
0 Passes (need 2 implementation passes):
4.5.3.a xforms-link-error (http://www.w3.org/TR/xforms11/#evt-linkError)
4.5.7.a xforms-version-exception
(http://www.w3.org/TR/xforms11/#evt-versionException)

Required (has 1 implementation, needs 1 implementation):
4.2.2.c2 invalid QNAME causes xforms-binding-exception (FF)
4.3.6.b navigation sequence with navindex (EMC)
4.5.2.a xforms-compute-exception
(http://www.w3.org/TR/xforms11/#evt-computeExceptionhttp://www.w3.org/TR/xforms11/#evt-computeException)
 (FF)
4.6.1.a2 event sequenceing for range and upload controls (EMC)
4.6.3.b event sequencing for select/select1 controls without
incremental="true" (http://www.w3.org/TR/xforms11/#sequence-for-select)(FF)
4.6.3.c event sequencing for select/select1 controls (focus changes) (FF)
4.8.1.a getInstanceDocument() method (FF)

Recommended (has 0 implementation passes, needs 1 implementation pass):
4.5.5.a xforms-output-error event
(http://www.w3.org/TR/xforms11/#evt-output-error)

>From chapter 5:
0 Passes (need 2 implementation passes):
5.2.7.b card-number datatype - credit card example
(http://www.w3.org/TR/xforms11/#dt-card-number)

Required (has 1 implementation, needs 1 implementation):
5.1.a built-in primitive types (EMC)
5.1.c supported primitive XML schema types in basic processors (EMC)
5.2.1.a XForms datatypes to allow empty content - built-in primitive types
(EMC)
5.2.1.b XForms datatypes to allow empty content - built-in derived types
(EMC)
5.2.1.c built-in data types which allow empty content for basic processors
(EMC)
5.2.4.a dayTimeDuration datatype (EMC)

>From chapter 6:
0 Passes (need 2 implementation passes):
Required (has 1 implementation, needs 1 implementation):
Optional( needs 1 implementation pass):

>From chapter 7:
0 Passes (need 2 implementation passes):

Required (has 1 implementation, needs 1 implementation):
7.5.a error in modal item property causes an xforms-compute-exception
(http://www.w3.org/TR/xforms11/#expr-lib) (FF)
7.5.b error not in modal item property causes an xforms-binding-exception
(http://www.w3.org/TR/xforms11/#expr-lib) (FF)
7.8.4.a hmac() function using sha1, md5, and sha256 (FF)
7.10.3.b id() function with xml:id (http://www.w3.org/TR/xforms11/#fn-id)
(UX)
7.10.3.c id() function with xsi:type (http://www.w3.org/TR/xforms11/#fn-id)
(UX)
7.11.2.a event() function with binding property
(http://www.w3.org/TR/xforms11/#fn-event) (UX)
7.11.2.b event() function with resource-uri property (EMC)
Optional( has 0 implementation pass, needs 1 implementation pass):

>From chapter 8:
0 Passes (need 2 implementation passes):

Required (has 1 implementation, needs 1 implementation):
8.1.a navindex and accesskey (EMC)
8.1.6.a mediatype attribute for upload element (FF)
8.1.6.d data binding restrictions for upload element(FF)
8.1.7.f data binding restrictions on range element (EMC)
8.1.7.g data binding restrictions on range element for basic processors
(EMC)
8.1.10.a selection attribute of select element (EMC)

>From chapter 9:
0 Passes (need 2 implementation passes):

Recommended (has 0 implementation passes, needs 1 implementation pass):
9.1.1.a2 group element inside case element of a switch (EMC)
9.2.1.a2 switch element receives events (EMC)
9.3.7.b copy element has xforms-binding-exception event (EMC)

>From chapter 10:
0 Passes (need 2 implementation passes):
10.4.f delete action and repeat element
(http://www.w3.org/TR/xforms11/#action-delete)

Required (has 1 implementation, needs 1 implementation):
10.3.j insert action - copying an attribute (EMC)
10.4.d delete action using at attribute
(http://www.w3.org/TR/xforms11/#action-delete) (UX)
10.7.1.a setfocus element with value child element Failed (EMC)
10.7.1.b control element precedence tests (EMC)
10.8.1.c value attribute has precedence in name element (EMC)
10.8.2.c value attribute has precedence in target element (EMC)
10.8.3.c value attribute has precedence in delay element (EMC)

Recommended (has 0 implementation passes, needs 1 implementation pass):
10.14.1.b value attribute has precedence in load element

>From chapter 11:
* Submission Module is Recommended (but if implemented, it has required
features)
0 Passes (need 2 implementation passes):
11.7.1.a method element with value attribute
(http://www.w3.org/TR/xforms11/#submit-method-elem)
(uses a non-required feature to test a required feature) 11.9.4.b delete
submission method deletes a file
(http://www.w3.org/TR/xforms11/#submit-delete)
11.10.a submission response with invalid target
(http://www.w3.org/TR/xforms11/#submit-data-replacement)
11.11.3.d SOAP HTTP binding with get method and encoding attribute
(http://www.w3.org/TR/xforms11/#SOAP-HTTP-Binding)

Recommended (has 1 implementation, needs 1 implementation) :
11.1.v includenamespaceprefixes attribute of submission element (FF)
11.2.c xforms-submit with empty instance data (FF)
11.2.d xforms-submit with empty instance data and required attribute
(http://www.w3.org/TR/xforms11/#submit-evt-submit) (FF)
11.2.e xforms-submit stops with invalid instance data (FF)
11.3.a xforms-submit-serialize event (FF)
11.8.c header element of submission element
(http://www.w3.org/TR/xforms11/#submit-header) (EMC)
11.9.o File Put as a submission option (FF)
11.9.3.b put submission method to local file (FF)
11.10.b submission response with target receiving text
(http://www.w3.org/TR/xforms11/#submit-data-replacement) (EMC)
11.11.3.a SOAP HTTP binding with get method
(http://www.w3.org/TR/xforms11/#SOAP-HTTP-Binding)(EMC)
11.11.3.e SOAP HTTP binding with post method and encoding attribute
(http://www.w3.org/TR/xforms11/#SOAP-HTTP-Binding) (UX)

Optional( has 0 implementation pass, but needs 1 implementation pass):
11.9.m mailto Post as a submission option
(http://www.w3.org/TR/xforms11/#submit-options)
11.9.p mailto multipart-post as a submission option
(http://www.w3.org/TR/xforms11/#submit-options)
11.9.q mailto form-data-post as a submission option
(http://www.w3.org/TR/xforms11/#submit-options)
11.9.r mailto urlencoded-posts as a submission option
(http://www.w3.org/TR/xforms11/#submit-options)

[1] http://code.google.com/p/ubiquity-xforms/
[2] http://www.w3.org/MarkUp/Forms/specs/XForms1.1/index-diff.html#conform
[3]
http://www.w3.org/MarkUp/Forms/Test/XForms1.1/Edition1/driverPages/html/

Keith
Received on Tuesday, 17 February 2009 19:16:25 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 October 2013 22:06:50 UTC