W3C home > Mailing lists > Public > public-ws-addressing-eds@w3.org > January to March 2006

2004/ws/addressing ws-addr-core.xml,1.134,1.135 ws-addr-soap.xml,1.125,1.126

From: Marc Hadley via cvs-syncmail <cvsmail@w3.org>
Date: Mon, 13 Mar 2006 14:45:53 +0000
To: public-ws-addressing-eds@w3.org
Message-Id: <E1FIoIz-0008Ei-Iz@lionel-hutz.w3.org>

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

Modified Files:
	ws-addr-core.xml ws-addr-soap.xml 
Log Message:
Added editorial fixes from Hugo

Index: ws-addr-core.xml
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-core.xml,v
retrieving revision 1.134
retrieving revision 1.135
diff -C2 -d -r1.134 -r1.135
*** ws-addr-core.xml	10 Mar 2006 19:00:14 -0000	1.134
--- ws-addr-core.xml	13 Mar 2006 14:45:51 -0000	1.135
***************
*** 249,253 ****
                                              The precise meaning of this URI is defined by the binding of 
                                              Addressing to a specific protocol and/or the context in
!                                             which the EPR is used and/or the context in which the EPR is used.</td>
                                      </tr>
                                      <tr>
--- 249,253 ----
                                              The precise meaning of this URI is defined by the binding of 
                                              Addressing to a specific protocol and/or the context in
!                                             which the EPR is used.</td>
                                      </tr>
                                      <tr>
***************
*** 467,471 ****
              <div2 id="resourceidentification">
                  <head>Identifying Resources in an Endpoint Reference</head>
!                 <p>The Architecture of the World Wide Web, Volume One <bibref ref="AoWWW"/>
                      recommends [<bibref ref="AoWWW"/>, Section 2] the use of URIs to identify
                      resources. Using abstract properties of an EPR other than [destination] to
--- 467,471 ----
              <div2 id="resourceidentification">
                  <head>Identifying Resources in an Endpoint Reference</head>
!                 <p>The Architecture of the World Wide Web, Volume One [<bibref ref="AoWWW"/>]
                      recommends [<bibref ref="AoWWW"/>, Section 2] the use of URIs to identify
                      resources. Using abstract properties of an EPR other than [destination] to
***************
*** 603,607 ****
                      and the verb or intent of the message respectively. The values of these
                      properties can be used to facilitate the dispatch of messages.</p>
!                 <p>A binding of WS_Addressing message addressing properties MUST reflect the
                      property cardinality shown above. &wsa-soap.title;[<bibref ref="WSADDR-SOAP"
                      />] defines such a binding for the SOAP [<bibref ref="SOAP12-PART1"/>, <bibref
--- 603,607 ----
                      and the verb or intent of the message respectively. The values of these
                      properties can be used to facilitate the dispatch of messages.</p>
!                 <p>A binding of WS-Addressing message addressing properties MUST reflect the
                      property cardinality shown above. &wsa-soap.title;[<bibref ref="WSADDR-SOAP"
                      />] defines such a binding for the SOAP [<bibref ref="SOAP12-PART1"/>, <bibref

Index: ws-addr-soap.xml
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-soap.xml,v
retrieving revision 1.125
retrieving revision 1.126
diff -C2 -d -r1.125 -r1.126
*** ws-addr-soap.xml	10 Mar 2006 19:01:08 -0000	1.125
--- ws-addr-soap.xml	13 Mar 2006 14:45:51 -0000	1.126
***************
*** 465,477 ****
            <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
              that have other behaviours (similar to the anonymous URI).</p>
-           <ednote>
-             <edtext>See, e.g., the one-way/request-optional-response SOAP 1.1/HTTP MEP note as
-               per <xspecref href="http://lists.w3.org/Archives/Public/public-ws-addressing/2006Feb/0107.html">David Orchard's draft.</xspecref>
-             </edtext>
-           </ednote>
          </div3>
          <div3>
--- 465,473 ----
            <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 (e.g. see [<bibref ref="SOAP11-ROR"/>]). 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
              that have other behaviours (similar to the anonymous URI).</p>
          </div3>
          <div3>
***************
*** 898,902 ****
            the SOAP message using an X.509 certificate for the domain addressed by the [address] of
            the EPR. If the certificate is issued by a certificate authority trusted by the receiver
!           of the message then the receiver can can have some level of confidence that the message
            sender has authority to represent the [address] of the EPR.</p>
        </div2>
--- 894,898 ----
            the SOAP message using an X.509 certificate for the domain addressed by the [address] of
            the EPR. If the certificate is issued by a certificate authority trusted by the receiver
!           of the message then the receiver can have some level of confidence that the message
            sender has authority to represent the [address] of the EPR.</p>
        </div2>
***************
*** 1041,1045 ****
  		  href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf"
  		  ><titleref>Web Services Security: SOAP Message Security 1.0 (WS-Security 2004)</titleref>, A. Nadalin, C. Kaler, P. Hallam-Baker, R. Monzillo, Editors. OASIS Standard, OASIS,
! 	    March 2004.</bibl>
        </blist>
      </div1>
--- 1037,1051 ----
  		  href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf"
  		  ><titleref>Web Services Security: SOAP Message Security 1.0 (WS-Security 2004)</titleref>, A. Nadalin, C. Kaler, P. Hallam-Baker, R. Monzillo, Editors. OASIS Standard, OASIS,
! 	      March 2004.</bibl>
!         <bibl id="SOAP11-ROR" key="SOAP 1.1 Request Optional Response HTTP Binding" 
!           href="http://www.w3.org/2002/ws/addr/6/03/drafts/NOTE-soap11-ror-httpbinding-20060399/">
!           <titleref>SOAP 1.1 Request Optional Response HTTP Binding</titleref>, D. Orchard, Editor.
!           W3C Note, World Wide Web Consortium, March 2006. This version of the "SOAP 1.1 Request
!           Optional Response HTTP Binding" is
!           http://www.w3.org/2002/ws/addr/6/03/drafts/NOTE-soap11-ror-httpbinding-20060399/. The <loc
!             href="http://www.w3.org/TR/soap11-ror-httpbinding">latest version of "SOAP 1.1 Request
!             Optional Response HTTP Binding"</loc> is available
!             http://www.w3.org/TR/soap11-ror-httpbinding.
!         </bibl>
        </blist>
      </div1>
Received on Monday, 13 March 2006 14:46:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:19:41 GMT