2004/ws/addressing ws-addr-soap.xml,1.113,1.114

Update of /sources/public/2004/ws/addressing
In directory hutz:/tmp/cvs-serv11893

Modified Files:
	ws-addr-soap.xml 
Log Message:
Added definition of term 'response endpoint'

Index: ws-addr-soap.xml
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-soap.xml,v
retrieving revision 1.113
retrieving revision 1.114
diff -C2 -d -r1.113 -r1.114
*** ws-addr-soap.xml	2 Mar 2006 08:51:45 -0000	1.113
--- ws-addr-soap.xml	2 Mar 2006 10:14:49 -0000	1.114
***************
*** 435,438 ****
--- 435,440 ----
      <div1 id="addressesinsoap">
        <head>Addresses in SOAP</head>
+       <p> In the following text, the term 'response endpoint' refers to the [reply endpoint]
+         and [fault endpoint] message addressing properties collectively.</p>
        <div2 id="anonaddress">
          <head>Use of Anonymous Address in SOAP</head>
***************
*** 441,451 ****
          <div3>
            <head>SOAP 1.1/HTTP</head>
!           <p>When "&nsuri;/anonymous" is specified for the [reply
!             endpoint] property then there is no change to the SOAP 1.1/ HTTP binding. </p>
          </div3>
          <div3>
            <head>SOAP 1.2</head>
!           <p>When "&nsuri;/anonymous" is specified for the [reply
!             endpoint] property and the message is the request part of a SOAP request-response MEP [<bibref
                ref="SOAP12-PART2"/>], then any response MUST be the response part of the same SOAP
              request-response MEP [<bibref ref="SOAP12-PART2"/>].</p>
--- 443,453 ----
          <div3>
            <head>SOAP 1.1/HTTP</head>
!           <p>When "&nsuri;/anonymous" is specified for the response
!             endpoint then there is no change to the SOAP 1.1/ HTTP binding. </p>
          </div3>
          <div3>
            <head>SOAP 1.2</head>
!           <p>When "&nsuri;/anonymous" is specified for the response
!             endpoint and the message is the request part of a SOAP request-response MEP [<bibref
                ref="SOAP12-PART2"/>], then any response MUST be the response part of the same SOAP
              request-response MEP [<bibref ref="SOAP12-PART2"/>].</p>
***************
*** 456,461 ****
          <div3>
            <head>SOAP 1.1/HTTP</head>
!           <p>When "&nsuri;/anonymous" is not specified for the [reply
!             endpoint] property, then the message SHOULD be part of a binding that supports not returning a SOAP envelope in the HTTP response. Any
              response message SHOULD be sent using a separate connection and using the address value
              specified by response endpoint. Note that other specifications MAY define special URIs
--- 458,463 ----
          <div3>
            <head>SOAP 1.1/HTTP</head>
!           <p>When "&nsuri;/anonymous" is not specified for the response
!             endpoint, then the message SHOULD be part of a binding that supports not returning a SOAP envelope in the HTTP response. Any
              response message SHOULD be sent using a separate connection and using the address value
              specified by response endpoint. Note that other specifications MAY define special URIs
***************
*** 469,474 ****
          <div3>
            <head>SOAP 1.2</head>
!           <p>When "&nsuri;/anonymous" is not specified for the [reply
!             endpoint] property, then any response SHOULD not be the response part of the same SOAP
              request-response MEP [<bibref ref="SOAP12-PART2"/>]. For instance, a SOAP 1.2 HTTP
              binding that supports a one-way MEP could put the reply message in a separate one-way
--- 471,476 ----
          <div3>
            <head>SOAP 1.2</head>
!           <p>When "&nsuri;/anonymous" is not specified for the response
!             endpoint, then any response SHOULD not be the response part of the same SOAP
              request-response MEP [<bibref ref="SOAP12-PART2"/>]. For instance, a SOAP 1.2 HTTP
              binding that supports a one-way MEP could put the reply message in a separate one-way

Received on Thursday, 2 March 2006 10:14:56 UTC