- From: Roberto Chinnici via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 13 Apr 2005 01:39:59 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv27934
Modified Files:
wsdl20-adjuncts.html wsdl20-adjuncts.xml
Log Message:
Implemented resolution of LC75h.
Index: wsdl20-adjuncts.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-adjuncts.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -C2 -d -r1.19 -r1.20
*** wsdl20-adjuncts.html 8 Apr 2005 12:11:07 -0000 1.19
--- wsdl20-adjuncts.html 13 Apr 2005 01:39:57 -0000 1.20
***************
*** 4,8 ****
<head>
<meta name="generator" content=
! "HTML Tidy for Linux/x86 (vers 1st August 2004), see www.w3.org" />
<meta http-equiv="Content-Type" content=
"text/html; charset=utf-8" />
--- 4,8 ----
<head>
<meta name="generator" content=
! "HTML Tidy for Linux/x86 (vers 1st February 2005), see www.w3.org" />
<meta http-equiv="Content-Type" content=
"text/html; charset=utf-8" />
***************
*** 445,451 ****
(Non-Normative)<br />
B. <a href="#changelog">Part 2 Change Log</a> (Non-Normative)<br />
! B.1 <a href="#id2299090">WSDL 2.0
Extensions Change Log</a><br />
! B.2 <a href="#id2300084">WSDL 2.0 Bindings
Change Log</a><br /></p>
</div>
--- 445,451 ----
(Non-Normative)<br />
B. <a href="#changelog">Part 2 Change Log</a> (Non-Normative)<br />
! B.1 <a href="#id2299905">WSDL 2.0
Extensions Change Log</a><br />
! B.2 <a href="#id2300898">WSDL 2.0 Bindings
Change Log</a><br /></p>
</div>
***************
*** 1095,1098 ****
--- 1095,1108 ----
</li>
</ol>
+ <div class="note">
+ <p class="prefix"><b>Note:</b></p>
+ <p>The <code>wrpc:signature</code> extension allows the
+ specification of multiple return values for an operation. Several
+ popular programming languages support multiple return values for a
+ function. Moreover, for languages who do not, the burden on
+ implementors should be small, as typically multiple return values
+ will be mapped to a single return value of a structure type (or its
+ closest language-specific equivalent).</p>
+ </div>
</div>
<div class="div3">
***************
*** 1182,1187 ****
</div>
<div class="div2">
! <h3><a name="_operation_uri_style" id=
! "_operation_uri_style"></a>3.2 URI Style</h3>
<p>The URI style may be used for Interface Operation components
using a message exchange pattern with an initial message.</p>
--- 1192,1196 ----
</div>
<div class="div2">
! <h3><a name="_operation_uri_style"></a>3.2 URI Style</h3>
<p>The URI style may be used for Interface Operation components
using a message exchange pattern with an initial message.</p>
***************
*** 1234,1239 ****
</div>
<div class="div2">
! <h3><a name="_operation_multipart_style" id=
! "_operation_multipart_style"></a>3.3 Multipart style</h3>
<p>The Multipart style may be used for Interface Operation
components using a message exchange pattern with an initial
--- 1243,1248 ----
</div>
<div class="div2">
! <h3><a name="_operation_multipart_style"></a>3.3 Multipart
! style</h3>
<p>The Multipart style may be used for Interface Operation
components using a message exchange pattern with an initial
***************
*** 2694,2699 ****
</div>
<div class="div2">
! <h3><a name="_http_binding_default_rules" id=
! "_http_binding_default_rules"></a>5.3 Default Binding Rules</h3>
<ul>
<li>
--- 2703,2708 ----
</div>
<div class="div2">
! <h3><a name="_http_binding_default_rules"></a>5.3 Default Binding
! Rules</h3>
<ul>
<li>
***************
*** 3619,3624 ****
</div>
<div class="div2">
! <h3><a name="_http_serialization" id="_http_serialization"></a>5.9
! Serialization Format of Instance Data</h3>
<p>The following serialization formats can be used to encode the
<a title="instance_data" href="#instance_data">instance data</a>
--- 3628,3633 ----
</div>
<div class="div2">
! <h3><a name="_http_serialization"></a>5.9 Serialization Format of
! Instance Data</h3>
<p>The following serialization formats can be used to encode the
<a title="instance_data" href="#instance_data">instance data</a>
***************
*** 3628,3634 ****
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>5.9.1 Serialization as
! "application/x-www-form-urlencoded"</h4>
<p>This serialization format is designed to allow a Web service to
produce a URI based on the <a title="instance_data" href=
--- 3637,3642 ----
restrictions on the style of the Interface Operation bound.</p>
<div class="div3">
! <h4><a name="_http_x-www-form-urlencoded"></a>5.9.1 Serialization
! as "application/x-www-form-urlencoded"</h4>
<p>This serialization format is designed to allow a Web service to
produce a URI based on the <a title="instance_data" href=
***************
*** 3689,3695 ****
Component Model</b></a>.</p>
<div class="div4">
! <h5><a name="_http_operation_location_cited_get" id=
! "_http_operation_location_cited_get"></a>5.9.1.1 Case of elements
! cited in the {http location} property</h5>
<table border="1" summary=
"Editorial note: URIPath Feedback Requested">
--- 3697,3702 ----
Component Model</b></a>.</p>
<div class="div4">
! <h5><a name="_http_operation_location_cited_get"></a>5.9.1.1 Case
! of elements cited in the {http location} property</h5>
<table border="1" summary=
"Editorial note: URIPath Feedback Requested">
***************
*** 3741,3747 ****
</div>
<div class="div4">
! <h5><a name="_http_operation_location_notcited_get" id=
! "_http_operation_location_notcited_get"></a>5.9.1.2 Case elements
! NOT cited in the {http location} property</h5>
<p>If not all elements from the <a title="instance_data" href=
"#instance_data">instance data</a> are cited in the {http location}
--- 3748,3753 ----
</div>
<div class="div4">
! <h5><a name="_http_operation_location_notcited_get"></a>5.9.1.2
! Case elements NOT cited in the {http location} property</h5>
<p>If not all elements from the <a title="instance_data" href=
"#instance_data">instance data</a> are cited in the {http location}
***************
*** 3756,3762 ****
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>5.9.1.2.1 Serialization
! in the request URI</h6>
<p>Non-nil elements with a possibly empty single value of the
<a title="instance_data" href="#instance_data">instance data</a>
--- 3762,3767 ----
Serialization in the request URI</b></a>).</p>
<div class="div5">
! <h6><a name="_http_operation_location_notcited_uri"></a>5.9.1.2.1
! Serialization in the request URI</h6>
<p>Non-nil elements with a possibly empty single value of the
<a title="instance_data" href="#instance_data">instance data</a>
***************
*** 3791,3796 ****
</div>
<div class="div5">
! <h6><a name="_http_operation_location_notcited_body" id=
! "_http_operation_location_notcited_body"></a>5.9.1.2.2
Serialization in the message body</h6>
<p>In addition to the serialization in the request URI of the
--- 3796,3800 ----
</div>
<div class="div5">
! <h6><a name="_http_operation_location_notcited_body"></a>5.9.1.2.2
Serialization in the message body</h6>
<p>In addition to the serialization in the request URI of the
***************
*** 3853,3859 ****
</div>
<div class="div3">
! <h4><a name="_http_operation_xml_encoding" id=
! "_http_operation_xml_encoding"></a>5.9.2 Serialization as
! "application/xml"</h4>
<p>The <a title="instance_data" href="#instance_data">instance
data</a> of the input, output or fault message is serialized as an
--- 3857,3862 ----
</div>
<div class="div3">
! <h4><a name="_http_operation_xml_encoding"></a>5.9.2 Serialization
! as "application/xml"</h4>
<p>The <a title="instance_data" href="#instance_data">instance
data</a> of the input, output or fault message is serialized as an
***************
*** 3868,3874 ****
</div>
<div class="div3">
! <h4><a name="_http_operation_multipart_encoding" id=
! "_http_operation_multipart_encoding"></a>5.9.3 Serialization as
! "multipart/form-data"</h4>
<p>This format is for legacy compatibility to permit the use of
XForms clients with [<cite><a href="#RFC2388">IETF RFC
--- 3871,3876 ----
</div>
<div class="div3">
! <h4><a name="_http_operation_multipart_encoding"></a>5.9.3
! Serialization as "multipart/form-data"</h4>
<p>This format is for legacy compatibility to permit the use of
XForms clients with [<cite><a href="#RFC2388">IETF RFC
***************
*** 4582,4585 ****
--- 4584,4593 ----
</tr>
<tr>
+ <td rowspan="1" colspan="1">20050412</td>
+ <td rowspan="1" colspan="1">RRC</td>
+ <td rowspan="1" colspan="1">LC75h: added note on multiple return
+ values in rpc style</td>
+ </tr>
+ <tr>
<td rowspan="1" colspan="1">20050408</td>
<td rowspan="1" colspan="1">HH</td>
***************
*** 4696,4700 ****
<br />
<div class="div2">
! <h3><a name="id2299090" id="id2299090"></a>B.1 WSDL 2.0 Extensions
Change Log</h3>
<a name="wsdl-changelog-table" id="wsdl-changelog-table"></a><br />
--- 4704,4708 ----
<br />
<div class="div2">
! <h3><a name="id2299905" id="id2299905"></a>B.1 WSDL 2.0 Extensions
Change Log</h3>
<a name="wsdl-changelog-table" id="wsdl-changelog-table"></a><br />
***************
*** 4916,4920 ****
<br /></div>
<div class="div2">
! <h3><a name="id2300084" id="id2300084"></a>B.2 WSDL 2.0 Bindings
Change Log</h3>
<a name="wsdl-spec3-changelog-table" id=
--- 4924,4928 ----
<br /></div>
<div class="div2">
! <h3><a name="id2300898" id="id2300898"></a>B.2 WSDL 2.0 Bindings
Change Log</h3>
<a name="wsdl-spec3-changelog-table" id=
Index: wsdl20-adjuncts.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-adjuncts.xml,v
retrieving revision 1.28
retrieving revision 1.29
diff -C2 -d -r1.28 -r1.29
*** wsdl20-adjuncts.xml 8 Apr 2005 12:10:21 -0000 1.28
--- wsdl20-adjuncts.xml 13 Apr 2005 01:39:57 -0000 1.29
***************
*** 728,731 ****
--- 728,742 ----
</item>
</olist>
+
+ <note>
+ <p>The <att>wrpc:signature</att> extension allows the specification
+ of multiple return values for an operation. Several popular programming
+ languages support multiple return values for a function. Moreover, for
+ languages who do not, the burden on implementors should be small,
+ as typically multiple return values will be mapped to a single
+ return value of a structure type (or its closest language-specific
+ equivalent). </p>
+ </note>
+
</div3>
***************
*** 4317,4320 ****
--- 4328,4336 ----
-->
<tr>
+ <td>20050412</td>
+ <td>RRC</td>
+ <td>LC75h: added note on multiple return values in rpc style</td>
+ </tr>
+ <tr>
<td>20050408</td>
<td>HH</td>
Received on Wednesday, 13 April 2005 01:40:01 UTC