W3C home > Mailing lists > Public > www-forms@w3.org > May 2006

Re: Because type is for datatype, there should not be a problem for XForms Basic

From: David Landwehr <david.landwehr@solidapp.com>
Date: Wed, 03 May 2006 20:33:00 +0200
Message-ID: <4458F75C.8040109@solidapp.com>
To: John Boyer <boyerj@ca.ibm.com>
Cc: www-forms@w3.org

Hi

For clarity could you please write if this is the official WG answer or 
your own opinion (when I read this aloud it sounds like the WG answer)?

>
> When an unrecognized type is referenced, it defaults down to 
> xsd:string, which matches pretty much everything.
But then mixed content will always be invalid, correct?
E.g.
<data>
  <value>v</value>
</data>

and <xforms:input ref="/data">... if no datatypes is assigned to <data> 
and it defaults to xsd:string, then it will be invalid because of the 
<value/>. Is that really what the working group intent? The very funny 
implication of this is that a form with an instance that has no types 
assigned and has more than a document element will always be invalid and 
will never submit (unless you go to corner examples as having a ref to a 
node with hasn't got element in its content).

IMO the validation scheme used in XForms is totally broke and under 
specified and should be fixed from scratched.

Best regards,
David
Received on Wednesday, 3 May 2006 18:33:16 GMT

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