- From: Nick Van den Bleeken <Nick.Van.den.Bleeken@inventivegroup.com>
- Date: Tue, 17 Apr 2012 07:15:58 +0000
- To: John Boyer <boyerj@ca.ibm.com>
- CC: "<public-forms@w3.org>" <public-forms@w3.org>
- Message-ID: <9A77491B-0870-4E61-971F-8D83CAE4426C@inventivegroup.com>
John, Great work! I have one remark though ;) the actions to add xf:veal-in-context(), xf:replace() and xf:matches() pre-date the decision to target XPath 2.0 for XForms 2.0. And you don't need those functions if you have an XPath 2.0 engine. We have three possibilities: 1) Add those functions to XForms 2.0 like you have done 2) Don't add those functions to XForms 2.0 because you don't need them in XPath 2.0 3) Create a separate section were we group all the functions that are no longer needed if you have an XPath 2.0 engine, but are there for 'backwards compatibility'. 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 17 Apr 2012, at 00:36, John Boyer wrote: See http://www.w3.org/MarkUp/Forms/wiki/XPath_Expressions_Module 1) Added functions xf:eval() and xf:eval-in-context() per Action-1836 (https://www.w3.org/2005/06/tracker/xforms/actions/1836) 2) Added functions xf:matches() and xf:replace() per Action-1813 (https://www.w3.org/2005/06/tracker/xforms/actions/1813) 3) Amended existing example descriptions and added example to adjust-dateTime-to-timezone() per Action-1805 (https://www.w3.org/2005/06/tracker/xforms/actions/1805) 4) Fixed return type of xf:attribute() function, which claimed to return an element() 5) Added the frequently used but undefined namespace prefix "xf" 6) Changed example in index() and valid() functions to remove unnecessary xforms namespacing and add following descriptions. Note that <xforms:instance> remains in examples of instance() and current() because the examples would break if prefix removed. Those examples use the best practice of putting xmlns="" on the <xforms:instance> element to avoid infesting the XML data with xmlns="". 7) Fixed one incorrectly placed id anchor for boolean functions. 8) Added id anchor spans for almost all functions in the spec 9) Made numerous fixes to spurious div end tags 10) Added one missing "Examples:" and removed one duplicate "Examples:" 11) Made some changes to the acknowledgements (Remaining issues: Is Steven Pemberton entry accurate, what do we do about past members) 12) Changed editor list :-) 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 -- 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 Tuesday, 17 April 2012 07:18:28 UTC