- From: Frederick Hirsch via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 16 Mar 2007 01:46:08 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv8742
Modified Files:
ws-policy-primer.html ws-policy-primer.xml
Log Message:
Implement resolution for issue issue 4255 (editors action 192)
Index: ws-policy-primer.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-primer.html,v
retrieving revision 1.40
retrieving revision 1.41
diff -u -d -r1.40 -r1.41
--- ws-policy-primer.html 15 Mar 2007 01:02:56 -0000 1.40
+++ ws-policy-primer.html 16 Mar 2007 01:46:05 -0000 1.41
@@ -75,10 +75,11 @@
2.5 <a href="#combining-policy-assertions">Combining Policy Assertions</a><br>
2.6 <a href="#optional-policy-assertion">Optional Policy Assertion</a><br>
2.7 <a href="#ignorable-policy-assertions">Ignorable Policy Expressions</a><br>
- 2.8 <a href="#nested-policy-expressions">Nested Policy Expressions</a><br>
- 2.9 <a href="#Referencing_Policy_Expressions">Referencing Policy Expressions</a><br>
- 2.10 <a href="#attaching-policy-expressions-to-wsdl">Attaching Policy Expressions to WSDL</a><br>
- 2.11 <a href="#policy-automates-web-services-interaction">Policy Automates Web Services Interaction</a><br>
+ 2.8 <a href="#Both-Optional-Ignorable">Marking Assertions both Optional and Ignorable</a><br>
+ 2.9 <a href="#nested-policy-expressions">Nested Policy Expressions</a><br>
+ 2.10 <a href="#Referencing_Policy_Expressions">Referencing Policy Expressions</a><br>
+ 2.11 <a href="#attaching-policy-expressions-to-wsdl">Attaching Policy Expressions to WSDL</a><br>
+ 2.12 <a href="#policy-automates-web-services-interaction">Policy Automates Web Services Interaction</a><br>
3. <a href="#advanced-concepts-policy-expression">Advanced Concepts: Policy Expression</a><br>
3.1 <a href="#policy-expression">Policy Expression</a><br>
3.2 <a href="#normal-form-for-policy-expressions">Normal Form for Policy Expressions</a><br>
@@ -364,12 +365,22 @@
Omitting this attribute is semantically equivalent to including it with a value of "false".
</p><p>
The use of the <code>wsp:Ignorable</code> attribute has no impact on normalization.
- Assertions marked with the <code>wsp:Ignorable</code> attribute remain marked with the <code>wsp:Ignorable</code> attribute
- after normalization.
- Ignorable assertions may have an impact on determining compatibility of policies
- (See <a href="#strict-lax-policy-intersection"><b>3.4.1 Strict and Lax Policy Intersection</b></a> ).
+ Assertions marked with the <code>wsp:Ignorable</code> attribute remain marked with
+ the <code>wsp:Ignorable</code> attribute after normalization.
+ Please note that the impact of the ignorable attribute is at the discretion of
+ policy consumers through selection of "lax" or "strict" mode (See <a href="#strict-lax-policy-intersection"><b>3.4.1 Strict and Lax Policy Intersection</b></a>).
+ Therefore ignorable assertions may have an effect on determining compatibility of provider and consumer policies.
</p></div><div class="div2">
-<h3><a name="nested-policy-expressions" id="nested-policy-expressions"></a>2.8 Nested Policy Expressions</h3><p>In the previous sections, we considered two security policy assertions. In this section,
+<h3><a name="Both-Optional-Ignorable" id="Both-Optional-Ignorable"></a>2.8 Marking Assertions both Optional and Ignorable</h3><p>As described in the sections above and in Section <a href="#strict-lax-policy-intersection"><b>3.4.1 Strict and Lax Policy Intersection</b></a>,
+ the WS-Policy 1.5 specification defines two
+ attributes that can be used to mark an assertion: wsp:Optional and wsp:Ignorable.</p><p>The WS-Policy Framework allows a policy assertion to be marked with both "optional"
+ and "Ignorable" attributes simultaneously. The presence of "@wsp:optional=true" on an assertion
+ is a syntactic compact form for two alternatives in normal form, one with the assertion
+ and the other without the assertion. Hence syntactically marking an assertion "A" with both the
+ @wsp:Optional and @wsp:Ignorable with the value of "true" for both, is equivalent to
+ two alternatives; one where the assertion A exists with @wsp:Ignorable=true and the
+ second where the assertion A does not exist.</p></div><div class="div2">
+<h3><a name="nested-policy-expressions" id="nested-policy-expressions"></a>2.9 Nested Policy Expressions</h3><p>In the previous sections, we considered two security policy assertions. In this section,
let us look at one of the security policy assertions in little more detail.</p><p>As you would expect, securing messages is a complex usage scenario. Contoso uses the
<code>sp:TransportBinding</code> policy assertion to indicate the use of transport-level
security for protecting messages. Just indicating the use of transport-level security for
@@ -417,7 +428,7 @@
transport-level security and its dependent behaviors automatically. That is, the
complexity of security usage is absorbed by a policy-aware client and hidden from these
Web service developers.</p></div><div class="div2">
-<h3><a name="Referencing_Policy_Expressions" id="Referencing_Policy_Expressions"></a>2.9 Referencing Policy Expressions</h3><p>Contoso has numerous Web service offerings that provide different kinds of real-time
+<h3><a name="Referencing_Policy_Expressions" id="Referencing_Policy_Expressions"></a>2.10 Referencing Policy Expressions</h3><p>Contoso has numerous Web service offerings that provide different kinds of real-time
quotes and book information on securities such as
<code>GetRealQuote</code>, <code>GetRealQuotes</code> and
<code>GetExtendedRealQuote</code>. To accommodate the diversity of Contoso’s customers,
@@ -425,7 +436,17 @@
consistent ways to interact with their services and wants to represent these capabilities
and requirements consistently across all of their offerings without duplicating policy
expressions multiple times. How? It is simple - a policy expression can be named and
- referenced for re-use.</p><p>A policy expression may be identified by an IRI and referenced for re-use as a standalone
+ referenced for re-use.</p><p>
+ Section <a href="#simple-message"><b>2.2 Simple Message</b></a>,
+ showed how a
+ policy expression can be attached directly to a binding inline. A
+ single policy
+ expression may be used in several parts of a WSDL document. In this
+ case it is
+ desirable to use references to the policy expression rather than to
+ directly
+ inline the policy expression.
+ </p><p>A policy expression may be identified by an IRI and referenced for re-use as a standalone
policy or within another policy expression. There are three mechanisms to identify a policy
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
@@ -483,7 +504,7 @@
<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></div><div class="div2">
-<h3><a name="attaching-policy-expressions-to-wsdl" id="attaching-policy-expressions-to-wsdl"></a>2.10 Attaching Policy Expressions to WSDL</h3><p>A majority of Contoso’s customers use WSDL for building their client applications.
+<h3><a name="attaching-policy-expressions-to-wsdl" id="attaching-policy-expressions-to-wsdl"></a>2.11 Attaching Policy Expressions to WSDL</h3><p>A majority of Contoso’s customers use WSDL for building their client applications.
Contoso leverages this usage by attaching policy expressions to the WSDL binding
descriptions.</p><p>In the example below, the <code>SecureBinding</code> WSDL binding description defines a
binding for an interface that provides real-time quotes and book information on
@@ -533,7 +554,7 @@
documents and engages behaviors automatically for each of these endpoints. Any complexity
of varying behaviors across Web service endpoints is absorbed by a policy-aware client or
tool and hidden from these Web service developers.</p></div><div class="div2">
-<h3><a name="policy-automates-web-services-interaction" id="policy-automates-web-services-interaction"></a>2.11 Policy Automates Web Services Interaction</h3><p>As you have seen, Web Services Policy is a simple language that has four elements -
+<h3><a name="policy-automates-web-services-interaction" id="policy-automates-web-services-interaction"></a>2.12 Policy Automates Web Services Interaction</h3><p>As you have seen, Web Services Policy is a simple language that has four elements -
<code>Policy, All</code>, <code>ExactlyOne</code> and <code>PolicyReference</code> - and
one attribute - <code>wsp:Optional</code>. In practice, service providers, like Contoso,
use policy expressions to represent combinations of capabilities and requirements. Web
@@ -840,7 +861,7 @@
imported WSDL documents constitute separate XML documents each. If e.g. the
importing WSDL document references a policy in the imported WSDL document, the
rules for policy references between separate XML documents apply as described
- in <a href="#Referencing_Policy_Expressions"><b>2.9 Referencing Policy Expressions</b></a>.
+ in <a href="#Referencing_Policy_Expressions"><b>2.10 Referencing Policy Expressions</b></a>.
</p></div><div class="div2">
<h3><a name="combine-policies" id="combine-policies"></a>3.7 Combine Policies</h3><p>Multiple policy expressions may be attached to WSDL constructs. Let us consider how
Contoso could have used multiple policy expressions in a WSDL document. In the example
@@ -1444,4 +1465,16 @@
to <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4263">issue 4263</a>
(editors action
<a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/195">195</a>).
+ </td></tr><tr><td rowspan="1" colspan="1">20070315</td><td rowspan="1" colspan="1">PY</td><td rowspan="1" colspan="1">Applied <a href="http://www.w3.org/2007/03/13-ws-policy-irc#T22-27-24">the resolution</a>
+ to <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4339">issue 4339</a>
+ (editors action
+ <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/194">194</a>).
+ </td></tr><tr><td rowspan="1" colspan="1">20070315</td><td rowspan="1" colspan="1">PY</td><td rowspan="1" colspan="1">Applied <a href="http://www.w3.org/2007/03/14-ws-policy-irc#T17-29-32">the resolution</a>
+ to <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4262">issue 4262</a>
+ (editors action
+ <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/201">201</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=4255">issue 4255</a>
+ (editors action
+ <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/192">192</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.36
retrieving revision 1.37
diff -u -d -r1.36 -r1.37
--- ws-policy-primer.xml 15 Mar 2007 21:50:31 -0000 1.36
+++ ws-policy-primer.xml 16 Mar 2007 01:46:05 -0000 1.37
@@ -561,6 +561,17 @@
and requirements consistently across all of their offerings without duplicating policy
expressions multiple times. How? It is simple - a policy expression can be named and
referenced for re-use.</p>
+ <p>
+ Section <specref ref="simple-message" />,
+ showed how a
+ policy expression can be attached directly to a binding inline. A
+ single policy
+ expression may be used in several parts of a WSDL document. In this
+ case it is
+ desirable to use references to the policy expression rather than to
+ directly
+ inline the policy expression.
+ </p>
<p>A policy expression may be identified by an IRI and referenced for re-use as a standalone
policy or within another policy expression. There are three mechanisms to identify a policy
expression: the <code>wsu:Id</code> <code>xml:id</code> and <code>Name</code> attributes. A
@@ -2226,7 +2237,18 @@
<loc
href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/201">201</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=4255">issue 4255</loc>
+ (editors action
+ <loc
+ href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/192">192</loc>).
+ </td>
+
+ </tr>
</tbody>
</table>
</inform-div1>
Received on Friday, 16 March 2007 01:46:16 UTC