W3C home > Mailing lists > Public > www-forms@w3.org > November 2001

RE: Control heirarchies

From: Micah Dubinko <MDubinko@cardiff.com>
Date: Mon, 5 Nov 2001 12:24:42 -0800
Message-ID: <E840F0B7E6189547BDB91DA8BF2228AB28BFC1@csmail.cardiff.com>
To: "'Jim Wissner'" <jim@jbrix.org>, "'www-forms@w3.org'" <www-forms@w3.org>
Hi Jim,

In your example, <app:table ref="addressBook/person"> has a 'ref' attribute
that looks much like the XForms 'ref' attribute, but it isn't. So, no XForms
processor would be obligated to process it, or adjust context nodes for
inner XPath expressions, etc.

As long as the processor for the http://www.jbrix.org/ApplicationSchema took
care of all the app:prefixed markup, the below could probably be made to
work, though not in an interoperable way.

Whether or not the conformance section of XForms would permit, deny, or
remain silent on the below sample hasn't been decided yet.

Thanks,

.micah


-----Original Message-----
From: Jim Wissner [mailto:jim@jbrix.org]
Sent: Monday, November 05, 2001 11:46 AM
To: www-forms@w3.org
Subject: Control heirarchies



Hi,

Let me try a different question.  It's short, I promise.  I need input if 
possible.  A short "yes or no" to "is it valid?" is ok if that is all I 
receive.

Xforms doesn't seem to impose a specific control layout anymore.  So, for 
instance, in an xhtml document you can have controls wherever, and the 
model in the head section.  For non-xhtml container docs, could i 
legitimately have a table that enumerates a nodeset, and then can be 
"zoomed in" on to show more controls?

Example:


<app:application
     xmlns:xforms="http://www.w3.org/2001/08/xforms"
     xmlns:app="http://www.jbrix.org/ApplicationSchema">

     <xforms:model>
         <xforms:instance> . . . </xforms:instance>
         <xforms:bind ref="addressBook/person/firstName" required="true"/>
         <xforms:bind ref="addressBook/person/lastName" required="true"/>
     </xforms:model>

     <xforms:input ref="@name">
         <xforms:caption>Address Book Name:</xforms:caption>
     </xforms:input>
     <app:table ref="addressBook/person">
         <app:caption>People</app:caption>
         <app:column name="Name" ref="{lastName}, {firstName}"/>
         <app:zoomed-view>
             <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>
         </app:zoomed-view>
     </app:table>

</app:application>

Does any of this invalidate xforms conformance?  And if it doesn't, which 
from the spec I don't see why it would, then how can such documents be 
compatible between "xforms compliant clients"?  What am I missing?

I'm trying to keep my questions short, but I don't know how else to find 
the answers, and users of my software are requesting conformance, so any 
help with this would be fantastic.

Thanks,
Jim
Received on Monday, 5 November 2001 15:25:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 10 March 2012 06:21:50 GMT