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

2002/ws/desc/wsdl20 wsdl20-adjuncts.xml,1.153,1.154

From: Amelia Lewis via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 01 Mar 2006 04:13:41 +0000
To: public-ws-desc-eds@w3.org
Message-Id: <E1FEIib-0002ye-JL@lionel-hutz.w3.org>

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

Modified Files:
	wsdl20-adjuncts.xml 
Log Message:
Added or updated assertions for Predefined MEPs, Predefined Extensions, and the Introduction

Index: wsdl20-adjuncts.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-adjuncts.xml,v
retrieving revision 1.153
retrieving revision 1.154
diff -C2 -d -r1.153 -r1.154
*** wsdl20-adjuncts.xml	27 Feb 2006 10:52:12 -0000	1.153
--- wsdl20-adjuncts.xml	1 Mar 2006 04:13:38 -0000	1.154
***************
*** 252,256 ****
  </p>
  <note>
!     <p>A node may be accessible via more than one physical address or transport.</p>
  </note>
  
--- 252,257 ----
  </p>
  <note>
!     <p><assert class="exchange" id="NodeIdentity-2200000" required="false">A
!         node MAY be accessible via more than one physical address or transport.</assert></p>
  </note>
  
***************
*** 274,278 ****
  <p>
  Unless explicitly stated otherwise, WSDL message exchange patterns also
! abstract out binding-specific information like timing between
  messages, whether the pattern is synchronous or asynchronous, and
  whether the message are sent over a single or multiple channels.
--- 275,279 ----
  <p>
  Unless explicitly stated otherwise, WSDL message exchange patterns also
! 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.
***************
*** 282,288 ****
  Like interfaces and operations, WSDL message exchange patterns do not
  exhaustively describe the set of messages exchanged between a service
! and other nodes; by some prior agreement, another node and/or the
! service may send other messages (to each other or to other nodes) that
! are not described by the pattern. 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.
--- 283,290 ----
  Like interfaces and operations, WSDL message exchange patterns do not
  exhaustively describe the set of messages exchanged between a service
! and other nodes; <assert class="exchange" id="MEPDescriptiveness-2200001"
! required="false">by some prior agreement, another node and/or the
! service MAY send other messages (to each other or to other nodes) that
! 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.
***************
*** 301,304 ****
--- 303,307 ----
  <div2 id="mep-template">
  <head>Template for Message Exchange Patterns</head>
+ <!-- should this section be marked "informative"? -->
  
  <p>New Message Exchange Patterns may be defined by any organization able and
***************
*** 348,364 ****
  
  <p>WSDL patterns specify propagation of faults, not their generation.  
! <assert class="component" id="FaultPropagation-5003">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="component" id="FaultPropagation-5004">When a fault is generated, the generating node MUST attempt to 
  propagate the fault, and MUST do so in the direction and to the 
! recipient specified by the ruleset.</assert>  However, extensions or binding extensions
! MAY modify these rulesets.  For example, WS-Addressing <bibref ref="WSA-Core"/>
  defines a "FaultTo" address for messages, which is used in lieu of the recipient
  nominated by the ruleset.</p> 
  
! <p>Generation of a fault, regardless of ruleset, terminates the exchange.</p>
  
  <p>Binding extensions, features, or extension specifications may override the 
--- 351,369 ----
  
  <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 
! recipient specified by the ruleset.</assert>  <assert class="component"
! id="FaultPropagationModification-2200103" required="false">However, extensions or binding extensions
! MAY modify these rulesets.</assert>  For example, WS-Addressing <bibref ref="WSA-Core"/>
  defines a "FaultTo" address for messages, which is used in lieu of the recipient
  nominated by the ruleset.</p> 
  
! <p><assert class="exchange" id="MEPTermination-2200104">Generation of a fault, regardless of 
! ruleset, terminates the exchange.</assert></p>
  
  <p>Binding extensions, features, or extension specifications may override the 
***************
*** 370,378 ****
  
  <p>
! 	<assert class="component" id="FaultReplacesMessage-5000">
  		Any message after the first in the pattern MAY be replaced with
  		a fault message, which MUST have identical direction.
  	</assert>
! 	<assert class="component" id="FaultDelivery-5005">The fault message MUST be delivered to the same target node as the
  	message it replaces, unless otherwise specified by an extension or
  	binding extension. If there is no path to this node, the fault MUST
--- 375,383 ----
  
  <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>
! 	<assert class="exchange" id="FaultDelivery-2200202">The fault message MUST be delivered to the same target node as the
  	message it replaces, unless otherwise specified by an extension or
  	binding extension. If there is no path to this node, the fault MUST
***************
*** 388,396 ****
  
  <p>
! 	<assert class="component" id="MessageTriggersFault-5001">
  		Any message, including the first in the pattern, MAY trigger a
  		fault message, which MUST have opposite direction.
  	</assert>
! 	<assert class="component" id="FaultDelivery-5006">The fault message MUST be delivered to the originator of the
  	triggering message, unless otherwise specified by an extension of
  	binding extension. Any node MAY propagate a fault message, and MUST
--- 393,401 ----
  
  <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>
! 	<assert class="exchange" id="FaultDelivery-2200202">The fault message MUST be delivered to the originator of the
  	triggering message, unless otherwise specified by an extension of
  	binding extension. Any node MAY propagate a fault message, and MUST
***************
*** 406,410 ****
  <head>No Faults</head>
  <p>
! 	<assert class="component" id="NoFaults-5002">
  		Faults MUST NOT be propagated.
  	</assert>
--- 411,415 ----
  <head>No Faults</head>
  <p>
! 	<assert class="exchange" id="NoFaults-2200401">
  		Faults MUST NOT be propagated.
  	</assert>
***************
*** 427,431 ****
  <head>In-Only</head>
  <p>
! This pattern consists of exactly one message as follows:
  </p>
  <olist>
--- 432,437 ----
  <head>In-Only</head>
  <p>
! <assert class="component" id="InOnlyComposition-2200501">This pattern consists of exactly one message as
! follows:</assert>
  </p>
  <olist>
***************
*** 451,455 ****
  </olist>
  
! <p>This pattern uses the rule <specref ref='no-fault'/>.</p>
  <p>
  An operation using this message exchange pattern has a
--- 457,462 ----
  </olist>
  
! <p><assert class="exchange" id="InOnlyFaults-2200502">This pattern uses the rule <specref
! ref='no-fault'/>.</assert></p>
  <p>
  An operation using this message exchange pattern has a
***************
*** 461,465 ****
  <div3 id="robust-in-only">
  <head>Robust In-Only</head>
! <p>This pattern consists of exactly one message as follows:</p>
  <olist>
    <item><p>A message:</p>
--- 468,473 ----
  <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>
***************
*** 472,476 ****
    </item>
  </olist>
! <p>This pattern uses the rule <specref ref='fault-trigger'/>.</p>
  <p>An operation using this message exchange pattern has a
  <prop comp="Interface Operation">message exchange pattern</prop> property with
--- 480,485 ----
    </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
  <prop comp="Interface Operation">message exchange pattern</prop> property with
***************
*** 480,484 ****
  <div3 id="in-out">
  <head>In-Out</head>
! <p>This pattern consists of exactly two messages, in order, as follows:</p>
  <olist>
    <item>
--- 489,494 ----
  <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>
***************
*** 521,525 ****
    </item>
  </olist>
! <p>This pattern uses the rule <specref ref='fault-replacement'/>.</p>
  <p>
  An operation using this message exchange pattern has
--- 531,536 ----
    </item>
  </olist>
! <p><assert class="exchange" id="InOutFaults-2200702">This pattern uses the rule <specref
! ref='fault-replacement'/>.</assert></p>
  <p>
  An operation using this message exchange pattern has
***************
*** 531,536 ****
  <div3 id="in-opt-out">
  <head>In-Optional-Out</head>
! <p>This pattern consists of one or two messages, in order, as
! follows:</p>
  <olist>
    <item><p>A message:</p>
--- 542,547 ----
  <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>
    <item><p>A message:</p>
***************
*** 551,555 ****
    </item>
  </olist>
! <p>This pattern uses the rule <specref ref='fault-trigger'/>.</p>
  <p>An operation using this message exchange pattern has
  a <prop comp="Interface Operation">message exchange pattern</prop> property
--- 562,567 ----
    </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
  a <prop comp="Interface Operation">message exchange pattern</prop> property
***************
*** 559,563 ****
  <div3 id="out-only">
  <head>Out-Only</head>
! <p>This pattern consists of exactly one message as follows:</p>
  <olist>
    <item>
--- 571,576 ----
  <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>
***************
*** 581,585 ****
    </item>
  </olist>
! <p>This pattern uses the rule <specref ref='no-fault'/>.</p>
  <p>
  An operation using this message exchange pattern has
--- 594,599 ----
    </item>
  </olist>
! <p><assert class="exchange" id="OutOnlyFaults-2200902">This pattern uses the rule <specref
! ref='no-fault'/>.</assert></p>
  <p>
  An operation using this message exchange pattern has
***************
*** 591,595 ****
  <div3 id="robust-out-only">
  <head>Robust Out-Only</head>
! <p>This pattern consists of exactly one message as follows:</p>
  <olist>
    <item><p>message:</p>
--- 605,610 ----
  <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>
***************
*** 602,606 ****
    </item>
  </olist>
! <p>This pattern uses the rule <specref ref='fault-trigger'/>.</p>
  <p>An operation using this message exchange pattern has
  a <prop comp="Interface Operation">message exchange pattern</prop> property with
--- 617,622 ----
    </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
  a <prop comp="Interface Operation">message exchange pattern</prop> property with
***************
*** 610,614 ****
  <div3 id="out-in">
  <head>Out-In</head>
! <p>This pattern consists of exactly two messages, in order, as follows:</p>
  <olist>
    <item>
--- 626,631 ----
  <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>
    <item>
***************
*** 651,655 ****
    </item>
  </olist>
! <p>This pattern uses the rule <specref ref='fault-replacement'/>.</p>
  <p>
  An operation using this message exchange pattern has
--- 668,673 ----
    </item>
  </olist>
! <p><assert class="exchange" id="OutInFaults-2201102">This pattern uses the rule <specref
! ref='fault-replacement'/>.</assert></p>
  <p>
  An operation using this message exchange pattern has
***************
*** 661,666 ****
  <div3 id="out-opt-in">
  <head>Out-Optional-In</head>
! <p>This pattern consists of one or two messages, in order, as
! follows:</p>
  <olist>
    <item><p>A message:</p>
--- 679,684 ----
  <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>
    <item><p>A message:</p>
***************
*** 681,685 ****
    </item>
  </olist>
! <p>This pattern uses the rule <specref ref='fault-trigger'/>.</p>
  <p>An operation using this message exchange pattern has
  a <prop comp="Interface Operation">message exchange pattern</prop> property with
--- 699,704 ----
    </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
  a <prop comp="Interface Operation">message exchange pattern</prop> property with
***************
*** 699,704 ****
  network, host, or services. When such responses are directed to an
  address other than that originating the initial message, the source of
! an attack may be obscured, or blame laid on a third party, or may
! enable or exacerbate denial-of-service attacks.</p>
  
  <p>Security mechanisms addressing such attacks may prevent the
--- 718,723 ----
  network, host, or services. When such responses are directed to an
  address other than that originating the initial message, the source of
! an attack may be obscured, or blame laid on a third party, or
! denial-of-service attacks may be enabled or exacerbated.</p>
  
  <p>Security mechanisms addressing such attacks may prevent the
***************
*** 720,724 ****
  	<p>
  	  This section defines an extension to WSDL 2.0 <bibref
! 	  ref="WSDL-PART1"/> which allows to mark an operation as a
  	  safe interaction, as defined in <xspecref
  	  href='http://www.w3.org/TR/2004/REC-webarch-20041215/#safe-interaction'>section
--- 739,743 ----
  	<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
***************
*** 746,752 ****
  	    property is <attval>false</attval>, then no assertion has been made about
  	    the safety of the operation, thus the operation MAY or MAY
! 	    NOT be safe.  However, an operation SHOULD be marked safe
  	    if it meets the criteria for a safe interaction defined in
! 	    Section 3.5 of <bibref ref="webarch"/>.</p></item>
  	  </ulist>
  	</div3>
--- 765,772 ----
  	    property is <attval>false</attval>, then no assertion has been made about
  	    the safety of the operation, thus the operation MAY or MAY
! 	    NOT be safe.  <assert class="component"
! id="OperationSafety-2300001" required="false">However, an operation SHOULD be marked safe
  	    if it meets the criteria for a safe interaction defined in
! 	    Section 3.5 of <bibref ref="webarch"/>.</assert></p></item>
  	  </ulist>
  	</div3>
***************
*** 766,772 ****
  	  <ulist>
  	    <item>
! 	      <p>An OPTIONAL <att>safe</att>
  	      &AII; with the following
! 	      Infoset properties:</p>
                    <ulist>
                      <item>
--- 786,793 ----
  	  <ulist>
  	    <item>
! 	      <p><assert class="document" id="OperationSafety-2300002"
! required="false">An OPTIONAL <att>safe</att>
  	      &AII; with the following
! 	      Infoset properties:</assert></p>
                    <ulist>
                      <item>
Received on Wednesday, 1 March 2006 04:13:52 GMT

This archive was generated by hypermail 2.2.0+W3C0.50 : Wednesday, 1 March 2006 04:13:52 GMT