- From: Hugo Haas <hugo@dev.w3.org>
- Date: Fri, 23 Jul 2004 10:40:16 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory homer:/tmp/cvs-serv18150
Modified Files:
wsdl20-bindings.xml
Log Message:
Issue 246:
- limited MEP for HTTP binding
- simplified table 3-2; I now feel that people won't be confused by it
Index: wsdl20-bindings.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-bindings.xml,v
retrieving revision 1.77
retrieving revision 1.78
diff -C2 -d -r1.77 -r1.78
*** wsdl20-bindings.xml 23 Jul 2004 09:58:56 -0000 1.77
--- wsdl20-bindings.xml 23 Jul 2004 10:40:14 -0000 1.78
***************
*** 246,250 ****
component.</p>
! <p>A subset of the HTTP properties specified in the HTTP Binding
defined in section <specref ref="http-binding"/> may be
expressed in a SOAP binding when the SOAP binding uses HTTP as
--- 246,250 ----
component.</p>
! <p>A subset of the HTTP properties specified in the HTTP binding
defined in section <specref ref="http-binding"/> may be
expressed in a SOAP binding when the SOAP binding uses HTTP as
***************
*** 427,431 ****
<attval>http://www.w3.org/2003/05/soap/mep/soap-response/</attval>
then the URI to execute the HTTP GET against MUST be
! generated using the HTTP Binding's rules for generating a
URI for HTTP GET (see <specref
ref="http-binding"/>). The input serialization format of
--- 427,431 ----
<attval>http://www.w3.org/2003/05/soap/mep/soap-response/</attval>
then the URI to execute the HTTP GET against MUST be
! generated using the HTTP binding's rules for generating a
URI for HTTP GET (see <specref
ref="http-binding"/>). The input serialization format of
***************
*** 468,472 ****
<p>The SOAP binding defined by this specification supports
! the SOAP HTTP Binding defined by the <bibref
ref="SOAP12-PART2"/> specification. This is indicated by
assigning the URI
--- 468,472 ----
<p>The SOAP binding defined by this specification supports
! the SOAP HTTP binding defined by the <bibref
ref="SOAP12-PART2"/> specification. This is indicated by
assigning the URI
***************
*** 1021,1026 ****
<bibref ref="WSDL-PART1"/> to enable Web Services applications to use
HTTP 1.1 <bibref ref="RFC2616"/> and HTTPS <bibref ref="RFC2818"/>. This binding extends WSDL 2.0
! by adding properties to the component model defined in <bibref ref="WSDL-PART1"/> at two places: to the Binding component and to the
! Service Endpoint component. In addition an XML Infoset representation
for these additional properties is provided, along with a mapping from
that representation to the various component properties.</p>
--- 1021,1025 ----
<bibref ref="WSDL-PART1"/> to enable Web Services applications to use
HTTP 1.1 <bibref ref="RFC2616"/> and HTTPS <bibref ref="RFC2818"/>. This binding extends WSDL 2.0
! by adding properties to the component model defined in <bibref ref="WSDL-PART1"/>. In addition an XML Infoset representation
for these additional properties is provided, along with a mapping from
that representation to the various component properties.</p>
***************
*** 1170,1174 ****
<p>Section <specref ref="_http_serialization"/> defines
! serialization formats supported by this binding.</p>
</item>
--- 1169,1174 ----
<p>Section <specref ref="_http_serialization"/> defines
! serialization formats supported by this binding along with
! their constraints.</p>
</item>
***************
*** 1181,1197 ****
<table border="1" summary="The first column contains the value
! of the {http method} property. The second column contains the corresponding default for http:inputSerialization, and the third column the one for http:outputSerialization. The fourth column contains the HTTP method to be used, and the last two columns contain corresponding default values for the operation's message exchange pattern and URI style." id="method_value">
<caption>Default values for GET, POST, PUT and DELETE</caption>
<tbody>
<tr>
! <th rowspan="1" colspan="1">{http method}</th>
! <th rowspan="1" colspan="1">Default Input serialization</th>
! <th rowspan="1" colspan="1">Default Output serialization</th>
! <th rowspan="1" colspan="1">HTTP Method</th>
! <th rowspan="1" colspan="1">Message Patterns</th>
! <th rowspan="1" colspan="1">Operation Style</th>
</tr>
<tr>
! <td rowspan="1" colspan="1">"GET"</td>
<td rowspan="1" colspan="1">
<code>application/x-www-form-urlencoded</code>
--- 1181,1196 ----
<table border="1" summary="The first column contains the value
! of the {http method} property. The second column contains the corresponding default for http:inputSerialization, and the third column the one for http:outputSerialization. The fourth column contains the HTTP method to be used, and the last column contains corresponding default values for the operation style." id="method_value">
<caption>Default values for GET, POST, PUT and DELETE</caption>
<tbody>
<tr>
! <th rowspan="1" colspan="1"><p>HTTP Method</p><p>{http method}</p></th>
! <th rowspan="1" colspan="1"><p>Default Input serialization</p>
! <p>{http input serialization}</p></th>
! <th rowspan="1" colspan="1"><p>Default Output serialization</p>
! <p>{http output serialization}</p></th>
</tr>
<tr>
! <td rowspan="1" colspan="1">GET</td>
<td rowspan="1" colspan="1">
<code>application/x-www-form-urlencoded</code>
***************
*** 1200,1209 ****
<code>application/xml</code>
</td>
- <td rowspan="1" colspan="1">HTTP GET</td>
- <td rowspan="1" colspan="1">In-Only, Robust In-Only, In-Out</td>
- <td rowspan="1" colspan="1">URI Style (see <specref ref="_operation_uri_style"/>)</td>
</tr>
<tr>
! <td rowspan="1" colspan="1">"POST"</td>
<td rowspan="1" colspan="1">
<code>application/xml</code>
--- 1199,1205 ----
<code>application/xml</code>
</td>
</tr>
<tr>
! <td rowspan="1" colspan="1">POST</td>
<td rowspan="1" colspan="1">
<code>application/xml</code>
***************
*** 1212,1241 ****
<code>application/xml</code>
</td>
- <td rowspan="1" colspan="1">HTTP POST</td>
- <td rowspan="1" colspan="1">In-Only, Robust In-Only, In-Out</td>
- <td rowspan="1" colspan="1">any</td>
</tr>
<tr>
! <td rowspan="1" colspan="1">"PUT"</td>
<td rowspan="1" colspan="1">
<code>application/xml</code>
</td>
<td rowspan="1" colspan="1"><code>application/xml</code></td>
- <td rowspan="1" colspan="1">HTTP PUT</td>
- <td rowspan="1" colspan="1">In-Only, Robust In-Only, In-Out</td>
- <td rowspan="1" colspan="1">any</td>
</tr>
<tr>
! <td rowspan="1" colspan="1">"DELETE"</td>
<td rowspan="1" colspan="1">
<code>application/x-www-form-urlencoded</code>
</td>
<td rowspan="1" colspan="1"><code>application/xml</code></td>
- <td rowspan="1" colspan="1">HTTP DELETE</td>
- <td rowspan="1" colspan="1">In-Only, Robust In-Only, In-Out</td>
- <td rowspan="1" colspan="1">URI Style (see <specref ref="_operation_uri_style"/>)</td>
</tr>
</tbody>
</table>
<p>The default vales for the {http input serialization} and
{http output serialization} properties for any other {http
--- 1208,1235 ----
<code>application/xml</code>
</td>
</tr>
<tr>
! <td rowspan="1" colspan="1">PUT</td>
<td rowspan="1" colspan="1">
<code>application/xml</code>
</td>
<td rowspan="1" colspan="1"><code>application/xml</code></td>
</tr>
<tr>
! <td rowspan="1" colspan="1">DELETE</td>
<td rowspan="1" colspan="1">
<code>application/x-www-form-urlencoded</code>
</td>
<td rowspan="1" colspan="1"><code>application/xml</code></td>
</tr>
</tbody>
</table>
+
+ <note id="operation-style-default"><p>The
+ <code>application/x-www-form-urlencoded</code> serialization
+ format places constraints on the stype of the interface
+ operation bound (see <specref
+ ref="_http_x-www-form-urlencoded"/>).</p></note>
+
<p>The default vales for the {http input serialization} and
{http output serialization} properties for any other {http
***************
*** 1409,1414 ****
<div3 id="http-operation-decl-dest">
<head>Description</head>
! <p>For every Binding operation component, this binding
! specification allows the user to indicate:@@@</p>
</div3>
<div3 id="http-operation-decl-relate">
--- 1403,1419 ----
<div3 id="http-operation-decl-dest">
<head>Description</head>
!
! <p>This binding specification provides a binding to HTTP of
! Interface Operation components whose
! &interface_operation-message_exchange_pattern-p; property
! has the value '&wsdl-mep-in-only;',
! '&wsdl-mep-robust-in-only;' or '&wsdl-mep-in-out;'.</p>
!
! <p>For every Binding operation component corresponding to
! such Interface Operation components, this binding
! specification allows the user to indicate the HTTP method to
! use, the input, output and fault serialization, and the
! location of the bound operation.</p>
!
</div3>
<div3 id="http-operation-decl-relate">
***************
*** 1793,1797 ****
</p>
<p>
! The URI style may only be used for Interface Operation
components whose &interface_operation-message_exchange_pattern-p; property has the
value '&wsdl-mep-in-only;', '&wsdl-mep-robust-in-only;' or
--- 1798,1802 ----
</p>
<p>
! The Multipart style may only be used for Interface Operation
components whose &interface_operation-message_exchange_pattern-p; property has the
value '&wsdl-mep-in-only;', '&wsdl-mep-robust-in-only;' or
***************
*** 2697,2700 ****
--- 2702,2710 ----
<td>20040723</td>
<td>HH</td>
+ <td>Addressed issue 246: limited MEP to In-Out, In-Only and Robust In-Only</td>
+ </tr>
+ <tr>
+ <td>20040723</td>
+ <td>HH</td>
<td>Addressed issue 226.</td>
</tr>
Received on Friday, 23 July 2004 06:40:30 UTC