- From: Asir Vedamuthu via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 16 Mar 2007 03:29:45 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv7190
Modified Files:
ws-policy-primer.html ws-policy-primer.xml
ws-policy-guidelines.html ws-policy-guidelines.xml
Log Message:
Implemented the resolution for issue 3979. Editors' action 198.
Index: ws-policy-primer.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-primer.html,v
retrieving revision 1.42
retrieving revision 1.43
diff -u -d -r1.42 -r1.43
--- ws-policy-primer.html 16 Mar 2007 03:16:10 -0000 1.42
+++ ws-policy-primer.html 16 Mar 2007 03:29:42 -0000 1.43
@@ -508,7 +508,17 @@
<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></div><div class="div2">
+<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
+ 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
+ building more complicated policy scenerios easily. This approach enables
+ the association of additional policy subjects to identified policy
+ expressions. It also promotes manageability of the expressions as they
+ are uniquely identified and allows profiles for common scenerios to be
+ developed. Note that when a named expression has assertions that
+ contains parametrized expressions, care must be given to ensure that the
+ parameterized content is statically available to enable reuse.</p></div><div class="div2">
<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
@@ -1486,4 +1496,8 @@
for <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4288">issue 4288</a>.
Editors' action
<a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/196">196</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://www.w3.org/Bugs/Public/show_bug.cgi?id=3979#c1">resolution</a>
+ 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></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.38
retrieving revision 1.39
diff -u -d -r1.38 -r1.39
--- ws-policy-primer.xml 16 Mar 2007 03:16:10 -0000 1.38
+++ ws-policy-primer.xml 16 Mar 2007 03:29:42 -0000 1.39
@@ -664,6 +664,17 @@
<head>PolicyReference to Common Policy Expression</head>
<eg xml:space="preserve"><PolicyReference URI="http://real.contoso.com/policy/common"/></eg>
</example>
+ <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
+ building more complicated policy scenerios easily. This approach enables
+ the association of additional policy subjects to identified policy
+ expressions. It also promotes manageability of the expressions as they
+ are uniquely identified and allows profiles for common scenerios to be
+ developed. Note that when a named expression has assertions that
+ contains parametrized expressions, care must be given to ensure that the
+ parameterized content is statically available to enable reuse.</p>
</div2>
<div2 id="attaching-policy-expressions-to-wsdl">
<head>Attaching Policy Expressions to WSDL</head>
@@ -2263,7 +2274,17 @@
<loc
href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/196">196</loc>.
</td>
- </tr>
+ </tr>
+ <tr>
+ <td>20070315</td>
+ <td>ASV</td>
+ <td>Implemented the <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3979#c1">resolution</loc>
+ for <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3979">issue 3979</loc>.
+ Editors' action
+ <loc
+ href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/198">198</loc>.
+ </td>
+ </tr>
</tbody>
</table>
</inform-div1>
Index: ws-policy-guidelines.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-guidelines.html,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -d -r1.32 -r1.33
--- ws-policy-guidelines.html 15 Mar 2007 01:27:08 -0000 1.32
+++ ws-policy-guidelines.html 16 Mar 2007 03:29:42 -0000 1.33
@@ -883,20 +883,20 @@
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>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
- other policy expressions by reference. Assertion
- authors, especially those defining complex assertions that
- include nesting or complex types should consider specifying or recommending
- naming conventions in order to promote reuse. Reuse through
- referencing allows a policy expression to be utilized not only
- within another expression but also allows specification of
- additional policy subjects and their association to common
- policy expressions that are identified. It also promotes
- manageability of the expressions as they are uniquely
- identified.
- </p></div><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
+ other policy expressions by reference. Reuse may also be useful for
+ domain assertion authors, especially those defining complex assertions
+ utilizing references to policy expressions by nesting. Statically
+ available parameterized content may also be reused by different
+ assertions. However, such referencing mechanism is outside the scope of
+ WS-Policy naming and referencing framework and other mechanisms could be used.
+ As an example, in <cite><a href="#WS-Policy-Primer">Web Services Policy Primer</a></cite>
+ Section 4.2, the <code>sp:issuedToken</code> assertion utilizes the
+ <code>sp:RequestSecurityTokenTemplate</code> parameter that contains necessary
+ information to request a security token. The contents of the parameter
+ are static and allows reuse in different security scenerios.</p></div><div class="div2">
<h3><a name="extending-assertions" id="extending-assertions"></a>5.2 Evolution of Assertions (Versioning and Compatibility)</h3><p>Over time, there may be multiple equivalent behaviors emerging in the Web
Service interaction space. Examples of such multiple equivalent behaviors are WSS: SOAP Message Security 1.0
vs. 1.1 and WS-Addressing August 2004 version vs. WS-Addressing W3C Recommendation
@@ -1368,4 +1368,8 @@
<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
+ Editorial action <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/203">203</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://www.w3.org/Bugs/Public/show_bug.cgi?id=3979#c1">resolution</a>
+ 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></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.41
retrieving revision 1.42
diff -u -d -r1.41 -r1.42
--- ws-policy-guidelines.xml 15 Mar 2007 01:27:08 -0000 1.41
+++ ws-policy-guidelines.xml 16 Mar 2007 03:29:42 -0000 1.42
@@ -1202,20 +1202,20 @@
<div2 id="Referencing_Policy_Expressions">
<head>Referencing Policy Expressions</head>
- <p>The <bibref ref="WS-Policy-Primer"/> 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
- other policy expressions by reference. Assertion
- authors, especially those defining complex assertions that
- include nesting or complex types should consider specifying or recommending
- naming conventions in order to promote reuse. Reuse through
- referencing allows a policy expression to be utilized not only
- within another expression but also allows specification of
- additional policy subjects and their association to common
- policy expressions that are identified. It also promotes
- manageability of the expressions as they are uniquely
- identified.
- </p>
+ <p>The <bibref ref="WS-Policy-Primer"/> 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
+ other policy expressions by reference. Reuse may also be useful for
+ domain assertion authors, especially those defining complex assertions
+ utilizing references to policy expressions by nesting. Statically
+ available parameterized content may also be reused by different
+ assertions. However, such referencing mechanism is outside the scope of
+ WS-Policy naming and referencing framework and other mechanisms could be used.
+ As an example, in <bibref ref="WS-Policy-Primer"/>
+ Section 4.2, the <code>sp:issuedToken</code> assertion utilizes the
+ <code>sp:RequestSecurityTokenTemplate</code> parameter that contains necessary
+ information to request a security token. The contents of the parameter
+ are static and allows reuse in different security scenerios.</p>
</div2>
<div2 id="extending-assertions">
<head> Evolution of Assertions (Versioning and Compatibility)</head>
@@ -2025,7 +2025,17 @@
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>
+ </tr>
+ <tr>
+ <td>20070315</td>
+ <td>ASV</td>
+ <td>Implemented the <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3979#c1">resolution</loc>
+ for <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3979">issue 3979</loc>.
+ Editors' action
+ <loc
+ href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/198">198</loc>.
+ </td>
+ </tr>
</tbody>
</table>
</inform-div1>
Received on Friday, 16 March 2007 03:29:57 UTC