- From: Asir Vedamuthu via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 16 Mar 2007 04:14:06 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv20269
Modified Files:
ws-policy-guidelines.html ws-policy-guidelines.xml
Log Message:
Implemented the resolution for issue 3981. Editors' action 205.
Index: ws-policy-guidelines.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-guidelines.html,v
retrieving revision 1.34
retrieving revision 1.35
diff -u -d -r1.34 -r1.35
--- ws-policy-guidelines.html 16 Mar 2007 04:09:02 -0000 1.34
+++ ws-policy-guidelines.html 16 Mar 2007 04:14:03 -0000 1.35
@@ -89,8 +89,8 @@
4.4.2 <a href="#nested-assertions">Nested Assertions</a><br>
4.4.3 <a href="#which-one-to-use">Considerations for choosing parameters vs nesting</a><br>
4.5 <a href="#optional-policy-assertion">Designating Optional Behaviors</a><br>
- 4.5.1 <a href="#d3e519">Optional behavior in Compact authoring</a><br>
- 4.5.2 <a href="#d3e527">Optional behavior at runtime</a><br>
+ 4.5.1 <a href="#d3e521">Optional behavior in Compact authoring</a><br>
+ 4.5.2 <a href="#d3e529">Optional behavior at runtime</a><br>
4.6 <a href="#typing-assertions">Typing Assertions</a><br>
4.7 <a href="#levels-of-abstraction">Levels of Abstraction in WSDL </a><br>
4.8 <a href="#interrelated-domains">Interrelated domains</a><br>
@@ -372,9 +372,11 @@
Best practice: The semantics a policy assertion should not depend on the
attachment mechanism used.
</p></div><div class="div2">
-<h3><a name="compact-full" id="compact-full"></a>4.2 Authoring Styles </h3><p> WS-Policy supports two different authoring styles. A compact form is one in which an expression consists of three
- constructs: an attribute to decorate an assertion (to indicate whether it is required or optional), semantics for
- recursively nested policy operators, and a policy reference/inclusion mechanism.
+<h3><a name="compact-full" id="compact-full"></a>4.2 Authoring Styles </h3><p>WS-Policy supports two different authoring styles, compact form and
+ normal form. A compact form is one in which an expression consists of
+ three constructs: an attribute to decorate an assertion (to indicate
+ whether it is required or optional), semantics for recursively nested
+ policy operators, and a policy reference/inclusion mechanism.
</p><div class="exampleOuter"><div class="exampleInner"><pre><wsp:Policy xmlns:wsp='http://www.w3.org/ns/ws-policy'
xmlns:sp='http://schemas.xmlsoap.org/ws/2005/07/securitypolicy'
xmlns:wsrmp='http://docs.oasis-open.org/ws-rx/wsrmp/200608'>
@@ -385,53 +387,61 @@
<wsp:Policy>
<sp:TransportToken>
<wsp:Policy>
- <sp:HttpsToken RequireClientCertificate='xs:boolean' />
+ <sp:HttpsToken RequireClientCertificate='true' />
</wsp:Policy>
</sp:TransportToken>
</sp:TransportBinding>
</wsp:All>
</wsp:ExactlyOne>
-</wsp:Policy></pre></div></div><p>An alternative style is a "normal form" in which the optional attribute is replaced by the expression of the
- alternatives allowed by the set of policy assertions.
+</wsp:Policy></pre></div></div><p>A policy expression in the compact form can be translated into its
+ normal form using the policy normalization algorithm described in the
+ Web Service Policy Framework (see section 4.3 Compact Policy
+ Expression).
</p><div class="exampleOuter"><div class="exampleInner"><pre><wsp:Policy xmlns:wsp='http://www.w3.org/ns/ws-policy'
xmlns:sp='http://schemas.xmlsoap.org/ws/2005/07/securitypolicy'
xmlns:wsrmp='http://docs.oasis-open.org/ws-rx/wsrmp/200608'>
<wsp:ExactlyOne>
<wsp:All>
- <wsrmp:RMAssertion>
- <sp:TransportBinding>
- <wsp:Policy>
- <sp:TransportToken>
- <wsp:Policy>
- <sp:HttpsToken RequireClientCertificate='true' />
- </wsp:Policy>
- </sp:TransportToken>
- </wsp:Policy>
+ <wsrmp:RMAssertion/>
+ <sp:TransportBinding>
+ <wsp:Policy>
+ <sp:TransportToken>
+ <wsp:Policy>
+ <sp:HttpsToken RequireClientCertificate='true' />
+ </wsp:Policy>
+ </sp:TransportToken>
+ </wsp:Policy>
</sp:TransportBinding>
</wsp:All>
<wsp:All>
- <sp:TransportBinding>
- <wsp:Policy>
- <sp:TransportToken>
- <wsp:Policy>
- <sp:HttpsToken RequireClientCertificate='true' />
- </wsp:Policy>
- </sp:TransportToken>
- </wsp:Policy>
- </sp:TransportBinding>
+ <sp:TransportBinding>
+ <wsp:Policy>
+ <sp:TransportToken>
+ <wsp:Policy>
+ <sp:HttpsToken RequireClientCertificate='true' />
+ </wsp:Policy>
+ </sp:TransportToken>
+ </wsp:Policy>
+ </sp:TransportBinding>
</wsp:All>
</wsp:ExactlyOne>
-</wsp:Policy></pre></div></div><p> Note that both authoring styles are equivalent, however
- there may be reasons to choose one form over another
- depending on the use. For example, when multiple alternatives are present
- in a policy, the normal form may express the choices more explicitly.
- On the other hand, the compact form is more
- readable for humans when an assertion is marked as optional
- using the <code>wsp:optional</code> attribute as our example illustrates above.
- </p><p>Best practice: use the authoring style most appropriate for the target audience </p></div><div class="div2">
+</wsp:Policy></pre></div></div><p>These two forms of the same policy expression are semantically
+ equivalent. When multiple alternatives are present in a policy, the
+ normal form may express the choices more explicitly. On the other hand,
+ the compact form may be more readable for humans when an assertion is
+ marked as optional using the <code>wsp:optional</code> attribute as our example
+ illustrates above.</p><p>A policy processor may normalize a policy expression originally authored
+ in compact form at any time without changing the semantics of the
+ policy. In general, it is not possible to guarantee in what form a
+ policy expression would be when it is processed. As a result, the
+ description for a policy assertion should not depend on the style used
+ to author a policy expression that contains the assertion.
+ </p><p>Best practice: the semantics of an assertion should be independent of
+ the form (compact or normal form) of policy expressions that contain the
+ assertion.</p></div><div class="div2">
<h3><a name="new-guidelines-domains" id="new-guidelines-domains"></a>4.3 Considerations when Modeling New Assertions</h3><p>When creating a new policy domain, it is important to
understand how policy expressions are used by a
framework implementation that has followed the specifications.
@@ -663,7 +673,7 @@
to the WS-Policy framework.
</p></div></div><div class="div2">
<h3><a name="optional-policy-assertion" id="optional-policy-assertion"></a>4.5 Designating Optional Behaviors</h3><div class="div3">
-<h4><a name="d3e519" id="d3e519"></a>4.5.1 Optional behavior in Compact authoring</h4><p>Optional behaviors represent behaviors which may be engaged by a consumer. When using the
+<h4><a name="d3e521" id="d3e521"></a>4.5.1 Optional behavior in Compact authoring</h4><p>Optional behaviors represent behaviors which may be engaged by a consumer. When using the
compact authoring form for assertions, behaviors are marked by
using <code>wsp:Optional</code> attribute that has a value,
"true". During the process of normalization, the runtime
@@ -674,7 +684,7 @@
runtime behavior. In order to simplify reference to such
assertions, we just use the term optional assertions in this section.
</p></div><div class="div3">
-<h4><a name="d3e527" id="d3e527"></a>4.5.2 Optional behavior at runtime</h4><p>The <cite><a href="#WS-Policy-Primer">Web Services Policy Primer</a></cite> document contains an
+<h4><a name="d3e529" id="d3e529"></a>4.5.2 Optional behavior at runtime</h4><p>The <cite><a href="#WS-Policy-Primer">Web Services Policy Primer</a></cite> document contains an
example that proposes the use of <cite><a href="#MTOM">MTOM</a></cite> as an
optional behavior that can be engaged by a consumer. The
primer proposes that an assertion that identifies the use of
@@ -1370,6 +1380,10 @@
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">ASV</td><td rowspan="1" colspan="1">Implemented the <a href="http://lists.w3.org/Archives/Public/public-ws-policy/2007Feb/0000.html">resolution</a>
+ for <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3981">issue 3981</a>.
+ Editors' action
+ <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/205">205</a>.
</td></tr><tr><td rowspan="1" colspan="1">20070315</td><td rowspan="1" colspan="1">FJH</td><td rowspan="1" colspan="1">Implemented <a href="http://www.w3.org/2007/03/13-ws-policy-irc#T23-08-08">resolution</a> for issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4035">4035</a>
as outlined in
Index: ws-policy-guidelines.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-guidelines.xml,v
retrieving revision 1.43
retrieving revision 1.44
diff -u -d -r1.43 -r1.44
--- ws-policy-guidelines.xml 16 Mar 2007 04:09:02 -0000 1.43
+++ ws-policy-guidelines.xml 16 Mar 2007 04:14:04 -0000 1.44
@@ -478,9 +478,11 @@
</div2>
<div2 id="compact-full">
<head>Authoring Styles </head>
- <p> WS-Policy supports two different authoring styles. A compact form is one in which an expression consists of three
- constructs: an attribute to decorate an assertion (to indicate whether it is required or optional), semantics for
- recursively nested policy operators, and a policy reference/inclusion mechanism.
+ <p>WS-Policy supports two different authoring styles, compact form and
+ normal form. A compact form is one in which an expression consists of
+ three constructs: an attribute to decorate an assertion (to indicate
+ whether it is required or optional), semantics for recursively nested
+ policy operators, and a policy reference/inclusion mechanism.
</p>
<example>
<eg xml:space="preserve"><wsp:Policy xmlns:wsp='&nsuri;'
@@ -493,7 +495,7 @@
<wsp:Policy>
<sp:TransportToken>
<wsp:Policy>
- <sp:HttpsToken RequireClientCertificate='xs:boolean' />
+ <sp:HttpsToken RequireClientCertificate='true' />
</wsp:Policy>
</sp:TransportToken>
</sp:TransportBinding>
@@ -502,8 +504,10 @@
</wsp:Policy></eg>
</example>
- <p>An alternative style is a "normal form" in which the optional attribute is replaced by the expression of the
- alternatives allowed by the set of policy assertions.
+ <p>A policy expression in the compact form can be translated into its
+ normal form using the policy normalization algorithm described in the
+ Web Service Policy Framework (see section 4.3 Compact Policy
+ Expression).
</p>
@@ -514,44 +518,51 @@
<wsp:ExactlyOne>
<wsp:All>
- <wsrmp:RMAssertion>
- <sp:TransportBinding>
- <wsp:Policy>
- <sp:TransportToken>
- <wsp:Policy>
- <sp:HttpsToken RequireClientCertificate='true' />
- </wsp:Policy>
- </sp:TransportToken>
- </wsp:Policy>
+ <wsrmp:RMAssertion/>
+ <sp:TransportBinding>
+ <wsp:Policy>
+ <sp:TransportToken>
+ <wsp:Policy>
+ <sp:HttpsToken RequireClientCertificate='true' />
+ </wsp:Policy>
+ </sp:TransportToken>
+ </wsp:Policy>
</sp:TransportBinding>
</wsp:All>
<wsp:All>
- <sp:TransportBinding>
- <wsp:Policy>
- <sp:TransportToken>
- <wsp:Policy>
- <sp:HttpsToken RequireClientCertificate='true' />
- </wsp:Policy>
- </sp:TransportToken>
- </wsp:Policy>
- </sp:TransportBinding>
+ <sp:TransportBinding>
+ <wsp:Policy>
+ <sp:TransportToken>
+ <wsp:Policy>
+ <sp:HttpsToken RequireClientCertificate='true' />
+ </wsp:Policy>
+ </sp:TransportToken>
+ </wsp:Policy>
+ </sp:TransportBinding>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy></eg>
</example>
- <p> Note that both authoring styles are equivalent, however
- there may be reasons to choose one form over another
- depending on the use. For example, when multiple alternatives are present
- in a policy, the normal form may express the choices more explicitly.
- On the other hand, the compact form is more
- readable for humans when an assertion is marked as optional
- using the <code>wsp:optional</code> attribute as our example illustrates above.
- </p>
+ <p>These two forms of the same policy expression are semantically
+ equivalent. When multiple alternatives are present in a policy, the
+ normal form may express the choices more explicitly. On the other hand,
+ the compact form may be more readable for humans when an assertion is
+ marked as optional using the <code>wsp:optional</code> attribute as our example
+ illustrates above.</p>
+ <p>A policy processor may normalize a policy expression originally authored
+ in compact form at any time without changing the semantics of the
+ policy. In general, it is not possible to guarantee in what form a
+ policy expression would be when it is processed. As a result, the
+ description for a policy assertion should not depend on the style used
+ to author a policy expression that contains the assertion.
+ </p>
- <p>Best practice: use the authoring style most appropriate for the target audience </p>
+ <p>Best practice: the semantics of an assertion should be independent of
+ the form (compact or normal form) of policy expressions that contain the
+ assertion.</p>
</div2>
<div2 id="new-guidelines-domains">
@@ -2034,7 +2045,17 @@
<loc
href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/198">198</loc>.
</td>
- </tr>
+ </tr>
+ <tr>
+ <td>20070315</td>
+ <td>ASV</td>
+ <td>Implemented the <loc href="http://lists.w3.org/Archives/Public/public-ws-policy/2007Feb/0000.html">resolution</loc>
+ for <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3981">issue 3981</loc>.
+ Editors' action
+ <loc
+ href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/205">205</loc>.
+ </td>
+ </tr>
<tr>
<td>20070315</td>
<td>FJH</td>
Received on Friday, 16 March 2007 04:14:10 UTC