W3C home > Mailing lists > Public > public-ws-policy-eds@w3.org > July 2007

2006/ws/policy ws-policy-guidelines.xml,1.101,1.102 ws-policy-guidelines.html,1.86,1.87

From: David Orchard via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 18 Jul 2007 16:11:43 +0000
To: public-ws-policy-eds@w3.org
Message-Id: <E1IBC7r-0006K7-J5@lionel-hutz.w3.org>

Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv24022

Modified Files:
	ws-policy-guidelines.xml ws-policy-guidelines.html 
Log Message:
bug 4664

Index: ws-policy-guidelines.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-guidelines.html,v
retrieving revision 1.86
retrieving revision 1.87
diff -u -d -r1.86 -r1.87
--- ws-policy-guidelines.html	18 Jul 2007 15:52:16 -0000	1.86
+++ ws-policy-guidelines.html	18 Jul 2007 16:11:40 -0000	1.87
@@ -724,7 +724,10 @@
 &lt;/wsp:Policy&gt;</pre></div></div></div><div class="div3">
 <h4><a name="nested-assertions" id="nested-assertions"></a>5.4.2 Nested Assertions</h4><p>The framework provides the ability to "nest" policy assertions. For domains with a complex set of
         				options, nesting provides one way to indicate dependent
-        				elements within a behavior.</p><p>
+        				elements within a behavior.   In particular, when assertion authors define an assertion
+type that allows nested policy expression, it is important to also define the
+semantics of that assertion when it contains an empty nested policy expression
+(for example: &lt;wsam:Addressing&gt;&lt;wsp:Policy/&gt;&lt;/wsam:Addressing&gt;).</p><p>
 						The following design questions below can help
 						to determine when to use nested policy expressions:</p><ul><li><p>Are these assertions designed for the same policy subject? </p></li><li><p>Do these assertions represent dependent behaviors?</p></li></ul><p>If the answers are yes to both of these questions then leveraging nested policy
 						expressions is something to consider. Keep in mind that a nested policy expression participates in
@@ -1529,4 +1532,7 @@
 								6 Applying Best Practices for Policy Attachment</a></td></tr><tr><td rowspan="1" colspan="1">20070718</td><td rowspan="1" colspan="1">DBO</td><td rowspan="1" colspan="1">Implemented the resolution 
 							for issue <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4661">4661</a>, <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4662">4662</a>, <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4861">4861</a>. 
 							Editors' action: 
-							<a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/342">342</a>, <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/346">346</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/342">342</a>, <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/346">346</a>. </td></tr><tr><td rowspan="1" colspan="1">20070718</td><td rowspan="1" colspan="1">DBO</td><td rowspan="1" colspan="1">Implemented the resolution 
+							for issue <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4664">4664</a>. 
+							Editors' action: 
+							<a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/343">343</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.101
retrieving revision 1.102
diff -u -d -r1.101 -r1.102
--- ws-policy-guidelines.xml	18 Jul 2007 15:52:16 -0000	1.101
+++ ws-policy-guidelines.xml	18 Jul 2007 16:11:40 -0000	1.102
@@ -907,7 +907,10 @@
 				<head>Nested Assertions</head>
 						<p>The framework provides the ability to "nest" policy assertions. For domains with a complex set of
         				options, nesting provides one way to indicate dependent
-        				elements within a behavior.</p>
+        				elements within a behavior.   In particular, when assertion authors define an assertion
+type that allows nested policy expression, it is important to also define the
+semantics of that assertion when it contains an empty nested policy expression
+(for example: &lt;wsam:Addressing&gt;&lt;wsp:Policy/&gt;&lt;/wsam:Addressing&gt;).</p>
 					<p>
 						The following design questions below can help
 						to determine when to use nested policy expressions:</p>
@@ -2485,7 +2488,15 @@
 							for issue <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4661">4661</loc>, <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4662">4662</loc>, <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4861">4861</loc>. 
 							Editors' action: 
 							<loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/342">342</loc>, <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/346">346</loc>. </td>
-</tr>                   		              			                          		              			 
+</tr>                   		              			        
+<tr>
+<td>20070718</td>
+<td>DBO</td>
+						<td>Implemented the resolution 
+							for issue <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4664">4664</loc>. 
+							Editors' action: 
+							<loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/343">343</loc>. </td>
+</tr>                   		              	                  		              			 
 				</tbody>
 			</table>
 		</inform-div1>
Received on Wednesday, 18 July 2007 16:11:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:21:03 GMT