_[_W_3_C_]
************ WWeebb SSeerrvviicceess DDeessccrriippttiioonn LLaanngguuaaggee ((WWSSDDLL)) VVeerrssiioonn 22..00 PPaarrtt 22:: MMeessssaaggee
EExxcchhaannggee PPaatttteerrnnss ************
********** WW33CC WWoorrkkiinngg DDrraafftt 2266 MMaarrcchh 22000044 **********
  This version:
      _h_t_t_p_:_/_/_w_w_w_._w_3_._o_r_g_/_T_R_/_2_0_0_4_/_W_D_-_w_s_d_l_2_0_-_p_a_t_t_e_r_n_s_-_2_0_0_4_0_3_2_6
  Latest version:
      _h_t_t_p_:_/_/_w_w_w_._w_3_._o_r_g_/_T_R_/_w_s_d_l_2_0_-_p_a_t_t_e_r_n_s
  Previous versions:
      _h_t_t_p_:_/_/_w_w_w_._w_3_._o_r_g_/_T_R_/_2_0_0_3_/_W_D_-_w_s_d_l_2_0_-_p_a_t_t_e_r_n_s_-_2_0_0_3_1_1_1_0
  Editors:
      Martin Gudgin, Microsoft
      Amy Lewis, TIBCO
      Jeffrey Schlimmer, Microsoft
This document is also available in these non-normative formats: _p_o_s_t_s_c_r_i_p_t,
_P_D_F, _X_M_L, and _p_l_a_i_n_ _t_e_x_t.
_C_o_p_y_r_i_g_h_t © 2004 _W_3_C® (_M_I_T, _E_R_C_I_M, _K_e_i_o), All Rights Reserved. W3C _l_i_a_b_i_l_i_t_y,
_t_r_a_d_e_m_a_r_k, _d_o_c_u_m_e_n_t_ _u_s_e and _s_o_f_t_w_a_r_e_ _l_i_c_e_n_s_i_n_g rules apply.
===============================================================================
********** AAbbssttrraacctt **********
This document describes Web Services Description Language (WSDL) Version 2.0
message exchange patterns. These patterns are intended for use with the Web
Services Description Language (WSDL).
********** SSttaattuuss ooff tthhiiss DDooccuummeenntt **********
TThhiiss sseeccttiioonn ddeessccrriibbeess tthhee ssttaattuuss ooff tthhiiss ddooccuummeenntt aatt tthhee ttiimmee ooff iittss
ppuubblliiccaattiioonn.. OOtthheerr ddooccuummeennttss mmaayy ssuuppeerrsseeddee tthhiiss ddooccuummeenntt.. AA lliisstt ooff ccuurrrreenntt WW33CC
ppuubblliiccaattiioonnss aanndd tthhee llaatteesstt rreevviissiioonn ooff tthhiiss tteecchhnniiccaall rreeppoorrtt ccaann bbee ffoouunndd iinn
tthhee _WW_33_CC_ _tt_ee_cc_hh_nn_ii_cc_aa_ll_ _rr_ee_pp_oo_rr_tt_ss_ _ii_nn_dd_ee_xx aatt hhttttpp::////wwwwww..ww33..oorrgg//TTRR//..
This is a _W_3_C_ _W_o_r_k_i_n_g_ _D_r_a_f_t of the WSDL Version 2.0 Message Patterns
specification for review by W3C members and other interested parties.
A _d_i_f_f_-_m_a_r_k_e_d_ _v_e_r_s_i_o_n_ _a_g_a_i_n_s_t_ _t_h_e_ _p_r_e_v_i_o_u_s_ _v_e_r_s_i_o_n_ _o_f_ _t_h_i_s_ _d_o_c_u_m_e_n_t is
available. For a detailed list of changes since the last publication of this
document, please refer to appendix _BB_.._ _CC_hh_aa_nn_gg_ee_ _LL_oo_gg. A _l_i_s_t_ _o_f_ _o_p_e_n_ _i_s_s_u_e_s_ _a_g_a_i_n_s_t
_t_h_i_s_ _d_o_c_u_m_e_n_t is also available.
This document has been produced as part of the _W_3_C_ _W_e_b_ _S_e_r_v_i_c_e_s_ _A_c_t_i_v_i_t_y. The
authors of this document are the _W_e_b_ _S_e_r_v_i_c_e_s_ _D_e_s_c_r_i_p_t_i_o_n_ _W_o_r_k_i_n_g Group
members.
Publication as a Working Draft does not imply endorsement by the W3C
Membership. This is a draft document and may be updated, replaced or obsoleted
by other documents at any time. It is inappropriate to cite this document as
other than work in progress.
Comments on this document are invited and are to be sent to the public _w_w_w_-_w_s_-
_d_e_s_c_@_w_3_._o_r_g mailing list (_p_u_b_l_i_c_ _a_r_c_h_i_v_e).
This document has been produced under the _2_4_ _J_a_n_u_a_r_y_ _2_0_0_2_ _C_u_r_r_e_n_t_ _P_a_t_e_n_t
_P_r_a_c_t_i_c_e as amended by the _W_3_C_ _P_a_t_e_n_t_ _P_o_l_i_c_y_ _T_r_a_n_s_i_t_i_o_n_ _P_r_o_c_e_d_u_r_e. Patent
disclosures relevant to this specification may be found on the Working Group's
_p_a_t_e_n_t_ _d_i_s_c_l_o_s_u_r_e_ _p_a_g_e. An individual who has actual knowledge of a patent
which the individual believes contains Essential Claim(s) with respect to this
specification should disclose the information in accordance with _s_e_c_t_i_o_n_ _6_ _o_f
_t_h_e_ _W_3_C_ _P_a_t_e_n_t_ _P_o_l_i_c_y.
===============================================================================
********** SShhoorrtt TTaabbllee ooff CCoonntteennttss **********
1. _I_n_t_r_o_d_u_c_t_i_o_n
2. _F_a_u_l_t_ _G_e_n_e_r_a_t_i_o_n_ _R_u_l_e_s
3. _M_e_s_s_a_g_e_ _E_x_c_h_a_n_g_e_ _P_a_t_t_e_r_n_s
4. _R_e_f_e_r_e_n_c_e_s
A. _A_c_k_n_o_w_l_e_d_g_e_m_e_n_t_s (Non-Normative)
B. _C_h_a_n_g_e_ _L_o_g (Non-Normative)
===============================================================================
********** TTaabbllee ooff CCoonntteennttss **********
1. _I_n_t_r_o_d_u_c_t_i_o_n
    1.1 _N_o_t_a_t_i_o_n_a_l_ _C_o_n_v_e_n_t_i_o_n_s
2. _F_a_u_l_t_ _G_e_n_e_r_a_t_i_o_n_ _R_u_l_e_s
    2.1 _F_a_u_l_t_ _R_e_p_l_a_c_e_s_ _M_e_s_s_a_g_e
    2.2 _M_e_s_s_a_g_e_ _T_r_i_g_g_e_r_s_ _F_a_u_l_t
    2.3 _N_o_ _F_a_u_l_t_s
3. _M_e_s_s_a_g_e_ _E_x_c_h_a_n_g_e_ _P_a_t_t_e_r_n_s
    3.1 _I_n_-_O_n_l_y
    3.2 _R_o_b_u_s_t_ _I_n_-_O_n_l_y
    3.3 _I_n_-_O_u_t
    3.4 _I_n_-_O_p_t_i_o_n_a_l_-_O_u_t
    3.5 _O_u_t_-_O_n_l_y
    3.6 _R_o_b_u_s_t_ _O_u_t_-_O_n_l_y
    3.7 _O_u_t_-_I_n
    3.8 _O_u_t_-_O_p_t_i_o_n_a_l_-_I_n
4. _R_e_f_e_r_e_n_c_e_s
    4.1 _N_o_r_m_a_t_i_v_e_ _R_e_f_e_r_e_n_c_e_s
    4.2 _I_n_f_o_r_m_a_t_i_v_e_ _R_e_f_e_r_e_n_c_e_s
******** AAppppeennddiicceess ********
A. _A_c_k_n_o_w_l_e_d_g_e_m_e_n_t_s (Non-Normative)
B. _C_h_a_n_g_e_ _L_o_g (Non-Normative)
    B.1 _C_h_a_n_g_e_s
===============================================================================
11.. IInnttrroodduuccttiioonn
Web Services Description Language (WSDL) message exchange 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.
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.
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.
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.
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.
This specification defines several message exchange patterns for use with WWSSDDLL
VVeerrssiioonn 22..00 PPaarrtt 11:: CCoorree LLaanngguuaaggee [_W_S_D_L_ _2_._0_ _C_o_r_e_ _L_a_n_g_u_a_g_e].
11..11 NNoottaattiioonnaall CCoonnvveennttiioonnss
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 RFC 2119 [_I_E_T_F_ _R_F_C_ _2_1_1_9].
22.. FFaauulltt GGeenneerraattiioonn RRuulleess
WSDL patterns specify their fault generation model using standard rulesets to
indicate where faults may occur. The two most common patterns for fault
generation are defined here, and referenced by patterns later in the document.
Generation of a fault, regardless of ruleset, terminates the exchange.
22..11 FFaauulltt RReeppllaacceess MMeessssaaggee
Any message after the first in the pattern MAY be replaced with a fault
message, which MUST have identical cardinality and direction. The fault message
MUST be delivered to the same target node as the message it replaces.
22..22 MMeessssaaggee TTrriiggggeerrss FFaauulltt
Any message, including the first, MAY trigger a fault message in response. Each
recipient MAY generate a fault message, and MUST generate no more than one
fault for each triggering message. Each fault message has direction the reverse
of its triggering message. The fault message MUST be delivered to the
originator of the message which triggered it. If there is no path to this node,
the fault MUST be discarded.
22..33 NNoo FFaauullttss
No faults may be generated.
 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
|_EE_dd_ii_tt_oo_rr_ii_aa_ll_ _nn_oo_tt_ee_::_ _II_nn_tt_rr_oo_dd_uu_cc_tt_ii_oo_nn_ _oo_ff_ _NN_oo_ _FF_aa_uu_ll_tt_ss_ _rr_uu_ll_ee_ss_ee_tt_|_ _ _ _ _ _ _ _ _ _ _ _ _ _ _1_2_ _J_u_n_e_ _2_0_0_3|
|The No Faults ruleset has been introduced primarily to clarify the confusion|
|otherwise introduced by applying the Fault Replaces Message ruleset to      |
|single-message patterns (which implicitly disallows faults). Some concern   |
|_h_a_s_ _b_e_e_n_ _e_x_p_r_e_s_s_e_d_ _t_h_a_t_ _a_ _n_o_-_f_a_u_l_t_ _r_u_l_e_s_e_t_ _c_o_u_l_d_ _e_a_s_i_l_y_ _b_e_ _a_b_u_s_e_d_._ _ _ _ _ _ _ _ _ _ |
33.. MMeessssaaggee EExxcchhaannggee PPaatttteerrnnss
WSDL patterns are described in terms of the WSDL component model, specifically
the Label and Fault Reference components.
33..11 IInn--OOnnllyy
This pattern consists of exactly one message as follows:
   1. A message:
          o indicated by a Label component whose {label} is 'In' and
            {direction} is 'in'
          o received from some node N
This pattern uses the rule _22_.._33_ _NN_oo_ _FF_aa_uu_ll_tt_ss.
An operation using this message exchange pattern has a {pattern} property with
the value 'http://www.w3.org/2004/03/wsdl/in-only'.
33..22 RRoobbuusstt IInn--OOnnllyy
This pattern consists of exactly one message as follows:
   1. message:
          o indicated by a Label component whose {label} is 'In' and
            {direction} is 'in'
          o received from some node N
This pattern uses the rule _22_.._22_ _MM_ee_ss_ss_aa_gg_ee_ _TT_rr_ii_gg_gg_ee_rr_ss_ _FF_aa_uu_ll_tt.
An operation using this message exchange pattern has a {pattern} property with
the value 'http://www.w3.org/2004/03/wsdl/robust-in-only'.
33..33 IInn--OOuutt
This pattern consists of exactly two messages, in order, as follows:
   1. A message:
          o indicated by a Label component whose {label} is 'In' and
            {direction} is 'in'
          o received from some node N
   2. A message:
          o indicated by a Label component whose {label} is 'Out' and
            {direction} is 'out'
          o sent to node N
This pattern uses the rule _22_.._11_ _FF_aa_uu_ll_tt_ _RR_ee_pp_ll_aa_cc_ee_ss_ _MM_ee_ss_ss_aa_gg_ee.
An operation using this message exchange pattern has a {pattern} property with
the value 'http://www.w3.org/2004/03/wsdl/in-out'.
33..44 IInn--OOppttiioonnaall--OOuutt
This pattern consists of one or two messages, in order, as follows:
   1. A message:
          o indicated by a Label component whose {label} is 'In' and
            {direction} is 'in'
          o received from some node N
   2. An optional message:
          o indicated by a Label component whose {label} is 'Out' and
            {direction} is 'out'
          o sent to node N
This pattern uses the rule _22_.._22_ _MM_ee_ss_ss_aa_gg_ee_ _TT_rr_ii_gg_gg_ee_rr_ss_ _FF_aa_uu_ll_tt.
An operation using this message exchange pattern has a {pattern} property with
the value 'http://www.w3.org/2004/03/wsdl/in-opt-out'.
33..55 OOuutt--OOnnllyy
This pattern consists of exactly one message as follows:
   1. A message:
          o indicated by a Label component whose {label} is 'Out' and
            {direction} is 'out'
          o sent to some node N
This pattern uses the rule _22_.._33_ _NN_oo_ _FF_aa_uu_ll_tt_ss.
An operation using this message exchange pattern has a {pattern} property with
the value 'http://www.w3.org/2004/03/wsdl/out-only'.
33..66 RRoobbuusstt OOuutt--OOnnllyy
This pattern consists of exactly one message as follows:
   1. message:
          o indicated by a Label component whose {label} is 'Out' and
            {direction} is 'out'
          o sent to some node N
This pattern uses the rule _22_.._22_ _MM_ee_ss_ss_aa_gg_ee_ _TT_rr_ii_gg_gg_ee_rr_ss_ _FF_aa_uu_ll_tt.
An operation using this message exchange pattern has a {pattern} property with
the value 'http://www.w3.org/2004/03/wsdl/robust-out-only'.
33..77 OOuutt--IInn
This pattern consists of exactly two messages, in order, as follows:
   1. A message:
          o indicated by a Label component whose {label} is 'Out' and
            {direction} is 'out'
          o sent to some node N
   2. A message:
          o indicated by a Label component whose {label} is 'In' and
            {direction} is 'in'
          o sent from node N
This pattern uses the rule _22_.._11_ _FF_aa_uu_ll_tt_ _RR_ee_pp_ll_aa_cc_ee_ss_ _MM_ee_ss_ss_aa_gg_ee.
An operation using this message exchange pattern has a {pattern} property with
the value 'http://www.w3.org/2004/03/wsdl/out-in'.
33..88 OOuutt--OOppttiioonnaall--IInn
This pattern consists of one or two messages, in order, as follows:
   1. A message:
          o indicated by a Label component whose {label} is 'Out' and
            {direction} is 'out'
          o sent to some node N
   2. An optional message:
          o indicated by a Label component whose {label} is 'In' and
            {direction} is 'in'
          o sent from node N
This pattern uses the rule _22_.._22_ _MM_ee_ss_ss_aa_gg_ee_ _TT_rr_ii_gg_gg_ee_rr_ss_ _FF_aa_uu_ll_tt.
An operation using this message exchange pattern has a {pattern} property with
the value 'http://www.w3.org/2004/03/wsdl/out-opt-in'.
44.. RReeffeerreenncceess
44..11 NNoorrmmaattiivvee RReeffeerreenncceess
  [IETF RFC 2119]
      _K_e_y_ _w_o_r_d_s_ _f_o_r_ _u_s_e_ _i_n_ _R_F_C_s_ _t_o_ _I_n_d_i_c_a_t_e_ _R_e_q_u_i_r_e_m_e_n_t_ _L_e_v_e_l_s, S. Bradner,
      Author. Internet Engineering Task Force, June 1999. Available at http://
      www.ietf.org/rfc/rfc2119.txt.
  [WSDL 2.0 Core Language]
      _W_e_b_ _S_e_r_v_i_c_e_s_ _D_e_s_c_r_i_p_t_i_o_n_ _(_W_S_D_L_)_ _V_e_r_s_i_o_n_ _2_._0_ _P_a_r_t_ _1_:_ _C_o_r_e_ _L_a_n_g_u_a_g_e,
      R.Chinnici, M.Gudgin, J-J. Moreau, S.Weerawarana Editors. World Wide Web
      Consortium, 26 March 2004. This version of the "Web Services Description
      Version 2.0 Part 1: Core Language" Specification is available is
      available at http://www.w3.org/TR/2004/WD-wsdl20-20040326. The _l_a_t_e_s_t
      _v_e_r_s_i_o_n_ _o_f_ _"_W_e_b_ _S_e_r_v_i_c_e_s_ _D_e_s_c_r_i_p_t_i_o_n_ _V_e_r_s_i_o_n_ _2_._0_ _P_a_r_t_ _1_:_ _C_o_r_e_ _L_a_n_g_u_a_g_e_"
      is available at http://www.w3.org/TR/wsdl20.
44..22 IInnffoorrmmaattiivvee RReeffeerreenncceess
  [WSD Requirements]
      _W_e_b_ _S_e_r_v_i_c_e_s_ _D_e_s_c_r_i_p_t_i_o_n_ _R_e_q_u_i_r_e_m_e_n_t_s, J. Schlimmer, Editor. World Wide
      Web Consortium, 28 October 2002. This version of the Web Services
      Description Requirements document is http://www.w3.org/TR/2002/WD-ws-
      desc-reqs-20021028. The _l_a_t_e_s_t_ _v_e_r_s_i_o_n_ _o_f_ _W_e_b_ _S_e_r_v_i_c_e_s_ _D_e_s_c_r_i_p_t_i_o_n
      _R_e_q_u_i_r_e_m_e_n_t_s is available at http://www.w3.org/TR/ws-desc-reqs.
AA.. AAcckknnoowwlleeddggeemmeennttss ((NNoonn--NNoorrmmaattiivvee))
This document is the work of the _W_3_C_ _W_e_b_ _S_e_r_v_i_c_e_ _D_e_s_c_r_i_p_t_i_o_n_ _W_o_r_k_i_n_g_ _G_r_o_u_p.
Members of the Working Group are (at the time of writing, and by alphabetical
order): Mike Ballantyne (Electronic Data Systems), David Booth (W3C), Allen
Brookes (Rogue Wave Softwave), Roberto Chinnici (Sun Microsystems), Glen
Daniels (Sonic Software), Alan Davies (SeeBeyond), Mike Davoren (W. W.
Grainger), Paul Downey (British Telecommunications), Youenn Fablet (Canon),
Yaron Goland (BEA), Martin Gudgin (Microsoft Corporation), Hugo Haas (W3C), Hao
He (The Thomson Corporation), Tom Jordahl (Macromedia), Jacek Kopecky
(Systinet), Dan Kulp (IONA Technologies), Sandeep Kumar (Cisco Systems), Amelia
Lewis (TIBCO Software, Inc.), Kevin Canyang Liu (SAP), Michael Mahan (Nokia),
Jonathan Marsh (Microsoft Corporation), Mike McHugh (W. W. Grainger), Michael
Mealling (Verisign), Ingor Melzer (DaimlerChrysler Research and Technology),
Jeff Mischkinsky (Oracle Corporation), Dale Moberg (Cyclone Commerce), Jean-
Jacques Moreau (Canon), David Orchard (BEA), Bijan Parsia (University of
Maryland), Arthur Ryman (IBM), Waqar Sadiq (Electronic Data Systems), Adi
Sakala (IONA Technologies), Jeffrey Schlimmer (Microsoft Corporation), Igor
Sedukhin (Computer Associates), Sandra Swearingen (U.S. Department of Defense,
U.S. Air Force), Bryan Thompson (Hicks & Associates), Jerry Thrasher (Lexmark),
William Vambenepe (Hewlett-Packard Company), Asir Vedamuthu (webMethods, Inc.),
Sanjiva Weerawarana (IBM), Ümit Yalçınalp (Oracle Corporation), Prasad
Yendluri (webMethods, Inc.).
Previous members were: Lily Liu (webMethods, Inc.), Don Wright (Lexmark), Joyce
Yang (Oracle Corporation), Daniel Schutzer (Citigroup), Dave Solo (Citigroup),
Stefano Pogliani (Sun Microsystems), William Stumbo (Xerox), Stephen White
(SeeBeyond), Barbara Zengler (DaimlerChrysler Research and Technology), Tim
Finin (University of Maryland), Laurent De Teneuille (L'Echangeur), Johan
Pauhlsson (L'Echangeur), Mark Jones (AT&T), Steve Lind (AT&T), Philippe Le
Hégaret (W3C), Jim Hendler (University of Maryland), Dietmar Gaertner (Software
AG), Michael Champion (Software AG), Don Mullen (TIBCO Software, Inc.), Steve
Graham (Global Grid Forum), Steve Tuecke (Global Grid Forum).
The people who have contributed to _d_i_s_c_u_s_s_i_o_n_s_ _o_n_ _w_w_w_-_w_s_-_d_e_s_c_@_w_3_._o_r_g are also
gratefully acknowledged.
BB.. CChhaannggee LLoogg ((NNoonn--NNoorrmmaattiivvee))
BB..11 CChhaannggeess

 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
|_DD_aa_tt_ee_ _ _ _ _|_AA_uu_tt_hh_oo_rr_|_DD_ee_ss_cc_rr_ii_pp_tt_ii_oo_nn_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
|_2_0_0_4_0_2_2_5_|_a_a_l_ _ _ _|_a_d_d_ _i_n_-_o_p_t_i_o_n_a_l_-_o_u_t_ _p_e_r_ _m_i_n_u_t_e_s_ _o_f_ _2_0_ _f_e_b_ _2_0_0_4_ _t_e_l_e_c_o_n_ _ _ _ _ _ _ |
|20040212|aal   |change {messageReference} to {label} and "Message Reference  |
|_ _ _ _ _ _ _ _ _|_ _ _ _ _ _ _|_c_o_m_p_o_n_e_n_t_"_ _t_o_ _"_L_a_b_e_l_ _c_o_m_p_o_n_e_n_t_"_ _p_e_r_ _2_0_0_4_0_2_1_2_ _t_e_l_e_c_o_n_f_e_r_e_n_c_e_ _ |
|20040205|aal   |change all 'A' and 'B' message labels into 'Out' or 'In',    |
|_ _ _ _ _ _ _ _ _|_ _ _ _ _ _ _|_d_e_p_e_n_d_i_n_g_ _u_p_o_n_ _d_i_r_e_c_t_i_o_n_._ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
|_2_0_0_4_0_2_0_5_|_a_a_l_ _ _ _|_s_/_m_e_s_s_a_g_e_ _p_a_t_t_e_r_n_/_m_e_s_s_a_g_e_ _e_x_c_h_a_n_g_e_ _p_a_t_t_e_r_n_/_g_i_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
|20031204|jcs   |Removed change marks; note that some were on div2 tag and did|
|_ _ _ _ _ _ _ _ _|_ _ _ _ _ _ _|_n_o_t_ _s_h_o_w_ _w_h_e_n_ _t_r_a_n_s_f_o_r_m_e_d_ _i_n_t_o_ _H_T_M_L_._ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
|20031204|jcs   |Per 4 Dec 2003 telecon, decided to rename 'Asynchronous Out- |
|_ _ _ _ _ _ _ _ _|_ _ _ _ _ _ _|_I_n_'_ _p_a_t_t_e_r_n_ _t_o_ _'_O_u_t_p_u_t_-_O_p_t_i_o_n_a_l_-_I_n_p_u_t_'_._ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
|20031105|aal   |Fix titles of added patterns. Move them to be in conjunction |
|_ _ _ _ _ _ _ _ _|_ _ _ _ _ _ _|_w_i_t_h_ _s_i_m_i_l_a_r_ _p_a_t_t_e_r_n_s_._ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
|        |      |Per action item from October 16 teleconference, added the    |
|20031022|aal   |three patterns using message-triggers-fault as published on  |
|        |      |the mailing list (robust-in-only, robust-out-only, asynch-   |
|_ _ _ _ _ _ _ _ _|_ _ _ _ _ _ _|_o_u_t_-_i_n_)_._ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
|20031022|aal   |Added internal linkage (using specref) from patterns to the  |
|_ _ _ _ _ _ _ _ _|_ _ _ _ _ _ _|_f_a_u_l_t_ _r_u_l_e_s_e_t_s_ _w_h_i_c_h_ _t_h_e_y_ _u_s_e_._ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
|20031022|aal   |Per 9 and 16 Oct 2003 teleconferences, marked in-multi-out   |
|_ _ _ _ _ _ _ _ _|_ _ _ _ _ _ _|_a_n_d_ _o_u_t_-_m_u_l_t_i_-_i_n_ _p_a_t_t_e_r_n_s_ _d_e_l_e_t_e_d_._ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
|20031022|aal   |Per 16 Oct 2003 teleconference, added a paragraph/sentence   |
|_ _ _ _ _ _ _ _ _|_ _ _ _ _ _ _|_s_t_a_t_i_n_g_ _t_h_a_t_ _g_e_n_e_r_a_t_i_o_n_ _o_f_ _a_ _f_a_u_l_t_ _t_e_r_m_i_n_a_t_e_s_ _a_n_ _e_x_c_h_a_n_g_e_._ _ _ |
|20031007|JCS   |Per 2 Oct 2003 teleconference, changed "broadcast" to        |
|_ _ _ _ _ _ _ _ _|_ _ _ _ _ _ _|_"_m_u_l_t_i_c_a_s_t_"_ _i_n_ _t_h_e_ _i_n_t_r_o_d_u_c_t_i_o_n_._ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
|        |      |Per 22 Sep 2003 meeting in Palo Alto, CA, removed "Pattern   |
|20030922|JCS   |Review" editorial note; added specific editorial notes for   |
|_ _ _ _ _ _ _ _ _|_ _ _ _ _ _ _|_I_n_-_M_u_l_t_i_-_O_u_t_ _a_n_d_ _O_u_t_-_M_u_l_t_i_-_I_n_._ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
|20030911|RRC   |Changed the "name" property of the message reference         |
|_ _ _ _ _ _ _ _ _|_ _ _ _ _ _ _|_c_o_m_p_o_n_e_n_t_ _t_o_ _"_m_e_s_s_a_g_e_R_e_f_e_r_e_n_c_e_"_._ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
|_2_0_0_3_0_9_0_4_|_J_C_S_ _ _ _|_I_n_c_o_r_p_o_r_a_t_e_d_ _c_l_a_r_i_f_i_c_a_t_i_o_n_s_ _s_u_g_g_e_s_t_e_d_ _b_y_ _W_3_C_\_D_a_v_i_d_ _B_o_o_t_h_._ _ _ _ |
|20030801|JCS   |Per 30 July meeting, added recommendations from patterns task|
|_ _ _ _ _ _ _ _ _|_ _ _ _ _ _ _|_f_o_r_c_e_._ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
|20030612|AAL   |Added fault generation rulesets and references to them from  |
|_ _ _ _ _ _ _ _ _|_ _ _ _ _ _ _|_p_a_t_t_e_r_n_s_._ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
|_2_0_0_3_0_3_1_3_|_M_J_G_ _ _ _|_C_h_a_n_g_e_d_ _t_o_ _P_a_r_t_ _2_ _(_ _f_r_o_m_ _P_a_r_t_ _3_ _)_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
|_2_0_0_3_0_3_0_6_|_J_C_S_ _ _ _|_P_r_o_p_o_s_e_d_ _n_a_m_e_ _f_o_r_ _M_E_P_7_._ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
|        |      |Per 4 Mar 03 meeting, renamed 'message exchange pattern' to  |
|20030305|JCS   |'message pattern' or 'pattern', added pattern for request-   |
|_ _ _ _ _ _ _ _ _|_ _ _ _ _ _ _|_r_e_s_p_o_n_s_e_,_ _a_d_d_e_d_ _e_d_n_o_t_e_ _a_b_o_u_t_ _r_e_v_i_e_w_ _o_f_ _p_a_t_t_e_r_n_s_._ _ _ _ _ _ _ _ _ _ _ _ _ |
|20030217|MJG   |Fixed some issues with entities and validity errors WRT      |
|_ _ _ _ _ _ _ _ _|_ _ _ _ _ _ _|_u_l_i_s_t_s_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |
|_2_0_0_3_0_2_1_2_|_J_C_S_ _ _ _|_I_n_i_t_i_a_l_ _d_r_a_f_t_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |