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

Hi Nick,

Oh, I now see and agree with your point that it wouldn't be necessary in 
those places to change from having special attributes to using binding 
attributes, since we changed over to having @context to Common instead of 
binding attributes. 

That being said, you raised the very interesting point that we hadn't 
discussed, which is the interplay between @model and @context.  I think 
you're right that @model *must* go to Common as well.  At that point, 
virtually all the changes described below must be made anyway, and it 
would make little sense to keep around ref/nodeset as a special attribute 
in a few places.

Unfortunately, I won't be able to join next week's call, so I'd like to 
say by email that I support the change to put @model in Common, and all 
that it implies.

Thanks,
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:   Nick Van den Bleeken <Nick.Van.den.Bleeken@inventivegroup.com>
To:     John Boyer/CanWest/IBM@IBMCA
Cc:     Leigh L Klotz Jr <leigh.klotz@xerox.com>, Public Forms 
<public-forms@w3.org>, "<public-xformsusers@w3.org>" 
<public-xformsusers@w3.org>
Date:   24/05/2012 11:33 PM
Subject:        Re: Added context everywhere (by adding it to the binding  
 attributes)



John, 

I thought that the last two resolutions/actions invalidated the previous 
resolutions/actions. If we still want to go forward with this I can make 
the changes. But we should put it back on the agenda then, or agree by 
e-mail.

One thing, it might make sense to add model also to common attributes, 
because all XForms elements can now have  XPath expressions (AVT's in 
attributes and context attribute). 

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
www.inventivedesigners.com




On 24 May 2012, at 16:11, John Boyer wrote:

Hi Nick and Leigh, 

It hasn't been done yet, but this action is to correspond with 
1) removing ref/nodeset as special attributes from elements like header 
and bind 
2) adding binding exceptions on header and bind if you bind to a model 
other than the containing one with a model or a bind attribute 
3) removing model as special attribute from elements like var and 
rebuild/recalculate/revalidate/refresh 
4) clarifying special handling of model attribute on these elements 

Also, Leigh, we were thinking that perhaps you were asking about whether 
context applied to only to single node bindings (versus also nodeset 
bindings) due to something specific you were reading that needed 
clarification, and if so, could you indicate what that is (unless it is 
now clear by the move of context attribute to the Common group). 

Thanks, 
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:        Nick Van den Bleeken <Nick.Van.den.Bleeken@inventivegroup.com
> 
To:        Leigh L Klotz Jr <leigh.klotz@xerox.com> 
Cc:        "<public-xformsusers@w3.org>" <public-xformsusers@w3.org>, 
Public Forms <public-forms@w3.org> 
Date:        24/05/2012 12:41 AM 
Subject:        Re: Added context everywhere (by adding it to the binding  
 attributes) 



Leigh, 

Thank you for the great input! 

We've added @context to Common attributes because now that we have AVT's 
(and if, while attribute on actions) it makes indeed sense to have context 
everywhere, this was the intention anyway. (We also ensured that all 
XForms elements allow at least the common attributes). 

Could you elaborate a bit why you are thinking @context may not go on both 
single-node-binding and sequence-binding? It is intended to go everywhere. 


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
www.inventivedesigners.com


<Mail Attachment.png><Mail Attachment.png><Mail Attachment.png> 

On 21 Apr 2012, at 01:15, Leigh L Klotz Jr wrote: 

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.

-- 
This message has been scanned for viruses and 
dangerous content by MailScanner, and is 
believed to be clean. 



Inventive Designers' Email Disclaimer:
http://www.inventivedesigners.com/email-disclaimer 

-- 
This message has been scanned for viruses and 
dangerous content by MailScanner, and is 
believed to be clean. 



Inventive Designers' Email Disclaimer:
http://www.inventivedesigners.com/email-disclaimer