RE: Added context everywhere (by adding it to the binding attributes)

Hi Leigh,

Do you mean just that you will try to get to reading the changes?
We did already change the spec to reflect these.  I'm just letting you 
know that we did some good fixes as a result of your feedback.  So you 
don't have to do anything more... unless you see a place where we need to 
make any further fixes.

Thanks again,
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: 
http://www.ibm.com/developerworks/blogs/rss/JohnBoyer?flavor=rssdw





From:   "Klotz, Leigh" <Leigh.Klotz@xerox.com>
To:     John Boyer/CanWest/IBM@IBMCA
Cc:     Public Forms <public-forms@w3.org>, <public-xformsusers@w3.org>
Date:   13/06/2012 03:24 PM
Subject:        RE: Added context everywhere (by adding it to the binding  
attributes)



I will try to get to these changes.

From: John Boyer [mailto:boyerj@ca.ibm.com] 
Sent: Wednesday, June 13, 2012 10:28 AM
To: Klotz, Leigh
Cc: Public Forms; public-xformsusers@w3.org
Subject: Re: Added context everywhere (by adding it to the binding 
attributes)

Hi Leigh, 

Further response to this line of inquiry: 
- Yes context goes everywhere, so we moved it to the Common group 
- As a result, the model attribute had to be moved to the Common group, 
which applied model in places not previously applied 
- The bind element is explicitly restricted to binding to the current 
model, if the model is expressed, to avoid cross-model computation 
dependencies. 
- The header and var elements are not restricted in terms of the model to 
which they can bind as they are like actions, which are not restricted 
from referring to another model. 
- As Nick previously responded, model and context apply to any kind of 
binding. 
- Actions such as rebuild, recalculate, revalidate, refresh and reset were 
amended to remove model as a special attribute, since it is in Common. The 
text was changed to use the model of the inscope evaluation context 
instead, along with a Note indicating that the model attribute could be 
used to change the context. 
- Actions and their children/descendants, such as dispatch and its 
children, get context and model.  For example, it is at least feasible (if 
not terribly useful) to get the dispatch name from the data of one model 
and the dispatch targetid from the data of another model. 

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 

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:        Leigh L Klotz Jr <leigh.klotz@xerox.com> 
To:        public-xformsusers@w3.org 
Cc:        Public Forms <public-forms@w3.org> 
Date:        20/04/2012 04:16 PM 
Subject:        Re: Added context everywhere (by adding it to the binding  
attributes) 



There is still a distinction between 
single-node binding: @model, @ref, @bind 
and 
sequence-binding (formerly nodeset) binding @model, @ref, @nodeset, @bind 
In that single-node-binding is used on 
label, hjelp, hint, alert, message, item/value, item/copy, 
upload/filename, upload, output, output/mediatype, input, textarea, 
secret, select,select1, range, trigger, submit, load, setvalue, group, 
switch, 
and sequence-binding is used on 
itemset, insert, delete, repeat. 

Q: Does @context go on both single-node-binding and sequence-binding?

Q: Also, does @context go in any of the following places, which currently 
have @nodeset, @ref, or @model: 
header, bind
other actions (rebuild, dispatch, send, setfocus, etc)
var

Leigh.