Re: Proposal for MTOM section 4 conformance in MTOM policy assertion doc

This is a multipart message in MIME format.
--=_alternative 0047DCC5852573A7_=
Content-Type: text/plain; charset="US-ASCII"

Anish,

Looks good, just a couple of minor editorial tweaks. Other than that, I 
would think that this is an effective
resolution. Do others agree?

When the binding used for a service is SOAP 1.2 HTTP binding 
[http://www.w3.org/TR/2007/REC-soap12-part2-20070427/#soapinhttp], and 
the MTOM policy assertion is in scope, that binding MUST conform to 
section 4 of the SOAP Message Transmission Optimization Mechanism [MTOM] 
specification.

Cheers,

Christopher Ferris
STSM, Software Group Standards Strategy
email: [email protected]
blog: http://www.ibm.com/developerworks/blogs/page/chrisferris
phone: +1 508 234 2986



Anish Karmarkar <[email protected]> 
Sent by: [email protected]
11/21/2007 03:57 PM

To
"Xml-Dist-App@W3. Org" <[email protected]>
cc

Subject
Proposal for MTOM section 4 conformance in MTOM policy assertion  doc







Resending with an appropriate subject.
-Anish
--

Anish Karmarkar wrote:
> 
> I took an AI to send a proposal to amend section 3.3 of MTOM policy 
> assertion [1] document to talk about what is the expected behavior when 
> SOAP/HTTP binding is used, i.e., whether or not section 4 of MTOM is 
> engaged. Below is the proposal:
> 
> Add the following at the end of section 3.3:
> ----------
> When the binding used for a service is SOAP 1.2 HTTP binding 
> [http://www.w3.org/TR/2007/REC-soap12-part2-20070427/#soapinhttp], and 
> the MTOM policy assertion is in scope that binding MUST conform to 
> section 4 of SOAP Message Transmission Optimization Mechanism [MTOM] 
> specification.
> ----------
> 
> Comments?
> 
> -Anish
> -- 
> 
> [1] http://www.w3.org/TR/2007/WD-soap12-mtom-policy-20070918/
> 



--=_alternative 0047DCC5852573A7_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Anish,</font>
<br>
<br><font size=2 face="sans-serif">Looks good, just a couple of minor editorial
tweaks. Other than that, I would think that this is an effective</font>
<br><font size=2 face="sans-serif">resolution. Do others agree?</font>
<br>
<br><tt><font size=2>When the binding used for a service is SOAP 1.2 HTTP
binding </font></tt>
<br><tt><font size=2>[http://www.w3.org/TR/2007/REC-soap12-part2-20070427/#soapinhttp],
and </font></tt>
<br><tt><font size=2>the MTOM policy assertion is in scope, that binding
MUST conform to <br>
section 4 of the SOAP Message Transmission Optimization Mechanism [MTOM]
<br>
specification.</font></tt>
<br>
<br><font size=2 face="sans-serif">Cheers,</font>
<br>
<br><font size=2 face="sans-serif">Christopher Ferris<br>
STSM, Software Group Standards Strategy<br>
email: [email protected]<br>
blog: http://www.ibm.com/developerworks/blogs/page/chrisferris<br>
phone: +1 508 234 2986</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Anish Karmarkar &lt;[email protected]&gt;</b>
</font>
<br><font size=1 face="sans-serif">Sent by: [email protected]</font>
<p><font size=1 face="sans-serif">11/21/2007 03:57 PM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">&quot;Xml-Dist-App@W3. Org&quot; &lt;[email protected]&gt;</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Proposal for MTOM section 4 conformance
in MTOM policy assertion &nbsp;doc</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=2><br>
Resending with an appropriate subject.<br>
-Anish<br>
--<br>
<br>
Anish Karmarkar wrote:<br>
&gt; <br>
&gt; I took an AI to send a proposal to amend section 3.3 of MTOM policy
<br>
&gt; assertion [1] document to talk about what is the expected behavior
when <br>
&gt; SOAP/HTTP binding is used, i.e., whether or not section 4 of MTOM
is <br>
&gt; engaged. Below is the proposal:<br>
&gt; <br>
&gt; Add the following at the end of section 3.3:<br>
&gt; ----------<br>
&gt; When the binding used for a service is SOAP 1.2 HTTP binding <br>
&gt; [http://www.w3.org/TR/2007/REC-soap12-part2-20070427/#soapinhttp],
and <br>
&gt; the MTOM policy assertion is in scope that binding MUST conform to
<br>
&gt; section 4 of SOAP Message Transmission Optimization Mechanism [MTOM]
<br>
&gt; specification.<br>
&gt; ----------<br>
&gt; <br>
&gt; Comments?<br>
&gt; <br>
&gt; -Anish<br>
&gt; -- <br>
&gt; <br>
&gt; [1] http://www.w3.org/TR/2007/WD-soap12-mtom-policy-20070918/<br>
&gt; <br>
<br>
</font></tt>
<br>
--=_alternative 0047DCC5852573A7_=--