W3C home > Mailing lists > Public > public-forms@w3.org > April 2012

Definition of "dependent" and "reference" in Proposed Erratum 14, XForms 2.0, XPath Expression Module

From: John Boyer <boyerj@ca.ibm.com>
Date: Tue, 17 Apr 2012 15:52:30 -0700
To: public-forms@w3.org
Message-ID: <OF9DA2E3D1.CD199A3D-ON882579E3.007BFFC7-882579E3.007DA847@ca.ibm.com>
On Jan 20, 2011 (
http://lists.w3.org/Archives/Public/public-forms/2011Jan/0017.html) we 
discussed the issue that the definition of the term 'reference' was too 
broad and caused excessive circular references that made the recalculation 
engine malfunction in reasonable use cases. The outcome was an action item 
for me to "make it better somehow".

The longer term desire is to loosen the definition of 'reference' to the 
point where it is not so implementation specific and indeed where we could 
entirely get rid of manual rebuilds.

I find that I cannot currently loosen that definition at all without also 
radically changing our architecture so that the notions of manual rebuild 
and dynamic dependency are eliminated.  But, in the process I also 
realized that since the long term goal was to eliminate dynamic 
dependencies and rebuilding, then the short term erratum/correction is to 
fix the definition of 'dependent' for computed expressions, and leave the 
overhaul of the definitions for another time.

This has the desirable effect that the fix does not affect anyone who 
isn't using the actual recalculation graph algorithm, and this change does 
not affect anyone who might be concerned with doing static analysis as an 
alternative way of achieving the definition of 'reference'.  The 
definition of 'reference' is no better than before, but also no worse.  It 
simply isn't changed, so this Erratum can be clearly seen to be orthogonal 
to that concern.

Proposed Erratum 14: 

I've also made this change to the XForms 2.0 wiki spec (as you'll see, 
easy enough to roll back or further refine): 

Lastly, all this got started because I noticed that the definition of 
'reference' was XPath specific, so the XForms 2.0 spec indicated that the 
reference selection mechanism appears in the expression module, so I 
amended the expression module to actually contain it:

Note that this version simply preserves what we used to have in XForms 
1.1, so it needs to be looked at with XPath 2.0 eyes.

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

Twitter: http://twitter.com/johnboyerphd
Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer
Blog RSS feed: 
Received on Tuesday, 17 April 2012 22:54:00 UTC

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