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

XForms Test Suite 1.1 - Test case 2.4.a

From: Perquin, Mike <mjperquin@Seneca.nl>
Date: Fri, 14 Oct 2011 15:15:32 +0200
To: "'www-forms@w3.org'" <www-forms@w3.org>
Message-ID: <75E7B21D8A13D44CAE0ED2AE2DE3354024CA7BFA@SIMX02.Seneca.Intern>

I would like to discuss test case 2.4.a.

In my opinion, the xforms instance document shouldn't validate since it declares a default namespace on the top level of the document and therefore every child node is within the same namespace.

However, the inline schema within this example doesn't specify an elementFormDefault attribute and therefore when applying schema validation elementFormDefault unqualified will be used (which is the default).

This will cause an schema validation error (at least when using .NET XmlDocument schema validation): "The element 'payment' in namespace 'http://commerce.example.com/payment' has invalid child element 'number' in namespace 'http://commerce.example.com/payment'. List of possible elements expected: 'number, expiry'.".

When I change the test case and specify "elementFormDefault='qualified'", the instance document validates without any schema errors.

This is also what is to be expected reading the article: http://geekswithblogs.net/dmillard/archive/2004/10/20/12935.aspx

What's your opinion on this matter?

With kind regards,

Mike Perquin
Senior Developer
Research & Development


Elektronicaweg 31

2628 XG Delft, Nederland


+31 (0)15 - 251 37 00


+31 (0)15 - 251 37 01





Op dit mailbericht is onze disclaimer<http://www.seneca.nl/disclaimer> van kracht.

(image/png attachment: image001.png)

(image/png attachment: image003.png)

Received on Friday, 14 October 2011 22:12:04 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:36:25 UTC