2006/ws/policy ws-policy-guidelines.xml,1.44,1.45

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

Modified Files:
Log Message:
completed editor action item 199 to replace text for bug 4073  

Index: ws-policy-guidelines.xml
RCS file: /sources/public/2006/ws/policy/ws-policy-guidelines.xml,v
retrieving revision 1.44
retrieving revision 1.45
diff -u -d -r1.44 -r1.45
--- ws-policy-guidelines.xml	16 Mar 2007 04:14:04 -0000	1.44
+++ ws-policy-guidelines.xml	19 Mar 2007 14:43:52 -0000	1.45
@@ -280,8 +280,7 @@
 				<div3 id="domain-owners">
 				<head> Assertion Authors</head>
-				<p>Assertion Authors are defined
-       			 by the WS-Policy Framework to be a community that chooses to
+				<p>Assertion Authors are a community that chooses to
         		exploit the WS-Policy Framework by creating their own
         		specification to define a set of assertions that express the
         		capabilities and constraints of that target domain. The
@@ -299,9 +298,9 @@
     	    	must adhere to the MUST's and SHOULD's in the specification
     	    	and should review the conformance section of the specification. 
-    	   		 <p>Assertion Authors must also specify how to associate
-				the assertions they have defined with the policy subjects
-				identified by the WS-PolicyAttachment specification.
+    	   		 <p>An assertion author should also specify a policy subject. For
+				instance, if a policy assertion were to be used with WSDL, an assertion
+				description should specify a WSDL policy subject.
         		<p>An example of a domain specification that follows these practices is the WS-SecurityPolicy
         		specification [<bibref ref="WS-SecurityPolicy"/>]. The
@@ -363,10 +362,7 @@
 				and Web Services Policy 1.5 - Attachment [<bibref ref="WS-PolicyAttachment"/>] specifications.
 				The Web Services Policy 1.5 - Attachment specification has defined a set of
 	   			subjects and an extensible mechanism for attaching policies
-	   			to web services subjects. When a web service provider
-	   			chooses to make its capabilities and constraints available,
-	   			the provider may also need to conform to requirements of other policy
-	   			assertion specifications it utilizes ( i.e., WS-SecurityPolicy).
+	   			to web services subjects. 
 				<p>When deploying services with policies it is useful for providers to anticipate how
            		to evolve their services capabilities over time.  If
@@ -627,7 +623,7 @@
         		<div3 id="self-describing">
 					<head> Self Describing Messages </head>
-        			<p> WS-Policy is intended to communicate the requirements, capabilities, preferences and
+        			<p> WS-Policy is intended to communicate the requirements, capabilities and
     	 			behaviors of nodes that provide the message's path, not specifically to declare properties of the message semantics. One
     	 			of the advantages of Web services is that an XML message can be stored and later examined (e.g. as a record of a business
      				transaction) or interpreted by an intermediary; however, if information that is necessary to understand a message is not
@@ -869,7 +865,7 @@
         			<p>Best practice: If the assertion
         			authors want to delegate the processing to the framework,
         			utilizing nesting should be considered. Otherwise, domain
-        			specific comparison algorithms will need to be devised and be
+        			specific comparison algorithms may need to be devised and be
         			delegated to the specific domain handlers that are not visible
         			to the WS-Policy framework.
@@ -1289,10 +1285,7 @@
 				<p>Policy attachment should not affect the interpretation of
          Policy alternatives. If it did, each policy assertion would
          need to be written with different (and possibly unknown)
-         attachment mechanisms in mind. In particular, the timing of a
-         policy attachment or the role that a party who attaches
-         policy should have no bearing on the evaluation of the policy
-         assertion </p>
+         attachment mechanisms in mind.  </p>
 				<!-- EDS TO DO: [CLARIFY SUBJECT RELATIONSHIP] in the paragraph above -->
 			<div2 id="appropriate-attachment-assertion-subjects">
@@ -1561,8 +1554,9 @@
   will be intersected and merged with other assertions in the
   calculation of an effective policy and this also indicates they need
   to consider policy subjects.</p>
-			<p>The policy framework only defines an algorithm for calculating
-  effective policies for WSDL 1.1 based subjects. </p>
+			<p> The WS-Policy 1.5 - Attachment specification defines algorithms for calculating the 
+ effective policy for a given policy subject and effective policies for
+ WSDL 1.1, WSDL 2.0 and UDDI policy subjects.</p>
@@ -2064,6 +2058,17 @@
 							as outlined in 
 							<loc href="http://lists.w3.org/Archives/Public/public-ws-policy/2007Feb/0169.html">proposal</loc>.
 							Editorial action <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/197">197</loc>.	</td>
+					</tr>
+					<tr>
+						<td>20070319</td>
+						<td>MH</td>
+						<td> Implemented resolution for issue 
+							<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4073">4073</loc>
+							in response to editor's action 
+							<loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/199">199 </loc>
+							as outlined in 
+							<loc href="http://lists.w3.org/Archives/Public/public-ws-policy/2007Mar/0093.html">proposal </loc>.
+							</td>

Received on Monday, 19 March 2007 14:44:06 UTC