i061 resolution

After first paragraph of Section 4.1, insert the following.

The inclusion of wsaw:Action without inclusion of  
wsaw:UsingAddressing has no normative intent and is only  
informational. In other words, the inclusion of wsaw:Action  
attributes in WSDL alone does not imply a requirement on clients to  
use Message Addressing Properties in messages it sends to the  
service. A client, however, MAY include Message Addressing Properties  
in the messages it sends, either on its own initiative or as  
described by other elements of the service contract, regardless of  
the presence or absence of wsaw:UsingAddressing. Other specifications  
defining the value of [action] are under no constraint to be  
consistent with wsaw:Action.

Modify second paragraph in section 3.1 as follows:

A wsaw:UsingAddressing element with a wsdl:required attribute whose  
value is "true" indicates that messages exchanged with the endpoint  
MUST have WS-A engaged (as defined by a binding of the Message  
Addressing Properties to a protocol). A wsaw:UsingAddressing element  
with a wsdl:required attribute whose value is "false" indicates that  
the endpoint will accept input messages with or without WS-A engaged.  
In the latter case, if WS-A is engaged, the use of the Message  
Addressing Properties MUST be fully compliant with this  
specification; in particular, senders MUST use all Message Addressing  
Properties mandated by the [Core, Applicable WS-Addressing protocol  
bindings (e.g., SOAP), and this spec] and MUST follow all applicable  
WS-Addressing normative requirements. Such an endpoint MAY generate  
output messages with MAPs bound to them; however, if a message with  
WS-A engaged is sent to that endpoint, any subsequent messages in  
[that exchange pattern] MUST also have WS-A engaged.

If a SOAP binding is used and WS-Addressing header blocks are not  
present in an input message then WS-Addressing header blocks encoded  
in the corresponding output message MUST NOT be required to be  
understood using the SOAP mustUnderstand mechanism.


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

Received on Saturday, 1 October 2005 03:36:09 UTC