W3C home > Mailing lists > Public > public-forms@w3.org > August 2007

RE: Big update to XForms 1.1 spec; Ready for your review

From: Klotz, Leigh <Leigh.Klotz@xerox.com>
Date: Mon, 20 Aug 2007 14:13:28 -0700
Message-ID: <E254B0A7E0268949ABFE5EA97B7D0CF4036C08AC@USA7061MS01.na.xerox.net>
To: "John Boyer" <boyerj@ca.ibm.com>, "Forms WG (new)" <public-forms@w3.org>
This makes me nervous for a number of reasons; it may be better left
unsaid, as I'm not sure it adds any value, and has the following areas
of concern:
1. A11Y - Is this a presentation issue ("can't press enter")? 
2. M8A ("multimedia", is that a contraction?) - what if input is bound
to some type other than xsd:string and there is a chooser for it.  Is it
essential that the "should" be perserved?
3. How is multi-line text defined?   Is it a lexical representation
issue?  If so, see #2 and also we need to define a lexical pattern for
"multiple lines." I would think the mere mention of EBCIDIC would be
enough to scare off most, but we could refer to XML 1.0 (and then XML
1.1 whose sole difference appears to be newline patterns).  
4. Does secret have the same constraint?  If not, why not?


From: public-forms-request@w3.org [mailto:public-forms-request@w3.org]
On Behalf Of John Boyer
Sent: Thursday, August 16, 2007 10:46 PM
To: Forms WG (new)
Subject: Big update to XForms 1.1 spec; Ready for your review


 Pointed out in implementation requirements for element input that the
user should be prevented from entering multiline text (since that's what
textarea is for) 
Received on Monday, 20 August 2007 21:13:55 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:13:53 UTC