- From: Frederick Hirsch via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 07 Dec 2006 16:35:54 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv17618
Modified Files:
ws-policy-primer.xml
Log Message:
Implemented the resolution for issue 3952 as outlined in resolution proposed in 6 Dec 06 meeting, http://lists.w3.org/Archives/Public/public-ws-policy/2006Dec/0018.html" (with editorial correction replacing "for as" with "as"), Editors' action 92
Index: ws-policy-primer.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-primer.xml,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -d -r1.23 -r1.24
--- ws-policy-primer.xml 28 Nov 2006 00:45:59 -0000 1.23
+++ ws-policy-primer.xml 7 Dec 2006 16:35:51 -0000 1.24
@@ -400,7 +400,8 @@
</example>
<p>The <code>mtom:OptimizedMimeSerialization</code> element is a policy assertion. (The
prefix <code>mtom</code> is used here to denote the Optimized MIME Serialization Policy
- namespace.) This assertion identifies the use of MIME Multipart/Related serialization for
+ namespace.) This assertion identifies the use of MIME Multipart/Related serialization
+ as required for request and response
messages. Policy-aware clients can recognize this policy assertion and engage Optimized
MIME Serialization for messages. The semantics of this assertion are reflected in
messages: they use an optimized wire format (MIME Multipart/Related serialization).</p>
@@ -413,7 +414,13 @@
requirements of the service provider.</p>
<p>In the example below, the Optimized MIME Serialization policy assertion is marked
optional. This policy expression allows the use of optimization and requires the use of
- addressing and one of transport- or message-level security.</p>
+ addressing and one of transport- or message-level security.
+ If a client sends an optimized (MTOM) message, this will be indicated by characteristics associated
+ by using such an optimized message, including a wire format that is a Multipart/Related message and
+ a content-type header of "application/xop+xml" for the outer package. In this case, the response message
+ will also be optimized, also having a Multipart/Related message and content-type header of "application/xop+xml".
+ Note that when optimized messages are used, the Multipart/Related message can have a single part containing the
+ primary SOAP envelope.</p>
<example>
<head>Optional MIME Serialization, Addressing and Transport- OR Message-Level Security
Policy Expression</head>
@@ -1890,7 +1897,17 @@
<loc href="http://lists.w3.org/Archives/Public/public-ws-policy-eds/2006Nov/0054.html">Umit</loc> to the list of editors.
Editors' action <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/86">86</loc>.
</td>
- </tr>
+ </tr>
+ <tr>
+ <td>20061207</td>
+ <td>FH</td>
+ <td>Implemented the resolution for
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3952">issue 3952</loc>
+ <loc href="http://lists.w3.org/Archives/Public/public-ws-policy/2006Dec/0018.html">as outlined</loc>
+ (with editorial correction replacing "for as" with "as"),
+ Editors' action <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/92">92</loc>.
+ </td>
+ </tr>
</tbody>
</table>
</inform-div1>
Received on Thursday, 7 December 2006 16:36:04 UTC