W3C home > Mailing lists > Public > public-ws-desc-eds@w3.org > September 2006

2002/ws/desc/wsdl20 wsdl20-adjuncts.xml,1.190,1.191

From: Jean-Jacques Moreau via cvs-syncmail <cvsmail@w3.org>
Date: Fri, 08 Sep 2006 09:22:46 +0000
To: public-ws-desc-eds@w3.org
Message-Id: <E1GLcZS-0007az-QN@lionel-hutz.w3.org>

Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv28819/ws/desc/wsdl20

Modified Files:
	wsdl20-adjuncts.xml 
Log Message:
indicate the patterns and faults which were being described

Index: wsdl20-adjuncts.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-adjuncts.xml,v
retrieving revision 1.190
retrieving revision 1.191
diff -C 2 -d -r1.190 -r1.191
*** wsdl20-adjuncts.xml	8 Sep 2006 08:41:14 -0000	1.190
--- wsdl20-adjuncts.xml	8 Sep 2006 09:22:44 -0000	1.191
***************
*** 395,403 ****
  
  <div3 id="fault-replacement">
! <head>Fault Replaces Message</head>
  
  <p>
  	<assert class="exchange" id="FaultReplacesMessage-2200201" required="false">
! 		Any message after the first in the pattern MAY be replaced with
  		a fault message, which MUST have identical direction.
  	</assert>
--- 395,404 ----
  
  <div3 id="fault-replacement">
! <head>Fault Replaces Message propagation rule</head>
  
  <p>
  	<assert class="exchange" id="FaultReplacesMessage-2200201" required="false">
! 		When the Fault Replaces Message propagation rule is in effect,
! 		any message after the first in the pattern MAY be replaced with
  		a fault message, which MUST have identical direction.
  	</assert>
***************
*** 408,421 ****
  </p>
  
! <p>This fault propagation rule is identified by the following URI: <code>&wsdl-fault-replace;</code></p>
  
  </div3>
  
  <div3 id="fault-trigger">
! <head>Message Triggers Fault</head>
  
  <p>
  	<assert class="exchange" id="MessageTriggersFault-2200301" required="false">
! 		Any message, including the first in the pattern, MAY trigger a
  		fault message, which MUST have opposite direction.
  	</assert>
--- 409,423 ----
  </p>
  
! <p>The Fault Replaces Message propagation rule is identified by the following URI: <code>&wsdl-fault-replace;</code></p>
  
  </div3>
  
  <div3 id="fault-trigger">
! <head>Message Triggers Fault propagation rule</head>
  
  <p>
  	<assert class="exchange" id="MessageTriggersFault-2200301" required="false">
! 		When the Message Triggers Fault propagation rule is in effet, any message,
! 		including the first in the pattern, MAY trigger a
  		fault message, which MUST have opposite direction.
  	</assert>
***************
*** 427,443 ****
  </p>
  
! <p>This fault propagation rule is identified by the following URI: <code>&wsdl-fault-trigger;</code></p>
  
  </div3>
  
  <div3 id="no-fault">
! <head>No Faults</head>
  <p>
  	<assert class="exchange" id="NoFaults-2200401">
! 		Faults MUST NOT be propagated.
  	</assert>
  </p>
  
! <p>This fault propagation rule is identified by the following URI: <code>&wsdl-fault-none;</code></p>
  
  </div3>
--- 429,445 ----
  </p>
  
! <p>The Message Triggers Fault propagation rule is identified by the following URI: <code>&wsdl-fault-trigger;</code></p>
  
  </div3>
  
  <div3 id="no-fault">
! <head>No Faults propagation rule</head>
  <p>
  	<assert class="exchange" id="NoFaults-2200401">
! 		When the No Faults propagation rule is in effect, faults MUST NOT be propagated.
  	</assert>
  </p>
  
! <p>The No Faults propagation rule is identified by the following URI: <code>&wsdl-fault-none;</code></p>
  
  </div3>
***************
*** 453,460 ****
  
  <div3 id="in-only">
! <head>In-Only</head>
  <p>
! <assert class="component" id="InOnlyComposition-2200501">This pattern consists of exactly one message as
! follows:</assert>
  </p>
  <olist>
--- 455,462 ----
  
  <div3 id="in-only">
! <head>In-Only message exchange pattern</head>
  <p>
! <assert class="component" id="InOnlyComposition-2200501">The in-only message exchange pattern
! consists of exactly one message as follows:</assert>
  </p>
  <olist>
***************
*** 480,484 ****
  </olist>
  
! <p><assert class="exchange" id="InOnlyFaults-2200502">This pattern uses the rule <specref
  ref='no-fault'/>.</assert></p>
  <p>
--- 482,486 ----
  </olist>
  
! <p><assert class="exchange" id="InOnlyFaults-2200502">The in-only message exchange pattern uses the rule <specref
  ref='no-fault'/>.</assert></p>
  <p>
***************
*** 490,496 ****
  
  <div3 id="robust-in-only">
! <head>Robust In-Only</head>
! <p><assert class="component" id="RobustInOnlyComposition-2200601">This pattern consists of exactly one message as
! follows:</assert></p>
  <olist>
    <item><p>A message:</p>
--- 492,498 ----
  
  <div3 id="robust-in-only">
! <head>Robust In-Only message exchange pattern</head>
! <p><assert class="component" id="RobustInOnlyComposition-2200601">The robust in-only message exchange
! pattern consists of exactly one message as follows:</assert></p>
  <olist>
    <item><p>A message:</p>
***************
*** 503,507 ****
    </item>
  </olist>
! <p><assert class="exchange" id="RobustInOnlyFaults-2200602">This pattern uses the rule <specref
  ref='fault-trigger'/>.</assert></p>
  <p>An operation using this message exchange pattern has a
--- 505,509 ----
    </item>
  </olist>
! <p><assert class="exchange" id="RobustInOnlyFaults-2200602">The robust in-only message exchange pattern uses the rule <specref
  ref='fault-trigger'/>.</assert></p>
  <p>An operation using this message exchange pattern has a
***************
*** 511,517 ****
  
  <div3 id="in-out">
! <head>In-Out</head>
! <p><assert class="component" id="InOutComposition-2200701">This pattern consists of exactly two messages, in order, as
! follows:</assert></p>
  <olist>
    <item>
--- 513,519 ----
  
  <div3 id="in-out">
! <head>In-Out message exchange pattern</head>
! <p><assert class="component" id="InOutComposition-2200701">The in-out message exchange pattern
! consists of exactly two messages, in order, as follows:</assert></p>
  <olist>
    <item>
***************
*** 554,558 ****
    </item>
  </olist>
! <p><assert class="exchange" id="InOutFaults-2200702">This pattern uses the rule <specref
  ref='fault-replacement'/>.</assert></p>
  <p>
--- 556,560 ----
    </item>
  </olist>
! <p><assert class="exchange" id="InOutFaults-2200702">The in-out message exchange pattern uses the rule <specref
  ref='fault-replacement'/>.</assert></p>
  <p>
***************
*** 564,569 ****
  
  <div3 id="in-opt-out">
! <head>In-Optional-Out</head>
! <p><assert class="component" id="InOptOutComposition-2200801">This pattern consists of one or two messages, in order, as
  follows:</assert></p>
  <olist>
--- 566,571 ----
  
  <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>
***************
*** 585,589 ****
    </item>
  </olist>
! <p><assert class="exchange" id="InOptOutFaults-2200802">This pattern uses the rule <specref
  ref='fault-trigger'/>.</assert></p>
  <p>An operation using this message exchange pattern has
--- 587,591 ----
    </item>
  </olist>
! <p><assert class="exchange" id="InOptOutFaults-2200802">The in-optional-out message exchange pattern uses the rule <specref
  ref='fault-trigger'/>.</assert></p>
  <p>An operation using this message exchange pattern has
***************
*** 593,599 ****
  
  <div3 id="out-only">
! <head>Out-Only</head>
! <p><assert class="component" id="OutOnlyComposition-2200901">This pattern consists of exactly one message as
! follows:</assert></p>
  <olist>
    <item>
--- 595,601 ----
  
  <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>
    <item>
***************
*** 617,621 ****
    </item>
  </olist>
! <p><assert class="exchange" id="OutOnlyFaults-2200902">This pattern uses the rule <specref
  ref='no-fault'/>.</assert></p>
  <p>
--- 619,623 ----
    </item>
  </olist>
! <p><assert class="exchange" id="OutOnlyFaults-2200902">The out-only message exchange pattern uses the rule <specref
  ref='no-fault'/>.</assert></p>
  <p>
***************
*** 627,633 ****
  
  <div3 id="robust-out-only">
! <head>Robust Out-Only</head>
! <p><assert class="component" id="RobustOutOnlyComposition-2201001">This pattern consists of exactly one message as
! follows:</assert></p>
  <olist>
    <item><p>message:</p>
--- 629,635 ----
  
  <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>
    <item><p>message:</p>
***************
*** 640,644 ****
    </item>
  </olist>
! <p><assert class="exchange" id="RobustOutOnlyFaults-2201002">This pattern uses the rule <specref
  ref='fault-trigger'/>.</assert></p>
  <p>An operation using this message exchange pattern has
--- 642,646 ----
    </item>
  </olist>
! <p><assert class="exchange" id="RobustOutOnlyFaults-2201002">The robust out-only message exchange pattern uses the rule <specref
  ref='fault-trigger'/>.</assert></p>
  <p>An operation using this message exchange pattern has
***************
*** 648,653 ****
  
  <div3 id="out-in">
! <head>Out-In</head>
! <p><assert class="component" id="OutInComposition-2201101">This pattern consists of exactly two messages, in order, as
  follows:</assert></p>
  <olist>
--- 650,655 ----
  
  <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>
***************
*** 691,695 ****
    </item>
  </olist>
! <p><assert class="exchange" id="OutInFaults-2201102">This pattern uses the rule <specref
  ref='fault-replacement'/>.</assert></p>
  <p>
--- 693,697 ----
    </item>
  </olist>
! <p><assert class="exchange" id="OutInFaults-2201102">The out-in message exchange pattern uses the rule <specref
  ref='fault-replacement'/>.</assert></p>
  <p>
***************
*** 701,706 ****
  
  <div3 id="out-opt-in">
! <head>Out-Optional-In</head>
! <p><assert class="component" id="OutOptInComposition-2201201">This pattern consists of one or two messages, in order, as
  follows:</assert></p>
  <olist>
--- 703,708 ----
  
  <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>
***************
*** 722,726 ****
    </item>
  </olist>
! <p><assert class="exchange" id="OutOptInFaults-2201202">This pattern uses the rule <specref
  ref='fault-trigger'/>.</assert></p>
  <p>An operation using this message exchange pattern has
--- 724,728 ----
    </item>
  </olist>
! <p><assert class="exchange" id="OutOptInFaults-2201202">The out-optional-in message exchange pattern uses the rule <specref
  ref='fault-trigger'/>.</assert></p>
  <p>An operation using this message exchange pattern has
***************
*** 5398,5401 ****
--- 5400,5412 ----
  	    	<td>JJM</td>
  	      <td><loc
+ 	      href="http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR068">CR068</loc>:
+ 	      indicate the patterns and faults which were being described
+ 	      </td>
+ 	    </tr>
+ 
+ 	    <tr>
+ 	    	<td>20060908</td>
+ 	    	<td>JJM</td>
+ 	      <td><loc
  	      href="http://www.w3.org/2002/ws/desc/5/cr-issues/issues.html#CR055">CR055</loc>:
  	      Clarification on HTTP Transfer Coding
Received on Friday, 8 September 2006 09:23:14 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:32:19 UTC