Re: [Moderator Action] Re: Multiple pages per "form" - more clarity needed?

Leigh,

You are registered in the following mailing list under the following emails:
w3c-forms@w3.org mailing list:  klotz@adoc.xerox.com and
Leigh.Klotz@pahv.xerox.com
www-forms-editor@w3.org mailing list:   same as w3c-forms@w3.org
www-forms@w3.org mailing list:   Leigh.Klotz@pahv.xerox.com



Therefore if you send a message to any of the previous lists using
klotz@graflex.org, your message will not go through and will be moderate
(and delayed).
Same issue when sending  to www-forms@w3.org using the klotz@adoc.xerox.com.


Moderator: message sent to www-forms@w3.org <www-forms@w3.org>;
www-forms-editor@w3.org <www-forms-editor@w3.org>




----- Original Message -----
From: "Leigh Klotz" <klotz@graflex.org>
To: <www-forms-editor@w3.org>
Cc: <xforms@yahoogroups.com>; <www-forms@w3.org>; <www-forms-editor@w3.org>
Sent: Tuesday, September 03, 2002 4:15 AM
Subject: [Moderator Action] Re: Multiple pages per "form" - more clarity
needed?


>
>
> > From: AndrewWatt2001@aol.com
> > Message-ID: <38.2d6c9882.2aa4c3cd@aol.com>
> > Date: Mon, 2 Sep 2002 09:38:21 EDT
> > To: xforms@yahoogroups.com, www-forms@w3.org, www-forms-editor@w3.org
> > Subject: Multiple pages per "form" - more clarity needed?
> >
> > Chapter 4.3 of the XForms Requirements documents refers (among other
things)
> > to supporting multiple pages per form.
> >
> > It isn't obvious to me exactly how this normative requirement should be
> > interpreted. The vagueness about what is or is not an XForms "form"
again
> > arises here. Since I am presently unclear about what an XForms "form"
> > actually is I am not sure how to interpret the Requirements document.
> Compare with WML Cards and some similar constructs in Voice work (I'm
> unsure of the exact one).
>
> The goal is to have a form which is in one host document, retrieved and
> initialized once, yet able to switch its presentation to provide a
> moving "window" in the user interface layer to present different parts
> of the instance, under form author control, and in response to user
> input.  XForms does this with the switch, case, and toggle elements..
>
> See Section 9.2 (The Switch Module).
> http://www.w3.org/TR/2002/WD-xforms-20020821/slice9.html#id2628534
>
> >
> > Are we, for example, referring to an XForms model which is duplicated on
two
> > separate-but-related XHTML pages? With each page having some of the
XForms
> > form controls? Does xforms:instance on page 1 only have the
initialization
> > data for the form controls on page 1? Or for both pages?
> You've probably already figuredt this out from the previous paragraph,
> but the form is initialized once in the one host document, but its
> presentation is altered by the switch, so the model-level semantic
> questions you ask here don't arise.
>
> > If the latter scenario, then how is a field that is displayed on page 2
that
> > is required to be non-empty to be processed, assuming that data is
submitted
> > when the form controls on the first page are filled in?
> All validation is done at time of submission, but an author can use
> XPath expressions to disable the trigger that advances to the next
> toggle, etc.
>
> If this doesn't answer your questions below, please let me know.
>
> Leigh.
>
> >
> > Or is the type of layout solution I have used on http://www.XMML.com
with SVG
> > "mini pages" the kind of scenario which is envisaged? ... with, of
course,
> > XForms form controls where there are currently only SVG text-containing
> > mini-pages.
>
> >
> > To what extent, if any, is an XForms processor responsible for bringing
the
> > parts of the instance data together?
> >
> > Andrew Watt
> >

Received on Tuesday, 3 September 2002 12:34:05 UTC