RE: [xml-dev] Challenge

["Klotz, Leigh" <Leigh.Klotz@pahv.xerox.com>]

Actually, it was Mark who pointed out /demo/description.
On the XHTML widget side, I would suggest that you transform the
XForms/XHTML 2 widget into an XHTML 1 widget with you XSLT transform and
transform the attributes from the XForms ones to the XHTML 1 <input
name=...> as necessary; but perhaps you have your own reasons for wanting to
mix the vocabularies.

The lazy author processing is described normatively as a sequence in the
event handling of the XForms processor, at
http://www.w3.org/TR/xforms/index-all.html#evt-modelConstructDone

If the instance referenced on the form control did not exist when the first
form control for the same instance was processed, beginning at "If the
instance referenced on the form control did not exist when the first form
control for the same instance was processed...an instance a default instance
is created by following the rules described below."

Leigh.
 
-----Original Message-----
From: Didier PH Martin [mailto:martind@netfolder.com] 
Sent: Thursday, November 06, 2003 4:13 PM
To: 'Klotz, Leigh'; 'Mark Seaborne'; xml-dev@lists.xml.org
Subject: RE: [xml-dev] Challenge


Hi Klotz,

Klotz said:
  Why use //description, etc rather than /demo/description?

Actually, since XForms sets the XPath context node to be the document
element, you can jus tsay
       <xforms:bind id="version" nodeset="version" constraint=". = '1.0'"/>
       <xforms:bind id="name" nodeset="author/name"/>
       <xforms:bind id="email" nodeset="author/email"/>
       <xforms:bind id="description" nodeset="description"/>

  <!-- snip -->

Didier replies:
Yes you are right about /demo/description.

Klotz said:
Actually it would be
    <xforms:input
ref="version"><xforms:label>Version</xforms:label></xforms:input>

Didier replies:
Only if you want to use xforms widgets. If you implement the XForms engine
with XSLT which is, by the way, a kind of interpreter, and if you want to
use XHTML widgets, then you use 
<xforms:submission id="submit" 
                            xforms:replace="all"
                            xforms:action="http://mydomain.com/MyStorage";
                            xforms:method="PUT"/>
     <xforms:instance src=http://myDomain.com/theChallenge.xml"; />
                            .....
                            .....
     <!-- an XHTML widget -->
     <input ref="demo/version" type="text" name="version" size="20"/> 

Klotz said:
Note that the context node being "/data" means that you can just use the ref
to ne the immediate child name of the toplevel element,
so it looks a lot like what XHTML 1 does with <input name="version"/>.  In
fact, if you omit the <instance> from a model entirely,
XForms will notice that and make one up for you populated by elements with
names taken from the form controls bound to the model.
It's a good transition step from XHTML 1 to XHTML 2 or other XForms host
languages.

Didier replies:
I wasn't able to find what the spec says about that. Do you know where that
process is specified?

Cheers
Didier PH Martin
http://didier-martin.com



  All the best

  Mark  

  > Cheers
  > Didier PH Martin
  > http://didier-martin.com
  > 
  > 
  > 
  > 
  > -----------------------------------------------------------------
  > The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
  > initiative of OASIS <http://www.oasis-open.org>
  > 
  > The list archives are at http://lists.xml.org/archives/xml-dev/
  > 
  > To subscribe or unsubscribe from this list use the subscription
  > manager: <http://lists.xml.org/ob/adm.pl>
  > 


  -----------------------------------------------------------------
  The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
  initiative of OASIS <http://www.oasis-open.org>

  The list archives are at http://lists.xml.org/archives/xml-dev/

  To subscribe or unsubscribe from this list use the subscription
  manager: <http://lists.xml.org/ob/adm.pl>