- From: Jérôme Nègre <jerome.negre@e-xmlmedia.fr>
- Date: Thu, 10 Jan 2002 13:11:09 +0100
- To: "Roland Merrick" <roland_merrick@uk.ibm.com>
- Cc: "Steven Pemberton" <steven.pemberton@cwi.nl>, <www-forms@w3.org>
> Greetings, things are not as bad as people seem to be implying here.
I wonder who you're talking about ?
I have a few remarks on the *draft*, so I'm saying them. Once it'll be a
recommendation, it'll be too late.
<snip>
> I know this doesn't fix the cross model issue that you have recognised but
> is does reduce the number of practical, rather than theoretical,
situations
> where the form designer might have had to resort to two models.
In my example, everything was inline and made simple to be concise.
Let's go for a real-life, pratical example. I hope you'll like it.
Let's say I'm running an e-commerce site.
I have a XML catalog at http://mysite.com/catalog.xml.
Since my customers can save their basket between sessions, the current
basket of a customer is available at http://mysite.com/basket.xml
(identification being made with the help of cookies or whatever).
Of course, my form needs some working variables.
I might end up with something like that:
<html>
<head>
<xform:model id="catalog">
<xform:instance xlink:href="http://mysite.com/catalog.xml"/>
...
<xform:model id="basket">
<xform:instance xlink:href="http://mysite.com/basket.xml"/>
...
<xform:model id="working_variables">
<xform:instance>
...
</xform:instance>
...
</html>
So, this is a practical situation, how do you rewrite it with only one model
? Of course, it isn't allowed to write a server-side script, you must use
pure XForms.
Regards,
Jérôme
Received on Thursday, 10 January 2002 07:11:41 UTC