- From: Jean-Jacques Moreau via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 25 Oct 2006 08:05:05 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv18854
Added Files:
wsdl20-additional-meps.xml
Log Message:
New document containing additional MEPs (moved out of Part2).
--- NEW FILE: wsdl20-additional-meps.xml ---
<?xml version="1.0" encoding="utf-8"?>
<!-- $Id: wsdl20-additional-meps.xml,v 1.1 2006/10/25 08:05:02 jmoreau Exp $ -->
<?xml-stylesheet type='text/xsl' href='xmlspec-wsdl.xsl'?>
<!DOCTYPE spec PUBLIC
"-//W3C//DTD Specification V2.2+WSDL//EN"
"xmlspec.dtd" [
<!ENTITY component-table SYSTEM "adjuncts-component-table.xml">
<!ENTITY component-assertion-table SYSTEM "adjuncts-component-assertion-table.xml">
<!ENTITY document-assertion-table SYSTEM "adjuncts-document-assertion-table.xml">
<!ENTITY exchange-assertion-table SYSTEM "adjuncts-exchange-assertion-table.xml">
<!ENTITY assertion-summary SYSTEM "adjuncts-assertion-summary.xml">
<!ENTITY extra-ack "">
<!ENTITY % entities SYSTEM "entities.dtd" >
<!-- Should move the following entitites to ENTITY.dtd -->
<!ENTITY prefix "wsdl20-additional-meps">
<!ENTITY additionalmeps.title "WSDL 2.0 Additional MEPs">
<!ENTITY additionalmeps.prefix "wsdl20-additional-meps">
<!ENTITY w3c-designation-additionalmeps "&additionalmeps.prefix;.html">
<!ENTITY additionalmeps.latest "&w3c.tr.latest;/&additionalmeps.prefix;">
<!-- -->
%entities;
<!ENTITY document.status "Editors' copy $Date: 2006/10/25 08:05:02 $">
<!ENTITY thisdoc.title "&additionalmeps.title;">
<!ENTITY prevloc "http://none">
<!ENTITY status SYSTEM "status-adjuncts.xml">
]>
<spec w3c-doctype="&document.type;" role="&document.role;">
<header>
<title>&additionalmeps.title;</title>
<w3c-designation>&w3c-designation-additionalmeps;</w3c-designation>
<w3c-doctype>&document.status;</w3c-doctype>
<pubdate>
<day>&draft.day;</day>
<month>&draft.month;</month>
<year>&draft.year;</year>
</pubdate>
<publoc>
<loc
href="&w3c-designation-additionalmeps;">&w3c-designation-additionalmeps;</loc>
</publoc>
&altlocs;
<prevlocs>
<loc href="&prevloc;">&prevloc;</loc>
</prevlocs>
<latestloc>
<loc href="&additionalmeps.latest;">&additionalmeps.latest;</loc>
</latestloc>
<authlist>
<author>
<name>Amelia A. Lewis</name>
<affiliation>TIBCO Software</affiliation>
</author>
</authlist>
<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.
&additionalmeps.title; specifies predefined extensions for use in WSDL 2.0:
</p>
<ulist>
<item><p>Message exchange patterns</p></item>
</ulist>
<p>
This
specification depends on WSDL Version 2.0 <bibref ref="WSDL-PART2"/>.
</p>
</abstract>
&status;
<langusage>
<language id="en">English</language>
</langusage>
<revisiondesc>
<p>Last Modified: $Date: 2006/10/25 08:05:02 $ CET</p>
</revisiondesc>
</header>
<body>
<!-- *************************************************************** -->
<div1 id="intro">
<head>Introduction</head>
<p> The Web Services Description Language WSDL Version 2.0 (WSDL)
<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
communication. This document defines extensions for the WSDL 2.0
language:</p>
<ulist>
<item><p>Message exchange patterns: <specref ref='meps'/></p></item>
</ulist>
<p> WSDL 2.0 Primer <bibref ref="WSDL-PART0"/> is a non-normative
document intended to provide an easily understandable tutorial on the
features of the WSDL Version 2.0 specifications. </p>
<p> The Core Language <bibref ref="WSDL-PART1"/> of the WSDL 2.0
specification describes the core elements of the WSDL language. </p>
<!-- +++++++++ -->
<div2 id="notcon">
<head>Notational Conventions</head>
<p>The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC2119 <bibref ref="RFC2119"/>.</p>
<p>This specification uses a number of namespace prefixes throughout;
they are listed in <specref ref="tabprefns"/>. Note that the choice of
any namespace prefix is arbitrary and not semantically significant
(see <bibref ref="XMLInfoSet"/>).</p>
<table border="1" summary="Mapping of prefixes used in this document to their
 associated namespace name" id="tabprefns">
<caption>Prefixes and Namespaces used in this specification</caption>
<tbody>
<tr>
<th rowspan="1" colspan="1">Prefix</th>
<th rowspan="1" colspan="1">Namespace</th>
<th rowspan="1" colspan="1">Notes</th>
</tr>
<tr>
<td rowspan="1" colspan="1">wsdl</td>
<td rowspan="1" colspan="1">
<attval>&wsdl-ns;</attval>
</td>
<td rowspan="1" colspan="1">
This namespace is defined in <bibref ref="WSDL-PART1"/>.
A normative XML Schema <bibref ref="XMLSchemaP1"/>,
<bibref ref="XMLSchemaP2"/> document for the
<attval>&wsdl-ns;</attval>
namespace can be found at <loc
href="&wsdl-ns;">&wsdl-ns;</loc>. This namespace is used as
the default namespace throughout this specification.</td>
</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">
<attval>&wsdl-soap-ns;</attval>
</td>
<td rowspan="1" colspan="1">Defined by this
specification. A normative XML Schema <bibref ref="XMLSchemaP1"/>,
<bibref ref="XMLSchemaP2"/> document for the
<attval>&wsdl-soap-ns;</attval>
namespace can be found at <loc href="&wsdl-soap-ns;">&wsdl-soap-ns;</loc>.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">whttp</td>
<td rowspan="1" colspan="1">
<attval>&wsdl-http-ns;</attval>
</td>
<td rowspan="1" colspan="1">Defined by this
specification. A normative XML Schema <bibref ref="XMLSchemaP1"/>,
<bibref ref="XMLSchemaP2"/> document for the
<attval>&wsdl-http-ns;</attval>
namespace can be found at <loc href="&wsdl-http-ns;">&wsdl-http-ns;</loc>.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">wrpc</td>
<td rowspan="1" colspan="1">
<attval>&wsdl-rpc-ns;</attval>
</td>
<td rowspan="1" colspan="1">Defined by this
specification. A normative XML Schema <bibref ref="XMLSchemaP1"/>,
<bibref ref="XMLSchemaP2"/> document for the
<attval>&wsdl-rpc-ns;</attval>
namespace can be found at <loc href="&wsdl-rpc-ns;">&wsdl-rpc-ns;</loc>.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">xs</td>
<td rowspan="1" colspan="1">
<attval>http://www.w3.org/2001/XMLSchema</attval>
</td>
<td rowspan="1" colspan="1">Defined in the W3C XML Schema
specification <bibref ref="XMLSchemaP1"/>, <bibref ref="XMLSchemaP2"/>.</td>
</tr>
</tbody>
</table>
<p>Namespace names of the general form
<attval>http://example.org/...</attval> and
<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>
<div2 id="assertions">
<head>Assertions</head>
<p>
Assertions about WSDL 2.0 documents and components that are
not enforced by the normative XML schema for WSDL 2.0 are
marked by a dagger symbol (†) at the end of a
sentence. Each assertion has been assigned a unique
identifier that consists of a descriptive textual prefix and
a unique numeric suffix. The numeric suffixes are assigned
sequentially and never reused so there may be gaps in the
sequence. The assertion identifiers MAY be used by
implementations of this specification for any purpose,
e.g. error reporting.
</p>
<p>
The assertions and their identifiers are summarized in
section <specref ref="assertionsummary" />.
</p>
</div2>
</div1>
<!-- *************************************************************** -->
<div1 id="meps">
<head>Additional Message Exchange Patterns</head>
<p>
Web Services Description Language (WSDL) message exchange patterns (hereafter simply
'patterns') define the sequence and cardinality of abstract messages listed in
an operation. Message exchange patterns also define which other nodes send
messages to, and receive messages from, the service implementing the operation.
</p>
<p>
A <emph>node</emph> is an agent (<xspecref href="http://www.w3.org/TR/2004/NOTE-ws-arch-20040211/#agent">section 2.3.2.2
Agent of the Web Services Architecture</xspecref> <bibref ref="wsarch" />) that can transmit and/or receive message(s)
described in WSDL description(s) and process them.
</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>
<p>
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>
By design, WSDL message exchange patterns abstract out specific message types.
Patterns identify placeholders for messages, and placeholders are
associated with specific message types by the operation using the
pattern.
</p>
<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 messages are sent over a single or multiple channels.
</p>
<p>
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.
</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>
<p>This specification defines several message exchange patterns for
use with <emph>WSDL Version 2.0 Part 1: Core Language</emph> <bibref
ref='WSDL-PART1' />.</p>
<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
willing to do so. It is recommended that the patterns use the general
template provided here, after examination of existing predefined patterns.</p>
<div3 id="template-sample">
<head>Pattern Name</head>
<p>This pattern consists of [number] message[s, in order] as follows:</p>
<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>
<item><p>[received from|sent to] ['some' if first mention] node [node
identifier]</p></item>
</olist>
<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>
<p>Note: In the template, the bracketed items indicate a replacement operation.
Substitute the correct terms for each bracketed item.</p>
<p>Note: the "received from" and "sent to" are always from the point of
view of the service, and participating nodes other than the service are
implicitly identified as the originators of or destinations for
messages in the exchange.</p>
</div3>
</div2>
<div2 id="fault-rules">
<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>
<div2 id="patterns">
<head>Message Exchange Patterns</head>
<p>WSDL patterns are described in terms of the WSDL component model,
specifically the <comp>Interface Message Reference</comp>
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>
<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>
<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>An optional 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="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
with the value <attval>&wsdl-mep-in-opt-out;</attval>.</p>
</div3>
<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>
<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 some node N
</p>
</item>
</ulist>
</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
a <prop comp="Interface Operation">message exchange pattern</prop> property with
the value <attval>&wsdl-mep-out-only;</attval>.
</p>
</div3>
<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>
<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 some node N</p></item>
</ulist>
</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
the value <attval>&wsdl-mep-robust-out-only;</attval>.</p>
</div3>
<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>
<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 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>In</attval> and <prop comp="Interface Message Reference">direction</prop> is <attval>in</attval>
</p>
</item>
<item>
<p>
sent from node N
</p>
</item>
</ulist>
</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
a <prop comp="Interface Operation">message exchange pattern</prop> property with
the value <attval>&wsdl-mep-out-in;</attval>.
</p>
</div3>
<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>
<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 some node N</p></item>
</ulist>
</item>
<item><p>An optional 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>sent from node N</p></item>
</ulist>
</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
the value <attval>&wsdl-mep-out-opt-in;</attval>.</p>
</div3>
</div2><!-- message exchange patterns -->
<div2 id='mep-sec-sec'>
<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>
</div1><!-- section on meps -->
<div1 id="References">
<head>References</head>
<div2 id="Normative-References">
<head>Normative References</head>
<blist>
<bibl id="Canonical" key="Canonical XML" href="http://www.w3.org/TR/2001/REC-xml-c14n-20010315">
<titleref>Canonical XML</titleref>, J. Boyer, Author. World
Wide Web Consortium, 15 March 2001. This version of the
Canonical XML Recommendation is
http://www.w3.org/TR/2001/REC-xml-c14n-20010315. The <loc href="http://www.w3.org/TR/xml-c14n">latest version of
Canonical XML</loc> is available at
http://www.w3.org/TR/xml-c14n.
</bibl>
<bibl key="IETF RFC 2119" href="http://www.ietf.org/rfc/rfc2119.txt" id="RFC2119">
<titleref>Key words for use in RFCs to Indicate Requirement
Levels</titleref>, S. Bradner, Author. Internet Engineering
Task Force, June 1999. Available at
http://www.ietf.org/rfc/rfc2119.txt.
</bibl>
<bibl id="RFC2388" key="IETF RFC 2388" href="http://www.ietf.org/rfc/rfc2388.txt">
<titleref>Returning Values from Forms:
multipart/form-data</titleref>, L. Masinter,
Author. Internet Engineering Task Force, August
1998. Available at http://www.ietf.org/rfc/rfc2388.txt.
</bibl>
<bibl id="RFC2616" key="IETF RFC 2616" href="http://www.ietf.org/rfc/rfc2616.txt">
<titleref>Hypertext Transfer Protocol --
HTTP/1.1</titleref>, R. Fielding, J. Gettys, J. Mogul,
H. Frystyk, L. Masinter, P. Leach, T. Berners-Lee,
Authors. Internet Engineering Task Force, June
1999. Available at http://www.ietf.org/rfc/rfc2616.txt.
</bibl>
<bibl id="RFC2617" key="IETF RFC 2617" href="http://www.ietf.org/rfc/rfc2617.txt">
<titleref
>HTTP Authentication:
Basic and Digest Access
Authentication</titleref>, J. Franks,
P. Hallam-Baker, J. Hostetler, S. Lawrence,
P. Leach, A. Luotonen, L. Stewart, June
1999. Available at http://www.ietf.org/rfc/rfc2616.txt.
</bibl>
<bibl id="RFC2818" key="IETF RFC 2818" href="http://www.ietf.org/rfc/rfc2818.txt">
<titleref>HTTP Over TLS</titleref>,
E. Rescorla, Author. Internet Engineering
Task Force, May 2000. Available at
http://www.ietf.org/rfc/rfc2818.txt.
</bibl>
<bibl key="IETF RFC 2965" href="http://www.ietf.org/rfc/rfc2965.txt" id="RFC2965">
<titleref>HTTP State Management Mechanism</titleref>, D. Kristol, L. Montulli Authors. Internet Engineering
Task Force, October 2000. Available at
http://www.ietf.org/rfc/rfc2965.txt.
</bibl>
<bibl key="IETF RFC 3023" href="http://www.ietf.org/rfc/rfc3023.txt" id="RFC3023">
<titleref>XML Media Types</titleref>, M. Murata,
S. St. Laurent, D. Kohn, Authors. Internet Engineering Task
Force, January 2001. Available at
http://www.ietf.org/rfc/rfc3023.txt.
</bibl>
<bibl key="IETF RFC 3205" href="http://www.ietf.org/rfc/rfc3205.txt" id="RFC3205">
<titleref>On the use of HTTP as a Substrate</titleref>, K. Moore, Authors. Internet Engineering Task
Force, February 2002. Available at
http://www.ietf.org/rfc/rfc3205.txt.
</bibl>
<bibl id="RFC3986" key="IETF RFC 3986" href="http://www.ietf.org/rfc/rfc3986.txt">
<titleref>Uniform Resource Identifiers (URI): Generic
Syntax</titleref>, T. Berners-Lee, R. Fielding, L. Masinter,
Authors. Internet Engineering Task Force, January 2005. Available at http://www.ietf.org/rfc/rfc3986.txt.
</bibl>
<bibl id="RFC3987" key="IETF RFC 3987" href="http://www.ietf.org/rfc/rfc3987.txt">
<titleref>Internationalized Resource Identifiers
(IRIs)</titleref>, M. Duerst, M. Suignard,
Authors. Internet Engineering Task Force, January
2005. Available at http://www.ietf.org/rfc/rfc3987.txt.
</bibl>
<bibl id="XForms10" key="XForms 1.0" href="http://www.w3.org/TR/2003/REC-xforms-20031014/">
<titleref>XForms 1.0</titleref>, M. Dubinko, et al.,
Editors. World Wide Web Consortium, 14 October 2003. This
version of the XForms 1.0 Recommendation is
http://www.w3.org/TR/2003/REC-xforms-20031014/. The <loc href="http://www.w3.org/TR/xforms/">latest version of XForms
1.0</loc> is available at http://www.w3.org/TR/xforms/.
</bibl>
<bibl id="SOAP12-PART1" key="SOAP 1.2 Part 1: Messaging Framework" href="http://www.w3.org/TR/2003/REC-soap12-part1-20030624/">
<titleref>SOAP Version 1.2 Part 1: Messaging
Framework</titleref>, M. Gudgin, M. Hadley, N. Mendelsohn,
J-J. Moreau, H. Frystyk Nielsen, Editors. World Wide Web
Consortium, 24 June 2003. This version of the "SOAP Version
1.2 Part 1: Messaging Framework" Recommendation is
http://www.w3.org/TR/2003/REC-soap12-part1-20030624/. The
<loc href="http://www.w3.org/TR/soap12-part1/">latest
version of "SOAP Version 1.2 Part 1: Messaging
Framework"</loc> is available at
http://www.w3.org/TR/soap12-part1/.
</bibl>
<bibl id="SOAP12-PART2" key="SOAP 1.2 Part 2: Adjuncts" href="http://www.w3.org/TR/2003/REC-soap12-part2-20030624/">
<titleref>SOAP Version 1.2 Part 2: Adjuncts</titleref>,
M. Gudgin, M. Hadley, N. Mendelsohn, J-J. Moreau, and
H. Frystyk Nielsen, Editors. World Wide Web Consortium, 7
May 2003. This version of the "SOAP Version 1.2 Part 2:
Adjuncts" Recommendation is
http://www.w3.org/TR/2003/REC-soap12-part2-20030624/. The
<loc href="http://www.w3.org/TR/soap12-part2/">latest
version of "SOAP Version 1.2 Part 2: Adjuncts"</loc> is
available at http://www.w3.org/TR/soap12-part2/.
</bibl>
<bibl id="webarch" key="Web Architecture"
href="http://www.w3.org/TR/2004/REC-webarch-20041215/">
<titleref>Architecture of the World Wide Web, Volume
One</titleref>, I. Jacobs, and N. Walsh, Editors. World
Wide Web Consortium, 15 December 2004. This version of
the "Architecture of the World Wide Web, Volume One"
Recommendation is
http://www.w3.org/TR/2004/REC-webarch-20041215/. The <loc
href="http://www.w3.org/TR/webarch/">latest version of
"Architecture of the World Wide Web, Volume One"</loc> is
available at http://www.w3.org/TR/webarch/.
</bibl>
<bibl id="wsarch" key="Web Services Architecture" href="http://www.w3.org/TR/2004/NOTE-ws-arch-20040211/">
<titleref>Web Services Architecture</titleref>,
David Booth, Hugo Haas, Francis McCabe, Eric Newcomer, Michael Champion, Chris Ferris, David Orchard, Editors.
World Wide Web Consortium,
11 February 2004.
This version of the
"Web Services Architecture" Working Group Note is
http://www.w3.org/TR/2004/NOTE-ws-arch-20040211/. The <loc href="http://www.w3.org/TR/ws-arch/">latest version of
"Web Services Architecture"</loc> is available at
http://www.w3.org/TR/ws-arch/.
</bibl>
<bibl key="WSDL 2.0 Core Language" href="&w3c-designation-part1;" id="WSDL-PART1">
<titleref>&part1.title;</titleref>, R. Chinnici, M. Gudgin, J-J. Moreau,
S. Weerawarana, Editors. World Wide Web Consortium,
&draft.day; &draft.month;
&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
Edition)</titleref>, T. Bray, J. Paoli,
C. M. Sperberg-McQueen, E. Maler, and F. Yergeau, Editors. World Wide
Web Consortium, 4 February 2004. This version of the XML 1.0 Recommendation is
http://www.w3.org/TR/2004/REC-xml-20040204/. The <loc href="http://www.w3.org/TR/REC-xml">latest version of "Extensible Markup Language (XML) 1.0"</loc> is available at http://www.w3.org/TR/REC-xml.
</bibl>
<bibl id="XMLInfoSet" key="XML Information Set" href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204">
<titleref>XML Information Set (Second Edition)</titleref>, J. Cowan and R.
Tobin, Editors. World Wide Web Consortium, 4 February 2004.
This version of the XML Information Set Recommendation is
http://www.w3.org/TR/2004/REC-xml-infoset-20040204. The <loc href="http://www.w3.org/TR/xml-infoset">latest version of
XML Information Set</loc> is available at
http://www.w3.org/TR/xml-infoset.
</bibl>
<!--
<bibl id='XMLNS' key='XML Namespaces'
href='http://www.w3.org/TR/1999/REC-xml-names-19990114'>
<titleref>Namespaces in XML</titleref>, T. Bray, D.
Hollander, and A. Layman, Editors. World Wide Web
Consortium, 14 January 1999. This version of the XML
Information Set Recommendation is
http://www.w3.org/TR/1999/REC-xml-names-19990114. The <loc
href='http://www.w3.org/TR/REC-xml-names'>latest version of
Namespaces in XML</loc> is available at
http://www.w3.org/TR/REC-xml-names.
</bibl>
-->
<bibl id="XMLSchemaP1" key="XML Schema Structures" href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/">
<titleref>XML Schema Part 1: Structures Second Edition</titleref>,
H. Thompson, D. Beech, M. Maloney, and N. Mendelsohn,
Editors. World Wide Web Consortium, 28 October 2004. This version
of the XML Schema Part 1 Recommendation is
http://www.w3.org/TR/2004/REC-xmlschema-1-20041028. The <loc href="http://www.w3.org/TR/xmlschema-1/">latest version of
XML Schema Part 1</loc> is available at
http://www.w3.org/TR/xmlschema-1.
</bibl>
<bibl key="XML Schema Datatypes" id="XMLSchemaP2" href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/">
<titleref>XML Schema Part 2: Datatypes Second Edition</titleref>, P. Byron
and A. Malhotra, Editors. World Wide Web Consortium, 28
October 2004. This version of the XML Schema Part 2 Recommendation is
http://www.w3.org/TR/2004/REC-xmlschema-2-20041028. The <loc href="http://www.w3.org/TR/xmlschema-2/">latest version of
XML Schema Part 2</loc> is available at
http://www.w3.org/TR/xmlschema-2.
</bibl>
</blist>
</div2>
<div2 id="Informative-References">
<head>Informative References</head>
<blist>
<bibl id="MTOM" key="SOAP Message Transmission Optimization Mechanism" href="http://www.w3.org/TR/2005/REC-soap12-mtom-20050125/">
<titleref>SOAP Message Transmission Optimization
Mechanism</titleref>, N. Mendelsohn, M. Nottingham, and
H. Ruellan, Editors. World Wide Web Consortium, W3C
Recommendation, 25 January 2005. This version of SOAP
Message Transmission Optimization Mechanism is
http://www.w3.org/TR/2005/REC-soap12-mtom-20050125/. The
<loc href='http://www.w3.org/TR/soap12-mtom/'>latest
version of the "SOAP Message Transmission Optimization
Mechanism" document</loc> is available from
http://www.w3.org/TR/soap12-mtom/.
</bibl>
<bibl key="WSA 1.0 Core" href="http://www.w3.org/TR/2005/CR-ws-addr-core-20050817/" id="WSA-Core">
<titleref>Web Services Addressing 1.0 - Core</titleref>
, M. Gudgin, M. Hadley, Editors. World Wide Web Consortium,
17 August 2005<!--&draft.day; &draft.month; &draft.year;-->. This
version of Web Services Addressing 1.0 - Core is
http://www.w3.org/TR/2005/CR-ws-addr-core-20050817/
The latest version of the "Web Services Addressing 1.0 - Core"
document is available from http://www.w3.org/TR/ws-addr-core.
</bibl>
<bibl key="WSDL 2.0 Primer"
href="&w3c-designation-part0;" id="WSDL-PART0">
<titleref>
&part0.title;
</titleref>, D.Booth, C.K. Liu , Editors. World
Wide Web Consortium, &draft.day; &draft.month;
&draft.year;. This version of the "&part0.title;"
Specification is available at
&w3c-designation-part0;. The
<loc href="&part0.latest;">
latest version of "&part0.title;"
</loc>
is available at
&part0.latest;.
</bibl>
</blist>
</div2>
</div1>
</body>
<back>
&acknowledgements;
<inform-div1 id="changelog">
<head>Part 2 Change Log</head>
<table id="wsdl-spec-changelog-table" border="1" width="100%">
<col width="10%"/>
<col width="10%"/>
<col width="80%"/>
<tbody>
<tr>
<th rowspan="1" colspan="1">Date</th>
<th rowspan="1" colspan="1">Author</th>
<th rowspan="1" colspan="1">Description</th>
</tr>
<!-- template
<tr>
<td>200604</td>
<td></td>
<td></td>
</tr>
-->
<tr>
<td>20061025</td>
<td>JJM</td>
<td>Created skeleton document from Part 2.</td>
</tr>
</tbody>
</table>
</inform-div1>
</back>
</spec>
Received on Wednesday, 25 October 2006 08:05:48 UTC