- From: Hugo Haas <hugo@dev.w3.org>
- Date: Mon, 26 Jul 2004 11:35:22 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory homer:/tmp/cvs-serv30632
Modified Files:
wsdl20-bindings.html
Log Message:
Regenerated from XML
Index: wsdl20-bindings.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-bindings.html,v
retrieving revision 1.50
retrieving revision 1.51
diff -C2 -d -r1.50 -r1.51
*** wsdl20-bindings.html 23 Jul 2004 10:46:46 -0000 1.50
--- wsdl20-bindings.html 26 Jul 2004 11:35:20 -0000 1.51
***************
*** 263,290 ****
"#http-fault-decl-mapping">Mapping Between Component Properties and
XML Representation</a><br />
! 3.8 <a href="#_operation_styles">Operation
! Styles</a><br />
! 3.8.1 <a href=
! "#_operation_uri_style">URI Style</a><br />
! 3.8.2 <a href=
! "#_operation_multipart_style">Multipart style</a><br />
! 3.9 <a href=
"#_http_serialization">Serialization format of instance
data</a><br />
! 3.9.1 <a href=
"#_http_x-www-form-urlencoded">Serialization as
application/x-www-form-urlencoded</a><br />
! 3.9.1.1
<a href="#_http_operation_location_cited_get">Case of elements
cited in location attribute</a><br />
! 3.9.1.2
<a href="#_http_operation_location_notcited_get">Case elements NOT
cited in location attribute</a><br />
! 3.9.2 <a href=
"#_http_operation_xml_encoding">Serialization as
application/xml</a><br />
! 3.9.3 <a href=
"#_http_operation_multipart_encoding">Serialization as
multipart/form-data</a><br />
3.10 <a href=
"#http-transfer-coding-decl">Specifying the transfer
--- 263,296 ----
"#http-fault-decl-mapping">Mapping Between Component Properties and
XML Representation</a><br />
! 3.8 <a href=
"#_http_serialization">Serialization format of instance
data</a><br />
! 3.8.1 <a href=
"#_http_x-www-form-urlencoded">Serialization as
application/x-www-form-urlencoded</a><br />
! 3.8.1.1
<a href="#_http_operation_location_cited_get">Case of elements
cited in location attribute</a><br />
! 3.8.1.2
<a href="#_http_operation_location_notcited_get">Case elements NOT
cited in location attribute</a><br />
! 3.8.1.2.1
! <a href="#_http_operation_location_notcited_uri">Serialization in
! the request URI</a><br />
! 3.8.1.2.2
! <a href="#_http_operation_location_notcited_body">Serialization in
! the message body</a><br />
! 3.8.2 <a href=
"#_http_operation_xml_encoding">Serialization as
application/xml</a><br />
! 3.8.3 <a href=
"#_http_operation_multipart_encoding">Serialization as
multipart/form-data</a><br />
+ 3.9 <a href="#_operation_styles">Operation
+ Styles</a><br />
+ 3.9.1 <a href=
+ "#_operation_uri_style">URI Style</a><br />
+ 3.9.2 <a href=
+ "#_operation_multipart_style">Multipart style</a><br />
3.10 <a href=
"#http-transfer-coding-decl">Specifying the transfer
***************
*** 433,437 ****
</tr>
<tr>
! <td rowspan="1" colspan="1">xsd</td>
<td rowspan="1" colspan="1">"http://www.w3.org/2001/XMLSchema"</td>
<td rowspan="1" colspan="1">Defined in the W3C XML Schema
--- 439,443 ----
</tr>
<tr>
! <td rowspan="1" colspan="1">xs</td>
<td rowspan="1" colspan="1">"http://www.w3.org/2001/XMLSchema"</td>
<td rowspan="1" colspan="1">Defined in the W3C XML Schema
***************
*** 440,452 ****
Datatypes</a></cite>].</td>
</tr>
- <tr>
- <td rowspan="1" colspan="1">xsi</td>
- <td rowspan="1" colspan="1">
- "http://www.w3.org/2001/XMLSchema-instance"</td>
- <td rowspan="1" colspan="1">Defined in the W3C XML Schema
- specification [<cite><a href="#XMLSchemaP1">XML Schema
- Structures</a></cite>], [<cite><a href="#XMLSchemaP2">XML Schema
- Datatypes</a></cite>].</td>
- </tr>
</tbody>
</table>
--- 446,449 ----
***************
*** 1365,1372 ****
<operation ref="<em>xs:QName</em>"
<b>http:location</b>="<em>xs:anyURI</em>"?
! <b>http:method</b>="<em>xs:anyURI</em>"?
! <b>http:inputSerialization</b>="<em>xs:anyURI</em>"?
! <b>http:outputSerialization</b>="<em>xs:anyURI</em>"?
! <b>http:faultSerialization</b>="<em>xs:anyURI</em>"?
<b>http:defaultTransferCoding</b>="<em>xs:string</em>"? >
<documentation />?
--- 1362,1369 ----
<operation ref="<em>xs:QName</em>"
<b>http:location</b>="<em>xs:anyURI</em>"?
! <b>http:method</b>="<em>xs:string</em>"?
! <b>http:inputSerialization</b>="<em>xs:string</em>"?
! <b>http:outputSerialization</b>="<em>xs:string</em>"?
! <b>http:faultSerialization</b>="<em>xs:string</em>"?
<b>http:defaultTransferCoding</b>="<em>xs:string</em>"? >
<documentation />?
***************
*** 1404,1407 ****
--- 1401,1412 ----
<ul>
<li>
+ <p><em>HTTP Method Declaration.</em> When formulating the HTTP
+ message to be transmitted, the HTTP request method MUST be what is
+ defined by the <code>http:method</code> attribute on
+ <code>operation</code> , or with the
+ <code>http:defaultMethod</code> attribute on <code>binding</code>
+ .</p>
+ </li>
+ <li>
<p><em>Payload construction.</em> When formulating the HTTP message
to be transmitted, the contents of the payload (i.e. the contents
***************
*** 1433,1444 ****
</li>
<li>
- <p><em>HTTP Method Declaration.</em> When formulating the HTTP
- message to be transmitted, the HTTP request method MUST be what is
- defined by the <code>http:method</code> attribute on
- <code>operation</code> , or with the
- <code>http:defaultMethod</code> attribute on <code>binding</code>
- .</p>
- </li>
- <li>
<p><em>Serialization format.</em> The HTTP request serialization
format MUST be what is defined by the {http input serialization}
--- 1438,1441 ----
***************
*** 1447,1451 ****
serialization format of a fault MUST be what is defined by the
{http fault serialization} property.</p>
! <p>Section <a href="#_http_serialization"><b>3.9 Serialization
format of instance data</b></a> defines serialization formats
supported by this binding along with their constraints.</p>
--- 1444,1448 ----
serialization format of a fault MUST be what is defined by the
{http fault serialization} property.</p>
! <p>Section <a href="#_http_serialization"><b>3.8 Serialization
format of instance data</b></a> defines serialization formats
supported by this binding along with their constraints.</p>
***************
*** 1500,1504 ****
<p>The <code>application/x-www-form-urlencoded</code> serialization
format places constraints on the stype of the interface operation
! bound (see <a href="#_http_x-www-form-urlencoded"><b>3.9.1
Serialization as application/x-www-form-urlencoded</b></a> ).</p>
</div>
--- 1497,1501 ----
<p>The <code>application/x-www-form-urlencoded</code> serialization
format places constraints on the stype of the interface operation
! bound (see <a href="#_http_x-www-form-urlencoded"><b>3.8.1
Serialization as application/x-www-form-urlencoded</b></a> ).</p>
</div>
***************
*** 1516,1519 ****
--- 1513,1527 ----
1.2 Part 2: Adjuncts</a></cite>], Section 6.3).</p>
</li>
+ <li>
+ <p><em>Accept headers.</em> Standard HTTP accept headers (see
+ section 14 of [<cite><a href="#RFC2616">IETF RFC 2616</a></cite>])
+ MAY be used in an HTTP request. When constructing an HTTP
+ <code>Accept</code> header, the requester agent MAY take into
+ account the <code>expectedMediaType</code> information (see
+ [<cite><a href="#xmlbin-media-type">MTXML</a></cite>]) appearing on
+ an output message description to find out about the type of binary
+ element content which is expected to be sent by the provider
+ agent.</p>
+ </li>
</ul>
</div>
***************
*** 1727,1734 ****
<operation ref="<em>xs:QName</em>"
<b>http:location</b>="<em>xs:anyURI</em>"?
! <b>http:method</b>="<em>xs:anyURI</em>"?
! <b>http:inputSerialization</b>="<em>xs:anyURI</em>"?
! <b>http:outputSerialization</b>="<em>xs:anyURI</em>"?
! <b>http:faultSerialization</b>="<em>xs:anyURI</em>"? >
</operation>
</binding>
--- 1735,1742 ----
<operation ref="<em>xs:QName</em>"
<b>http:location</b>="<em>xs:anyURI</em>"?
! <b>http:method</b>="<em>xs:string</em>"?
! <b>http:inputSerialization</b>="<em>xs:string</em>"?
! <b>http:outputSerialization</b>="<em>xs:string</em>"?
! <b>http:faultSerialization</b>="<em>xs:string</em>"? >
</operation>
</binding>
***************
*** 1967,2087 ****
</div>
<div class="div2">
! <h3><a name="_operation_styles" id="_operation_styles"></a>3.8
! Operation Styles</h3>
! <p>This section defines operation styles in use in parallel to the
! HTTP 1.1 binding.</p>
! <div class="div3">
! <h4><a name="_operation_uri_style" id=
! "_operation_uri_style"></a>3.8.1 URI Style</h4>
! <p>The URI style is selected by assigning the Interface Operation
! component's <a href=
! "wsdl20.html#InterfaceOperation_details">{style}</a> property the
! value <em>http://www.w3.org/@@@@/@@/wsdl/style/uri</em>.</p>
! <p>The URI style may only be used for Interface Operation
! components whose <a href=
! "wsdl20.html#InterfaceOperation_details">{message exchange
! pattern}</a> property has the value
! 'http://www.w3.org/@@@@/@@/wsdl/in-only',
! 'http://www.w3.org/@@@@/@@/wsdl/robust-in-only' or
! 'http://www.w3.org/@@@@/@@/wsdl/in-out'.</p>
! <p>Use of this value indicates that XML Schema [<cite><a href=
! "#XMLSchemaP1">XML Schema Structures</a></cite>] was used to define
! the schemas of the <a href=
! "wsdl20.html#MessageReference_details#MessageReference_details">{element}</a>
! properties of all Message Reference components of the Interface
! Operation component with <a href=
! "wsdl20.html#MessageReference_details#MessageReference_details">{direction}</a>
! property <em>in</em>. Those schemas MUST adhere to the rules
! below.</p>
! <ul>
! <li>
! <p>The content model of input message elements are defined using a
! complex type that contains a sequence from XML Schema.</p>
! </li>
! <li>
! <p>The sequence MUST only contain elements. It MUST NOT contain
! other structures such as xs:choice.</p>
! </li>
! <li>
! <p>The sequence MUST contain only local element children. These
! child elements MAY contain the <code>nillable</code> attribute, and
! the attributes <code>minOccurs</code> and <code>maxOccurs</code>
! MUST have a value <code>0</code> or <code>1</code>.</p>
! </li>
! <li>
! <p>The localPart of input element's QName MUST be the same as the
! Interface operation component's name.</p>
! </li>
! <li>
! <p>The complex types that defines the body of an input element or
! its children elements MUST NOT contain any attributes.</p>
! </li>
! <li>
! <p>The input sequence MUST NOT contain multiple children element
! declared with the same local name.</p>
! </li>
! <li>
! <p>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>
! </li>
! </ul>
! </div>
! <div class="div3">
! <h4><a name="_operation_multipart_style" id=
! "_operation_multipart_style"></a>3.8.2 Multipart style</h4>
! <p>The Multipart style is selected by assigning the Interface
! Operation component's <a href=
! "wsdl20.html#InterfaceOperation_details">{style}</a> property the
! value <em>http://www.w3.org/@@@@/@@/wsdl/style/multipart</em>.</p>
! <p>The Multipart style may only be used for Interface Operation
! components whose <a href=
! "wsdl20.html#InterfaceOperation_details">{message exchange
! pattern}</a> property has the value
! 'http://www.w3.org/@@@@/@@/wsdl/in-only',
! 'http://www.w3.org/@@@@/@@/wsdl/robust-in-only' or
! 'http://www.w3.org/@@@@/@@/wsdl/in-out'.</p>
! <p>Use of this value indicates that XML Schema [<cite><a href=
! "#XMLSchemaP1">XML Schema Structures</a></cite>] was used to define
! the schemas of the <a href=
! "wsdl20.html#MessageReference_details#MessageReference_details">{element}</a>
! properties of all Message Reference components of the Interface
! Operation component with <a href=
! "wsdl20.html#MessageReference_details#MessageReference_details">{direction}</a>
! property <em>in</em>. Those schemas MUST adhere to the rules
! below.</p>
! <ul>
! <li>
! <p>The content model of input message elements are defined using a
! complex type that contains a sequence from XML Schema.</p>
! </li>
! <li>
! <p>The sequence MUST only contain elements. It MUST NOT contain
! other structures such as xs:choice.</p>
! </li>
! <li>
! <p>The sequence MUST contain only local element children. These
! child elements MAY contain the <code>nillable</code> attribute, and
! the attributes <code>minOccurs</code> and <code>maxOccurs</code>
! MUST have a value <code>1</code>.</p>
! </li>
! <li>
! <p>The localPart of input element's QName MUST be the same as the
! Interface operation component's name.</p>
! </li>
! <li>
! <p>The complex types that defines the body of an input element or
! its children elements MUST NOT contain any attributes.</p>
! </li>
! <li>
! <p>The input sequence MUST NOT contain multiple children element
! declared with the same local name.</p>
! </li>
! </ul>
! </div>
! </div>
! <div class="div2">
! <h3><a name="_http_serialization" id="_http_serialization"></a>3.9
Serialization format of instance data</h3>
<p>The following serialization formats can be used to encode the
--- 1975,1979 ----
</div>
<div class="div2">
! <h3><a name="_http_serialization" id="_http_serialization"></a>3.8
Serialization format of instance data</h3>
<p>The following serialization formats can be used to encode the
***************
*** 2089,2097 ****
corresponding to the input and output message, as well as the media
types and HTTP headers associated.</p>
! <p>Other serialization formats may be used. Those may place
restrictions on the style of the interface operation bound.</p>
<div class="div3">
<h4><a name="_http_x-www-form-urlencoded" id=
! "_http_x-www-form-urlencoded"></a>3.9.1 Serialization as
"application/x-www-form-urlencoded"</h4>
<p>This serialization format is designed to allow a Web Service to
--- 1981,1989 ----
corresponding to the input and output message, as well as the media
types and HTTP headers associated.</p>
! <p>Other serialization formats may be used. Those MAY place
restrictions on the style of the interface operation bound.</p>
<div class="div3">
<h4><a name="_http_x-www-form-urlencoded" id=
! "_http_x-www-form-urlencoded"></a>3.8.1 Serialization as
"application/x-www-form-urlencoded"</h4>
<p>This serialization format is designed to allow a Web Service to
***************
*** 2099,2103 ****
"#instance_data">instance data</a> of input messages. It may only
be used for interface operation using the URI Style format as
! defined in <a href="#_operation_uri_style"><b>3.8.1 URI
Style</b></a>.</p>
<p>Elements from the instance data can be inserted into the path of
--- 1991,1995 ----
"#instance_data">instance data</a> of input messages. It may only
be used for interface operation using the URI Style format as
! defined in <a href="#_operation_uri_style"><b>3.9.1 URI
Style</b></a>.</p>
<p>Elements from the instance data can be inserted into the path of
***************
*** 2107,2111 ****
<p class="exampleHead" style="text-align: left"><a name=
"urlencoded_example" id="urlencoded_example"></a><i><span>Example
! 3-1.</span> instance data serialized in a URI</i></p>
<p>The following instance data of an input message</p>
<div class="exampleInner">
--- 1999,2003 ----
<p class="exampleHead" style="text-align: left"><a name=
"urlencoded_example" id="urlencoded_example"></a><i><span>Example
! 3-1.</span> Instance data serialized in a URI</i></p>
<p>The following instance data of an input message</p>
<div class="exampleInner">
***************
*** 2120,2126 ****
<div class="exampleInner">
<pre>
! <http:operation
! location='temperature/{town}'
! method='get' />
</pre></div>
<p>will serialize the message in the URI as follow:</p>
--- 2012,2018 ----
<div class="exampleInner">
<pre>
! <operation
! http:location='temperature/{town}'
! http:method='GET' />
</pre></div>
<p>will serialize the message in the URI as follow:</p>
***************
*** 2141,2145 ****
<div class="div4">
<h5><a name="_http_operation_location_cited_get" id=
! "_http_operation_location_cited_get"></a>3.9.1.1 Case of elements
cited in <code>location</code> attribute</h5>
<table border="1" summary=
--- 2033,2037 ----
<div class="div4">
<h5><a name="_http_operation_location_cited_get" id=
! "_http_operation_location_cited_get"></a>3.8.1.1 Case of elements
cited in <code>location</code> attribute</h5>
<table border="1" summary=
***************
*** 2179,2195 ****
<p>An element MUST NOT be cited more than once within the
<code>location</code> <em>attribute information item</em>.</p>
<p>Strings enclosed within single curly braces MUST be element
names from the <a title="instance_data" href=
! "#instance_data">instance data</a> of the input message; any other
! strings enclosed within single curly braces are a fatal error.</p>
</div>
<div class="div4">
<h5><a name="_http_operation_location_notcited_get" id=
! "_http_operation_location_notcited_get"></a>3.9.1.2 Case elements
NOT cited in <code>location</code> attribute</h5>
<p>All elements of the <a title="instance_data" href=
"#instance_data">instance data</a> from the input message NOT cited
by the <code>location</code> <em>attribute information item</em>
! are serialized as query parameters appended to the request URI.</p>
<p>If the <code>location</code> attribute does not contain a '?'
(question mark) character, one is appended. If it does already
--- 2071,2106 ----
<p>An element MUST NOT be cited more than once within the
<code>location</code> <em>attribute information item</em>.</p>
+ <p>An element name MAY be followed by a slash (i.e. "/") inside
+ curly braces (e.g. location="temperature/{town/}") to indicate that
+ no other element must be serialized in the request URI (see
+ <a href="#_http_operation_location_notcited_get"><b>3.8.1.2 Case
+ elements NOT cited in location attribute</b></a>).</p>
<p>Strings enclosed within single curly braces MUST be element
names from the <a title="instance_data" href=
! "#instance_data">instance data</a> of the input message, possibly
! followed by a slash; any other strings enclosed within single curly
! braces are a fatal error.</p>
</div>
<div class="div4">
<h5><a name="_http_operation_location_notcited_get" id=
! "_http_operation_location_notcited_get"></a>3.8.1.2 Case elements
NOT cited in <code>location</code> attribute</h5>
+ <p>If an element name appears in the <code>location</code>
+ <em>attribute information item</em> followed by a slash, then other
+ elements must be serialized in the message body (see <a href=
+ "#_http_operation_location_notcited_body"><b>3.8.1.2.2
+ Serialization in the message body</b></a>), otherwise they must be
+ serialized as parameters in the request URI (see <a href=
+ "#_http_operation_location_notcited_uri"><b>3.8.1.2.1 Serialization
+ in the request URI</b></a>).</p>
+ <div class="div5">
+ <h6><a name="_http_operation_location_notcited_uri" id=
+ "_http_operation_location_notcited_uri"></a>3.8.1.2.1 Serialization
+ in the request URI</h6>
<p>All elements of the <a title="instance_data" href=
"#instance_data">instance data</a> from the input message NOT cited
by the <code>location</code> <em>attribute information item</em>
! are serialized as query parameters appended to the request URI
! (e.g. <a href="#urlencoded_example">Example 3-1</a>).</p>
<p>If the <code>location</code> attribute does not contain a '?'
(question mark) character, one is appended. If it does already
***************
*** 2212,2219 ****
</ul>
</div>
</div>
<div class="div3">
<h4><a name="_http_operation_xml_encoding" id=
! "_http_operation_xml_encoding"></a>3.9.2 Serialization as
"application/xml"</h4>
<p>The <a title="instance_data" href="#instance_data">instance
--- 2123,2189 ----
</ul>
</div>
+ <div class="div5">
+ <h6><a name="_http_operation_location_notcited_body" id=
+ "_http_operation_location_notcited_body"></a>3.8.1.2.2
+ Serialization in the message body</h6>
+ <p>All elements of the <a title="instance_data" href=
+ "#instance_data">instance data</a> from the input message NOT cited
+ by the <code>location</code> <em>attribute information item</em>
+ are serialized in the message body following the rules of the
+ "application/xml" (see <a href=
+ "#_http_operation_xml_encoding"><b>3.8.2 Serialization as
+ application/xml</b></a> ).</p>
+ <p>The <a title="instance_data" href="#instance_data">instance
+ data</a> serialized in the <a title="instance_data" href=
+ "#instance_data">instance data</a> of the input message with the
+ elements cited in the <code>location</code> <em>attribute
+ information item</em> removed.</p>
+ <div class="exampleOuter">
+ <p class="exampleHead" style="text-align: left"><a name=
+ "urlencoded_example_body" id=
+ "urlencoded_example_body"></a><i><span>Example 3-2.</span> Instance
+ data serialized in a URI and in a message body</i></p>
+ <p>The following instance data of an input message</p>
+ <div class="exampleInner">
+ <pre>
+ <data>
+ <town>Fréjus</town>
+ <date>2004-01-16</date>
+ <unit>C</unit>
+ <value>24</value>
+ </data>
+ </pre></div>
+ <p>with the following <code>operation</code> element:</p>
+ <div class="exampleInner">
+ <pre>
+ <operation
+ http:inputSerialization='application/x-www-form-urlencoded'
+ http:location='temperature/{town/}'
+ http:method='POST' />
+ </pre></div>
+ <p>will serialize the message in the URI as follow:</p>
+ <div class="exampleInner">
+ <pre>
+ temperature/Fr%C3%A9jus
+ </pre></div>
+ <p>and in the message as follow:</p>
+ <div class="exampleInner">
+ <pre>
+ Content-Type: application/xml
+ Content-Length: xxx
+
+ <data>
+ <date>2004-01-16</date>
+ <unit>C</unit>
+ <value>24</value>
+ </data>
+ </pre></div>
+ </div>
+ </div>
+ </div>
</div>
<div class="div3">
<h4><a name="_http_operation_xml_encoding" id=
! "_http_operation_xml_encoding"></a>3.8.2 Serialization as
"application/xml"</h4>
<p>The <a title="instance_data" href="#instance_data">instance
***************
*** 2230,2234 ****
<div class="div3">
<h4><a name="_http_operation_multipart_encoding" id=
! "_http_operation_multipart_encoding"></a>3.9.3 Serialization as
"multipart/form-data"</h4>
<p>This format is for legacy compatibility to permit the use of
--- 2200,2204 ----
<div class="div3">
<h4><a name="_http_operation_multipart_encoding" id=
! "_http_operation_multipart_encoding"></a>3.8.3 Serialization as
"multipart/form-data"</h4>
<p>This format is for legacy compatibility to permit the use of
***************
*** 2236,2240 ****
2387</a></cite>] servers. This serialization format may only be
used for interface operations using the Multipart Style format as
! defined in <a href="#_operation_multipart_style"><b>3.8.2 Multipart
style</b></a>.</p>
<p>Each element in the sequence is serialized into a part as
--- 2206,2210 ----
2387</a></cite>] servers. This serialization format may only be
used for interface operations using the Multipart Style format as
! defined in <a href="#_operation_multipart_style"><b>3.9.2 Multipart
style</b></a>.</p>
<p>Each element in the sequence is serialized into a part as
***************
*** 2256,2260 ****
<li>
<p><code>application/octet-stream</code> if the element is of type
! <code>xsd:base64Binary</code>, <code>xsd:hexBinary</code>, or a
derived type;</p>
</li>
--- 2226,2230 ----
<li>
<p><code>application/octet-stream</code> if the element is of type
! <code>xs:base64Binary</code>, <code>xs:hexBinary</code>, or a
derived type;</p>
</li>
***************
*** 2267,2276 ****
</li>
<li>
! <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 is serialized
following the rules defined in the <a href=
! "#_http_operation_xml_encoding"><b>3.9.2 Serialization as
application/xml</b></a> .</p>
</li>
--- 2237,2246 ----
</li>
<li>
! <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 is serialized
following the rules defined in the <a href=
! "#_http_operation_xml_encoding"><b>3.8.2 Serialization as
application/xml</b></a> .</p>
</li>
***************
*** 2278,2282 ****
<div class="exampleOuter">
<p class="exampleHead" style="text-align: left"><i><span>Example
! 3-2.</span> Example of multipart/form-data</i></p>
<p>The following instance data of an input message:</p>
<div class="exampleInner">
--- 2248,2252 ----
<div class="exampleOuter">
<p class="exampleHead" style="text-align: left"><i><span>Example
! 3-3.</span> Example of multipart/form-data</i></p>
<p>The following instance data of an input message:</p>
<div class="exampleInner">
***************
*** 2307,2313 ****
Content-Type: application/xml
<town>
! <name>Fréjus</name>
! <country>France</country>
! </town>
--AaB03x
Content-Disposition: form-data; name="date"
--- 2277,2283 ----
Content-Type: application/xml
<town>
! <name>Fréjus</name>
! <country>France</country>
! </town>
--AaB03x
Content-Disposition: form-data; name="date"
***************
*** 2320,2323 ****
--- 2290,2410 ----
</div>
<div class="div2">
+ <h3><a name="_operation_styles" id="_operation_styles"></a>3.9
+ Operation Styles</h3>
+ <p>This section defines operation styles in use in parallel to the
+ HTTP 1.1 binding.</p>
+ <div class="div3">
+ <h4><a name="_operation_uri_style" id=
+ "_operation_uri_style"></a>3.9.1 URI Style</h4>
+ <p>The URI style is selected by assigning the Interface Operation
+ component's <a href=
+ "wsdl20.html#InterfaceOperation_details">{style}</a> property the
+ value <em>http://www.w3.org/@@@@/@@/wsdl/style/uri</em>.</p>
+ <p>The URI style may only be used for Interface Operation
+ components whose <a href=
+ "wsdl20.html#InterfaceOperation_details">{message exchange
+ pattern}</a> property has the value
+ 'http://www.w3.org/@@@@/@@/wsdl/in-only',
+ 'http://www.w3.org/@@@@/@@/wsdl/robust-in-only' or
+ 'http://www.w3.org/@@@@/@@/wsdl/in-out'.</p>
+ <p>Use of this value indicates that XML Schema [<cite><a href=
+ "#XMLSchemaP1">XML Schema Structures</a></cite>] was used to define
+ the schemas of the <a href=
+ "wsdl20.html#MessageReference_details#MessageReference_details">{element}</a>
+ properties of all Message Reference components of the Interface
+ Operation component with <a href=
+ "wsdl20.html#MessageReference_details#MessageReference_details">{direction}</a>
+ property <em>in</em>. Those schemas MUST adhere to the rules
+ below.</p>
+ <ul>
+ <li>
+ <p>The content model of input message elements are defined using a
+ complex type that contains a sequence from XML Schema.</p>
+ </li>
+ <li>
+ <p>The sequence MUST only contain elements. It MUST NOT contain
+ other structures such as xs:choice.</p>
+ </li>
+ <li>
+ <p>The sequence MUST contain only local element children. These
+ child elements MAY contain the <code>nillable</code> attribute, and
+ the attributes <code>minOccurs</code> and <code>maxOccurs</code>
+ MUST have a value <code>0</code> or <code>1</code>.</p>
+ </li>
+ <li>
+ <p>The localPart of input element's QName MUST be the same as the
+ Interface operation component's name.</p>
+ </li>
+ <li>
+ <p>The complex types that defines the body of an input element or
+ its children elements MUST NOT contain any attributes.</p>
+ </li>
+ <li>
+ <p>The input sequence MUST NOT contain multiple children element
+ declared with the same local name.</p>
+ </li>
+ <li>
+ <p>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>
+ </li>
+ </ul>
+ </div>
+ <div class="div3">
+ <h4><a name="_operation_multipart_style" id=
+ "_operation_multipart_style"></a>3.9.2 Multipart style</h4>
+ <p>The Multipart style is selected by assigning the Interface
+ Operation component's <a href=
+ "wsdl20.html#InterfaceOperation_details">{style}</a> property the
+ value <em>http://www.w3.org/@@@@/@@/wsdl/style/multipart</em>.</p>
+ <p>The Multipart style may only be used for Interface Operation
+ components whose <a href=
+ "wsdl20.html#InterfaceOperation_details">{message exchange
+ pattern}</a> property has the value
+ 'http://www.w3.org/@@@@/@@/wsdl/in-only',
+ 'http://www.w3.org/@@@@/@@/wsdl/robust-in-only' or
+ 'http://www.w3.org/@@@@/@@/wsdl/in-out'.</p>
+ <p>Use of this value indicates that XML Schema [<cite><a href=
+ "#XMLSchemaP1">XML Schema Structures</a></cite>] was used to define
+ the schemas of the <a href=
+ "wsdl20.html#MessageReference_details#MessageReference_details">{element}</a>
+ properties of all Message Reference components of the Interface
+ Operation component with <a href=
+ "wsdl20.html#MessageReference_details#MessageReference_details">{direction}</a>
+ property <em>in</em>. Those schemas MUST adhere to the rules
+ below.</p>
+ <ul>
+ <li>
+ <p>The content model of input message elements are defined using a
+ complex type that contains a sequence from XML Schema.</p>
+ </li>
+ <li>
+ <p>The sequence MUST only contain elements. It MUST NOT contain
+ other structures such as xs:choice.</p>
+ </li>
+ <li>
+ <p>The sequence MUST contain only local element children. These
+ child elements MAY contain the <code>nillable</code> attribute, and
+ the attributes <code>minOccurs</code> and <code>maxOccurs</code>
+ MUST have a value <code>1</code>.</p>
+ </li>
+ <li>
+ <p>The localPart of input element's QName MUST be the same as the
+ Interface operation component's name.</p>
+ </li>
+ <li>
+ <p>The complex types that defines the body of an input element or
+ its children elements MUST NOT contain any attributes.</p>
+ </li>
+ <li>
+ <p>The input sequence MUST NOT contain multiple children element
+ declared with the same local name.</p>
+ </li>
+ </ul>
+ </div>
+ </div>
+ <div class="div2">
<h3><a name="http-transfer-coding-decl" id=
"http-transfer-coding-decl"></a>3.10 Specifying the transfer
***************
*** 2821,2824 ****
--- 2908,2920 ----
"Informative-References"></a>4.2 Informative References</h3>
<dl>
+ <dt class="label"><a name="xmlbin-media-type" id=
+ "xmlbin-media-type"></a>[MTXML]</dt>
+ <dd><cite><a href=
+ "http://www.w3.org/TR/2004/WD-xml-media-types-20040608/">Assigning
+ Media Types to Binary Data in XML</a></cite>, A. Karmarkar, Ü.
+ Yalçınalp, W3C Working Draft, 8 June 2004. The <a href=
+ "http://www.w3.org/TR/xml-media-types/">latest version of the
+ "Assigning Media Types to Binary Data in XML" document</a> is
+ available from http://www.w3.org/TR/xml-media-types/.</dd>
<dt class="label"><a name="WSDL-PART0" id="WSDL-PART0"></a>[WSDL
2.0 Primer]</dt>
***************
*** 2905,2908 ****
--- 3001,3010 ----
</tr>
<tr>
+ <td rowspan="1" colspan="1">20040726</td>
+ <td rowspan="1" colspan="1">HH</td>
+ <td rowspan="1" colspan="1">Restricted URI style with regards to
+ QNames and added trailing / in URL-encoded syntax</td>
+ </tr>
+ <tr>
<td rowspan="1" colspan="1">20040723</td>
<td rowspan="1" colspan="1">HH</td>
Received on Monday, 26 July 2004 07:35:23 UTC