W3C home > Mailing lists > Public > public-forms@w3.org > October 2014

Concerns related backwards compatibility in XForms 2.0

From: Nick Van den Bleeken <Nick.Van.den.Bleeken@inventivegroup.com>
Date: Fri, 31 Oct 2014 22:11:55 +0000
To: Public Forms <public-forms@w3.org>
Message-ID: <D0795737.CBCF%Nick.Van.den.Bleeken@inventivegroup.com>
All,

During the XForms editorial meeting concerns related related backwards compatibility in XForms 2.0 were expressed.

More exactly with providing the type information to the XPath engine when the instance data node is invalid related to its type (eg: a + b could result in a dynamic error in XForms 2.0 apposed to NaN in XForms 1.1).

In XPath 2.0 you have a compatibility mode to make the transition from Xpath 1.0 to Xpath 2.0 smoother (i.e.: expressions run in compatibility mode behave closer to what was the case in Xpath 1.0 then if they were ran in the normal Xpath 2.0 mode). The question arrises if we need a way to trigger the Xpath 2.0 compatibility mode.

Kind Regards,

Nick Van den Bleeken
Product Evangelist
T +32 3 425 41 02
E nick.van.den.bleeken@inventivegroup.com<mailto:nick.van.den.bleeken@inventivegroup.com>

Inventive Designers nv
Sint-Bernardsesteenweg 552
2660 Hoboken  (Belgium)

www.inventivedesigners.com<https://www.inventivedesigners.com/>   Follow us on: Facebook<https://www.facebook.com/inventivedesigners> * Twitter<https://twitter.com/inventivedes> * YouTube<https://www.youtube.com/user/invdes>
Received on Friday, 31 October 2014 22:12:25 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:14:10 UTC