Re: Updated SOAP 1.2 Part 3 document
[email protected] Wed, 19 Jul 2006 22:12:33 -0400
| Newsgroups | gmane.text.xml.distributed |
|---|---|
| Message-ID | <OF4F15DFB8.168BAB52-ON852571B1.000BD0D9-852571B1.000C2391@lotus.com> |
Note that this is a very belated reply to a message sent by Dave at the end of May, a copy of which is attached. Unless he's replaced it, I believe that the attached is the draft he's proposing as the working base for our one-way MEP. Having re-read it tonight, my feeling is that overall it's very close to being ready for acceptance as a Recommendation, should we wish to publish a one-way MEP. Though I'd want to read it once or twice in more detail the only concern I caught this time was relatively minor. Section 2.2 now says: "2.2 Description "The SOAP One-way MEP defines properties for the exchange of a SOAP message. In the absence of failure in the underlying protocol, this MEP consists of one SOAP message. "Abnormal operation during a one-way message exchange might be caused by a failure to transfer the message or a failure at the receiving SOAP node to process the message. Such failures might be silent at either or both of the sending and recieving SOAP nodes involved, or might result in the generation of a SOAP or binding-specific fault (see 2.4 Fault Handling). Also, during abnormal operation each SOAP node involved in the message exchange might differ in its determination of the successful completion of the message exchange. " It seems to me that, editorially, it's a bit jarring to jump immediately to the abnormal case. I think I'd move the abnormal operation paragraph down below some of the ones describing the usual operation. Otherwise, it looked pretty good to me overall. Thanks! Noah -------------------------------------- Noah Mendelsohn IBM Corporation One Rogers Street Cambridge, MA 02142 1-617-693-4036 -------------------------------------- "David Orchard" <[email protected]> Sent by: [email protected] 05/31/2006 08:13 PM To: <[email protected]> cc: (bcc: Noah Mendelsohn/Cambridge/IBM) Subject: Updated SOAP 1.2 Part 3 document I've added some text based upon Noah's suggestions for describing sender and receiver responsibilities and changed to be SOAP 1.2 Part 3. Let's talk on the list and the next telcon, whenever that occurs. Cheers, Dave
soap12-part3.xml
(application/octet-stream, 12.3 KB)
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type='text/xsl' href='xmlspec.xsl'?>
<!DOCTYPE spec PUBLIC "-//W3C//DTD Specification V2.2//EN" "xmlspec.dtd" [
<!ENTITY % entities SYSTEM "entitiesedcopy.dtd">
<!ENTITY wgmb SYSTEM "wgmb.txt">
<!ENTITY prevwgmb SYSTEM "prevwgmb.txt">
%entities;
<!ENTITY status "Editors Copy $Date: 2006/03/30 09:53:43 $">
]>
<spec w3c-doctype="wd" role="editors-copy">
<header>
<title>SOAP 1.2 Part 3: One-Way MEP</title>
<w3c-designation>&w3c-designation;</w3c-designation>
<w3c-doctype>&status;</w3c-doctype>
<pubdate>
<day>&draft.day;</day>
<month>&draft.month;</month>
<year>&draft.year;</year>
</pubdate>
<publoc>
<loc xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:show="replace" xlink:actuate="onRequest" href="&dated;/">&dated;/</loc>
</publoc>
<!-- <latestloc>
<loc xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:show="replace" xlink:actuate="onRequest" href="http://www.w3.org/TR/&shortname;/">http://www.w3.org/TR/&shortname;/</loc>
</latestloc>
-->
<authlist>
<author>
<name>David Orchard</name>
<affiliation>BEA Systems</affiliation>
</author>
</authlist>
<abstract>
<p>SOAP Version 1.2 Part 2 provides a request-response MEP and a response-only MEP. This, the SOAP 1.2 Part 3, provides a one-way MEP.</p>
</abstract>
<status>
<p>
<emph>This section describes the status of this document
at the time of its publication. Other documents may
supersede this document. The latest status of this document
series is maintained at the W3C.</emph>
</p>
</status>
<langusage>
<language id="en">English</language>
</langusage>
<revisiondesc>
<p>Last Modified: $Date: 2006/03/30 09:53:43 $ CET</p>
</revisiondesc>
</header>
<body>
<div1 id="intro">
<head>Introduction</head>
<p>SOAP Version 1.2 Part 2 provides a request-response MEP and a response-only MEP. This, the SOAP 1.2 Part 3, provides a one-way MEP.
</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 RFC 2119 <bibref ref="RFC2119"/>.</p>
<p>With the exception of examples and sections explicitly marked
as "Non-Normative", all parts of this specification are
normative.</p>
</div2>
</div1>
<div1 id="singlereqmep">
<head>SOAP One-way Message Exchange Pattern</head>
<p>This section defines the message exchange pattern (MEP) called "One-way". The
description is an abstract presentation of the operation of
this MEP. It is not intended to describe a real
implementation or to suggest how a real implementation should
be structured.</p>
<div2 id="mepname">
<head>SOAP Feature Name</head>
<p>This message exchange pattern is identified by
the URI (see SOAP 1.2 Part 1 <bibref ref="SOAP-PART1"/>
<xspecref xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" href="&dated-part1;/#soapfeature">SOAP Features</xspecref>):</p>
<ulist>
<item>
<p>
<attval>http://www.w3.org/2006/03/soap/mep/one-way/</attval>
</p>
</item>
</ulist>
</div2>
<div2 id="bindinfdesc">
<head>Description</head>
<p>The SOAP One-way MEP defines
properties for the exchange of a SOAP message. In the absence of failure in the underlying
protocol, this MEP consists of one SOAP message.</p>
<p>Abnormal operation during a one-way message exchange
might be caused by a failure to transfer the message or a
failure at the receiving SOAP node to process the
message. Such
failures might be silent at either or both of the sending and
recieving SOAP nodes involved, or might result in the generation of a SOAP
or binding-specific fault (see <specref ref="bindfaulthdn"/>).
Also, during abnormal operation
each SOAP node involved in the message exchange might differ in
its determination of the successful completion of the message
exchange. </p>
<p>The scope of a one-way MEP is limited to
the exchange of a message between
one sending and one receiving SOAP node. Implementations MAY choose
to support multiple meps at the same time.</p>
<p>The sending node MUST send the SOAP Message provided in http://www.w3.org/2003/05/soap/mep/OutboundMessage to the node identified by http://www.w3.org/2003/05/soap/mep/ImmediateDestination. The sender is not required to detect whether transmission succeeds or fails, but the sender SHOULD fault in a binding specific manner if it descovers that transmission is unsuccessful. </p>
<p>The receiving node MUST determine whether a given message is successfully received, and if so, MUST process the received message in http://www.w3.org/2003/05/soap/mep/InboundMessage according to the SOAP Processing Model (see SOAP 1.2 Part 1 <bibref ref="SOAP-PART1"/> <xspecref xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" href="&dated-part1;/#procsoapmsgs">Processing SOAP messages</xspecref>). Determination of success by the receiver MAY be conservative, I.e. the receiver may in exceptional circumstances treat as erroneous or lost a message which is received intact (typical reasons for making such decisions might include shortage of buffer space, network interface overruns, etc.). Receivers MAY fault in a binding-specific manner if some particular message is declared in error (note, however, that in many cases where receipt is unsuccessful, information identifying the message or its sender may be unreliable, in which case there may be little if any value in reflecting a message-specific fault.)</p>
</div2>
<div2 id="bindformdesc">
<head>Property Description</head>
<p>The One-way MEP defines a set of properties described below.</p>
<table border="1" id="tabonewayprops">
<caption>Property definitions for One-way MEP</caption>
<tbody>
<tr>
<th>Property Name</th>
<th>Property Description</th>
<th>Property Type</th>
</tr>
<tr>
<td>
<att>http://www.w3.org/2003/05/soap/mep/OutboundMessage</att>
</td>
<td>An abstract structure that represents the current
outbound message in the message exchange. This
abstracts both SOAP Envelope and any other
information structures that are transferred along
with the envelope.</td>
<td>Not specified</td>
</tr>
<tr>
<td>
<att>http://www.w3.org/2003/05/soap/mep/ImmediateDestination</att>
</td>
<td>The identifier of the immediate destination of an
outbound message.</td>
<td>xs:anyURI</td>
</tr>
<tr>
<td>
<att>http://www.w3.org/2003/05/soap/mep/ImmediateSender</att>
</td>
<td>The identifier of the immediate sender of an inbound
message.</td>
<td>xs:anyURI</td>
</tr>
<tr>
<td>
<att>http://www.w3.org/2003/05/soap/bindingFramework/ExchangeContext/FailureReason</att>
</td>
<td>A value that denotes a pattern-specific, binding-independent reason for the failure of a message exchange. Underlying protocol binding specifications may define properties to convey more binding-specific details of the failure. </td>
<td>xs:anyURI</td>
</tr>
<tr>
<td>
<att>http://www.w3.org/2003/05/soap/bindingFramework/ExchangeContext/State</att>
</td>
<td>The identifier of the state of the message exchange. This value is managed by the binding instance and may be inspected by other entities monitoring the progress of the message exchange. At a terminal state, it contains either Success or Fail
</td>
<td>xs:anyURI</td>
</tr>
</tbody>
</table>
<p>There may be other properties related to the operation of
the message exchange and are processed according to their own feature specifications.
</p>
</div2>
<div2 id="bindfaulthdn">
<head>Fault Handling</head>
<p>During the operation of the One-way MEP, the
participating SOAP nodes may generate SOAP faults. This MEP makes no claims about the disposition or
handling of SOAP faults generated by the sending SOAP node or the receiving SOAP node.</p>
</div2>
</div1>
<div1 id="refs">
<head>References</head>
<div2 id="refs-norm">
<head>Normative References</head>
<blist>
<bibl key="SOAP Part 1" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:show="replace" xlink:actuate="onRequest" href="http://www.w3.org/TR/2003/REC-soap12-part1-20030624/" id="SOAP-PART1">W3C Proposed Recommendation
"SOAP Version 1.2 Part 1: Messaging
Framework", Martin Gudgin, Marc Hadley, Noah Mendelsohn, Jean-Jacques Moreau,
Henrik Frystyk Nielsen, 24 June 2003</bibl>
<bibl key="SOAP Part 2" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:show="replace" xlink:actuate="onRequest" href="http://www.w3.org/TR/2003/REC-soap12-part2-20030624/" id="SOAP-PART2">W3C Proposed Recommendation
"SOAP Version 1.2 Part 2: Adjuncts", Martin Gudgin, Marc Hadley, Noah Mendelsohn, Jean-Jacques Moreau,
Henrik Frystyk Nielsen, 24 June 2003</bibl>
<bibl key="RFC 2119" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:show="replace" xlink:actuate="onRequest" id="RFC2119" href="http://www.ietf.org/rfc/rfc2119.txt">IETF "RFC 2119:
Key words for use in RFCs to Indicate Requirement Levels",
S. Bradner, March 1997.</bibl>
<bibl key="RFC 2396" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:show="replace" xlink:actuate="onRequest" id="RFC2396" href="http://www.ietf.org/rfc/rfc2396.txt">IETF "RFC 2396:
Uniform Resource Identifiers (URI): Generic Syntax",
T. Berners-Lee, R. Fielding, L. Masinter, August
1998.</bibl>
</blist>
</div2>
<div2 id="refs-inform">
<head>Informative References</head>
<blist>
<bibl key="SOAP Part 0" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:show="replace" xlink:actuate="onRequest" href="http://www.w3.org/TR/2003/REC-soap12-part0-20030624/" id="SOAP-PART0">W3C Proposed Recommendation "SOAP Version 1.2 Part 0:
Primer", Nilo Mitra, 24 June 2003</bibl>
<bibl key="XMLP Comments" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:show="replace" xlink:actuate="onRequest" href="http://lists.w3.org/Archives/Public/xmlp-comments/" id="CommentArchive">XML Protocol Comments Archive</bibl>
<bibl key="XMLP Dist-App" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:show="replace" xlink:actuate="onRequest" href="http://lists.w3.org/Archives/Public/xml-dist-app/" id="DiscussionArchive">XML Protocol Discussion
Archive</bibl>
<bibl key="XMLP Charter" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:show="replace" xlink:actuate="onRequest" href="http://www.w3.org/2000/09/XML-Protocol-Charter" id="XMLPCharter">XML Protocol Charter</bibl>
<bibl key="RFC 2045" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:show="replace" xlink:actuate="onRequest" href="http://www.ietf.org/rfc/rfc2045.txt" id="RFC2045">IETF "RFC2045: Multipurpose Internet Mail
Extensions (MIME) Part One: Format of Internet Message
Bodies", N. Freed, N. Borenstein, November 1996.</bibl>
<bibl key="RFC 2026" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:show="replace" xlink:actuate="onRequest" id="RFC2026" href="http://www.ietf.org/rfc/rfc2026.txt">IETF "RFC 2026:
The Internet Standards Process -- Revision 3", section
4.2.3, S. Bradner, October 1996.</bibl>
</blist>
</div2>
</div1>
</body>
<back>
<inform-div1 id="changelog">
<head>Change Log</head>
<table border="1">
<caption>Changes</caption>
<thead>
<tr>
<th>Who</th>
<th>When</th>
<th>What</th>
</tr>
</thead>
<tbody>
<tr>
<td>DBO</td>
<td>20041208</td>
<td>Initial Revision</td>
</tr>
<tr>
<td>DBO</td>
<td>20060330</td>
<td>2nd Revision</td>
</tr>
<tr>
<td>DBO</td>
<td>20060530</td>
<td>Adding sending and receiver MUSTs</td>
</tr>
</tbody>
</table>
</inform-div1>
</back>
</spec>
soap12-part3.html
(text/html, 14.4 KB)
<?xml version="1.0" encoding="ISO-8859-1"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml" lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/><title>SOAP 1.2 Part 3: One-Way MEP</title><style type="text/css">
code { font-family: monospace; }
div.constraint,
div.issue,
div.note,
div.notice { margin-left: 2em; }
li p { margin-top: 0.3em;
margin-bottom: 0.3em; }
div.exampleInner pre { margin-left: 1em;
margin-top: 0em; margin-bottom: 0em}
div.exampleOuter {border: 4px double gray;
margin: 0em; padding: 0em}
div.exampleInner { background-color: #d5dee3;
border-top-width: 4px;
border-top-style: double;
border-top-color: #d3d3d3;
border-bottom-width: 4px;
border-bottom-style: double;
border-bottom-color: #d3d3d3;
padding: 4px; margin: 0em }
div.exampleWrapper { margin: 4px }
div.exampleHeader { font-weight: bold;
margin: 4px}
</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base.css"/></head><body><div class="head">
<h1><a name="title" id="title"/>SOAP 1.2 Part 3: One-Way MEP</h1>
<h2><a name="w3c-doctype" id="w3c-doctype"/>Editors Copy $Date: 2006/03/30 09
53:43 $ 31 May 2006</h2><dl><dt>This version:</dt><dd><a href="/">/</a></dd><dt>Editor:</dt><dd>David Orchard, BEA Systems</dd></dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice-20000612#Copyright">Copyright</a> © 2006 <a href="http://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup> (<a href="http://www.lcs.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>, <a href="http://www.inria.fr/"><abbr lang="fr" title="Institut National de Recherche en Informatique et Automatique">INRIA</abbr></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice-20000612#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice-20000612#W3C_Trademarks">trademark</a>, <a href="http://www.w3.org/Consortium/Legal/copyright-documents-19990405">document use</a>, and <a href="http://www.w3.org/Consortium/Legal/copyright-software-19980720">software licensing</a> rules apply.</p></div><hr/><div>
<h2><a name="abstract" id="abstract"/>Abstract</h2><p>SOAP Version 1.2 Part 2 provides a request-response MEP and a response-only MEP. This, the SOAP 1.2 Part 3, provides a one-way MEP.</p></div><div>
<h2><a name="status" id="status"/>Status of this Document</h2><p><strong>This document is an editors' copy that has
no official standing.</strong></p><p><em>This section describes the status of this document
at the time of its publication. Other documents may
supersede this document. The latest status of this document
series is maintained at the W3C.</em></p></div><div class="toc">
<h2><a name="contents" id="contents"/>Table of Contents</h2><p class="toc">1 <a href="#intro">Introduction</a><br/> 1.1 <a href="#notcon">Notational Conventions</a><br/>2 <a href="#singlereqmep">SOAP One-way Message Exchange Pattern</a><br/> 2.1 <a href="#mepname">SOAP Feature Name</a><br/> 2.2 <a href="#bindinfdesc">Description</a><br/> 2.3 <a href="#bindformdesc">Property Description</a><br/> 2.4 <a href="#bindfaulthdn">Fault Handling</a><br/>3 <a href="#refs">References</a><br/> 3.1 <a href="#refs-norm">Normative References</a><br/> 3.2 <a href="#refs-inform">Informative References</a><br/></p>
<h3><a name="appendices" id="appendices"/>Appendix</h3><p class="toc">A <a href="#changelog">Change Log</a> (Non-Normative)<br/></p></div><hr/><div class="body"><div class="div1">
<h2><a name="intro" id="intro"/>1 Introduction</h2><p>SOAP Version 1.2 Part 2 provides a request-response MEP and a response-only MEP. This, the SOAP 1.2 Part 3, provides a one-way MEP.
</p><div class="div2">
<h3><a name="notcon" id="notcon"/>1.1 Notational Conventions</h3><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 RFC 2119 <a href="#RFC2119">[RFC 2119]</a>.</p><p>With the exception of examples and sections explicitly marked
as "Non-Normative", all parts of this specification are
normative.</p></div></div><div class="div1">
<h2><a name="singlereqmep" id="singlereqmep"/>2 SOAP One-way Message Exchange Pattern</h2><p>This section defines the message exchange pattern (MEP) called "One-way". The
description is an abstract presentation of the operation of
this MEP. It is not intended to describe a real
implementation or to suggest how a real implementation should
be structured.</p><div class="div2">
<h3><a name="mepname" id="mepname"/>2.1 SOAP Feature Name</h3><p>This message exchange pattern is identified by
the URI (see SOAP 1.2 Part 1 <a href="#SOAP-PART1">[SOAP Part 1]</a><a href="http://www.w3.org/TR/2003/REC-soap12-part1-20030624//#soapfeature">SOAP Features</a>):</p><ul><li><p>"http://www.w3.org/2006/03/soap/mep/one-way/"</p></li></ul></div><div class="div2">
<h3><a name="bindinfdesc" id="bin
infdesc"/>2.2 Description</h3><p>The SOAP One-way MEP defines
properties for the exchange of a SOAP message. In the absence of failure in the underlying
protocol, this MEP consists of one SOAP message.</p><p>Abnormal operation during a one-way message exchange
might be caused by a failure to transfer the message or a
failure at the receiving SOAP node to process the
message. Such
failures might be silent at either or both of the sending and
recieving SOAP nodes involved, or might result in the generation of a SOAP
or binding-specific fault (see <a href="#bindfaulthdn"><b>2.4 Fault Handling</b></a>).
Also, during abnormal operation
each SOAP node involved in the message exchange might differ in
its determination of the successful completion of the message
exchange. </p><p>The scope of a one-way MEP is limited to
the exchange of a message between
one sending and one receiving SOAP node. Implementations MAY choose
to support multiple meps at the same time.</p><p>The sending node MUST send the SOAP Message provided in http://www.w3.org/2003/05/soap/mep/OutboundMessage to the node identified by http://www.w3.org/2003/05/soap/mep/ImmediateDestination. The sender is not required to detect whether transmission succeeds or fails, but the sender SHOULD fault in a binding specific manner if it descovers that transmission is unsuccessful. </p><p>The receiving node MUST determine whether a given message is successfully received, and if so, MUST process the received message in http://www.w3.org/2003/05/soap/mep/InboundMessage according to the SOAP Processing Model (see SOAP 1.2 Part 1 <a href="#SOAP-PART1">[SOAP Part 1]</a><a href="http://www.w3.org/TR/2003/REC-soap12-part1-20030624//#procsoapmsgs">Processing SOAP messages</a>). Determination of success by the receiver MAY be conservative, I.e. the receiver may in exceptional circumstances treat as erroneous or lost a message which is received intact (typical reasons for making such decisions might include shortage of buffer space, network interface overruns, etc.). Receivers MAY fault in a binding-specific manner if some particular message is declared in error (note, however, that in many cases where receipt is unsuccessful, information identifying the message or its sender may be unreliable, in which case there may be little if any value in reflecting a message-specific fault.)</p></div><div class="div2">
<h3><a name="bindformdesc" id="bindformdesc"/>2.3 Property Description</h3><p>The One-way MEP defines a set of properties described below.</p><table border="1" id="tabonewayprops"><caption>Property definitions for One-way MEP</caption><tbody><tr><th rowspan="1" colspan="1">Property Name</th><th rowspan="1" colspan="1">Property Description</th><th rowspan="1" colspan="1">Property Type</th></tr><tr><td rowspan="1" colspan="1"><code>http://www.w3.org/2003/05/soap/mep/OutboundMessage</code></td><td rowspan="1" colspan="1">An abstract structure that represents the current
outbound message in the message exchange. This
abstracts both SOAP Envelope and any other
information structures that are transferred along
with the envelope.</td><td rowspan="1" colspan="1">Not specified</td></tr><tr><td rowspan="1" colspan="1"><code>http://www.w3.org/2003/05/soap/mep/ImmediateDestination</code></td><td rowspan="1" colspan="1">The identifier of the immediate destination of an
outbound message.</td><td rowspan="1" colspan="1">xs:anyURI</td></tr><tr><td rowspan="1" colspan="1"><code>http://www.w3.org/2003/05/soap/mep/ImmediateSender</code></td><td rowspan="1" colspan="1">The identifier of the immediate sender of an inbound
message.</td><td rowspan="1" colspan="1">xs:anyURI</td></tr><tr><td rowspan="1" colspan="1"><code>http://www.w3.org/2003/05/soap/bindingFramework/ExchangeContext/FailureReason</code></td><td rowspan="1" colspan="1">A value that denotes a pattern-specific, bindi
g-independent reason for the failure of a message exchange. Underlying protocol binding specifications may define properties to convey more binding-specific details of the failure. </td><td rowspan="1" colspan="1">xs:anyURI</td></tr><tr><td rowspan="1" colspan="1"><code>http://www.w3.org/2003/05/soap/bindingFramework/ExchangeContext/State</code></td><td rowspan="1" colspan="1">The identifier of the state of the message exchange. This value is managed by the binding instance and may be inspected by other entities monitoring the progress of the message exchange. At a terminal state, it contains either Success or Fail
</td><td rowspan="1" colspan="1">xs:anyURI</td></tr></tbody></table><p>There may be other properties related to the operation of
the message exchange and are processed according to their own feature specifications.
</p></div><div class="div2">
<h3><a name="bindfaulthdn" id="bindfaulthdn"/>2.4 Fault Handling</h3><p>During the operation of the One-way MEP, the
participating SOAP nodes may generate SOAP faults. This MEP makes no claims about the disposition or
handling of SOAP faults generated by the sending SOAP node or the receiving SOAP node.</p></div></div><div class="div1">
<h2><a name="refs" id="refs"/>3 References</h2><div class="div2">
<h3><a name="refs-norm" id="refs-norm"/>3.1 Normative References</h3><dl><dt class="label"><a name="SOAP-PART1" id="SOAP-PART1"/>SOAP Part 1</dt><dd><a href="http://www.w3.org/TR/2003/REC-soap12-part1-20030624/">W3C Proposed Recommendation
"SOAP Version 1.2 Part 1: Messaging
Framework", Martin Gudgin, Marc Hadley, Noah Mendelsohn, Jean-Jacques Moreau,
Henrik Frystyk Nielsen, 24 June 2003</a> (See http://www.w3.org/TR/2003/REC-soap12-part1-20030624/.)</dd><dt class="label"><a name="SOAP-PART2" id="SOAP-PART2"/>SOAP Part 2</dt><dd><a href="http://www.w3.org/TR/2003/REC-soap12-part2-20030624/">W3C Proposed Recommendation
"SOAP Version 1.2 Part 2: Adjuncts", Martin Gudgin, Marc Hadley, Noah Mendelsohn, Jean-Jacques Moreau,
Henrik Frystyk Nielsen, 24 June 2003</a> (See http://www.w3.org/TR/2003/REC-soap12-part2-20030624/.)</dd><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt">IETF "RFC 2119:
Key words for use in RFCs to Indicate Requirement Levels",
S. Bradner, March 1997.</a> (See http://www.ietf.org/rfc/rfc2119.txt.)</dd><dt class="label"><a name="RFC2396" id="RFC2396"/>RFC 2396</dt><dd><a href="http://www.ietf.org/rfc/rfc2396.txt">IETF "RFC 2396:
Uniform Resource Identifiers (URI): Generic Syntax",
T. Berners-Lee, R. Fielding, L. Masinter, August
1998.</a> (See http://www.ietf.org/rfc/rfc2396.txt.)</dd></dl></div><div class="div2">
<h3><a name="refs-inform" id="refs-inform"/>3.2 Informative References</h3><dl><dt class="label"><a name="SOAP-PART0" id="SOAP-PART0"/>SOAP Part 0</dt><dd><a href="http://www.w3.org/TR/2003/REC-soap12-part0-20030624/">W3C Proposed Recommendation "SOAP Version 1.2 Part 0:
Primer", Nilo Mitra, 24 June 2003</a> (See http://www.w3.org/TR/2003/REC-soap12-part0-20030624/.)</dd><dt class="label"><a name="CommentArchive" id="CommentArchive"/>XMLP Comments</dt><dd><a href="http://lists.w3.org/Archives/Public/xmlp-comments/">XML Protocol Comments Archive</a> (See http://lists.w3.org/Archives/Public/xmlp-comments/.)</dd><dt class="label"><a name="DiscussionArchive" id="DiscussionArchive"/>XMLP Dist-App</dt><dd><a href="http://lists.w3.org/Archives/Public/xml-dist-app/">XML Protocol Discussion
Archive</a> (See http://lists.w3.org/Archives/Public/xml-dist-app/.)</dd><dt class="label"><a name="XMLPCharter" id="XMLPCharter"/>XMLP Charter</dt><dd><a href="http://www.w3.org/2000/09/XML-Protocol-Charter">XML Protocol Charter</a> (See http://www.w3.org/2000/09/XML-Protocol-Charter.)</dd><dt class="label"><a name="RFC2045" id="RFC2045"/>RFC 2045</dt><dd><a href="http://www.ietf.org/rfc/rfc2045.txt">IETF "RFC2045: Multipurpose
Internet Mail
Extensions (MIME) Part One: Format of Internet Message
Bodies", N. Freed, N. Borenstein, November 1996.</a> (See http://www.ietf.org/rfc/rfc2045.txt.)</dd><dt class="label"><a name="RFC2026" id="RFC2026"/>RFC 2026</dt><dd><a href="http://www.ietf.org/rfc/rfc2026.txt">IETF "RFC 2026:
The Internet Standards Process -- Revision 3", section
4.2.3, S. Bradner, October 1996.</a> (See http://www.ietf.org/rfc/rfc2026.txt.)</dd></dl></div></div></div><div class="back"><div class="div1">
<h2><a name="changelog" id="changelog"/>A Change Log (Non-Normative)</h2><table border="1"><caption>Changes</caption><thead><tr><th rowspan="1" colspan="1">Who</th><th rowspan="1" colspan="1">When</th><th rowspan="1" colspan="1">What</th></tr></thead><tbody><tr><td rowspan="1" colspan="1">DBO</td><td rowspan="1" colspan="1">20041208</td><td rowspan="1" colspan="1">Initial Revision</td></tr><tr><td rowspan="1" colspan="1">DBO</td><td rowspan="1" colspan="1">20060330</td><td rowspan="1" colspan="1">2nd Revision</td></tr><tr><td rowspan="1" colspan="1">DBO</td><td rowspan="1" colspan="1">20060530</td><td rowspan="1" colspan="1">Adding sending and receiver MUSTs</td></tr></tbody></table></div></div></body></html>