W3C home > Mailing lists > Public > public-forms@w3.org > June 2011

Re: Updated XPath Expression module

From: John Boyer <boyerj@ca.ibm.com>
Date: Thu, 30 Jun 2011 14:34:50 -0700
To: Nick Van den Bleeken <Nick.Van.den.Bleeken@inventivegroup.com>
Cc: Public Forms <public-forms@w3.org>, public-forms-request@w3.org
Message-ID: <OFF099BC45.FD60A501-ON882578BF.0075ECB4-882578BF.00768DA0@ca.ibm.com>
Hi Nick,

I would've made the suggested changes below on the wiki, but it actually 
looks like this this module is being done with spec xml?

Wording looks good overall.

I'd recommend getting rid of the "note" aspect and just make this another 
paragraph.  Some readers of W3C specs (not equal to me) have interpreted 
notes as informative rather than normative, whereas we're using the word 
"may" to indicate a legitimate implementation option.

Second, I'd recommend the sentence be rearranged a bit to enable you to 
change from "engine" to "implementation" and also to formally specref 
XPath 1.0 and XPath 2.0 in the sentence as you go.  Like this:

If XPath 1.0 compatibility mode is requesed, an XForms processor may use 
either an XPath 1.0 implementation [XPath 1.0] or an XPath 2.0 
implementaiton in XPath 1.0 compatibility mode [XPath 2.0]. 

Then your following sentence that starts "Be aware that some 
expressions..." could instead just start as "Some expressions...".  It is 
tempting to make that sentence a note, but best not to because your final 
sentence says something normative again, namely that exceptions can 

John M. Boyer, Ph.D.
Distinguished Engineer, IBM Forms and Smarter Web Applications
IBM Canada Software Lab, Victoria
E-Mail: boyerj@ca.ibm.com 

Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer
Blog RSS feed: 

From:   Nick Van den Bleeken <Nick.Van.den.Bleeken@inventivegroup.com>
To:     Public Forms <public-forms@w3.org>
Date:   06/30/2011 01:18 PM
Subject:        Updated XPath Expression module
Sent by:        public-forms-request@w3.org


I updated the XPath expression module.

I added the node creation functions to the module and added the follwing 
note to the xpath-version attribute:

If an XForm processor has no access to an XPath 2.0 engine, an XPath 1.0 
engine may be used if XPath 1.0 compatibility mode is requested. Be aware 
that some expressions can't be executed with an XPath 1.0 engine and that 
some functions defined in [Functions and Operators] may be missing if an 
XPath 1.0 engine is used. If the XPath 1.0 engine can't evaluate the 
expression an xforms-compute-exceptionXF or an xforms-binding-exceptionXF 
will be dispatched.

The full version is available at [1] and a diff marked version is 
available at [2]
Comments are welcome.
Kind regards,

Nick Van den Bleeken
R&D Manager

Phone: +32 3 821 01 70
Office fax: +32 3 821 01 71


Inventive Designers' Email Disclaimer:
Received on Thursday, 30 June 2011 21:35:21 UTC

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