- From: Umit Yalsinap via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 30 Jan 2007 22:34:12 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv7030
Modified Files:
ws-policy-guidelines.html ws-policy-guidelines.xml
Log Message:
Action item 137, Resolution of Issue 4198
Index: ws-policy-guidelines.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-guidelines.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -d -r1.19 -r1.20
--- ws-policy-guidelines.html 30 Jan 2007 22:18:15 -0000 1.19
+++ ws-policy-guidelines.html 30 Jan 2007 22:34:09 -0000 1.20
@@ -63,7 +63,7 @@
guide to using the specifications. </p></div><div>
<h2><a name="status">Status of this Document</a></h2><p><strong>This document is an editors' copy that has
no official standing.</strong></p><p></p></div><hr><div class="toc">
-<h2><a name="contents">Table of Contents</a></h2><p class="toc">1. <a href="#introduction">Introduction</a><br>2. <a href="#Assertions">What is an Assertion? </a><br>3. <a href="#d3e169">Who is involved in authoring Assertions? </a><br> 3.1 <a href="#roles"> Roles and Responsibilities </a><br> 3.1.1 <a href="#domain-owners"> Assertion Authors</a><br> 3.1.2 <a href="#consumers">Consumers</a><br> 3.1.3 <a href="#providers">Providers</a><br>4. <a href="#general-guidelines">General Guidelines for Assertion Authors</a><br> 4.1 <a href="#assertion-target">Assertions and Their Target Use</a><br> 4.2 <a href="#compact-full">Authoring Styles </a><br> 4.3 <a href="#new-guidelines-domains">Considerations when Modeling New Assertions</a><br> 43.1 <a href="#minimal-approach">Minimal approach</a><br> 4.3.2 <a href="#QName_and_XML_Information_Set_representation">QName and XML Information Set representation</a><br> 4.3.3 <a href="#self-describing"> Self Describing Messages </a><br> 4.3.4 <a href="#single-domains">Single Domains</a><br> 4.4 <a href="#comparison">Comparison of Nested and Parameterized Assertions</a><br> 4.4.1 <a href="#parameterized-assertions">Assertions with Parameters</a><br> 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> nbsp; 4.5.1 <a href="#d3e504">Optional behavior in Compact authoring</a><br> 4.5.2 <a href="#d3e512">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>5. <a href="#lifecycle">Lifecycle of Assertions</a><br> 5.1 <a href="#Referencing_Policy_Expressions">Referencing Policy Expressions</a><br> 5.2 <a href="#extending-assertions"> Evolution of Assertions (Versioning and Compatibility)</a><br>6. <a href="#inter-policy">Inter-domain Policy and Composition Issues</a><br>7. <a href="#best-practices-attachment">Applying Best Practices for Policy Attachment</a><br> 7.1 <a href="#context-free-policies">Appropriate Attachment: Preserving Context-Free Policies</a><br> 7.2 <a href="#apropriate-attachment-assertion-subjects">Appropriate Attachment: Identifying Assertion Subjects</a><br> 7.2.1 <a href="#interaction">Interaction between Subjects</a><br> 7.3 <a href="#identifying-assertion-sources">Appropriate Attachment: Identifying Assertion Sources </a><br>8. <a href="#scenario">Scenario and a worked example</a><br></p>
+<h2><a name="contents">Table of Contents</a></h2><p class="toc">1. <a href="#introduction">Introduction</a><br>2. <a href="#Assertions">What is an Assertion? </a><br>3. <a href="#d3e169">Who is involved in authoring Assertions? </a><br> 3.1 <a href="#roles"> Roles and Responsibilities </a><br> 3.1.1 <a href="#domain-owners"> Assertion Authors</a><br> 3.1.2 <a href="#consumers">Consumers</a><br> 3.1.3 <a href="#providers">Providers</a><br>4. <a href="#general-guidelines">General Guidelines for Assertion Authors</a><br> 4.1 <a href="#assertion-target">Assertions and Their Target Use</a><br> 4.2 <a href="#compact-full">Authoring Styles </a><br> 4.3 <a href="#new-guidelines-domains">Considerations when Modeling New Assertions</a><br> 43.1 <a href="#minimal-approach">Minimal approach</a><br> 4.3.2 <a href="#QName_and_XML_Information_Set_representation">QName and XML Information Set representation</a><br> 4.3.3 <a href="#self-describing"> Self Describing Messages </a><br> 4.3.4 <a href="#single-domains">Single Domains</a><br> 4.4 <a href="#comparison">Comparison of Nested and Parameterized Assertions</a><br> 4.4.1 <a href="#parameterized-assertions">Assertions with Parameters</a><br> 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> nbsp; 4.5.1 <a href="#d3e506">Optional behavior in Compact authoring</a><br> 4.5.2 <a href="#d3e514">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>5. <a href="#lifecycle">Lifecycle of Assertions</a><br> 5.1 <a href="#Referencing_Policy_Expressions">Referencing Policy Expressions</a><br> 5.2 <a href="#extending-assertions"> Evolution of Assertions (Versioning and Compatibility)</a><br>6. <a href="#inter-policy">Inter-domain Policy and Composition Issues</a><br>7. <a href="#best-practices-attachment">Applying Best Practices for Policy Attachment</a><br> 7.1 <a href="#context-free-policies">Appropriate Attachment: Preserving Context-Free Policies</a><br> 7.2 <a href="#apropriate-attachment-assertion-subjects">Appropriate Attachment: Identifying Assertion Subjects</a><br> 7.2.1 <a href="#interaction">Interaction between Subjects</a><br> 7.3 <a href="#identifying-assertion-sources">Appropriate Attachment: Identifying Assertion Sources </a><br>8. <a href="#scenario">Scenario and a worked example</a><br></p>
<h3><a name="appendix" id="appendix">Appendices</a></h3><p class="toc">A. <a href="#security-considerations">Security Considerations</a><br>B. <a href="#xml-namespaces">XML Namespaces</a><br>C. <a href="#references">References</a><br>D. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>E. <a href="#change-description">Changes in this Version of
the Document</a> (Non-Normative)<br>F. <a href="#change-log">Web Services Policy 1.5 - Guidelines for Policy Assertion Authors Change Log</a> (Non-Normative)<br></p></div><hr><div class="body"><div class="div1">
<h2><a name="introduction"></a>1. Introduction</h2><p>The WS-Policy specification defines a policy to be a collection
@@ -302,7 +302,23 @@
environment; when creating a domain specific
attachment in multiple WSDL files or Endpoint
References in which the same set of policies are expected to be applied.
- </p><p>Best practice: Assertion Authors should include the following
+ </p><p>WS-PolicyAttachment provides various
+ mechanisms to attach a policy to a policy
+ subject. Although a policy assertion may be
+ tailored for or constrained to a specific set
+ of policy subjects by design, its semantics
+ are not dependent upon the mechanism by which
+ a policy expression is attached to a given
+ policy subject. For instance, an assertion
+ "Foo" has the same semantic when attached to a
+ WSDL1.1 operation regardless of whether it was
+ attached using XML element policy attachment
+ or the external URI attachment mechanism.
+ Independence from a specific
+ attachment mechanism allows policy tools to choose the most
+ appropriate mechanism to attach a policy without having to
+ analyze the contents of the policy.
+ </p><p>Best practice: Assertion Authors should include the following
items in the dialect specification:
</p><ul><li><p><em>The definition of the
assertion</em>. Does the assertion pertain to a specific
@@ -613,7 +629,7 @@
to the WS-Policy framework.
</p></div></div><div class="div2">
<h3><a name="optional-policy-assertion"></a>4.5 Designating Optional Behaviors</h3><div class="div3">
-<h4><a name="d3e504"></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="d3e506"></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
@@ -624,7 +640,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="d3e512"></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="d3e514"></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
@@ -1254,5 +1270,7 @@
</td></tr><tr><td rowspan="1" colspan="1">20070122</td><td rowspan="1" colspan="1">PY</td><td rowspan="1" colspan="1">Completed action item:
<a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/127">127</a>
Resolution for issue <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4197">4197</a></td></tr><tr><td rowspan="1" colspan="1">20070130</td><td rowspan="1" colspan="1">UY</td><td rowspan="1" colspan="1">Completed action item:
- <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/144">144</a>
- Resolution for issues <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3985">3985</a> and <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3986">3986</a></td></tr></tbody></table><br></div></div></body></html>
\ No newline at end of file
+ <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/144">144</a>.
+ Resolution for issues <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3985">3985</a> and <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3986">3986</a></td></tr><tr><td rowspan="1" colspan="1">20070130</td><td rowspan="1" colspan="1">UY</td><td rowspan="1" colspan="1">Completed action item:
+ <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/137">137</a>.
+ Resolution for issue <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4198">4198</a></td></tr></tbody></table><br></div></div></body></html>
\ No newline at end of file
Index: ws-policy-guidelines.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-guidelines.xml,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -d -r1.28 -r1.29
--- ws-policy-guidelines.xml 30 Jan 2007 22:18:15 -0000 1.28
+++ ws-policy-guidelines.xml 30 Jan 2007 22:34:09 -0000 1.29
@@ -448,6 +448,24 @@
attachment in multiple WSDL files or Endpoint
References in which the same set of policies are expected to be applied.
</p>
+
+ <p>WS-PolicyAttachment provides various
+ mechanisms to attach a policy to a policy
+ subject. Although a policy assertion may be
+ tailored for or constrained to a specific set
+ of policy subjects by design, its semantics
+ are not dependent upon the mechanism by which
+ a policy expression is attached to a given
+ policy subject. For instance, an assertion
+ "Foo" has the same semantic when attached to a
+ WSDL1.1 operation regardless of whether it was
+ attached using XML element policy attachment
+ or the external URI attachment mechanism.
+ Independence from a specific
+ attachment mechanism allows policy tools to choose the most
+ appropriate mechanism to attach a policy without having to
+ analyze the contents of the policy.
+ </p>
<p>Best practice: Assertion Authors should include the following
items in the dialect specification:
</p>
@@ -1913,13 +1931,20 @@
<loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/127">127</loc>
Resolution for issue <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4197">4197</loc></td>
</tr>
-<tr>
+ <tr>
<td>20070130</td>
<td>UY</td>
<td>Completed action item:
- <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/144">144</loc>
+ <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/144">144</loc>.
Resolution for issues <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3985">3985</loc> and <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3986">3986</loc></td>
</tr>
+ <tr>
+ <td>20070130</td>
+ <td>UY</td>
+ <td>Completed action item:
+ <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/137">137</loc>.
+ Resolution for issue <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4198">4198</loc></td>
+ </tr>
</tbody>
</table>
</inform-div1>
Received on Tuesday, 30 January 2007 22:34:17 UTC