W3C home > Mailing lists > Public > public-ws-desc-eds@w3.org > October 2004

2002/ws/desc/wsdl20 wsdl20-bindings.xml,1.127,1.128

From: Hugo Haas <hugo@dev.w3.org>
Date: Wed, 27 Oct 2004 18:26:26 +0000
To: public-ws-desc-eds@w3.org
Message-ID: <E1CMsV8-0002wC-DU@lionel-hutz.w3.org>

Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv11252

Modified Files:
	wsdl20-bindings.xml 
Log Message:
LC45


Index: wsdl20-bindings.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-bindings.xml,v
retrieving revision 1.127
retrieving revision 1.128
diff -C2 -d -r1.127 -r1.128
*** wsdl20-bindings.xml	27 Oct 2004 18:16:32 -0000	1.127
--- wsdl20-bindings.xml	27 Oct 2004 18:26:24 -0000	1.128
***************
*** 1471,1483 ****
            <ulist>
              <item>
!               <p>{http location}, a <emph>wsdls:anyURI</emph>. The value of this property specifies a template
! 				for the relative portion of the request URI for an
! 				operation. This URI is combined with the base URI
! 				specified in the
!                 &endpoint-address-p; property of the endpoint element to form the
! 				full URI for the HTTP request to invoke the
! 				operation.   It MUST contain an absolute or a
! 	    relative URI, i.e. it MUST NOT include a fragment identifier
! 	    in the URI.
  	      </p>
  	      <p>If the resulting URI uses the <code>https</code>
--- 1471,1489 ----
            <ulist>
              <item>
!               <p>{http location}, a <emph>wsdls:anyURI</emph>.  This
!               URI is combined with the base URI specified in the
!               &endpoint-address-p; property of the endpoint element to
!               form the full URI for the HTTP request to invoke the
!               operation. It MUST contain an absolute or a relative
!               URI, i.e. it MUST NOT include a fragment identifier in
!               the URI. Input serializations may define additional
!               processing rules to be applied to the value of {http
!               location} before combining it with the
!               &endpoint-address-p; property of the endpoint element to
!               form the HTTP request URI. For example, the
!               application/x-www-form-urlencoded serialization defined
!               in section <specref ref='_http_x-www-form-urlencoded'/>
!               defines a syntax to use the {http location} as a
!               template using element of the instance data.
  	      </p>
  	      <p>If the resulting URI uses the <code>https</code>
***************
*** 1981,1984 ****
--- 1987,1997 ----
  	  </p>
            </note>
+ 
+ 	  <p>In this serialization, the value of the {http location}
+ 	  property is used as a template which is combined with the
+ 	  &endpoint-address-p; property of the endpoint element to
+ 	  form the full URI to be used in an HTTP request, as
+ 	  specified in section <specref ref="http-operation-decl-relate"/>.</p>
+ 
            <div4 id="_http_operation_location_cited_get">
              <head>Case of elements cited in the {http location}
***************
*** 2867,2870 ****
--- 2880,2889 ----
   <td>HH</td>
   <td><loc
+ 	 href='http://www.w3.org/2002/ws/desc/4/lc-issues/issues.html#LC45'>LC45</loc>: {http location} may or may not be a template</td>
+ </tr>
+ <tr>
+  <td>20041027</td>
+  <td>HH</td>
+  <td><loc
  	 href='http://www.w3.org/2002/ws/desc/4/lc-issues/issues.html#LC44'>LC44</loc>: URL serialization expressed in terms of the component model</td>
  </tr>
Received on Wednesday, 27 October 2004 18:26:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.2 : Wednesday, 27 October 2004 18:26:26 GMT