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

2002/ws/desc/wsdl20 wsdl20-additional-meps.xml,1.1,1.2

From: Amelia Lewis via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 07 Nov 2006 18:25:14 +0000
To: public-ws-desc-eds@w3.org
Message-Id: <E1GhVdK-0004lj-4A@lionel-hutz.w3.org>

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

Modified Files:
	wsdl20-additional-meps.xml 
Log Message:
initial revision of additional meps note

Index: wsdl20-additional-meps.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-additional-meps.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -C 2 -d -r1.1 -r1.2
*** wsdl20-additional-meps.xml	25 Oct 2006 08:05:02 -0000	1.1
--- wsdl20-additional-meps.xml	7 Nov 2006 18:25:11 -0000	1.2
***************
*** 134,150 ****
              </tr>
              <tr>
-               <td rowspan="1" colspan="1">wsdlx</td>
-               <td rowspan="1" colspan="1">
-                 <attval>&wsdl-x-ns;</attval>
-               </td>
-               <td rowspan="1" colspan="1">
- 		This specification extends in section <specref ref="ext"/> the
- 		<attval>&wsdl-x-ns;</attval> namespace defined in <bibref ref="WSDL-PART1"/>.
- 		A normative XML Schema <bibref ref="XMLSchemaP1"/>,
-         <bibref ref="XMLSchemaP2"/> document for the
-         <attval>&wsdl-x-ns;</attval>
-         namespace can be found at <loc href="&wsdl-x-ns;">&wsdl-x-ns;</loc>.</td>
-             </tr>
-             <tr>
                <td rowspan="1" colspan="1">wsoap</td>
                <td rowspan="1" colspan="1">
--- 134,137 ----
***************
*** 193,202 ****
  <attval>http://example.com/...</attval> represent application or
  context-dependent URIs <bibref ref="RFC3986"/>.</p>
!         <p>All parts of this specification are normative, with the EXCEPTION
! of pseudo-schemas, examples, and sections explicitly marked as
! "Non-Normative".  Pseudo-schemas are provided for each component,
! before the description of this component. They provide visual help for
! the XML <bibref ref="XML10"/> serialization. The <xspecref href='&w3c-designation-part1;#bnfpseudoschemas'>syntax of BNF
! 	pseudo-schemas</xspecref> is the same as the one used in <bibref ref="WSDL-PART1"/>.</p>
        </div2>
  
--- 180,184 ----
  <attval>http://example.com/...</attval> represent application or
  context-dependent URIs <bibref ref="RFC3986"/>.</p>
!         <p>This document is non-normative.</p>
        </div2>
  
***************
*** 215,222 ****
  	  e.g. error reporting.
  	</p>
- 	<p>
- 	  The assertions and their identifiers are summarized in
- 	  section <specref ref="assertionsummary" />.
- 	</p>
        </div2>
  
--- 197,200 ----
***************
*** 248,257 ****
  WSDL message exchange patterns describe the interaction at the abstract 
  (interface) level, which may be distinct from the pattern used by the 
! underlying protocol binding (e.g. SOAP Message Exchange
! Patterns; section <specref ref="soap12-defaults"/> contains the
! binding rules for the selection of a SOAP 1.2 message exchange
! pattern based on the WSDL message exchange pattern in use for the SOAP
! binding extension defined in this specification in section <specref ref='soap-binding'/>).
! </p>
  
  <p>
--- 226,230 ----
  WSDL message exchange patterns describe the interaction at the abstract 
  (interface) level, which may be distinct from the pattern used by the 
! underlying protocol binding.</p>
  
  <p>
***************
*** 333,413 ****
  <head>Fault Propagation Rules</head>
  
! <p>WSDL patterns specify their fault propagation model using standard
! rulesets to indicate where faults may occur.  The most common patterns
! for fault propagation are defined here, and referenced by patterns later in
! the document.  "Propagation" is defined as a best-effort attempt to transmit
! the fault message to its designated recipient.</p>
! 
! <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 
! 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 
! semantics of a fault propagation ruleset, but this practice is strongly 
! discouraged.</p> 
! 
! <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>
! 	<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
! 	be discarded.</assert>
! </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>
! 	<assert class="exchange" id="FaultDelivery-2200302">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
! 	not do so more than once for each triggering message. If there is no
! 	path to the originator, the fault MUST be discarded.</assert>
! </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>
  
  </div2>
--- 306,311 ----
  <head>Fault Propagation Rules</head>
  
! <p>These patterns use the fault propagation rulesets defined in <bibref
! ref="WSDL-PART2" />.
  
  </div2>
***************
*** 420,534 ****
  and <comp>Interface Fault Reference</comp> components. </p>
  
- <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>
-   <item>
-     <p>
- A message:
-     </p>
-     <ulist>
-       <item>
-         <p>
- indicated by a <comp>Interface Message Reference</comp> component
- whose <prop comp="Interface Message Reference">message label</prop>
- is <attval>In</attval> and <prop comp="Interface Message Reference">direction</prop> is <attval>in</attval>
-         </p>
-       </item>
-       <item>
-         <p>
- received from some node N
-         </p>
-       </item>
-     </ulist>
-   </item>
- </olist>
- 
- <p><assert class="exchange" id="InOnlyFaults-2200502">The in-only message exchange pattern uses the rule <specref
- ref='no-fault'/>.</assert></p>
- <p>
- An operation using this message exchange pattern has a
- <prop comp="Interface Operation">message exchange pattern</prop> property with
- the value <attval>&wsdl-mep-in-only;</attval>.
- </p>
- </div3>
- 
- <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>
-     <ulist>
-       <item><p>indicated by a <comp>Interface Message Reference</comp> component whose
- <prop comp="Interface Message Reference">message label</prop> is <attval>In</attval> and
- <prop comp="Interface Message Reference">direction</prop> is <attval>in</attval></p></item>
-       <item><p>received from some node N</p></item>
-     </ulist>
-   </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
- <prop comp="Interface Operation">message exchange pattern</prop> property with
- the value <attval>&wsdl-mep-robust-in-only;</attval>.</p>
- </div3>
- 
- <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>
-     <p>
- A message:
-     </p>
-     <ulist>
-       <item>
-         <p>
- indicated by a <comp>Interface Message Reference</comp> component
- whose <prop comp="Interface Message Reference">message label</prop>
- is <attval>In</attval> and <prop comp="Interface Message Reference">direction</prop> is <attval>in</attval>
-         </p>
-       </item>
-       <item>
-         <p>
- received from some node N
-         </p>
-       </item>
-     </ulist>
-   </item>
-   <item>
-     <p>
- A message:
-     </p>
-     <ulist>
-       <item>
-         <p>
- indicated by a <comp>Interface Message Reference</comp> component
- whose <prop comp="Interface Message Reference">message label</prop>
- is <attval>Out</attval> and <prop comp="Interface Message Reference">direction</prop> is <attval>out</attval>
-         </p>
-       </item>
-       <item>
-         <p>
- sent to node N
-         </p>
-       </item>
-     </ulist>
-   </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>
- An operation using this message exchange pattern has
- a <prop comp="Interface Operation">message exchange pattern</prop> property with
- the value <attval>&wsdl-mep-in-out;</attval>.
- </p>
- </div3>
- 
  <div3 id="in-opt-out">
  <head>In-Optional-Out message exchange pattern</head>
--- 318,321 ----
***************
*** 553,558 ****
    </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
  a <prop comp="Interface Operation">message exchange pattern</prop> property
--- 340,347 ----
    </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
! Fault</xpecref>.</assert></p>
  <p>An operation using this message exchange pattern has
  a <prop comp="Interface Operation">message exchange pattern</prop> property
***************
*** 585,590 ****
    </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>
  An operation using this message exchange pattern has
--- 374,380 ----
    </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>
  <p>
  An operation using this message exchange pattern has
***************
*** 608,613 ****
    </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
  a <prop comp="Interface Operation">message exchange pattern</prop> property with
--- 398,405 ----
    </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
! Fault</xspecref>.</assert></p>
  <p>An operation using this message exchange pattern has
  a <prop comp="Interface Operation">message exchange pattern</prop> property with
***************
*** 659,664 ****
    </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>
  An operation using this message exchange pattern has
--- 451,458 ----
    </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
! Message</xspecref>.</assert></p>
  <p>
  An operation using this message exchange pattern has
***************
*** 690,695 ****
    </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
  a <prop comp="Interface Operation">message exchange pattern</prop> property with
--- 484,491 ----
    </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
! Fault</xspecref>.</assert></p>
  <p>An operation using this message exchange pattern has
  a <prop comp="Interface Operation">message exchange pattern</prop> property with
***************
*** 702,719 ****
    <head>Security Considerations</head>
  
! <p>Note that many of the message exchange patterns defined above describe
! responses to an initial message (either a normal response message or a
! fault.)</p>
! 
! <p>Such responses may be used in attempts to disrupt, attack, or map a
! 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
- delivery of response messages to the receiving node. Conformance to
- the message exchange pattern is measured prior to the application of
- these security mechanisms.</p>
  </div2>
  
--- 498,503 ----
    <head>Security Considerations</head>
  
! <p>Security considerations are discussed in <bibref ref="WSDL-PART2" />.</p>
  
  </div2>
  
***************
*** 854,860 ****
              &draft.year;. This version of the
  	    "&part1.title;" Specification is
! 	    available is available at &w3c-designation-part1;. The <loc href="&part1.latest;">latest version of "&part1.title;"</loc> is available at
  	    &part1.latest;.
  	  </bibl>
            <bibl id="XML10" key="XML 1.0" href="http://www.w3.org/TR/2004/REC-xml-20040204/">
              <titleref>Extensible Markup Language (XML) 1.0 (Third
--- 638,652 ----
              &draft.year;. This version of the
  	    "&part1.title;" Specification is
! 	    available at &w3c-designation-part1;. The <loc href="&part1.latest;">latest version of "&part1.title;"</loc> is available at
  	    &part1.latest;.
  	  </bibl>
+ 	  <bibl key="WSDL 2.0 Adjuncts" href="&w3c-designation-part2;" id="WSDL-PART2">
+ 	    <titleref>&part2.title;</titleref>, R. Chinnici, H. Haas, A.
+             Lewis, J-J. Moreau, D. Orchard, S. Weerawarana, Editors.  World
+             Wide Web Consortium, &draft.day; &draft.month; &draft.year;. 
+             This version of the "&part2.title;" Specification is
+ 	    available at &w3c-designation-part2;. The <loc href="&part2.latest;">latest version of
+             "&part2.title;"</loc> is available at &part2.latest;.
+           </bibl>
            <bibl id="XML10" key="XML 1.0" href="http://www.w3.org/TR/2004/REC-xml-20040204/">
              <titleref>Extensible Markup Language (XML) 1.0 (Third
***************
*** 974,977 ****
--- 766,774 ----
  	    -->
  
+             <tr>
+                 <td>20061107</td>
+                 <td>aal</td>
+                 <td>First pass revision/cleanup, mostly removing things.</td>
+             </tr>
  	    <tr>
  	    	<td>20061025</td>
Received on Tuesday, 7 November 2006 18:25:25 UTC

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