The action items for issues 72 and 73

Today we discussed two issues on the telecon that unfortunately were 
already resolved and already have action items.

The problem has occurred because Nick was unable to produce the updated 
action item list for the third day of our face to face meeting, so when I 
looked for action items on these I regrettably didn't find them.

This means that todays action item for Steven to resolve issue #72 was a 
duplicate.
Also, Steven already has the action item to resolve issue #73 by adding 
producing spec ready text that adds a value attribute to the mediatype 
element of output (without removing the ref attribute, as resolved).

It was not my intent to reopen the discussion today, but rather just to 
make sure we had the action item, which we already do have.

In today's meeting it was expressed that retaining the ref attribute on 
output's mediatype for the sake of consistency with the expression of an 
upload that might feed content to the output was "not enough" 
justification.  Respectfully, I don't agree; we have had no small number 
of wraps on the knuckles for just such inconsistencies of expression, this 
point was made and resolved already at the face to face meeting, and no 
net new technical information exists to warrant reopening the issue.  It 
is clearly implementable, and consistency of expression has clearly been 
an issue for XForms in the past that we have done much work to improve.

To the larger issue, I will now fish through the actions created on the 
third day of our FtF to make sure that issues for which actions already 
exist are not raised until working group members do the action items.

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