garbled text in MTOM Serialization Policy Assertion

Fabian Ritzmann <[email protected]> Tue, 09 Oct 2007 15:48:44 +0300
Newsgroups gmane.text.xml.distributed
Message-ID <[email protected]> 
This is a multi-part message in MIME format.

--Boundary_(ID_WfcEv3PfNLTC6uCQyHUnuQ)
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT

Hi,

I am commenting in lieu of Monica Martin and Pete Wenzel. They had 
reviewed the LC edition [1] of the MTOM Serialization Policy Assertion 
1.1 document. The same issue is present in the latest editor's working 
draft [2].

The text in paragraph 3.2 is garbled. Here is how it looks like now:

/wsoma:MTOM/@wsp:Optional="true"

    Per Web Services Policy [WS-Policy]
    <http://www.w3.org/2000/xp/Group/2/06/LC/mtompolicy.html#WS-Policy>,
    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.

    When an endpoint reflects a compact policy expression with the MTOM
    assertion marked with |wsp:Optional='true'|, it may be difficult to
    know which alternative has been engaged. In such cases, if a request
    message is received that is an |application/soap+xml| message, then
    the receiving endpoint SHOULD respond (if at all) with an
    |application/soap+xml| response message unless there is some other
    indicator that specifies that the response is to be sent using MTOM
    encoding.

    ensure that a response message is serialized as
    |application/xop+xml| a client can send an |application/xop+xml|
    request message.

    For example, when using SOAP/HTTP binding, the |Accept| HTTP header
    value of |multipart/related; type=application/xop+xml| in the
    request message indicates that the response may be sent using MTOM
    encoding.


We assume that it was intended to say instead:

/wsoma:MTOM/@wsp:Optional="true"

    Per Web Services Policy [WS-Policy]
    <http://www.w3.org/2000/xp/Group/2/06/LC/mtompolicy.html#WS-Policy>,
    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.

    When an endpoint reflects a compact policy expression with the MTOM
    assertion marked with |wsp:Optional='true'|, it may be difficult to
    know which alternative has been engaged. In such cases, if a request
    message is received that is an |application/soap+xml| message, then
    the receiving endpoint SHOULD respond (if at all) with an
    |application/soap+xml| response message unless there is some other
    indicator that specifies that the response is to be sent using MTOM
    encoding.

    For example, when using SOAP/HTTP binding, the |Accept| HTTP header
    value of |multipart/related; type=application/xop+xml| in the
    request message indicates that the response may be sent using MTOM
    encoding.

    In the absence of such an indicator, a client can ensure that a
    response message is serialized as |application/xop+xml| by sending
    an |application/xop+xml| request message.


Best regards,

Fabian Ritzmann


[1] http://www.w3.org/2000/xp/Group/2/06/LC/mtompolicy.html
[2] http://www.w3.org/TR/2007/WD-soap12-mtom-policy-20070918/

-- 
Fabian Ritzmann
Sun Microsystems, Inc.
Stella Business Park             Phone +358-9-525 562 96
Lars Sonckin kaari 12            Fax   +358-9-525 562 52
02600 Espoo                      Email [email protected]
Finland


--Boundary_(ID_WfcEv3PfNLTC6uCQyHUnuQ)
Content-type: text/html; charset=ISO-8859-1
Content-transfer-encoding: 7BIT

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
Hi,<br>
<br>
I am commenting in lieu of Monica Martin and Pete Wenzel. They had
reviewed the LC edition [1] of the MTOM Serialization Policy Assertion
1.1 document. The same issue is present in the latest editor's working
draft [2].<br>
<br>
The text in paragraph 3.2 is garbled. Here is how it looks like now:<br>
<br>
<dl>
  <dt class="label">/wsoma:MTOM/@wsp:Optional="true"</dt>
  <dd>
    <p>Per Web Services Policy <a
 href="http://www.w3.org/2000/xp/Group/2/06/LC/mtompolicy.html#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>
</dl>
<br>
We assume that it was intended to say instead:<br>
<br>
<dl>
  <dt class="label">/wsoma:MTOM/@wsp:Optional="true"</dt>
  <dd>
    <p>Per Web Services Policy <a
 href="http://www.w3.org/2000/xp/Group/2/06/LC/mtompolicy.html#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>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>
    <p>In the absence of such an indicator, a client can ensure that a
response message is serialized as <code>application/xop+xml</code> by
sending an <code>application/xop+xml</code> request message.</p>
  </dd>
  <dt><br>
  </dt>
</dl>
Best regards,<br>
<br>
Fabian Ritzmann<br>
<br>
<br>
[1] <a class="moz-txt-link-freetext" href="http://www.w3.org/2000/xp/Group/2/06/LC/mtompolicy.html">http://www.w3.org/2000/xp/Group/2/06/LC/mtompolicy.html</a><br>
[2] <a class="moz-txt-link-freetext" href="http://www.w3.org/TR/2007/WD-soap12-mtom-policy-20070918/">http://www.w3.org/TR/2007/WD-soap12-mtom-policy-20070918/</a><br>
<br>
<pre class="moz-signature" cols="72">-- 
Fabian Ritzmann
Sun Microsystems, Inc.
Stella Business Park             Phone +358-9-525 562 96
Lars Sonckin kaari 12            Fax   +358-9-525 562 52
02600 Espoo                      Email <a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a>
Finland</pre>
</body>
</html>

--Boundary_(ID_WfcEv3PfNLTC6uCQyHUnuQ)--