CR spec draft now contains text for issues 102 and 72; here's what's left...

The spec now contains the commentary on the effects of required, type and 
constraint on form controls.

As required by the LC comment, the changes to type and constraint simply 
indicated they contribute to the overall validity assessment and see 
"Implementation requirements common to all form controls" in Chapter 8 for 
what effect that has on form control rendition.

In the case of the required MIP, both the section 6 text and the section 8 
"implementation requirements..." were amended to indicate that controls 
must show a difference, except for controls that don't render the actual 
string value of the node, including trigger and the container controls.

The render effects of MIPs and in-range/out-of-range are now indicated to 
occur on *relevant* controls.

The "implementation requirements common to all form controls" now also 
contains the commentary about all controls defaulting to display:inline 
and repeat items default to display:block

This means that we are done addressing all LC comments except as follows:

1) Issue 87 on strict and lax schema validation, which Leigh and Erik are 
working on (hoping for that today :-)

2) Issue 106 on inputmode, which Martin is working on (hoping for that on 
Friday :-)

3) Two editorial adjustments from Nick and Erik for Appendix B 
insert/delete examples (will do that myself before the FtF).

To actually transition to CR, we need the LC issues report, which I 
requested from Shane already.  And we need to have answers for a number of 
process questions, which I have already collected and will publish in an 
updated FtF agenda.

Cheers,
John M. Boyer, Ph.D.
STSM: 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