- From: Micah Dubinko <MDubinko@cardiff.com>
- Date: Mon, 5 Nov 2001 17:45:01 -0800
- To: "'Jim Wissner'" <jim@jbrix.org>, www-forms@w3.org
Jim wrote: >So, if I understand, a compliant xforms processor must examine all elements, independent of namespace or node name, to see if they have an attribute "ref" or "nodeset"? I apologize if I'm unclear. What you wrote above is exactly what we _don't_ want. :-) The 'ref' (or 'nodeset') attributes only have special meaning when attached to elements from the XForms namespace. A 'ref' (or 'nodeset') attribute from an element in any other namespace shouldn't have any effect on XForms processing. The earlier example led me to believe that your 'ref' attributes are intended to have special meaning to the XForms processor. Take the inner form controls: > > <xforms:input ref="firstName" accessKey="f"> > > <xforms:caption>First Name:</xforms:caption> > > </xforms:input> > > <xforms:input ref="lastName" accessKey="l"> > > <xforms:caption>Last Name:</xforms:caption> > > </xforms:input> The XForms Processor considers these form controls as "outermost", since you can follow the parents all the way up to the root and not see any xforms namespaced elements. The XPath context node for outermost elements is "/", so your ref expressions are equivalent to: ref="/firstName" ref="/lastName" Perhaps if you included full instance data in your example it would be clearer for all. Thanks, .micah
Received on Monday, 5 November 2001 20:45:32 UTC