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

RE: evaluation context

From: Josef Dietl <josef@mozquito.com>
Date: Tue, 23 Oct 2001 10:31:31 +0200
Message-ID: <D0F1529EE943B3449F755CA1A40887464E0FFE@winserver.windomain.mozquito.com>
To: "Erik van Oosten" <erik.van.oosten@backstream.com>, "www-forms mailinglist (E-mail)" <www-forms@w3.org>
OK, we'll see what we can do in the framework XML Schema gives us.

Josef

> -----Original Message-----
> From: Erik van Oosten [mailto:erik.van.oosten@backstream.com]
> Sent: Monday, October 22, 2001 11:00 AM
> To: www-forms mailinglist (E-mail)
> Subject: RE: evaluation context
> 
> 
> > > Weeell... this example is precisely one of the more 
> tricky cases. I
> do
> > > remember extended discussions about having form controls inside
> captions
> > > - or more precisely, about prohibiting them. What is the 
> use or need
> (or
> > > meaning) of having, say, a xf:input _inside_ a 
> xf:caption? or inside
> a
> > > xf:help or xf:hint? We do have open content models for these three
> > > because we believe that for the integration in other markup
> languages,
> > > it doesn' make sense to disallow markup from _these_ 
> languages (like
> for
> > > example XHTML). In the group, we are pretty convinced that XForms
> inside
> > > caption, help and hint does not make sense.
> > >
> > > What do you think about that?
> > 
> > Except for xf:output, xf:repeat, xf:switch. These form controls and
> > structures are useful inside caption, help and hint, I think...
> 
> That is correct. The xf:output is useful for example when a 
> novice user
> would get an elaborate explanation or hint where an expert would only
> get a small reminder.
> (The term 'explanation' shows more respect to the user then the term
> 'help', but who cares?)
> 
>     Erik.
> 
> 
Received on Tuesday, 23 October 2001 04:32:02 GMT

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