- From: Erik Bruchez <ebruchez@orbeon.com>
- Date: Mon, 18 Jun 2007 18:18:27 +0200
- To: public-forms@w3.org
- CC: www-forms-editor@w3.org
All, Just to make things clear: the request for use case clarification falls on John, or on whoever thinks that the "binding" property as currently specified should stay in the spec. If no compelling use case is proposed, we need to drop the current "binding" property (but other properties can be proposed if they satisfy a use case deemed worthy by the WG). Best, -Erik Ulrich Nicolas LissXX wrote: > Erik, > > we accept your request to clarify that the empty is string is returned by insert > event binding if none is specified. We also ask for clarification on the > feature and its use case, because in general, it is not possible for the form > author to resolve the value without knowing the context and without knowing > whether the binding is a bind IDREF or an XPath expression. > > Regards, > Ulrich Nicolas Lissé. > For the Forms WG > >> All, >> >> This is a comment about the "binding" property or these sections. >> Section 4.4.5 says: >> >> "The attribute value of the insert action's nodeset or bind attribute." >> >> However, both @bind and @nodeset are optional with xforms:insert. We >> should say what the "binding" property returns when this occurs. >> >> By the way, I believe I raised this in the past already, but I am not >> sure why this property is useful anyway. I would suggest simply getting >> rid of it unless a compelling use case for it is proposed. >> >> -Erik >> >> -- >> Orbeon Forms - Web Forms for the Enterprise Done the Right Way >> http://www.orbeon.com/ >> >> -- Orbeon Forms - Web Forms for the Enterprise Done the Right Way http://www.orbeon.com/
Received on Monday, 18 June 2007 16:18:34 UTC