Re: Issue 211: Omitting interface messages in bindings

I had an AI to propose a solution to 211 that was in the definition of 
Binding Operations, rather than Binding Message References, and in 
clearer prose.

Add this after the third paragraph ("For each Binding Operation...") of 
2.11.1:

For each Binding Message Reference in the {message references} property 
of a Binding Operation component, there MUST be an Interface Message 
Reference with the same {message label} and {direction} properties in 
the corresponding Interface Operation. Note that the converse is not 
required; i.e., there need not be a Binding Message Reference 
corresponding to each Interface Message Reference in the Interface 
Operation component.


--
Mark Nottingham   Principal Technologist
Office of the CTO   BEA Systems