- From: Arthur Ryman via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 04 May 2006 04:47:16 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv32505/wsdl20
Modified Files:
wsdl20-adjuncts.xml
Log Message:
Made edits to sections 1, 2, and 3.
Index: wsdl20-adjuncts.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-adjuncts.xml,v
retrieving revision 1.162
retrieving revision 1.163
diff -C2 -d -r1.162 -r1.163
*** wsdl20-adjuncts.xml 3 May 2006 23:42:27 -0000 1.162
--- wsdl20-adjuncts.xml 4 May 2006 04:47:13 -0000 1.163
***************
*** 77,87 ****
<abstract>
<p>
! WSDL is an XML format for describing network services as a set
of endpoints operating on messages containing either
document-oriented or procedure-oriented information.
! &part2.title; defines predefined extensions for use in WSDL 2.0:
</p>
<ulist>
<item><p>Message exchange patterns</p></item>
<item><p>Operation styles</p></item>
<item><p>Binding Extensions</p></item>
--- 77,88 ----
<abstract>
<p>
! WSDL 2.0 is an XML format for describing network services as a set
of endpoints operating on messages containing either
document-oriented or procedure-oriented information.
! &part2.title; specifies predefined extensions for use in WSDL 2.0:
</p>
<ulist>
<item><p>Message exchange patterns</p></item>
+ <item><p>Operation safety</p></item>
<item><p>Operation styles</p></item>
<item><p>Binding Extensions</p></item>
***************
*** 110,114 ****
<bibref ref="WSDL-PART1"/> 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
--- 111,115 ----
<bibref ref="WSDL-PART1"/> defines an XML language
for describing network services as collections of communication
! endpoints capable of exchanging messages. WSDL service descriptions
provide documentation for distributed systems and serve as a recipe
for automating the details involved in applications
***************
*** 299,303 ****
abstract out binding-specific information such as timing between
messages, whether the pattern is synchronous or asynchronous, and
! whether the message are sent over a single or multiple channels.
</p>
--- 300,304 ----
abstract out binding-specific information such as timing between
messages, whether the pattern is synchronous or asynchronous, and
! whether the messages are sent over a single or multiple channels.
</p>
***************
*** 310,320 ****
are not described by the pattern.</assert> For instance, even though a pattern
may define a single message sent from a service to one other node, the
! Web Service may multicast that message to other nodes.
</p>
<p>
To maximize reuse, WSDL message exchange patterns identify a minimal contract
! between other parties and Web Services, and contain only information
! that is relevant to both the Web Service and another party.
</p>
--- 311,321 ----
are not described by the pattern.</assert> For instance, even though a pattern
may define a single message sent from a service to one other node, the
! Web service may multicast that message to other nodes.
</p>
<p>
To maximize reuse, WSDL message exchange patterns identify a minimal contract
! between other parties and Web services, and contain only information
! that is relevant to both the Web service and another party.
</p>
***************
*** 327,331 ****
<!-- should this section be marked "informative"? -->
! <p>New Message Exchange Patterns may be defined by any organization able and
willing to do so. It is recommended that the patterns use the general
template provided here, after examination of existing predefined patterns.</p>
--- 328,332 ----
<!-- should this section be marked "informative"? -->
! <p>New message exchange patterns may be defined by any organization able and
willing to do so. It is recommended that the patterns use the general
template provided here, after examination of existing predefined patterns.</p>
***************
*** 338,342 ****
<p>[enumeration, specifying, for each message] A[n optional] message:</p>
<olist>
! <item><p>indicated by a <comp>Interface Message Reference</comp> component whose
<prop comp="Interface Message Reference">message label</prop> is
<attval>[label]</attval> and <prop comp="Interface Message Reference">direction</prop> is <attval>[direction]</attval></p></item>
--- 339,343 ----
<p>[enumeration, specifying, for each message] A[n optional] message:</p>
<olist>
! <item><p>indicated by an <comp>Interface Message Reference</comp> component whose
<prop comp="Interface Message Reference">message label</prop> is
<attval>[label]</attval> and <prop comp="Interface Message Reference">direction</prop> is <attval>[direction]</attval></p></item>
***************
*** 347,351 ****
<p>This pattern uses the rule [fault ruleset reference].</p>
! <p>An operation using this message exchange pattern has a
<prop comp="Interface Operation">message exchange pattern</prop>
property with the value <attval>[pattern IRI]</attval>.</p>
--- 348,352 ----
<p>This pattern uses the rule [fault ruleset reference].</p>
! <p>An <comp>Interface Operation</comp> using this message exchange pattern has a
<prop comp="Interface Operation">message exchange pattern</prop>
property with the value <attval>[pattern IRI]</attval>.</p>
***************
*** 373,381 ****
<p>WSDL patterns specify propagation of faults, not their generation.
! <assert class="exchange" id="FaultPropagation-2200101">Nodes which generate a fault MUST attempt to propagate the faults in
accordance with the governing ruleset, but it is understood that any
delivery of a network message is best effort, not guaranteed.</assert> The
rulesets establish the direction of the fault message and the fault
! recipient, they do not provide reliability or other delivery guarantees.
<assert class="exchange" id="FaultPropagation-2200102">When a fault is generated, the generating node MUST attempt to
propagate the fault, and MUST do so in the direction and to the
--- 374,382 ----
<p>WSDL patterns specify propagation of faults, not their generation.
! <assert class="exchange" id="FaultPropagation-2200101">Nodes that generate faults MUST attempt to propagate the faults in
accordance with the governing ruleset, but it is understood that any
delivery of a network message is best effort, not guaranteed.</assert> The
rulesets establish the direction of the fault message and the fault
! recipient; they do not provide reliability or other delivery guarantees.
<assert class="exchange" id="FaultPropagation-2200102">When a fault is generated, the generating node MUST attempt to
propagate the fault, and MUST do so in the direction and to the
***************
*** 761,765 ****
<p>
This section defines an extension to WSDL 2.0 <bibref
! ref="WSDL-PART1"/> which allows marking an operation as a
safe interaction, as defined in <xspecref
href='http://www.w3.org/TR/2004/REC-webarch-20041215/#safe-interaction'>section
--- 762,766 ----
<p>
This section defines an extension to WSDL 2.0 <bibref
! ref="WSDL-PART1"/> that allows marking an operation as a
safe interaction, as defined in <xspecref
href='http://www.w3.org/TR/2004/REC-webarch-20041215/#safe-interaction'>section
***************
*** 1296,1300 ****
<p>The SOAP binding extension described in this section is SOAP version
independent ("1.2" as well as other versions) and an extension
! for <bibref ref="WSDL-PART1"/> to enable Web Services
applications to use SOAP. This
binding extension extends WSDL 2.0 by adding properties to the <xspecref
--- 1297,1301 ----
<p>The SOAP binding extension described in this section is SOAP version
independent ("1.2" as well as other versions) and an extension
! for <bibref ref="WSDL-PART1"/> to enable Web services
applications to use SOAP. This
binding extension extends WSDL 2.0 by adding properties to the <xspecref
***************
*** 2565,2569 ****
<p>The WSDL SOAP 1.2 binding extension defined in this section is an extension of the SOAP binding defined in section <specref ref="soap-binding"/>
! to enable Web Service applications to use SOAP 1.2 <bibref ref="SOAP12-PART1"/>.</p>
<p>The WSDL SOAP 1.2 binding extension supports
--- 2566,2570 ----
<p>The WSDL SOAP 1.2 binding extension defined in this section is an extension of the SOAP binding defined in section <specref ref="soap-binding"/>
! to enable Web service applications to use SOAP 1.2 <bibref ref="SOAP12-PART1"/>.</p>
<p>The WSDL SOAP 1.2 binding extension supports
***************
*** 2799,2803 ****
<p>The HTTP binding extension described in this section is an extension for
! <bibref ref="WSDL-PART1"/> to enable Web Services applications to use
HTTP 1.1 <bibref ref="RFC2616"/> (as well as other versions of HTTP) and HTTPS <bibref ref="RFC2818"/>. This binding extension extends WSDL 2.0
by adding properties to the component model defined in <bibref ref="WSDL-PART1"/>. In addition an XML Infoset representation
--- 2800,2804 ----
<p>The HTTP binding extension described in this section is an extension for
! <bibref ref="WSDL-PART1"/> to enable Web services applications to use
HTTP 1.1 <bibref ref="RFC2616"/> (as well as other versions of HTTP) and HTTPS <bibref ref="RFC2818"/>. This binding extension extends WSDL 2.0
by adding properties to the component model defined in <bibref ref="WSDL-PART1"/>. In addition an XML Infoset representation
***************
*** 5286,5289 ****
--- 5287,5292 ----
</table>
</inform-div1>
+
+ &assertion-summary;
<inform-div1 id="changelog">
***************
*** 5306,5310 ****
</tr>
-->
! <tr>
<td>20060405</td>
<td>HH</td>
--- 5309,5320 ----
</tr>
-->
!
! <tr>
! <td>20060503</td>
! <td>AGR</td>
! <td>Made editorial improvements.</td>
! </tr>
!
! <tr>
<td>20060405</td>
<td>HH</td>
***************
*** 7108,7113 ****
</inform-div1>
- &assertion-summary;
-
</back>
</spec>
--- 7118,7121 ----
Received on Thursday, 4 May 2006 04:47:23 UTC