Re: normalizedString/input and string/textarea?

Hi Alain,

xsd:string is the almost-right datatype, and so there has been no priority 
on doing better.
normalizedString does stuff to a string that we would not want.
The exact right datatype would be one pattern derived from string with the 
regex pattern [^\n] as the only thing input really says differently than 
textarea is single line input.

Cheers,
John M. Boyer, Ph.D.
Distinguished Engineer, IBM Forms and Smarter Web Applications
IBM Canada Software Lab, Victoria
E-Mail: boyerj@ca.ibm.com 

Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer
Blog RSS feed: 
http://www.ibm.com/developerworks/blogs/rss/JohnBoyer?flavor=rssdw





From:   Alain Couthures <alain.couthures@agencexml.com>
To:     "www-forms@w3.org" <www-forms@w3.org>
Date:   04/14/2011 09:03 AM
Subject:        normalizedString/input and string/textarea?
Sent by:        www-forms-request@w3.org



Hello,

I'm still perplex about the differences between core forms input controls.

More specifically, if I want to edit an instance according to types, I 
would consider that xsd:string is not correct for xf:input but for 
xf:textarea.

It is obvious that the carriage return, line feed and tab characters 
cannot be entered using xf:input but xf:textarea.

So, why isn't xsd:normalizedString the default type for xf:input?

Thank you very much for your answers!

Alain Couthures
<agenceXML>
http://www.agencexml.com/xsltforms