- From: Hugo Haas <hugo@dev.w3.org>
- Date: Tue, 20 Jul 2004 14:31:55 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory homer:/tmp/cvs-serv9063
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.40
retrieving revision 1.41
diff -C2 -d -r1.40 -r1.41
*** wsdl20-bindings.html 20 Jul 2004 11:48:32 -0000 1.40
--- wsdl20-bindings.html 20 Jul 2004 14:31:52 -0000 1.41
***************
*** 60,64 ****
<link type="text/css" rel="stylesheet" href=
"http://www.w3.org/StyleSheets/TR/base.css" />
! <link type="" href="" title=" " rel="alternate" />
<link href="#contents" rel="contents" />
</head>
--- 60,64 ----
<link type="text/css" rel="stylesheet" href=
"http://www.w3.org/StyleSheets/TR/base.css" />
! <link type="" href="" title="" rel="alternate" />
<link href="#contents" rel="contents" />
</head>
***************
*** 298,308 ****
<p>The Web Services Description Language WSDL Version 2.0 (WSDL)
[<cite><a href="#WSDL-PART1">WSDL 2.0 Core Language</a></cite>]
! defines an XML grammar [<cite><a href="#XML10">XML 1.0</a></cite>]
! for describing network services as collections of communication
! endpoints capable of exchanging messages. WSDL service definitions
! provide documentation for distributed systems and serve as a recipe
! for automating the details involved in applications communication.
! WSDL 2.0 Bindings (this document) defines binding extensions for
! the following protocols and message formats:</p>
<ul>
<li>
--- 298,308 ----
<p>The Web Services Description Language WSDL Version 2.0 (WSDL)
[<cite><a href="#WSDL-PART1">WSDL 2.0 Core Language</a></cite>]
! defines an XML language for describing network services as
! collections of communication endpoints capable of exchanging
! messages. WSDL service definitions provide documentation for
! distributed systems and serve as a recipe for automating the
! details involved in applications communication. WSDL 2.0 Bindings
! (this document) defines binding extensions for the following
! protocols and message formats:</p>
<ul>
<li>
***************
*** 411,417 ****
"http://example.com/..." represent application or context-dependent
URIs [<cite><a href="#RFC2396">IETF RFC 2396</a></cite>].</p>
- <p>This specification uses the Extended Backus-Naur Form (EBNF) as
- described in XML 1.0 [<cite><a href="#XML10">XML
- 1.0</a></cite>].</p>
<p>All parts of this specification are normative, with the
EXCEPTION of pseudo-schemas, examples, and sections explicitly
--- 411,414 ----
***************
*** 474,479 ****
"#WSDL-PART1">WSDL 2.0 Core Language</a></cite>]) is identified as
a SOAP binding by assigning the value
! "http://www.w3.org/@@@@/@@/wsdl/soap12" to the {type} property of
! the Binding component.</p>
</div>
<div class="div2">
--- 471,477 ----
"#WSDL-PART1">WSDL 2.0 Core Language</a></cite>]) is identified as
a SOAP binding by assigning the value
! "http://www.w3.org/@@@@/@@/wsdl/soap12" to the <a href=
! "wsdl20.html#Binding_details">{type}</a> property of the Binding
! component.</p>
</div>
<div class="div2">
***************
*** 492,498 ****
<ul>
<li>
! <p>If the value of the {message content model} property of the
! Message Reference component is <em>#any</em> then the payload MAY
! be any one XML element.</p>
</li>
<li>
--- 490,497 ----
<ul>
<li>
! <p>If the value of the <a href=
! "wsdl20.html#MessageReference_details">{message content model}</a>
! property of the Message Reference component is <em>#any</em> then
! the payload MAY be any one XML element.</p>
</li>
<li>
***************
*** 502,506 ****
<li>
<p>If the value is <em>#element</em> then the payload will be the
! <em>element information item</em> identified by the {element}
property of the Message Reference component.</p>
</li>
--- 501,506 ----
<li>
<p>If the value is <em>#element</em> then the payload will be the
! <em>element information item</em> identified by the <a href=
! "wsdl20.html#MessageReference_details#MessageReference_details">{element}</a>
property of the Message Reference component.</p>
</li>
***************
*** 528,532 ****
<li>
<p><em>SOAP MEP Selection.</em> If the Interface Operation
! component's {message exchange pattern} property has the value
"http://www.w3.org/@@@@/@@/wsdl/in-out" then the default value of
the {soap mep} property for the corresponding Binding Operation
--- 528,534 ----
<li>
<p><em>SOAP MEP Selection.</em> If the Interface Operation
! component's <a href=
! "wsdl20.html#InterfaceOperation_details">{message exchange
! pattern}</a> property has the value
"http://www.w3.org/@@@@/@@/wsdl/in-out" then the default value of
the {soap mep} property for the corresponding Binding Operation
***************
*** 535,541 ****
defined in [<cite><a href="#SOAP12-PART2">SOAP 1.2 Part 2:
Adjuncts</a></cite>]. If the Inteface Operation component has any
! other value for the {message exchange pattern} property, then no
! default value is defined for the {soap mep} property of the
! corresponding Binding Operation component.</p>
</li>
<li>
--- 537,545 ----
defined in [<cite><a href="#SOAP12-PART2">SOAP 1.2 Part 2:
Adjuncts</a></cite>]. If the Inteface Operation component has any
! other value for the <a href=
! "wsdl20.html#InterfaceOperation_details">{message exchange
! pattern}</a> property, then no default value is defined for the
! {soap mep} property of the corresponding Binding Operation
! component.</p>
</li>
<li>
***************
*** 560,564 ****
execute the HTTP GET against MUST be generated using the HTTP
Binding's rules for generating a URI for HTTP GET (see <a href=
! "#http-binding"><b>3. WSDL HTTP Binding</b></a>).</p>
</li>
</ul>
--- 564,592 ----
execute the HTTP GET against MUST be generated using the HTTP
Binding's rules for generating a URI for HTTP GET (see <a href=
! "#http-binding"><b>3. WSDL HTTP Binding</b></a>). The input
! serialization format of <code>x-www-form-urlencoded</code> is the
! only supported serialization format for HTTP GET in the SOAP
! Response Message Exchange Pattern.</p>
! <table border="1" summary="Editorial note">
! <tr>
! <td width="50%" valign="top" align="left"><b>Editorial
! note</b></td>
! <td width="50%" valign="top" align="right"> </td>
! </tr>
! <tr>
! <td valign="top" align="left" colspan="2">Use of a different input
! serialization format requires introduction of either a new MEP or a
! new binding. The Working Group considered the limitations of the
! <code>x-www-form-urlencoded</code> serialization format (see
! <a href=
! "http://lists.w3.org/Archives/Public/www-ws-desc/2004Jul/0061.html">
! points #2 and #3 of Binding message content to URI analysis</a>).
! It decided that the limitations of the serialization format, which
! could potentially be solved by a serialization format extension,
! were not sufficiently broad enough to warrant allowing
! extensibility in input serialization for the soap-response MEP. The
! Working Group solicits the public's feedback on this decision.</td>
! </tr>
! </table>
</li>
</ul>
***************
*** 1467,1477 ****
of the payload (i.e., the contents of the <code>HTTP Request
Body</code> ) MUST be what is defined by the corresponding Message
! Reference component. If the value of the {message content model}
property of the Message Reference component is <em>#any</em> then
the payload MAY be any one XML element. If the value is
<em>#none</em> then the payload MUST be empty. Finally if the value
is <em>#element</em> then the payload will be the <em>element
! information item</em> identified by the {element} property of the
! Message Reference component.</p>
<p>If the Message Reference component is declared using a non-XML
type system (as considered in the Types section of [<cite><a href=
--- 1495,1506 ----
of the payload (i.e., the contents of the <code>HTTP Request
Body</code> ) MUST be what is defined by the corresponding Message
! Reference component. If the value of the <a href=
! "wsdl20.html#MessageReference_details">{message content model}</a>
property of the Message Reference component is <em>#any</em> then
the payload MAY be any one XML element. If the value is
<em>#none</em> then the payload MUST be empty. Finally if the value
is <em>#element</em> then the payload will be the <em>element
! information item</em> identified by the property of the Message
! Reference component.</p>
<p>If the Message Reference component is declared using a non-XML
type system (as considered in the Types section of [<cite><a href=
***************
*** 1799,1806 ****
"_operation_uri_style"></a>3.5.1 URI Style</h4>
<p>The URI style is selected by assigning the Interface Operation
! component's {style} 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 {message exchange pattern} property has the value
'http://www.w3.org/@@@@/@@/wsdl/in-only',
'http://www.w3.org/@@@@/@@/wsdl/robust-in-only' or
--- 1828,1836 ----
"_operation_uri_style"></a>3.5.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 property has the value
'http://www.w3.org/@@@@/@@/wsdl/in-only',
'http://www.w3.org/@@@@/@@/wsdl/robust-in-only' or
***************
*** 1808,1812 ****
<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 {message} properties of all {message reference}
components of the Interface Operation component with {direction}
property <em>in</em>. Those schemas MUST adhere to the rules
--- 1838,1842 ----
<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 {message} properties of all Message Reference
components of the Interface Operation component with {direction}
property <em>in</em>. Those schemas MUST adhere to the rules
***************
*** 2556,2559 ****
--- 2586,2597 ----
</tr>
<tr>
+ <td rowspan="1" colspan="1">20040720</td>
+ <td rowspan="1" colspan="1">HH</td>
+ <td rowspan="1" colspan="1">Specified default serialization format
+ for HTTP binding, as well as made clear how the defined
+ serialization formats apply constraints on interface operation
+ styles</td>
+ </tr>
+ <tr>
<td rowspan="1" colspan="1">20040705</td>
<td rowspan="1" colspan="1">JJM</td>
Received on Tuesday, 20 July 2004 10:32:22 UTC