W3C home > Mailing lists > Public > www-forms-editor@w3.org > June 2007

Re: Section 8 (PR#117)

From: John Boyer <xforms-issues@mn.aptest.com>
Date: Thu, 28 Jun 2007 17:22:45 -0500
Message-Id: <200706282222.l5SMMjWi013538@htmlwg.mn.aptest.com>
To: aaronr@us.ibm.com
CC: www-forms-editor@w3.org

Hi Aaron,

Here are responses to a number of issues that you raised in a last call comment
email on April 30.  Spec changes can be found in the editor's copy available
from the Forms WG public site.  Please let us know if you have any further
concerns about these issues.

Thanks,
John Boyer

26) Section 8.1.1 - "If a form control violates its data binding
restriction, an xforms-binding-exception must occur."  How can a form
control violate its data binding restriction?  I would think that the bound
data would violate the data binding restriction of the control.

A form control can violate its data binding restriction by expressing
a binding that resolves to a node of a forbidden datatype.  Each form
control expresses its data binding restrictions.

27) Section 8.1.1 - a bulleted list of "Form control must..." items, but no
examples.  Any suggestions for  how I would "...render upon request an
explanation of the current state of a form control..."?  And what is the
request?

That bullet point and the one following have been removed.  Diff-marked.

28) Section 8.1.1 - the list of events that happen when a form control goes
from being irrelevant to relevant -> xforms-value-changed only MIGHT be
generated.  A control can become relevant without the value of the
control's bound node changing at all.

This was actually part of an erratum to XForms 1.0, not just new to 1.1.  The
intent here was to issue xforms-value-changed to the control when it becomes
relevant even if there was no change of value.  Implementations are not expected
to store the state of UI controls when last they were relevant, nor are they
required to store the changing states of controls based on their binding to a
non-relevant node. And last, implementations need not then choose which state is
the pertinent one for producing an xforms-value-changed.

29) Section 8.1.5 - the description is duplicated.

Done. Diff-marked.

30) Section 8.3.3 - "This required element labels the containing form
control with a descriptive label."  This isn't always required.  For
example repeat, output, choices, group, and case.

Fixed.  Diff-marked.  Improved wording of paragraph as well.
Received on Thursday, 28 June 2007 22:26:42 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 10 June 2009 18:12:15 GMT