W3C home > Mailing lists > Public > www-forms-editor@w3.org > February 2007

RE: XForms 1.1 "the next generation of forms for the Web" = too old school

From: Klotz, Leigh <Leigh.Klotz@xerox.com>
Date: Fri, 23 Feb 2007 09:27:57 -0800
Message-ID: <E254B0A7E0268949ABFE5EA97B7D0CF402CF055C@usa7061ms01.na.xerox.net>
To: "Steven Pemberton" <steven.pemberton@cwi.nl>, "Daniel Gr" <daniel@jaspoid.com>, <www-forms-editor@w3.org>

Yes, please see http://www.w3.org/TR/xforms11/#ui-upload for audio and

-----Original Message-----
From: w3c-forms-request@w3.org [mailto:w3c-forms-request@w3.org] On
Behalf Of Steven Pemberton
Sent: Friday, February 23, 2007 6:08 AM
To: Daniel Gr; www-forms-editor@w3.org
Subject: Re: XForms 1.1 "the next generation of forms for the Web" = too
old school

On Fri, 23 Feb 2007 12:29:03 +0100, Daniel Gr <daniel@jaspoid.com>
> Seriously:
> 1. Where's the audio input controls?
> 2. Where's the video input controls?

A flippant answer would be: In the same place as the date input

What you have to understand is that the XForms controls, in almost all  
cases, do not commit themselves to the type of the data that they are  
bound to.

So if you say

	<input ref="departure">...

and the datatype of 'departure' is a date, then you get a date picker.

The advantages of this is flexibility. If XForms had required a date  
picker control, then it would have required a control for every sort of

datatype, and when people needed new sorts of controls, the language
have to be updated.

With this design, the language stays stable, and implementations can  
compete on how good their controls are, and which types they support.

Best wishes,

Steven Pemberton
Received on Friday, 23 February 2007 17:28:22 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:25:11 UTC