You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
340 lines
32 KiB
340 lines
32 KiB
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
|
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>MTOM Serialization Policy Assertion 1.1</title><style type="text/css">
|
|
code { font-family: monospace; }
|
|
|
|
div.constraint,
|
|
div.issue,
|
|
div.note,
|
|
div.notice { margin-left: 2em; }
|
|
|
|
ol.enumar { list-style-type: decimal; }
|
|
ol.enumla { list-style-type: lower-alpha; }
|
|
ol.enumlr { list-style-type: lower-roman; }
|
|
ol.enumua { list-style-type: upper-alpha; }
|
|
ol.enumur { list-style-type: upper-roman; }
|
|
|
|
|
|
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/W3C-WD.css"></head><body><div class="head"><p><a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width="72"></a></p>
|
|
<h1><a name="title" id="title"></a>MTOM Serialization Policy Assertion 1.1</h1>
|
|
<h2><a name="w3c-doctype" id="w3c-doctype"></a>W3C Working Draft 18 September 2007</h2><dl><dt>This version:</dt><dd><a href="http://www.w3.org/TR/2007/WD-soap12-mtom-policy-20070918/">http://www.w3.org/TR/2007/WD-soap12-mtom-policy-20070918/</a></dd><dt>Latest version:</dt><dd><a href="http://www.w3.org/TR/soap12-mtom-policy">http://www.w3.org/TR/soap12-mtom-policy</a></dd><dt>Editors:</dt><dd>Christopher Ferris, IBM</dd><dd>Yves Lafon, W3C</dd></dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2007 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr><div>
|
|
<h2><a name="abstract" id="abstract"></a>Abstract</h2><p>This specification describes a domain-specific policy assertion that indicates
|
|
endpoint support of the optimized MIME multipart/related serialization of SOAP messages
|
|
defined in section 3 of the SOAP Message Transmission Optimization Mechanism <a href="#MTOM">[MTOM]</a> specification. This policy assertion can be specified within a policy
|
|
alternative as defined in Web Services Policy 1.5 - Framework <a href="#WS-Policy">[WS-Policy]</a> and attached
|
|
to a WSDL description as defined in Web Services Policy 1.5 - Attachment <a href="#WS-PolicyAttachment">[WS-PolicyAttachment]</a>. </p></div><div>
|
|
<h2><a name="status" id="status"></a>Status of this Document</h2><p><em>This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a> at http://www.w3.org/TR/.</em></p><p>This is the First Public Working Draft of the MTOM Serialization
|
|
Policy Assertion 1.1 document. This is also a Last Call Working Draft
|
|
of the specification. The Last Call period ends 15 October 2007. It
|
|
has been produced by the <a href="http://www.w3.org/2000/xp/Group/">XML Protocol Working Group</a>
|
|
which is part of the <a href="http://www.w3.org/2002/ws/Activity">Web Services Activity</a>.The Working
|
|
Group expects to advance this Working Draft to Recommendation.</p><p>Comments on this document are welcome. Please send them to the public
|
|
mailing-list <a href="mailto:xmlp-comments@w3.org">xmlp-comments@w3.org</a>
|
|
(<a href="http://lists.w3.org/Archives/Public/xmlp-comments/">archive</a>).
|
|
It is inappropriate to send discussion email to this address.
|
|
</p><p> This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 W3C Patent Policy</a>. W3C maintains a <a rel="disclosure" href="http://www.w3.org/2004/01/pp-impl/32157/status">public list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the W3C Patent Policy</a>. </p><p>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.</p><p>A list of current <a href="http://www.w3.org/TR/">W3C Recommendations and
|
|
other technical reports</a> can be found at <a href="http://www.w3.org/TR">http://www.w3.org/TR</a>.</p></div><div class="toc">
|
|
<h2><a name="contents" id="contents"></a>Table of Contents</h2><p class="toc">1 <a href="#intro">Introduction</a><br>
|
|
1.1 <a href="#example">Example</a><br>
|
|
2 <a href="#termsnotcon">Terminology and Notational Conventions</a><br>
|
|
2.1 <a href="#namespaces">XML Namespaces</a><br>
|
|
2.2 <a href="#notcon">Notational Conventions</a><br>
|
|
2.3 <a href="#compliance">Compliance</a><br>
|
|
3 <a href="#mtomassert">MTOM Policy Assertion</a><br>
|
|
3.1 <a href="#model">Assertion Model</a><br>
|
|
3.2 <a href="#syntax">Assertion Syntax</a><br>
|
|
3.3 <a href="#attachment">Assertion Attachment</a><br>
|
|
4 <a href="#security">Security</a><br>
|
|
5 <a href="#refs">References</a><br>
|
|
5.1 <a href="#refs-norm">Normative References</a><br>
|
|
5.2 <a href="#refs-inform">Informative References</a><br>
|
|
</p>
|
|
<h3><a name="appendices" id="appendices"></a>Appendices</h3><p class="toc">A <a href="#schema">Appendix I – XML Schema</a><br>
|
|
B <a href="#id2268410">Acknowledgements</a> (Non-Normative)<br>
|
|
</p></div><hr><div class="body"><div class="div1">
|
|
<h2><a name="intro" id="intro"></a>1 Introduction</h2><p>This specification describes a domain-specific policy assertion for the
|
|
SOAP Message Transmission Optimization Mechanism W3C Recommentation <a href="#MTOM">[MTOM]</a> that can be specified within a policy alternative as defined in
|
|
Web Services Policy 1.5 - Framework <a href="#WS-Policy">[WS-Policy]</a>.
|
|
For backwards compatibility, the policy assertion can also be used in conjunction
|
|
with the SOAP 1.1 Binding for MTOM 1.0 <a href="#MTOMS11">[MTOMS11]</a> Member Submission.</p><div class="div2">
|
|
<h3><a name="example" id="example"></a>1.1 Example</h3><p>The following tables list an example use of the MTOM policy assertion.</p><div class="exampleOuter">
|
|
<div class="exampleHeader"><a name="Table1" id="Table1"></a>Example: Table 1: Example WSDL 2.0 description with MTOM policy assertion.</div><div class="exampleInner"><pre>
|
|
|
|
1 <wsdl:description
|
|
2 targetNamespace="http://tns.example.com/"
|
|
3 xmlns:tns="http://tns.example.com/"
|
|
4 xmlns:wsdl="http://www.w3.org/ns/wsdl"
|
|
5 xmlns:wsp="http://www.w3.org/ns/ws-policy"
|
|
6 xmlns:wsoma="http://www.w3.org/2007/08/soap12-mtom-policy"
|
|
7 xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" >
|
|
8 <wsp:Policy wsu:Id="MyPolicy" >
|
|
9 <wsoma:MTOM />
|
|
10 <!-- omitted assertions -->
|
|
11 </wsp:Policy>
|
|
|
|
12 <!-- omitted elements -->
|
|
|
|
13 <wsdl:binding name="MyBinding" type="tns:MyInterface" >
|
|
14 <wsp:PolicyReference
|
|
15 URI="#MyPolicy"
|
|
16 wsdl:required="true" />
|
|
17 <!-- omitted elements -->
|
|
18 </wsdl:binding>
|
|
19 </wsdl:description>
|
|
</pre></div><p>Lines (8-11) in are a policy expression that includes an MTOM policy assertion (Line 9)
|
|
to indicate that the SOAP Message Transmission Optimization Mechanism <a href="#MTOM">[MTOM]</a> may be used.</p><p>Lines (13-18) are a WSDL 2.0 <a href="#WSDL2.0">[WSDL2.0]</a> binding. Lines (14-16) indicate that the policy in Lines (8-11) applies to this binding, specifically indicating that MTOM encodings must be accepted over all the
|
|
messages in the binding. Line (16) indicates policy is a required extension.</p></div><div class="exampleOuter">
|
|
<div class="exampleHeader"><a name="Table2" id="Table2"></a>Example: Table 2: Example WSDL 1.1 description with MTOM policy assertion.</div><div class="exampleInner"><pre>
|
|
|
|
1 <wsdl:definitions
|
|
2 targetNamespace="example.com"
|
|
3 xmlns:tns="example.com"
|
|
4 xmlns:wsdl11="http://schemas.xmlsoap.org/wsdl/"
|
|
5 xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"
|
|
6 xmlns:wsoma="http://www.w3.org/2007/08/soap12-mtom-policy"
|
|
7 xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" >
|
|
|
|
8 <wsp:Policy wsu:Id="MyPolicy" >
|
|
9 <wsoma:MTOM />
|
|
10 <!-- omitted assertions -->
|
|
11 </wsp:Policy>
|
|
|
|
12 <!-- omitted elements -->
|
|
|
|
13 <wsdl:binding name="MyBinding" type="tns:MyPortType" >
|
|
14 <wsp:PolicyReference
|
|
15 URI="#MyPolicy"
|
|
16 wsdl11:required="true" />
|
|
17 <!-- omitted elements -->
|
|
18 </wsdl:binding>
|
|
|
|
19 </wsdl:definitions>
|
|
</pre></div><p>Lines (8-11) in are a policy expression that includes an MTOM policy assertion (Line 9)
|
|
to indicate that the SOAP Message Transmission Optimization Mechanism <a href="#MTOM">[MTOM]</a> may be used.</p><p>Lines (13-18) are a WSDL 1.1 <a href="#WSDL1.1">[WSDL1.1]</a> binding. Lines (14-16) indicate that the policy in Lines (8-11) applies to this binding, specifically indicating that MTOM encodings must be accepted over all the
|
|
messages in the binding. Line (16) indicates policy is a required extension.</p></div></div></div><div class="div1">
|
|
<h2><a name="termsnotcon" id="termsnotcon"></a>2 Terminology and Notational Conventions</h2><div id="terms"><p>Definitions of <span class="label">Policy</span>, <span class="label">Policy Alternative</span>, <span class="label">Policy Expression</span> and <span class="label">Policy Subject</span> can be found in the Web Services Policy 1.5 - Framework specification <a href="#WS-Policy">[WS-Policy]</a>.</p></div><div class="div2">
|
|
<h3><a name="namespaces" id="namespaces"></a>2.1 XML Namespaces</h3><p>The XML Namespace URI that MUST be used by implementations of this specification is:</p><div class="exampleOuter"><div class="exampleInner"><pre>http://www.w3.org/2007/08/soap12-mtom-policy</pre></div></div><p>Table 3 lists XML namespaces that are used in this specification. The choice of any namespace
|
|
prefix is arbitrary and not semantically significant.</p><a name="Table3" id="Table3"></a><table border="1"><caption>Table 3: Prefixes and XML Namespaces used in this specification.</caption><tbody><tr><th>Prefix</th><th>Namespace</th><th>Notes</th></tr><tr><td>wsdl</td><td>"http://www.w3.org/ns/wsdl"</td><td><a href="#WSDL2.0">[WSDL2.0]</a>.</td></tr><tr><td>wsdl11</td><td>"http://schemas.xmlsoap.org/wsdl/"</td><td><a href="#WSDL1.1">[WSDL1.1]</a>.</td></tr><tr><td>wsp</td><td>"http://www.w3.org/ns/ws-policy"</td><td><a href="#WS-Policy">[WS-Policy]</a>.</td></tr><tr><td>wsoma</td><td>"http://www.w3.org/2007/08/soap12-mtom-policy"</td><td>This specification.<table border="1" summary="Editorial note"><tr><td align="left" valign="top" width="50%"><b>Editorial note</b></td><td align="right" valign="top" width="50%"> </td></tr><tr><td colspan="2" align="left" valign="top">When the specification will reach a stable point, the expected namespace should be http://www.w3.org/<em></em>ns/soap12-mtom-policy</td></tr></table></td></tr></tbody></table></div><div class="div2">
|
|
<h3><a name="notcon" id="notcon"></a>2.2 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>This specification uses the following syntax to define pseudo schemas for messages:</p><ul><li>The syntax appears as an XML instance, but values in italics indicate data types instead of literal values.</li><li>Characters are appended to elements and attributes to indicate cardinality:
|
|
<ul><li>"?" (0 or 1)</li><li>"*" (0 or more)</li><li>"+" (1 or more)</li></ul></li><li>The character "|" is used to indicate a choice between alternatives.</li><li>The characters "(" and ")" are used to indicate that contained items are to be
|
|
treated as a group with respect to cardinality or choice.</li><li>The characters "[" and "]" are used to call out references and property names.</li><li>Ellipses (i.e., "…") indicate points of extensibility. Additional children and/or
|
|
attributes MAY be added at the indicated extension points but MUST NOT contradict the
|
|
semantics of the parent and/or owner, respectively. By default, if a receiver does not
|
|
recognize an extension, the receiver SHOULD ignore the extension; exceptions to this
|
|
processing rule, if any, are clearly indicated below.</li><li>XML namespace prefixes (see Table 3) are used to indicate
|
|
the namespace of the element being defined.</li></ul></div><div class="div2">
|
|
<h3><a name="compliance" id="compliance"></a>2.3 Compliance</h3><p>An endpoint MAY implement more than one of the roles defined herein. An endpoint
|
|
is not compliant with this specification if it fails to satisfy one or more
|
|
of the MUST or REQUIRED level requirements defined herein for the roles it implements.</p><p>Normative text within this specification takes precedence over pseudo schemas, which
|
|
in turn take precedence over the XML Schema <a href="#">[XMLSchema1]</a> <a href="#">[XMLSchema2]</a> and
|
|
WSDL <a href="#WSDL1.1">[WSDL1.1]</a> descriptions, which in turn take precedence over examples.</p></div></div><div class="div1">
|
|
<h2><a name="mtomassert" id="mtomassert"></a>3 MTOM Policy Assertion</h2><p>The Web Services Policy 1.5 - Framework <a href="#WS-Policy">[WS-Policy]</a> and Web Services 1.5 -
|
|
Attachment <a href="#WS-PolicyAttachment">[WS-PolicyAttachment]</a> specifications collectively
|
|
define a framework, model and grammar for expressing the
|
|
requirements and general characteristics of entities in an XML Web services-based system.
|
|
To enable an endpoint to describe its ability to use the SOAP Message Transmission
|
|
Optimization Mechanism <a href="#MTOM">[MTOM]</a>, or MTOM with SOAP 1.1 <a href="#MTOMS11">[MTOMS11]</a>, this specification
|
|
defines a single policy assertion that leverages the Web Services Policy framework and attachment
|
|
model for WSDL.</p><div class="div2">
|
|
<h3><a name="model" id="model"></a>3.1 Assertion Model</h3><p>The MTOM policy assertion defines a behavior in which an endpoint
|
|
requires and generates messages serialized as specified in section 3 of the SOAP Message
|
|
Transmission Optimization Mechanism <a href="#MTOM">[MTOM]</a>, or MTOM with SOAP 1.1
|
|
<a href="#MTOMS11">[MTOMS11]</a> specifications.</p></div><div class="div2">
|
|
<h3><a name="syntax" id="syntax"></a>3.2 Assertion Syntax</h3><p>The normative pseudo schema for the MTOM policy assertion is:</p><div class="exampleOuter"><div class="exampleInner"><pre><wsoma:MTOM wsp:Optional? .../></pre></div></div><p>The following describes additional constraints on the pseudo schema listed above:</p><dl><dt class="label">/wsoma:MTOM</dt><dd><p>A policy assertion that specifies that MTOM <a href="#MTOM">[MTOM]</a> MUST be used in messages
|
|
sent to the Web service. It also specifies that responses from the Web service MUST
|
|
be optimized using MTOM <a href="#MTOM">[MTOM]</a>, i.e. that the messages must be sent using the
|
|
<code>multipart/related; type=application/xop+xml</code> mime type.</p></dd><dt class="label">/wsoma:MTOM/@wsp:Optional="true"</dt><dd><p>Per Web Services Policy <a href="#WS-Policy">[WS-Policy]</a>, this is compact notation for two policy
|
|
alternatives, one with and one without the assertion. This indicates that the
|
|
behavior indicated by the assertion is optional, specifically that non-MTOM-encoded exchanges
|
|
are also supported by the endpoint.</p><p>When an endpoint reflects a compact policy expression with the MTOM assertion
|
|
marked with <code>wsp:Optional='true'</code>, it may be difficult to know which alternative
|
|
has been engaged. In such cases, if a request message is received that is an
|
|
<code>application/soap+xml</code> message, then the receiving endpoint SHOULD respond (if at
|
|
all) with an <code>application/soap+xml</code> response message unless there is some other
|
|
indicator that specifies that the response is
|
|
to be sent using MTOM encoding.</p><p> ensure that a response message is serialized as <code>application/xop+xml</code> a client
|
|
can send an <code>application/xop+xml</code> request message.</p><p>For example, when using SOAP/HTTP binding, the <code>Accept</code> HTTP header value of
|
|
<code>multipart/related; type=application/xop+xml</code> in the request message indicates that the response may be
|
|
sent using MTOM encoding.</p></dd><dt class="label">/wsoma:MTOM/@any</dt><dd><p>This is an extensibility mechanism to allow additional attributes to be added to the element.</p></dd></dl><p>The MTOM policy assertion element information item MUST NOT include the
|
|
<code>wsp:Ignorable</code> attribute in its [<code>attributes</code>] property with a value of <code>true</code>.</p></div><div class="div2">
|
|
<h3><a name="attachment" id="attachment"></a>3.3 Assertion Attachment</h3><p>Because the MTOM policy assertion indicates behavior
|
|
over all messages in a binding, the assertion has Endpoint Policy Subject
|
|
<a href="#WS-PolicyAttachment">[WS-PolicyAttachment]</a>.</p><p>WS-PolicyAttachment defines three WSDL 2.0 <a href="#WSDL2.0">[WSDL2.0]</a> policy attachment
|
|
points with Endpoint Policy Subject:</p><ul><li>wsdl:interface</li><li>wsdl:binding</li><li>wsdl:endpoint</li></ul><p>WS-PolicyAttachment also defines three WSDL <a href="#WSDL1.1">[WSDL1.1]</a> policy attachment
|
|
points with Endpoint Policy Subject:</p><ul><li>wsdl:portType</li><li>wsdl:binding</li><li>wsdl:port</li></ul><p>A policy expression containing the MTOM policy assertion
|
|
MUST NOT be attached to a <code>wsdl:interface</code>/<code>wsdl11:portType</code>; the MTOM policy assertion
|
|
specifies a concrete behavior whereas the <code>wsdl:interface</code>/<code>wsdl11:portType</code> is an abstract construct.</p><p>A policy expression containing the MTOM policy assertion MUST, if
|
|
present be attached to either a <code>wsdl:binding</code>/<code>wsdl11:binding</code> or <code>wsdl:endpoint</code>/<code>wsdl11:port</code>.</p><p>When attached to either a <code>wsdl:binding</code>/<code>wsdl11:binding</code> or <code>wsdl:endpoint</code>/<code>wsdl11:port</code> representing a SOAP 1.2 binding,
|
|
the assertion indicates that the mechanism described in SOAP Message Transmission Optimization
|
|
Mechanism <a href="#MTOM">[MTOM]</a> applies for the designated endpoint. When attached to either a <code>wsdl:binding</code>/<code>wsdl11:binding</code> or
|
|
<code>wsdl:endpoint</code>/<code>wsdl11:port</code> representing a SOAP 1.1 binding, the assertion indicates that the mechanism described
|
|
in MTOM with SOAP 1.1 <a href="#MTOMS11">[MTOMS11]</a> applies for the designated endpoint.</p></div></div><div class="div1">
|
|
<h2><a name="security" id="security"></a>4 Security</h2><p>It is strongly RECOMMENDED that policies and assertions be signed to prevent tampering.</p><p>It is RECOMMENDED that policies SHOULD NOT be accepted unless they are signed and have an
|
|
associated security token to specify the signer has proper claims for the given policy. That
|
|
is, a relying party shouldn't rely on a policy unless the policy is signed and presented with
|
|
sufficient claims to pass the relying parties acceptance criteria.</p><p>It should be noted that the mechanisms described in this document could be secured as part
|
|
of a SOAP message using WS-Security <a href="#WS-Security">[WS-Security]</a> or embedded within other objects using
|
|
object-specific security mechanisms.</p><p>To avoid breaking signatures, intermediates MUST NOT change the XML representations
|
|
defined herein. Specifically, intermediaries MUST NOT rewrite XML namespace prefix mappings.
|
|
Similarly, intermediaries MUST NOT remove XML content that explicitly indicates otherwise-implied
|
|
content, and intermediaries MUST NOT insert XML content to make implied values explicit.
|
|
For instance, if a @wsp:Optional attribute is present with a value of "false" an intermediary
|
|
MUST NOT remove it; similarly, if there is no @wsp:Optional attribute, an intermediary MUST NOT add one.</p></div><div class="div1">
|
|
<h2><a name="refs" id="refs"></a>5 References</h2><div class="div2">
|
|
<h3><a name="refs-norm" id="refs-norm"></a>5.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"></a>RFC 2119</dt><dd>
|
|
<a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key words for
|
|
use in RFCs to Indicate Requirement Levels</cite></a>, S. Bradner,
|
|
Editor.
|
|
IETF, March 1997.
|
|
This RFC is available at http://www.ietf.org/rfc/rfc2119.txt.</dd><dt class="label"><a name="RFC2397" id="RFC2397"></a>RFC 2387</dt><dd>
|
|
<a href="http://www.ietf.org/rfc/rfc2616.txt"><cite>Hypertext
|
|
Transfer Protocol -- HTTP/1.1</cite></a>, R. Fielding,
|
|
J. Gettys, J. C. Mogul, H. Frystyk Nielsen, P. Leach,
|
|
L. Masinter and T. Berners-Lee,
|
|
Editors.
|
|
IETF, June 1999.
|
|
This RFC is available at http://www.ietf.org/rfc/rfc2616.txt.</dd><dt class="label"><a name="soap11" id="soap11"></a>SOAP 1.1</dt><dd>
|
|
<a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/"><cite>Simple Object
|
|
Access Protocol (SOAP) 1.1</cite></a>,
|
|
Don Box, David Ehnebuske, Gopal
|
|
Kakivaya, Andrew Layman, Noah Mendelsohn, Henrik Nielsen,
|
|
Satish Thatte, Dave Winer, Editors.
|
|
DevelopMentor, IBM, Microsoft, Lotus Development Corp.,
|
|
UserLand Software, Inc., 30 July 2003.
|
|
This version is http://www.w3.org/TR/2000/NOTE-SOAP-20000508/.</dd><dt class="label"><a name="SOAP-PART1" id="SOAP-PART1"></a>SOAP Part 1</dt><dd>
|
|
<a href="http://www.w3.org/TR/2007/REC-soap12-part1-20070427/"><cite>SOAP Version 1.2 Part 1: Messaging Framework</cite></a>,
|
|
Martin Gudgin, Marc Hadley, Noah Mendelsohn, Jean-Jacques Moreau,
|
|
Henrik Frystyk Nielsen, Anish Karmarkar, Yves Lafon, Editors.
|
|
World Wide Web Consortium, 27 April 2007.
|
|
This version is http://www.w3.org/TR/2007/REC-soap12-part1-20070427/.
|
|
The <a href="http://www.w3.org/TR/soap12-part1/">latest version</a> is
|
|
available at http://www.w3.org/TR/soap12-part1/.</dd><dt class="label"><a name="MTOM" id="MTOM"></a>MTOM</dt><dd>
|
|
<a href="http://www.w3.org/TR/2005/REC-soap12-mtom-20050125/"><cite>SOAP Message Transmission Optimization Mechanism</cite></a>,
|
|
M. Gudgin, et al, January 2005.</dd><dt class="label"><a name="XOP" id="XOP"></a>XOP</dt><dd>
|
|
<a href="http://www.w3.org/TR/xop10/"><cite>XML-binary Optimized Packaging</cite></a>,
|
|
M. Gudgin, et al, January 2005. </dd><dt class="label"><a name="WSDL2.0" id="WSDL2.0"></a>WSDL2.0</dt><dd>
|
|
<a href="http://www.w3.org/TR/2006/CR-wsdl20-20060327/"><cite>Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language</cite></a>,
|
|
Roberto Chinnici, Jean-Jacques Moreau, Arthur Ryman, Sanjiva Weerawarana, Editors.
|
|
World Wide Web Consortium, 26 June 2007.
|
|
This version is http://www.w3.org/TR/2007/REC-wsdl20-20070626/.
|
|
The <a href="http://www.w3.org/TR/wsdl20/">latest version</a> is
|
|
available at http://www.w3.org/TR/wsdl20/.</dd><dt class="label"><a name="WSDL1.1" id="WSDL1.1"></a>WSDL1.1</dt><dd>
|
|
<a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315"><cite>Web Services Description Language (WSDL) 1.1</cite></a>,
|
|
E. Christensen, et al, March 2001. </dd><dt class="label"><a name="WS-Policy" id="WS-Policy"></a>WS-Policy</dt><dd>
|
|
<a href="http://www.w3.org/TR/ws-policy"><cite>Web Services Policy 1.5 - Framework</cite></a>,
|
|
A. Vedamuthu, et al., Editors.
|
|
World Wide Web Consortium, 4 September 2007.
|
|
This version is http://www.w3.org/TR/2007/REC-ws-policy-20070904/.
|
|
The <a href="http://www.w3.org/TR/ws-policy">latest version</a> is available at http://www.w3.org/TR/ws-policy/.
|
|
</dd><dt class="label"><a name="WS-PolicyAttachment" id="WS-PolicyAttachment"></a>WS-PolicyAttachment</dt><dd>
|
|
<a href="http://www.w3.org/TR/ws-policy-attach"><cite>Web Services Policy 1.5 - Attachment</cite></a>,
|
|
Asir Vedamuthu, et al., Editors.
|
|
World Wide Web Consortium, 4 September 2007.
|
|
This version is http://www.w3.org/TR/2007/REC-ws-policy-attach-20070904/.
|
|
The <a href="http://www.w3.org/TR/ws-policy-attach">latest version</a> is available at http://www.w3.org/TR/ws-policy-attach/.
|
|
</dd><dt class="label"><a name="WS-Security" id="WS-Security"></a>WS-Security</dt><dd>
|
|
<a href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf"><cite>Web Services Security: SOAP Message Security 1.0</cite></a>,
|
|
A. Nadalin, et al, March 2004.</dd><dt class="label"><a name="XMLSchemaP1" id="XMLSchemaP1"></a>XML Schema Part 1</dt><dd>
|
|
<a href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/"><cite>
|
|
XML Schema Part 1:
|
|
Structures Second Edition</cite></a>, David Beech, Murray Maloney,
|
|
Henry S. Thompson, and Noah Mendelsohn, Editors.
|
|
World Wide Web Consortium, 28 October 2004.
|
|
This version is http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/
|
|
The <a href="http://www.w3.org/TR/xmlschema-1/">latest version</a> is
|
|
available at http://www.w3.org/TR/xmlschema-1/.</dd><dt class="label"><a name="XMLSchemaP2" id="XMLSchemaP2"></a>XML Schema Part 2</dt><dd>
|
|
<a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/"><cite>
|
|
XML Schema Part 2:
|
|
Datatypes Second Edition</cite></a>,
|
|
Ashok Malhotra and Paul V. Biron, Editors.
|
|
World Wide Web Consortium, 28 October 2004.
|
|
This version is http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/.
|
|
The <a href="http://www.w3.org/TR/xmlschema-2/">latest version</a> is
|
|
available at http://www.w3.org/TR/xmlschema-2/.</dd><dt class="label"><a name="RFC3986" id="RFC3986"></a>RFC 3986</dt><dd>
|
|
<a href="http://www.ietf.org/rfc/rfc3986.txt"><cite>Uniform Resource
|
|
Identifiers (URI): Generic Syntax</cite></a>, T. Berners-Lee,
|
|
R. Fielding and L. Masinter, Editors.
|
|
IETF, January 2005.
|
|
<em>Obsoletes: RFC 2396, RFC 2732</em>.
|
|
This RFC is available at http://www.ietf.org/rfc/rfc3986.txt.</dd><dt class="label"><a name="XMLNS" id="XMLNS"></a>Namespaces in XML</dt><dd>
|
|
<a href="http://www.w3.org/TR/2006/REC-xml-names-20060816"><cite>
|
|
Namespaces in
|
|
XML (Second Edition)</cite></a>, Tim Bray, Dave Hollander,
|
|
Andrew Layman, and Richard Tobin, Editors.
|
|
World Wide Web Consortium, 16 August 2006.
|
|
This version is http://www.w3.org/TR/2006/REC-xml-names-20060816.
|
|
The <a href="http://www.w3.org/TR/REC-xml-names">latest version</a> is
|
|
available at http://www.w3.org/TR/REC-xml-names.</dd><dt class="label"><a name="XML" id="XML"></a>XML 1.0</dt><dd>
|
|
<a href="http://www.w3.org/TR/2006/REC-xml-20060816"><cite>Extensible
|
|
Markup Language (XML) 1.0 (Fourth Edition)</cite></a>, Jean Paoli,
|
|
Eve Maler, Tim Bray, <em>et. al.</em>, Editors.
|
|
World Wide Web Consortium, 16 August 2006.
|
|
This version is http://www.w3.org/TR/2006/REC-xml-20060816.
|
|
The <a href="http://www.w3.org/TR/REC-xml">latest version</a> is
|
|
available at http://www.w3.org/TR/REC-xml.</dd><dt class="label"><a name="XMLInfoSet" id="XMLInfoSet"></a>XML InfoSet</dt><dd>
|
|
<a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204"><cite>XML
|
|
Information Set (Second Edition)</cite></a>, Richard Tobin and
|
|
John Cowan, Editors.
|
|
World Wide Web Consortium, 04 February 2004.
|
|
This version is http://www.w3.org/TR/2004/REC-xml-infoset-20040204.
|
|
The <a href="http://www.w3.org/TR/xml-infoset">latest version</a> is
|
|
available at http://www.w3.org/TR/xml-infoset.</dd></dl></div><div class="div2">
|
|
<h3><a name="refs-inform" id="refs-inform"></a>5.2 Informative References</h3><dl><dt class="label"><a name="MTOMS11" id="MTOMS11"></a>MTOMS11</dt><dd>
|
|
<a href="http://www.w3.org/Submission/soap11mtom10/"><cite>SOAP 1.1 Binding for MTOM 1.0</cite></a>,
|
|
J. Marsh, et al, April 2006.</dd><dt class="label"><a name="CommentArchive" id="CommentArchive"></a>XMLP Comments</dt><dd>XML Protocol Comments Archive (See http://lists.w3.org/Archives/Public/xmlp-comments/.)</dd><dt class="label"><a name="DiscussionArchive" id="DiscussionArchive"></a>XMLP Dist-App</dt><dd>XML Protocol Discussion
|
|
Archive (See http://lists.w3.org/Archives/Public/xml-dist-app/.)</dd><dt class="label"><a name="XMLPCharter" id="XMLPCharter"></a>XMLP Charter</dt><dd>XML Protocol Charter (See http://www.w3.org/2005/07/XML-Protocol-Charter.)</dd></dl></div></div></div><div class="back"><div class="div1">
|
|
<h2><a name="schema" id="schema"></a>A Appendix I – XML Schema</h2><p>A normative copy of the XML Schema <a href="#">[XMLSchema1]</a> <a href="#">[XMLSchema2]</a> description for this
|
|
specification can be retrieved from the following address:</p><div class="exampleOuter"><div class="exampleInner"><pre>http://www.w3.org/2007/08/soap12-mtom-policy.xsd</pre></div></div><p>A non-normative copy of the XML Schema description is listed below for convenience.</p><div class="exampleOuter"><div class="exampleInner"><pre><xs:schema
|
|
targetNamespace="http://www.w3.org/2007/08/soap12-mtom-policy"
|
|
xmlns:tns="http://www.w3.org/2007/08/soap12-mtom-policy"
|
|
xmlns:wsp="http://www.w3.org/ns/ws-policy"
|
|
xmlns:xs="http://www.w3.org/2001/XMLSchema"
|
|
elementFormDefault="qualified"
|
|
attributeFormDefault="unqualified" >
|
|
|
|
<xs:import
|
|
namespace="http://www.w3.org/ns/ws-policy"
|
|
schemaLocation="http://www.w3.org/2007/02/ws-policy.xsd" />
|
|
|
|
<xs:element
|
|
name="MTOM"
|
|
type="tns:MTOMType" />
|
|
|
|
<xs:complexType name="MTOMType" >
|
|
<xs:attribute ref="wsp:Optional" />
|
|
<xs:anyAttribute namespace="##other" processContents="lax" />
|
|
</xs:complexType>
|
|
</xs:schema>
|
|
</pre></div></div></div><div class="div1">
|
|
<h2><a name="id2268410" id="id2268410"></a>B Acknowledgements (Non-Normative)</h2><p>This document is the work of the W3C XML Protocol Working Group.</p><p>Participants in the Working Group are (at the time of writing, and by
|
|
alphabetical order): Glen Daniels (Progress Software),
|
|
Chris Ferris (IBM Corporation),
|
|
Anish Karmarkar (Oracle Corporation),
|
|
Doug Kohlert (Sun Microsystems, Inc.),
|
|
Yves Lafon (W3C),
|
|
Jonathan Marsh (WSO2),
|
|
Jeff Mischkinsky (Oracle Corporation),
|
|
Pete Wenzel (Sun Microsystems, Inc.).
|
|
</p><p>The people who have contributed to discussions on
|
|
<a href="mailto:xml-dist-app@w3.org">xml-dist-app@w3.org</a>
|
|
are also gratefully acknowledged.</p></div></div></body></html>
|