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

2006/ws/policy ws-policy-guidelines.html,1.65,1.66 ws-policy-guidelines.xml,1.79,1.80

From: Prasad Yendluri via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 29 May 2007 22:52:08 +0000
To: public-ws-policy-eds@w3.org
Message-Id: <E1HtAXw-0006HH-5m@lionel-hutz.w3.org>

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

Modified Files:
	ws-policy-guidelines.html ws-policy-guidelines.xml 
Log Message:
Implemented Resolution in Editors' action 291. Consistent use of should in place of must in the best practice statements

Index: ws-policy-guidelines.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-guidelines.html,v
retrieving revision 1.65
retrieving revision 1.66
diff -u -d -r1.65 -r1.66
--- ws-policy-guidelines.html	29 May 2007 22:45:12 -0000	1.65
+++ ws-policy-guidelines.html	29 May 2007 22:52:06 -0000	1.66
@@ -576,7 +576,7 @@
 &lt;/sp:IssuedToken&gt;
  
  </pre></div></div><div class="boxedtext"><p><a name="AssertionDefinitions" id="AssertionDefinitions"></a><span class="practicelab">Best
-Practice 6: Specify Semantics Clearly</span></p><p class="practice"> An assertion description must clearly and completely specify the semantics of a policy 
+Practice 6: Specify Semantics Clearly</span></p><p class="practice"> An assertion description should clearly and completely specify the semantics of a policy 
 			  	    assertion.
 			  	    </p></div><div class="boxedtext"><p><a name="XMLOutline" id="XMLOutline"></a><span class="practicelab">Best
 Practice 7: Provide an XML Outline</span></p><p class="practice"> An assertion description should provide an XML outline plus an XML schema to specify the
@@ -938,7 +938,7 @@
 				</p></div></div></div><div class="div2">
 <h3><a name="levels-of-abstraction" id="levels-of-abstraction"></a>5.7 Considerations for Policy Attachment in WSDL </h3><p>A behavior identified by a policy assertion applies to the
         		associated policy subject. If a policy assertion is to be used
-        		within WSDL, Assertion Authors must specify a WSDL
+        		within WSDL, Assertion Authors should specify a WSDL
         		policy subject. 
         		</p><p>The specific WSDL policy subject is determined with respect to 
 				a behavior as follows:</p><ul><li><p>If the behavior applies to any message exchange
@@ -1014,7 +1014,7 @@
 					is beyond single message exchanges. This is illustrative of how the 
 					Assertion Authors can specify additional constraints and assumptions 
 					for attachment and engagement of behavior. Such additional constraints 
-					must be clearly specified by the Assertion Authors.
+					should be clearly specified by the Assertion Authors.
 				</p><p>Since many attachment points are available in WSDL, it would be
 				necessary for Assertion Authors to recommend a preferred attachment 
 				point. One approach would be to identify different attachment points in
@@ -1697,4 +1697,7 @@
 						</td></tr><tr><td rowspan="1" colspan="1">20070529</td><td rowspan="1" colspan="1">PY</td><td rowspan="1" colspan="1">Implemented Resolution in Editors' action 
 							<a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/290">290</a>.
 							Consistent use of Assertion Authors.
+						</td></tr><tr><td rowspan="1" colspan="1">20070529</td><td rowspan="1" colspan="1">PY</td><td rowspan="1" colspan="1">Implemented Resolution in Editors' action 
+							<a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/291">291</a>.
+							Consistent use of should in place of must in the best practice statements.
 						</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.79
retrieving revision 1.80
diff -u -d -r1.79 -r1.80
--- ws-policy-guidelines.xml	29 May 2007 22:45:12 -0000	1.79
+++ ws-policy-guidelines.xml	29 May 2007 22:52:06 -0000	1.80
@@ -683,7 +683,7 @@
  </example>        		
  			  	
  			  	    <p role="practice" id="AssertionDefinitions"> <quote>Specify Semantics Clearly</quote> >
-			  	    <quote> An assertion description must clearly and completely specify the semantics of a policy 
+			  	    <quote> An assertion description should clearly and completely specify the semantics of a policy 
 			  	    assertion.
 			  	    </quote>
 			  	    </p>
@@ -1202,7 +1202,7 @@
 				<head>Considerations for Policy Attachment in WSDL </head>
 				<p>A behavior identified by a policy assertion applies to the
         		associated policy subject. If a policy assertion is to be used
-        		within WSDL, Assertion Authors must specify a WSDL
+        		within WSDL, Assertion Authors should specify a WSDL
         		policy subject. 
         		</p>
 				
@@ -1329,7 +1329,7 @@
 					is beyond single message exchanges. This is illustrative of how the 
 					Assertion Authors can specify additional constraints and assumptions 
 					for attachment and engagement of behavior. Such additional constraints 
-					must be clearly specified by the Assertion Authors.
+					should be clearly specified by the Assertion Authors.
 				</p>
 				
 				<p>Since many attachment points are available in WSDL, it would be
@@ -2604,6 +2604,14 @@
 							<loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/290">290</loc>.
 							Consistent use of Assertion Authors.
 						</td>
+					</tr>
+					<tr>
+						<td>20070529</td>
+						<td>PY</td>
+						<td>Implemented Resolution in Editors' action 
+							<loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/291">291</loc>.
+							Consistent use of should in place of must in the best practice statements.
+						</td>
 					</tr>                 			 
 				</tbody>
 			</table>
Received on Tuesday, 29 May 2007 22:52:12 GMT

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