- From: Frederick Hirsch via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 16 Mar 2007 04:58:50 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv984
Modified Files:
ws-policy-primer.html ws-policy-primer.xml
Log Message:
Resolution for issue 4253, editors item 191
Index: ws-policy-primer.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-primer.html,v
retrieving revision 1.43
retrieving revision 1.44
diff -u -d -r1.43 -r1.44
--- ws-policy-primer.html 16 Mar 2007 03:29:42 -0000 1.43
+++ ws-policy-primer.html 16 Mar 2007 04:58:46 -0000 1.44
@@ -192,10 +192,21 @@
illustrates a policy expression that requires the use of addressing.</p><div class="exampleOuter">
<p style="text-align: left" class="exampleHead"><i><span>Example 2-2. </span>Policy Expression</i></p><div class="exampleInner"><pre><Policy>
<wsap:UsingAddressing />
-</Policy></pre></div></div><p>The policy expression in the above example consists of a <code>Policy</code> main element
- and a child element <code>wsap:UsingAddressing.</code> Child elements of the
- <code>Policy</code> element are policy assertions. Contoso attaches the above policy
- expression to a WSDL binding description.</p><p>The <code>wsap:UsingAddressing</code> element is a policy assertion. (The prefix
+</Policy></pre></div></div><p>
+ The policy expression in the above example consists of a Policy main
+ element and a child element wsap:UsingAddressing. Child elements of
+ the Policy element are policy assertions. Contoso attaches the above
+ policy expression to a WSDL binding description.
+ </p><div class="exampleOuter">
+<p style="text-align: left" class="exampleHead"><i><span>Example 2-3. </span>Policy Expression Attached to Binding</i></p><div class="exampleInner"><pre><wsdl:binding name="AddressingBinding" type="tns:RealTimeDataInterface" >
+ <Policy>
+ <wsap:UsingAddressing />
+ </Policy>
+ ...
+</wsdl:binding>
+ </pre></div></div><p>
+ Policies can also be attached to WSDL using references (See <a href="#Referencing_Policy_Expressions"><b>2.10 Referencing Policy Expressions</b></a>.)
+ </p><p>The <code>wsap:UsingAddressing</code> element is a policy assertion. (The prefix
<code>wsap</code> is used here to denote the Web Services Addressing – WSDL Binding XML
Namespace.) This assertion identifies the use of Web Services Addressing information
headers. A policy-aware client can recognize this policy assertion, engage addressing
@@ -208,7 +219,7 @@
describes the message.</p></div><div class="div2">
<h3><a name="secure-message" id="secure-message"></a>2.3 Secure Message</h3><p>In addition to requiring the use of addressing, Contoso requires the use of
transport-level security for protecting messages.</p><div class="exampleOuter">
-<p style="text-align: left" class="exampleHead"><i><span>Example 2-3. </span>Secure Message</i></p><div class="exampleInner"><pre><soap:Envelope>
+<p style="text-align: left" class="exampleHead"><i><span>Example 2-4. </span>Secure Message</i></p><div class="exampleInner"><pre><soap:Envelope>
<soap:Header>
<wss:Security soap:mustUnderstand="1" >
<wsu:Timestamp wsu:Id="_0">
@@ -227,7 +238,7 @@
Security and Utility namespaces.)</p><p>Similar to the use of addressing, Contoso indicates the use of transport-level security
using a policy expression. The example below illustrates a policy expression that requires
the use of addressing and transport-level security for securing messages.</p><div class="exampleOuter">
-<p style="text-align: left" class="exampleHead"><i><span>Example 2-4. </span>Addressing and Security Policy Expression</i></p><div class="exampleInner"><pre><Policy>
+<p style="text-align: left" class="exampleHead"><i><span>Example 2-5. </span>Addressing and Security Policy Expression</i></p><div class="exampleInner"><pre><Policy>
<wsap:UsingAddressing />
<sp:TransportBinding>...</sp:TransportBinding>
</Policy></pre></div></div><p>The <code>sp:TransportBinding</code> element is a policy assertion. (The prefix
@@ -270,7 +281,7 @@
assertions. These assertions are combined using the <code>All</code> operator. Combining
policy assertions using the <code>Policy</code> or <code>All</code> operator means that
all the behaviors represented by these assertions are required.</p><div class="exampleOuter">
-<p style="text-align: left" class="exampleHead"><i><span>Example 2-5. </span>Addressing and Security Policy Expression</i></p><div class="exampleInner"><pre><All>
+<p style="text-align: left" class="exampleHead"><i><span>Example 2-6. </span>Addressing and Security Policy Expression</i></p><div class="exampleInner"><pre><All>
<wsap:UsingAddressing />
<sp:TransportBinding>…</sp:TransportBinding>
</All></pre></div></div><p>In addition to requiring the use of addressing, Contoso allows either the use of
@@ -278,7 +289,7 @@
can indicate this choice of behaviors in a machine-readable form. To indicate the use of
message-level security for protecting messages, Contoso uses the
<code>sp:AsymmetricBinding</code> policy assertion (see the example below).</p><div class="exampleOuter">
-<p style="text-align: left" class="exampleHead"><i><span>Example 2-6. </span>Asymmetric Binding Security Policy Assertion</i></p><div class="exampleInner"><pre><sp:AsymmetricBinding>…</sp:AsymmetricBinding></pre></div></div><p>The <code>sp:AsymmetricBinding</code> element is a policy assertion. (The prefix
+<p style="text-align: left" class="exampleHead"><i><span>Example 2-7. </span>Asymmetric Binding Security Policy Assertion</i></p><div class="exampleInner"><pre><sp:AsymmetricBinding>…</sp:AsymmetricBinding></pre></div></div><p>The <code>sp:AsymmetricBinding</code> element is a policy assertion. (The prefix
<code>sp</code> is used here to denote the Web Services Security Policy namespace.) This
assertion identifies the use of message-level security – such as <em>WS-Security
1.0</em> - for protecting messages. Policy-aware clients can recognize this policy
@@ -288,7 +299,7 @@
<code>ExactlyOne</code> operator requires exactly one of the behaviors represented by
the assertions. The policy expression in the example below requires the use of either
transport- or message-level security for protecting messages.</p><div class="exampleOuter">
-<p style="text-align: left" class="exampleHead"><i><span>Example 2-7. </span>Transport- or Message-Level Security Policy Expression</i></p><div class="exampleInner"><pre><ExactlyOne>
+<p style="text-align: left" class="exampleHead"><i><span>Example 2-8. </span>Transport- or Message-Level Security Policy Expression</i></p><div class="exampleInner"><pre><ExactlyOne>
<sp:TransportBinding>…</sp:TransportBinding>
<sp:AsymmetricBinding>…</sp:AsymmetricBinding>
</ExactlyOne></pre></div></div><p>Contoso requires the use of addressing and requires the use of either transport- or
@@ -297,7 +308,7 @@
to represent different combinations of behaviors (capabilities and requirements). The
policy expression in the example below requires the use of addressing and one of
transport- or message-level security for protecting messages.</p><div class="exampleOuter">
-<p style="text-align: left" class="exampleHead"><i><span>Example 2-8. </span>Addressing and Transport- OR Message-Level Security Policy Expression</i></p><div class="exampleInner"><pre><All>
+<p style="text-align: left" class="exampleHead"><i><span>Example 2-9. </span>Addressing and Transport- OR Message-Level Security Policy Expression</i></p><div class="exampleInner"><pre><All>
<wsap:UsingAddressing />
<ExactlyOne>
<sp:TransportBinding>…</sp:TransportBinding>
@@ -311,7 +322,7 @@
Optimized MIME Serialization and expresses this optional behavior in a machine-readable
form.</p><p>To indicate the use of optimization using the Optimized MIME Serialization, Contoso uses
the <code>mtom:OptimizedMimeSerialization</code> policy assertion (see the example below).</p><div class="exampleOuter">
-<p style="text-align: left" class="exampleHead"><i><span>Example 2-9. </span>Optimized MIME Serialization Policy Assertion</i></p><div class="exampleInner"><pre><mtom:OptimizedMimeSerialization /></pre></div></div><p>The <code>mtom:OptimizedMimeSerialization</code> element is a policy assertion. (The
+<p style="text-align: left" class="exampleHead"><i><span>Example 2-10. </span>Optimized MIME Serialization Policy Assertion</i></p><div class="exampleInner"><pre><mtom:OptimizedMimeSerialization /></pre></div></div><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
as required for request and response
@@ -332,7 +343,7 @@
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><div class="exampleOuter">
-<p style="text-align: left" class="exampleHead"><i><span>Example 2-10. </span>Optional MIME Serialization, Addressing and Transport- OR Message-Level Security
+<p style="text-align: left" class="exampleHead"><i><span>Example 2-11. </span>Optional MIME Serialization, Addressing and Transport- OR Message-Level Security
Policy Expression</i></p><div class="exampleInner"><pre><All>
<mtom:OptimizedMimeSerialization wsp:Optional="true"/>
<wsap:UsingAddressing />
@@ -363,7 +374,7 @@
Using the <code>wsp:Optional</code> attribute would be incorrect in this scenario, since it would indicate that the behavior
would not occur if the alternative without the assertion were selected.
</p><div class="exampleOuter">
-<p style="text-align: left" class="exampleHead"><i><span>Example 2-11. </span>Ignorable Logging Policy Assertion</i></p><div class="exampleInner"><pre><log:Logging wsp:Ignorable="true" /></pre></div></div><p>
+<p style="text-align: left" class="exampleHead"><i><span>Example 2-12. </span>Ignorable Logging Policy Assertion</i></p><div class="exampleInner"><pre><log:Logging wsp:Ignorable="true" /></pre></div></div><p>
(The log: prefix is used here to denote a hypothetical example namespace for this example logging policy assertion.)
</p><p>
The attribute <code>wsp:Ignorable</code> is of type <em>xs:boolean</em>.
@@ -409,7 +420,7 @@
assertion requires the use of a specific transport token and further qualifies the
behavior of the <code>sp:TransportBinding</code> policy assertion (which already requires
the use of transport-level security for protecting messages).</p><div class="exampleOuter">
-<p style="text-align: left" class="exampleHead"><i><span>Example 2-12. </span>Transport Security Policy Assertion</i></p><div class="exampleInner"><pre><sp:TransportBinding>
+<p style="text-align: left" class="exampleHead"><i><span>Example 2-13. </span>Transport Security Policy Assertion</i></p><div class="exampleInner"><pre><sp:TransportBinding>
<Policy>
<sp:TransportToken>
<Policy>
@@ -456,7 +467,7 @@
expression: the <code>wsu:Id</code> <code>xml:id</code> and <code>Name</code> attributes. A
<code>PolicyReference</code> element can be used to reference a policy expression
identified using either of these mechanisms.</p><div class="exampleOuter">
-<p style="text-align: left" class="exampleHead"><i><span>Example 2-13. </span>Common Policy Expression</i></p><div class="exampleInner"><pre><Policy wsu:Id=”common”>
+<p style="text-align: left" class="exampleHead"><i><span>Example 2-14. </span>Common Policy Expression</i></p><div class="exampleInner"><pre><Policy wsu:Id=”common”>
<mtom:OptimizedMimeSerialization wsp:Optional="true"/>
<wsap:UsingAddressing />
</Policy></pre></div></div><p>In the example above, the <code>wsu:Id</code> attribute is used to identify a policy
@@ -468,7 +479,7 @@
combining the document IRI, <code>#</code> and the value of the <code>wsu:Id</code>
attribute.)</p><p> In addition to the Example 2-12, Contoso could have used either the xml:id or wsu:Id.
An example of the use of xml:id similar to that of wsu:Id is shown in Example 2-13. </p><div class="exampleOuter">
-<p style="text-align: left" class="exampleHead"><i><span>Example 2-14. </span>Common Policy Expression [xml:id]</i></p><div class="exampleInner"><pre><Policy xml:id=”common”>
+<p style="text-align: left" class="exampleHead"><i><span>Example 2-15. </span>Common Policy Expression [xml:id]</i></p><div class="exampleInner"><pre><Policy xml:id=”common”>
<mtom:OptimizedMimeSerialization wsp:Optional="true"/>
<wsap:UsingAddressing />
</Policy></pre></div></div><p> Conditions and constraints on the use of the |xml:id| attribute in conjunction with Canonical
@@ -483,13 +494,13 @@
</p></div><p>For re-use, a <code>PolicyReference</code> element can be used to reference a policy
expression as a standalone policy or within another policy expression. The example below
is a policy expression that re-uses the common policy expression above.</p><div class="exampleOuter">
-<p style="text-align: left" class="exampleHead"><i><span>Example 2-15. </span>PolicyReference to Common Policy Expression</i></p><div class="exampleInner"><pre><PolicyReference URI="#common"/></pre></div></div><p>For referencing a policy expression within the same XML document, Contoso uses the
+<p style="text-align: left" class="exampleHead"><i><span>Example 2-16. </span>PolicyReference to Common Policy Expression</i></p><div class="exampleInner"><pre><PolicyReference URI="#common"/></pre></div></div><p>For referencing a policy expression within the same XML document, Contoso uses the
<code>wsu:Id</code> attribute for identifying a policy expression and an IRI to this ID
value for referencing this policy expression using a <code>PolicyReference</code> element.</p><p>The example below is a policy expression that re-uses the common policy expression within
another policy expression. This policy expression requires the use of addressing, one of
transport- or message-level security for protecting messages and allows the use of
optimization.</p><div class="exampleOuter">
-<p style="text-align: left" class="exampleHead"><i><span>Example 2-16. </span>Secure Policy Expression</i></p><div class="exampleInner"><pre><Policy wsu:Id=”secure”>
+<p style="text-align: left" class="exampleHead"><i><span>Example 2-17. </span>Secure Policy Expression</i></p><div class="exampleInner"><pre><Policy wsu:Id=”secure”>
<All>
<PolicyReference URI="#common"/>
<ExactlyOne>
@@ -504,11 +515,11 @@
relies on additional out of band information. In the example below, the <code>Name</code>
attribute identifies the policy expression. The IRI of this policy expression is
<code>http://real.contoso.com/policy/common</code>.</p><div class="exampleOuter">
-<p style="text-align: left" class="exampleHead"><i><span>Example 2-17. </span>Common Policy Expression</i></p><div class="exampleInner"><pre><Policy Name=”http://real.contoso.com/policy/common”>
+<p style="text-align: left" class="exampleHead"><i><span>Example 2-18. </span>Common Policy Expression</i></p><div class="exampleInner"><pre><Policy Name=”http://real.contoso.com/policy/common”>
<mtom:OptimizedMimeSerialization wsp:Optional="true"/>
<wsap:UsingAddressing />
</Policy></pre></div></div><p>The example below is a policy expression that re-uses the common policy expression above.</p><div class="exampleOuter">
-<p style="text-align: left" class="exampleHead"><i><span>Example 2-18. </span>PolicyReference to Common Policy Expression</i></p><div class="exampleInner"><pre><PolicyReference URI="http://real.contoso.com/policy/common"/></pre></div></div><p>As policy expressions are composed from other policy expressions and
+<p style="text-align: left" class="exampleHead"><i><span>Example 2-19. </span>PolicyReference to Common Policy Expression</i></p><div class="exampleInner"><pre><PolicyReference URI="http://real.contoso.com/policy/common"/></pre></div></div><p>As policy expressions are composed from other policy expressions and
assertions from different domains are used in a policy expression,
complex expressions will emerge. Naming parts of complex expressions for
reuse and building more complex policies through referencing enables
@@ -532,7 +543,7 @@
any message exchange associated with any <code>port</code> that supports this binding
description. This includes all the message exchanges described by operations in the
<code>RealTimeDataInterface</code>.</p><div class="exampleOuter">
-<p style="text-align: left" class="exampleHead"><i><span>Example 2-19. </span>Secure Policy Expression Attached to WSDL Binding</i></p><div class="exampleInner"><pre><wsdl:binding name="SecureBinding" type="tns:RealTimeDataInterface" >
+<p style="text-align: left" class="exampleHead"><i><span>Example 2-20. </span>Secure Policy Expression Attached to WSDL Binding</i></p><div class="exampleInner"><pre><wsdl:binding name="SecureBinding" type="tns:RealTimeDataInterface" >
<PolicyReference URI="#secure" />
<wsdl:operation name="GetRealQuote">…</wsdl:operation>
…
@@ -543,7 +554,7 @@
<code>GetSymbol</code> and <code>GetSymbols</code>). Contoso does not require the use of
security for these services, but requires the use of addressing and allows the use of
optimization.</p><div class="exampleOuter">
-<p style="text-align: left" class="exampleHead"><i><span>Example 2-20. </span>Open Policy Expression Attached to WSDL Binding</i></p><div class="exampleInner"><pre><wsdl:binding name="OpenBinding" type="tns:DelayedDataInterface" >
+<p style="text-align: left" class="exampleHead"><i><span>Example 2-21. </span>Open Policy Expression Attached to WSDL Binding</i></p><div class="exampleInner"><pre><wsdl:binding name="OpenBinding" type="tns:DelayedDataInterface" >
<PolicyReference URI="#common" />
<wsdl:operation name="GetDelayedQuote">…</wsdl:operation>
…
@@ -1500,4 +1511,8 @@
for <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3979">issue 3979</a>.
Editors' action
<a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/198">198</a>.
+ </td></tr><tr><td rowspan="1" colspan="1">20070315</td><td rowspan="1" colspan="1">FJH</td><td rowspan="1" colspan="1">Applied <a href="http://www.w3.org/2007/03/13-ws-policy-irc#T21-39-50">resolution</a>
+ to <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4253">issue 4253</a>
+ (editors action
+ <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/191">191</a>).
</td></tr></tbody></table><br></div></div></body></html>
\ No newline at end of file
Index: ws-policy-primer.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-primer.xml,v
retrieving revision 1.39
retrieving revision 1.40
diff -u -d -r1.39 -r1.40
--- ws-policy-primer.xml 16 Mar 2007 03:29:42 -0000 1.39
+++ ws-policy-primer.xml 16 Mar 2007 04:58:46 -0000 1.40
@@ -209,10 +209,25 @@
<wsap:UsingAddressing />
</Policy></eg>
</example>
- <p>The policy expression in the above example consists of a <code>Policy</code> main element
- and a child element <code>wsap:UsingAddressing.</code> Child elements of the
- <code>Policy</code> element are policy assertions. Contoso attaches the above policy
- expression to a WSDL binding description.</p>
+ <p>
+ The policy expression in the above example consists of a Policy main
+ element and a child element wsap:UsingAddressing. Child elements of
+ the Policy element are policy assertions. Contoso attaches the above
+ policy expression to a WSDL binding description.
+ </p>
+ <example>
+ <head>Policy Expression Attached to Binding</head>
+ <eg xml:space="preserve"><wsdl:binding name="AddressingBinding" type="tns:RealTimeDataInterface" >
+ <Policy>
+ <wsap:UsingAddressing />
+ </Policy>
+ ...
+</wsdl:binding>
+ </eg>
+ </example>
+ <p>
+ Policies can also be attached to WSDL using references (See <specref ref="Referencing_Policy_Expressions" />.)
+ </p>
<p>The <code>wsap:UsingAddressing</code> element is a policy assertion. (The prefix
<code>wsap</code> is used here to denote the Web Services Addressing – WSDL Binding XML
Namespace.) This assertion identifies the use of Web Services Addressing information
@@ -2284,7 +2299,18 @@
<loc
href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/198">198</loc>.
</td>
- </tr>
+ </tr>
+ <tr>
+ <td>20070315</td>
+ <td>FJH</td>
+ <td>Applied <loc href="http://www.w3.org/2007/03/13-ws-policy-irc#T21-39-50">resolution</loc>
+ to <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4253">issue 4253</loc>
+ (editors action
+ <loc
+ href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/191">191</loc>).
+ </td>
+
+ </tr>
</tbody>
</table>
</inform-div1>
Received on Friday, 16 March 2007 04:59:02 UTC