- From: Amelia Lewis via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 27 Feb 2007 13:59:49 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv11605
Modified Files:
wsdl20-additional-meps.xml
Log Message:
add markup to pattern names, per jjm
Index: wsdl20-additional-meps.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-additional-meps.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -C 2 -d -r1.5 -r1.6
*** wsdl20-additional-meps.xml 26 Feb 2007 17:57:34 -0000 1.5
--- wsdl20-additional-meps.xml 27 Feb 2007 13:59:46 -0000 1.6
***************
*** 184,188 ****
<div3 id="in-opt-out">
<head>In-Optional-Out message exchange pattern</head>
! <p><assert class="component" id="InOptOutComposition-2200801">The in-optional-out message exchange pattern consists of one or two messages, in order, as
follows:</assert></p>
<olist>
--- 184,188 ----
<div3 id="in-opt-out">
<head>In-Optional-Out message exchange pattern</head>
! <p><assert class="component" id="InOptOutComposition-2200801">The <el>in-optional-out message</el> exchange pattern consists of one or two messages, in order, as
follows:</assert></p>
<olist>
***************
*** 204,208 ****
</item>
</olist>
! <p><assert class="exchange" id="InOptOutFaults-2200802">The in-optional-out message exchange pattern uses the rule
<xspecref
href='&w3c-designation-part2;#fault-trigger'>Message Triggers
--- 204,208 ----
</item>
</olist>
! <p><assert class="exchange" id="InOptOutFaults-2200802">The <el>in-optional-out</el> message exchange pattern uses the rule
<xspecref
href='&w3c-designation-part2;#fault-trigger'>Message Triggers
***************
*** 215,219 ****
<div3 id="out-only">
<head>Out-Only message exchange pattern</head>
! <p><assert class="component" id="OutOnlyComposition-2200901">The out-only message exchange pattern
consists of exactly one message as follows:</assert></p>
<olist>
--- 215,219 ----
<div3 id="out-only">
<head>Out-Only message exchange pattern</head>
! <p><assert class="component" id="OutOnlyComposition-2200901">The <el>out-only</el> message exchange pattern
consists of exactly one message as follows:</assert></p>
<olist>
***************
*** 238,242 ****
</item>
</olist>
! <p><assert class="exchange" id="OutOnlyFaults-2200902">The out-only message exchange pattern uses the rule
<xspecref
href='&w3c-designation-part2;#no-fault'>No Fault</xspecref>.</assert></p>
--- 238,242 ----
</item>
</olist>
! <p><assert class="exchange" id="OutOnlyFaults-2200902">The <el>out-only</el> message exchange pattern uses the rule
<xspecref
href='&w3c-designation-part2;#no-fault'>No Fault</xspecref>.</assert></p>
***************
*** 250,254 ****
<div3 id="robust-out-only">
<head>Robust Out-Only message exchange pattern</head>
! <p><assert class="component" id="RobustOutOnlyComposition-2201001">The robust out-only message exchange pattern
consists of exactly one message as follows:</assert></p>
<olist>
--- 250,254 ----
<div3 id="robust-out-only">
<head>Robust Out-Only message exchange pattern</head>
! <p><assert class="component" id="RobustOutOnlyComposition-2201001">The <el>robust out-only</el> message exchange pattern
consists of exactly one message as follows:</assert></p>
<olist>
***************
*** 262,266 ****
</item>
</olist>
! <p><assert class="exchange" id="RobustOutOnlyFaults-2201002">The robust out-only message exchange pattern uses the rule
<xspecref
href='&w3c-designation-part2;#fault-trigger'>Message Triggers
--- 262,266 ----
</item>
</olist>
! <p><assert class="exchange" id="RobustOutOnlyFaults-2201002">The <el>robust out-only</el> message exchange pattern uses the rule
<xspecref
href='&w3c-designation-part2;#fault-trigger'>Message Triggers
***************
*** 273,277 ****
<div3 id="out-in">
<head>Out-In message exchange pattern</head>
! <p><assert class="component" id="OutInComposition-2201101">The out-in message exchange pattern consists of exactly two messages, in order, as
follows:</assert></p>
<olist>
--- 273,277 ----
<div3 id="out-in">
<head>Out-In message exchange pattern</head>
! <p><assert class="component" id="OutInComposition-2201101">The <el>out-in</el> message exchange pattern consists of exactly two messages, in order, as
follows:</assert></p>
<olist>
***************
*** 315,319 ****
</item>
</olist>
! <p><assert class="exchange" id="OutInFaults-2201102">The out-in message exchange pattern uses the rule
<xspecref
href='&w3c-designation-part2;#fault-replacement'>Fault Replaces
--- 315,319 ----
</item>
</olist>
! <p><assert class="exchange" id="OutInFaults-2201102">The <el>out-in</el> message exchange pattern uses the rule
<xspecref
href='&w3c-designation-part2;#fault-replacement'>Fault Replaces
***************
*** 328,332 ****
<div3 id="out-opt-in">
<head>Out-Optional-In message exchange pattern</head>
! <p><assert class="component" id="OutOptInComposition-2201201">The out-optional-in message exchange pattern consists of one or two messages, in order, as
follows:</assert></p>
<olist>
--- 328,332 ----
<div3 id="out-opt-in">
<head>Out-Optional-In message exchange pattern</head>
! <p><assert class="component" id="OutOptInComposition-2201201">The <el>out-optional-in</el> message exchange pattern consists of one or two messages, in order, as
follows:</assert></p>
<olist>
***************
*** 348,352 ****
</item>
</olist>
! <p><assert class="exchange" id="OutOptInFaults-2201202">The out-optional-in message exchange pattern uses the rule
<xspecref
href='&w3c-designation-part2;#fault-trigger'>Message Triggers
--- 348,352 ----
</item>
</olist>
! <p><assert class="exchange" id="OutOptInFaults-2201202">The <el>out-optional-in</el> message exchange pattern uses the rule
<xspecref
href='&w3c-designation-part2;#fault-trigger'>Message Triggers
***************
*** 451,454 ****
--- 451,459 ----
-->
+ <tr>
+ <td>20070227</td>
+ <td>aal</td>
+ <td>Add markup to pattern names, consistent with part 2, per jjm.</td>
+ </tr>
<tr>
<td>20070226</td>
Received on Tuesday, 27 February 2007 13:59:57 UTC