- From: Francisco Curbera <curbera@us.ibm.com>
- Date: Tue, 27 Sep 2005 19:40:39 -0400
- To: public-ws-addressing@w3.org, public-ws-addressing-request@w3.org
My action item, quoting from the minutes (9/12): "1) in case 2, if wsa headers are sent, they must be responded to by the service. 2) in case 2, client either chooses to honor Addressing, or not to include any wsa headers (whole enchilada) 3) in case 3, wsaw:Action is informational. Clarify these three items. <mnot> [numbered bullets are additions to 3' proposal in Jonathan's e-mail]" The two paragraphs below address this AI. 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 alone does not imply a requirement on clients to use wsa header blocks in messages it sends to the service. A client, however, MAY include wsa header blocks in the messages it sends, either on the client's own initiative or as described by other elements of the service contract. It MAY use the values of wsaw:Action in these headers. Additional mechanisms defining the value of [action] are under no constraint from this spec 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 contain WS-Addressing Message Addressing Properties. 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-Addressing header blocks. <add>In this case, if WS-Addressing header blocks are included in a message sent to the endpoint, their use MUST be fully compliant with this specification; in particular, senders MUST use all header blocks mandated by the WS-Addressing specification and MUST follow all applicable WS-Addressing normative requirements.</add> An endpoint MAY generate output messages containing WS-Addressing headers, <add>however, if a message including WS-Addressing header blocks is sent to the endpoint, any related messages sent by the endpoint MUST also contain WS-Addressing headers in accordance to WS-Addressing</add>. 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.
Received on Tuesday, 27 September 2005 23:40:59 UTC