Conclusion to effects of readonly on trigger

I think we were pretty close to a conclusion on the telecon about the 
interpretation of the readonly MIP for trigger.

Whatever the decision, it seems worthwhile make note of it in the spec 
given that we had some work to do getting through the points ourselves.

Let's see if we can get this wrapped up on the list during the week and/or 
get a clear statement of resolution that folks can vote on next week if 
necessary.

Here is what I understood from the discussion:

1) Like all other events for MIPs, the xforms-readonly and 
xforms-readwrite events are received by a trigger bound to a node (when 
the processing model says those events are to be dispatched, of course).

2) The readonly MIP is a statement about the what can happen to the data 
node.  Since a trigger does not directly manipulate the data node via  its 
UI binding, there is no direct relationship between the data node being 
readonly and presentational properties of the trigger.  Specifically,

a) The ability to activate a trigger is not disabled if the trigger is 
bound to a readonly node
b) The default countenance of the trigger is unaffected, i.e. it does not 
take on a disabled countenance

Cheers,
John M. Boyer, Ph.D.
STSM: Lotus Forms Architect and Researcher
Chair, W3C Forms Working Group
Workplace, Portal and Collaboration Software
IBM Victoria Software Lab
E-Mail: boyerj@ca.ibm.com 

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