Mutiple Model problem

[hcr]

 

 

 Hi,

    I have two question with xforms:model:

    1. could html:body have a child that is xforms:model ?

    2. How can I operator(setvalue, insert...) data in two model ? 

 

---

渊波阔宅 湖景人生

--
You receive this message as a subscriber of the ops-users@... mailing list.
To unsubscribe: mailto:ops-users-unsubscribe@...
For general help: mailto:sympa@...?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

[fs(ops-users)]

hechengrong,

>     I have two question with xforms:model:
>     1. could html:body have a child that is xforms:model ?

hmm - i didn't find a source that _prohibits_ to put the model into the
html:body, but i found the following quite convincing:

"There are several important things that can be gleaned from this sample, as
basic as it may seem. The first is the fact that the model in this particular
case, is situation not in the body (as is implicitly the case with HTML Forms)
but in the head. It doesn’t need to be, but given the model is by itself an
unrendered object - metadata in the purest sense of the word, having this in the
head of the document makes sense."

Source:
K. Cagle: Understanding XForms: The Model
http://www.oreillynet.com/xml/blog/2006/03/understanding_xforms_the_model.html


>     2. How can I operator(setvalue, insert...) data in two model ?

Tha's demonstrated in the XForms specs:
http://www.w3.org/TR/2007/REC-xforms-20071029/#concepts-multiple
http://www.w3.org/TR/xforms11/#concepts-multiple

HTH
florian


--
You receive this message as a subscriber of the ops-users@... mailing list.
To unsubscribe: mailto:ops-users-unsubscribe@...
For general help: mailto:sympa@...?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

[Erik Bruchez]

>>    1. could html:body have a child that is xforms:model ?

>
> hmm - i didn't find a source that _prohibits_ to put the model into  
> the html:body, but i found the following quite convincing:
>
> "There are several important things that can be gleaned from this  
> sample, as basic as it may seem. The first is the fact that the  
> model in this particular case, is situation not in the body (as is  
> implicitly the case with HTML Forms) but in the head. It doesn’t  
> need to be, but given the model is by itself an unrendered object -  
> metadata in the purest sense of the word, having this in the head of  
> the document makes sense."

Currently, xforms:model is placed under xhtml:head: that's all the  
XForms engine knows about.

But it can make a lot of sense to have local models in the view. The  
perfect use case is within xxforms:dialog. Form Builder makes use of  
this pattern, which for now is not native in the XForms engine but  
obtained by applying an XSLT stylesheet to place back the model under  
xhtml:head. Having a local model still helps as it logically groups  
within the dialog the data model and the controls.

In general, this idea could be extended for example to support custom  
components. This kind of ideas have been floated around in the XForms  
working group as well.

-Erik

--
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
http://www.orbeon.com/



--
You receive this message as a subscriber of the ops-users@... mailing list.
To unsubscribe: mailto:ops-users-unsubscribe@...
For general help: mailto:sympa@...?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

[Ryan Puddephatt-3]

Erik,
    Effectivly someone could put the same xml in the epilogue to move all the xforms:model elements to the head as a short term solution

I agree grouping models where the data is used can be very helpful, in large forms especially

Just my 2c

Ryan
------------------------
Ryan Puddephatt
FIX Developer
Fidessa LatentZero
1 Alfred Place
London WC1E 7EB
Office: [phone]
Direct: [phone]
Blackberry: [phone]
Fax: [phone]
Email: rpuddephatt@...
Web: http://www.latentzero.com
Sent from my blackberry device

----- Original Message -----
From: Erik Bruchez <ebruchez@...>
To: ops-users@... <ops-users@...>
Sent: Tue Jul 15 00:35:52 2008
Subject: [ops-users] Re: Re: Mutiple Model problem

>>    1. could html:body have a child that is xforms:model ?
>
> hmm - i didn't find a source that _prohibits_ to put the model into  
> the html:body, but i found the following quite convincing:
>
> "There are several important things that can be gleaned from this  
> sample, as basic as it may seem. The first is the fact that the  
> model in this particular case, is situation not in the body (as is  
> implicitly the case with HTML Forms) but in the head. It doesn’t  
> need to be, but given the model is by itself an unrendered object -  
> metadata in the purest sense of the word, having this in the head of  
> the document makes sense."

Currently, xforms:model is placed under xhtml:head: that's all the  
XForms engine knows about.

But it can make a lot of sense to have local models in the view. The  
perfect use case is within xxforms:dialog. Form Builder makes use of  
this pattern, which for now is not native in the XForms engine but  
obtained by applying an XSLT stylesheet to place back the model under  
xhtml:head. Having a local model still helps as it logically groups  
within the dialog the data model and the controls.

In general, this idea could be extended for example to support custom  
components. This kind of ideas have been floated around in the XForms  
working group as well.

-Erik

--
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
http://www.orbeon.com/


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

_______________________________________________________________________
The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.

_____________________________________________________________________
This e-mail has been scanned for viruses by Verizon Business Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.mci.com


--
You receive this message as a subscriber of the ops-users@... mailing list.
To unsubscribe: mailto:ops-users-unsubscribe@...
For general help: mailto:sympa@...?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

[hcr]

Some parts of this message have been removed. Learn more about Nabble's security policy.

 Thank you for all, I receive this message:

orbeon Orbeon Forms now supports AVTs outside the HTML body. It also supports XForms models placed outside the HTML head (e.g. within dialogs). 04:14 PM July 20, 2008 from twhirl

 

 

 

在2008-07-15，"Ryan Puddephatt" <rpuddephatt@...> 写道：
>Erik,
>    Effectivly someone could put the same xml in the epilogue to move all the xforms:model elements to the head as a short term solution
>
>I agree grouping models where the data is used can be very helpful, in large forms especially
>
>Just my 2c
>
>Ryan
>------------------------
>Ryan Puddephatt
>FIX Developer
>Fidessa LatentZero
>1 Alfred Place
>London WC1E 7EB
>Office: [phone]
>Direct: [phone]
>Blackberry: [phone]
>Fax: [phone]
>Email: rpuddephatt@...
>Web: http://www.latentzero.com
>Sent from my blackberry device
>
>----- Original Message -----
>From: Erik Bruchez 

---

亚胜·铂第公馆约35-101平米MINI小公馆 恭迎品鉴

--
You receive this message as a subscriber of the ops-users@... mailing list.
To unsubscribe: mailto:ops-users-unsubscribe@...
For general help: mailto:sympa@...?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

[Erik Bruchez]

That's right, there is now more freedom of placement for models, in  
particular you can place them within xxforms:dialog.

-Erik

On Jul 22, 2008, at 12:57 AM, hechengrong wrote:

>  Thank you for all, I receive this message:
> orbeon Orbeon Forms now supports AVTs outside the HTML body. It also  
> supports XForms models placed outside the HTML head (e.g. within  
> dialogs). 04:14 PM July 20, 2008 from twhirl
>
>
>
>
> 在2008-07-15，"Ryan Puddephatt" <rpuddephatt@...> 写道：
> >Erik,
> >    Effectivly someone could put the same xml in the epilogue to  
> move all the xforms:model elements to the head as a short term  
> solution
> >
> >I agree grouping models where the data is used can be very helpful,  
> in large forms especially
> >
> >Just my 2c
> >
> >Ryan
> >------------------------
> >Ryan Puddephatt
> >FIX Developer
> >Fidessa LatentZero
> >1 Alfred Place
> >London WC1E 7EB
> >Office: [phone]
> >Direct: [phone]
> >Blackberry: [phone]
> >Fax: [phone]
> >Email: rpuddephatt@...
> >Web: http://www.latentzero.com
> >Sent from my blackberry device
> >
> >----- Original Message -----
> >From: Erik Bruchez
>
>
> 亚胜·铂第公馆约35-101平米MINI小公馆 恭迎品鉴
> --
> You receive this message as a subscriber of the ops-users@...  
> mailing list.
> To unsubscribe: mailto:ops-users-unsubscribe@...
> For general help: mailto:sympa@...?subject=help
> OW2 mailing lists service home page: http://www.ow2.org/wws

--
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
http://www.orbeon.com/



--
You receive this message as a subscriber of the ops-users@... mailing list.
To unsubscribe: mailto:ops-users-unsubscribe@...
For general help: mailto:sympa@...?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws