- From: Frederick Hirsch via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 15 Mar 2007 01:27:10 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv21308
Modified Files:
ws-policy-guidelines.html ws-policy-guidelines.xml
Log Message:
Implement resolution for issue 3987 (editors action 203).
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3987
Index: ws-policy-guidelines.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-guidelines.html,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -d -r1.31 -r1.32
--- ws-policy-guidelines.html 15 Mar 2007 00:47:08 -0000 1.31
+++ ws-policy-guidelines.html 15 Mar 2007 01:27:08 -0000 1.32
@@ -97,6 +97,7 @@
5. <a href="#versioning-policy-assertions">Versioning Policy 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>
+ 5.3 <a href="#supporting-new-policy-subjects">Supporting New Policy Subjects</a><br>
6. <a href="#best-practices-attachment">Applying Best Practices for Policy Attachment</a><br>
6.1 <a href="#context-free-policies">Appropriate Attachment: Preserving Context-Free Policies</a><br>
6.2 <a href="#appropriate-attachment-assertion-subjects">Appropriate Attachment: Identifying Assertion Subjects</a><br>
@@ -881,7 +882,7 @@
and the specifications <cite><a href="#WS-Policy">Web Services Policy Framework</a></cite> <cite><a href="#WS-PolicyAttachment">Web Services Policy Attachment</a></cite>
for details on extensibility.
</p><p> The current WS-Policy language <cite><a href="#WS-Policy">Web Services Policy Framework</a></cite> provides extensibility points
- on 6 elements with a combination of attribute and/or element extensibility:</p><ol class="enumar"><li><p>Policy: element from ##other namespace and any attribute</p></li><li><p>ExactlyOne, All: element from ##other namespace; no attribute extensibility</p></li><li><p>PolicyReference: any element and any attribute</p></li><li><p>PolicyAttachment: element from ##other namespace and any attribute</p></li><li><p>AppliesTo: any element and any attribute</p></li><li><p>URI: any attribute</p></li></ol></li><li><p> Subject attachment Extensibility </p><p>PolicyAttachment and AppliesTo also have extensibility points.</p></li></ul><div class="div2">
+ on 6 elements with a combination of attribute and/or element extensibility:</p><ol class="enumar"><li><p>Policy: element from ##other namespace and any attribute</p></li><li><p>ExactlyOne, All: element from ##other namespace; no attribute extensibility</p></li><li><p>PolicyReference: any element and any attribute</p></li><li><p>PolicyAttachment: element from ##other namespace and any attribute</p></li><li><p>AppliesTo: any element and any attribute</p></li><li><p>URI: any attribute</p></li></ol></li><li><p>Supporting New Policy Subjects</p></li></ul><div class="div2">
<h3><a name="Referencing_Policy_Expressions" id="Referencing_Policy_Expressions"></a>5.1 Referencing Policy Expressions</h3><p>The <cite><a href="#WS-Policy-Primer">Web Services Policy Primer</a></cite> illustrates how
providers can utilize the identification mechanism defined in the Policy specification
to expose a complex policy expression as a reusable building block for
@@ -912,7 +913,28 @@
<p style="text-align: left" class="exampleHead"><i><span>Example 5-2. </span>Message-level Security and WSS: SOAP Message Security 1.1</i></p><div class="exampleInner"><pre><Policy>
<sp:Wss11>…</sp:Wss11>
</Policy></pre></div></div><p>Best practice: use independent assertions for modeling multiple equivalent
- behaviors.</p></div></div><div class="div1">
+ behaviors.</p></div><div class="div2">
+<h3><a name="supporting-new-policy-subjects" id="supporting-new-policy-subjects"></a>5.3 Supporting New Policy Subjects</h3><p>
+ <a href="#Assertions">Section 2</a> identifies that it is a best practice for policy authors to
+ define the set of policy subjects to which policy assertions can be
+ attached. Over time, new policy subjects may need to be defined. When
+ this occurs, a policy assertion author may update the list of policy
+ subjects supported by an assertion.
+ </p><p>
+ When the assertion's semantics do not change to invalidate any of the
+ original policy subjects but new policy subjects need to be added, it may
+ be possible to use the same assertion to designate the additional policy
+ subjects without a namespace change. For example, a policy assertion for
+ a protocol that is originally designed for endpoint policy subject may add
+ message policy subject to indicate finer granularity in the attachment
+ provided that endpoint policy subject is also retained in its design. When
+ new policy subjects are added it is incumbent on the authors to retain the
+ semantic of the policy assertion.
+ </p><p>Best Practice: An assertion description should specify a policy
+ subject.</p><p>Best Practice: If the policy subjects change over time,
+ the assertion description should also be versioned to reflect this
+ change.
+ </p></div></div><div class="div1">
<h2><a name="best-practices-attachment" id="best-practices-attachment"></a>6. Applying Best Practices for Policy Attachment</h2><div class="div2">
<h3><a name="context-free-policies" id="context-free-policies"></a>6.1 Appropriate Attachment: Preserving Context-Free Policies</h3><p>Policy attachment should not affect the interpretation of
Policy alternatives. If it did, each policy assertion would
@@ -1342,4 +1364,8 @@
</td></tr><tr><td rowspan="1" colspan="1">20070308</td><td rowspan="1" colspan="1">DBO</td><td rowspan="1" colspan="1">Changed "lifecycle" spec references to versioning to fix build. </td></tr><tr><td rowspan="1" colspan="1">20070314</td><td rowspan="1" colspan="1">FJH</td><td rowspan="1" colspan="1">Implemented <a href="http://www.w3.org/2007/03/14-ws-policy-irc#T18-14-48">resolution</a> for issue <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4072">4072</a>
as outlined in
<a href="http://lists.w3.org/Archives/Public/public-ws-policy/2007Mar/0103.html">proposal</a>.
- Editorial action <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/204">204</a>. </td></tr></tbody></table><br></div></div></body></html>
\ No newline at end of file
+ Editorial action <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/204">204</a>. </td></tr><tr><td rowspan="1" colspan="1">20070314</td><td rowspan="1" colspan="1">FJH</td><td rowspan="1" colspan="1">Implemented <a href="http://www.w3.org/2007/03/14-ws-policy-irc#T18-07-08">resolution</a> for issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3987">3987</a>
+ as outlined in
+ <a href="http://lists.w3.org/Archives/Public/public-ws-policy/2007Mar/0096.html">proposal</a>.
+ Editorial action <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/203">203</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.40
retrieving revision 1.41
diff -u -d -r1.40 -r1.41
--- ws-policy-guidelines.xml 15 Mar 2007 00:47:08 -0000 1.40
+++ ws-policy-guidelines.xml 15 Mar 2007 01:27:08 -0000 1.41
@@ -1196,10 +1196,10 @@
</item>
<item>
- <p> Subject attachment Extensibility </p>
- <p>PolicyAttachment and AppliesTo also have extensibility points.</p>
+ <p>Supporting New Policy Subjects</p>
</item>
</ulist>
+
<div2 id="Referencing_Policy_Expressions">
<head>Referencing Policy Expressions</head>
<p>The <bibref ref="WS-Policy-Primer"/> illustrates how
@@ -1242,7 +1242,34 @@
</Policy></eg></example>
<p>Best practice: use independent assertions for modeling multiple equivalent
behaviors.</p>
- </div2>
+ </div2>
+ <div2 id="supporting-new-policy-subjects">
+ <head>Supporting New Policy Subjects</head>
+ <p>
+ <loc href="#Assertions">Section 2</loc> identifies that it is a best practice for policy authors to
+ define the set of policy subjects to which policy assertions can be
+ attached. Over time, new policy subjects may need to be defined. When
+ this occurs, a policy assertion author may update the list of policy
+ subjects supported by an assertion.
+ </p>
+ <p>
+ When the assertion's semantics do not change to invalidate any of the
+ original policy subjects but new policy subjects need to be added, it may
+ be possible to use the same assertion to designate the additional policy
+ subjects without a namespace change. For example, a policy assertion for
+ a protocol that is originally designed for endpoint policy subject may add
+ message policy subject to indicate finer granularity in the attachment
+ provided that endpoint policy subject is also retained in its design. When
+ new policy subjects are added it is incumbent on the authors to retain the
+ semantic of the policy assertion.
+ </p>
+ <p>Best Practice: An assertion description should specify a policy
+ subject.</p>
+ <p>Best Practice: If the policy subjects change over time,
+ the assertion description should also be versioned to reflect this
+ change.
+ </p>
+ </div2>
</div1>
<div1 id="best-practices-attachment">
@@ -1989,7 +2016,16 @@
as outlined in
<loc href="http://lists.w3.org/Archives/Public/public-ws-policy/2007Mar/0103.html">proposal</loc>.
Editorial action <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/204">204</loc>. </td>
- </tr>
+ </tr>
+ <tr>
+ <td>20070314</td>
+ <td>FJH</td>
+ <td>Implemented <loc href="http://www.w3.org/2007/03/14-ws-policy-irc#T18-07-08">resolution</loc> for issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3987">3987</loc>
+ as outlined in
+ <loc href="http://lists.w3.org/Archives/Public/public-ws-policy/2007Mar/0096.html">proposal</loc>.
+ Editorial action <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/203">203</loc>. </td>
+ </tr>
</tbody>
</table>
</inform-div1>
Received on Thursday, 15 March 2007 01:27:19 UTC