2002/ws/desc/wsdl20 wsdl20-bindings.xml,1.84,1.85

Update of /sources/public/2002/ws/desc/wsdl20
In directory homer:/tmp/cvs-serv19448

Modified Files:
	wsdl20-bindings.xml 
Log Message:
Implemented proposal (c) of:
http://lists.w3.org/Archives/Public/www-ws-desc/2004Jun/0210.html

Fixed examples (http:operation -> operation, etc.)
Added HTTP headers in location example #2
s/xsd/xs/
Removed xsi


Index: wsdl20-bindings.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-bindings.xml,v
retrieving revision 1.84
retrieving revision 1.85
diff -C2 -d -r1.84 -r1.85
*** wsdl20-bindings.xml	26 Jul 2004 10:33:49 -0000	1.84
--- wsdl20-bindings.xml	26 Jul 2004 10:51:05 -0000	1.85
***************
*** 166,170 ****
  	    </tr>
              <tr>
!               <td rowspan="1" colspan="1">xsd</td>
                <td rowspan="1" colspan="1">
                  <attval>http://www.w3.org/2001/XMLSchema</attval>
--- 166,170 ----
  	    </tr>
              <tr>
!               <td rowspan="1" colspan="1">xs</td>
                <td rowspan="1" colspan="1">
                  <attval>http://www.w3.org/2001/XMLSchema</attval>
***************
*** 173,184 ****
            specification <bibref ref="XMLSchemaP1"/>, <bibref ref="XMLSchemaP2"/>.</td>
              </tr>
-             <tr>
-               <td rowspan="1" colspan="1">xsi</td>
-               <td rowspan="1" colspan="1">
-                 <attval>http://www.w3.org/2001/XMLSchema-instance</attval>
-               </td>
-               <td rowspan="1" colspan="1">Defined in the W3C XML Schema
-           specification <bibref ref="XMLSchemaP1"/>, <bibref ref="XMLSchemaP2"/>.</td>
-             </tr>
            </tbody>
          </table>
--- 173,176 ----
***************
*** 1768,1774 ****
  	    with the following <el>operation</el> element
  	  </p>
!             <eg xml:space="preserve">&lt;http:operation
!     location='temperature/{town}'
!     method='GET' /&gt;</eg>
              <p>
  	    will serialize the message in the URI as follow:
--- 1760,1766 ----
  	    with the following <el>operation</el> element
  	  </p>
!             <eg xml:space="preserve">&lt;operation
!     http:location='temperature/{town}'
!     http:method='GET' /&gt;</eg>
              <p>
  	    will serialize the message in the URI as follow:
***************
*** 1907,1914 ****
  	    with the following <el>operation</el> element:
  	  </p>
!             <eg xml:space="preserve">&lt;http:operation
!     inputSerialization='application/x-www-form-urlencoded'
!     location='temperature/{town/}'
!     method='POST' /&gt;</eg>
              <p>
  	    will serialize the message in the URI as follow:
--- 1899,1906 ----
  	    with the following <el>operation</el> element:
  	  </p>
!             <eg xml:space="preserve">&lt;operation
!     http:inputSerialization='application/x-www-form-urlencoded'
!     http:location='temperature/{town/}'
!     http:method='POST' /&gt;</eg>
              <p>
  	    will serialize the message in the URI as follow:
***************
*** 1916,1924 ****
              <eg xml:space="preserve">temperature/Fr%C3%A9jus</eg>
              <p>
! 	      and in the <code>application/xml</code> message body
! 	      as follow:
  	    </p>
  
!             <eg xml:space="preserve">&lt;data&gt;
    &lt;date&gt;2004-01-16&lt;/date&gt;
    &lt;unit&gt;C&lt;/unit&gt;
--- 1908,1918 ----
              <eg xml:space="preserve">temperature/Fr%C3%A9jus</eg>
              <p>
! 	      and in the message as follow:
  	    </p>
  
!             <eg xml:space="preserve">Content-Type: application/xml; charset="utf-8"
! Content-Length: xxx
! 
! &lt;data&gt;
    &lt;date&gt;2004-01-16&lt;/date&gt;
    &lt;unit&gt;C&lt;/unit&gt;
***************
*** 1984,1989 ****
                      <code>application/octet-stream</code> if the element
  		  is of type 
! 		  <code>xsd:base64Binary</code>,
! 		  <code>xsd:hexBinary</code>, or a derived type;
  		</p>
                  </item>
--- 1978,1983 ----
                      <code>application/octet-stream</code> if the element
  		  is of type 
! 		  <code>xs:base64Binary</code>,
! 		  <code>xs:hexBinary</code>, or a derived type;
  		</p>
                  </item>
***************
*** 1999,2004 ****
              <item>
                <p>
! 	      If the type is <code>xsd:base64Binary</code>,
! 	      <code>xsd:hexBinary</code>, <code>xsd:anySimpleType</code>
  	      or a derived type, the content of the part is the content
  	      of the element. If the type is a complex type, the element
--- 1993,1998 ----
              <item>
                <p>
! 	      If the type is <code>xs:base64Binary</code>,
! 	      <code>xs:hexBinary</code>, <code>xs:anySimpleType</code>
  	      or a derived type, the content of the part is the content
  	      of the element. If the type is a complex type, the element
***************
*** 2121,2127 ****
  	      If the children elements of the input sequence are
  	      defined using an XML Schema type, they MUST derive from
! 	      <code>xsd:simpleType</code>, and MUST NOT derive from
! 	      <code>xsd:hexBinary</code> or
! 	      <code>xsd:base64Binary</code>.
  	    </p>
              </item>
--- 2115,2122 ----
  	      If the children elements of the input sequence are
  	      defined using an XML Schema type, they MUST derive from
! 	      <code>xs:simpleType</code>, and MUST NOT be of the type
! 	      or derive from <code>xs:QName</code>,
! 	      <code>xs:NOTATION</code>, <code>xs:hexBinary</code> or
! 	      <code>xs:base64Binary</code>.
  	    </p>
              </item>
***************
*** 2801,2804 ****
--- 2796,2805 ----
  -->
  <tr>
+  <td>20040726</td>
+  <td>HH</td>
+  <td>Restricted URI style with regards to QNames and added trailing /
+  in URL-encoded syntax</td>
+ </tr>
+ <tr>
   <td>20040723</td>
   <td>HH</td>

Received on Monday, 26 July 2004 06:51:08 UTC