- From: Nick Van den Bleeken <Nick.Van.den.Bleeken@inventivegroup.com>
- Date: Wed, 18 Apr 2012 14:20:52 +0000
- To: John Boyer <boyerj@ca.ibm.com>
- CC: Public Forms <public-forms@w3.org>, "public-xformsusers@w3.org" <public-xformsusers@w3.org>
- Message-ID: <1DC50C9C-09DB-4F4E-B94B-059C741DE291@inventivegroup.com>
In my opnion "At the time of evaluation, an XPath expression must be syntactically correct. In addition, the namespaces the expression references must be in scope and the functions and variables it references must be defined. If any of these conditions is not satisfied, or a dynamic error or a type error occurs during evaluation, an exception (xforms-compute-exceptionXF) is raised, except for binding expressions, which produce a different exception (xforms-binding-exceptionXF)." clearly defines when an exception is raised. So for me those actions may be closed. Kind regards, Nick Van den Bleeken R&D Manager Phone: +32 3 425 41 02 Office fax: +32 3 821 01 71 nick.van.den.bleeken@inventivegroup.com<mailto:nick.van.den.bleeken@inventivegroup.com> www.inventivedesigners.com [cid:image001.png@01CBF2F8.1DA19110][cid:image002.png@01CBF2F8.1DA19110][cid:image003.png@01CBF2F8.1DA19110] On 18 Apr 2012, at 16:15, John Boyer wrote: Hi Nick, Does this section adequately capture the conditions under which an exception will be produced based on having an error of some kind in the XPath expression? I think it is sufficient. If so, then I think some of the action items I have around providing errata to make it more clear the conditions under which an error should occur are just spec nitpicks that should be closed without further work. The level of spec seems adequate to me for implementers to figure out when to emit an exception due to an xpath error. Do you agree? 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<mailto:boyerj@ca.ibm.com> Twitter: http://twitter.com/johnboyerphd Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer Blog RSS feed: http://www.ibm.com/developerworks/blogs/rss/JohnBoyer?flavor=rssdw From: Nick Van den Bleeken <Nick.Van.den.Bleeken@inventivegroup.com<mailto:Nick.Van.den.Bleeken@inventivegroup.com>> To: Public Forms <public-forms@w3.org<mailto:public-forms@w3.org>> Cc: "public-xformsusers@w3.org<mailto:public-xformsusers@w3.org>" <public-xformsusers@w3.org<mailto:public-xformsusers@w3.org>> Date: 18/04/2012 06:09 AM Subject: Made xpath error information available as context information for xforms-compute-exception and xforms-binding-exception ________________________________ All, I made the xpath error information available as context information for xforms-compute-exception and xforms-binding-exception. See http://www.w3.org/MarkUp/Forms/wiki/XPath_Expressions_Module#XPath_Expressions_in_XForms Kind regards, Nick Van den Bleeken R&D Manager Phone: +32 3 425 41 02 Office fax: +32 3 821 01 71 nick.van.den.bleeken@inventivegroup.com<mailto:nick.van.den.bleeken@inventivegroup.com> www.inventivedesigners.com ________________________________ Inventive Designers' Email Disclaimer: http://www.inventivedesigners.com/email-disclaimer -- This message has been scanned for viruses and dangerous content by MailScanner<http://www.mailscanner.info/>, and is believed to be clean. ________________________________ Inventive Designers' Email Disclaimer: http://www.inventivedesigners.com/email-disclaimer
Attachments
- image/png attachment: image001.png
- image/png attachment: image002.png
- image/png attachment: image003.png
Received on Wednesday, 18 April 2012 14:25:44 UTC