2006/ws/policy ws-policy-framework.xml,1.71,1.72 ws-policy-attachment.xml,1.51,1.52

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

Modified Files:
	ws-policy-framework.xml ws-policy-attachment.xml 
Log Message:
Addressed Paul's editorial comments from 10/18/06

Index: ws-policy-framework.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-framework.xml,v
retrieving revision 1.71
retrieving revision 1.72
diff -u -d -r1.71 -r1.72
--- ws-policy-framework.xml	13 Oct 2006 20:20:40 -0000	1.71
+++ ws-policy-framework.xml	19 Oct 2006 19:24:38 -0000	1.72
@@ -141,8 +141,8 @@
             <p>Lines (03-06) represent one
                 policy alternative for signing a message body.</p>
             
-            <p>Lines (08-11) represents a second policy alternative for encrypting a message body. </p>
-            <p>Lines (02-13) illustrates the <el>ExactlyOne</el> policy
+            <p>Lines (08-11) represent a second policy alternative for encrypting a message body. </p>
+            <p>Lines (02-13) illustrate the <el>ExactlyOne</el> policy
                 operator. Policy operators group policy assertions into
                 policy alternatives. A valid interpretation of the policy
                 above would be that an invocation of a Web service will either sign or encrypt the message body.</p>           
@@ -508,7 +508,7 @@
 	  (iii) Identification of policy expressions and (iv) Policy intersection. 
 	  </p>
 	  <p> The normal form of a policy expression is the most straightforward
-	  Infoset represenattion; equivalent, alternative Infosets allow compactly
+	  Infoset representation; equivalent, alternative Infosets allow compactly
 	  expressing a policy through a number of constructs.</p>
 	  
 	  <p>This specification does not define processing for arbitrary <el>wsp:Policy</el>
@@ -801,7 +801,7 @@
 role="infoset-property">children</emph> property; as explained in
 Section <specref ref='Policy_Operators'/>, this is equivalent to a
 nested policy expression with a single alternative that has zero
-assertions. The reason for requring least an empty <code>&lt;wsp:Policy/&gt;</code> 
+assertions. The reason for requiring at least an empty <code>&lt;wsp:Policy/&gt;</code> 
 Element above is to ensure that two assertions of the same type will always be 
 compatible and an intersection would not fail 
 (see Section <specref ref="Policy_Intersection"/>).</p>
@@ -1346,7 +1346,8 @@
             be mitigated by requiring authentication for sensitive information, by omitting sensitive
             information from the policy or by securing access to the policy. For securing access to
             policy metadata, policy providers can use mechanisms from other Web Services
-            specifications such as WS-Security and WS-MetadataExchange.</p>
+            specifications such as WS-Security [<bibref ref="WS-Security"/>] and 
+            WS-MetadataExchange [<bibref ref="WS-MetadataExchange"/>] .</p>
     </div2>
     <div2 id="spoofing-and-tampering-threats">
         <head>Spoofing and Tampering Threats</head>
@@ -1623,6 +1624,13 @@
 	  2.0</loc> is available at
 	  http://www.w3.org/TR/wsdl20.
 	</bibl>
+    <bibl id="WS-MetadataExchange" key="WS-MetadataExchange"
+       href="http://schemas.xmlsoap.org/ws/2004/09/mex/">
+       <titleref>Web Services Metadata Exchange (WS-MetadataExchange)</titleref>, K. Ballinger,
+       et al, Authors. BEA Systems Inc., Computer Associates International, Inc., International
+       Business Machines Corporation, Microsoft Corporation, Inc., SAP AG, Sun Microsystems, and
+       webMethods, August 2006. Available at http://schemas.xmlsoap.org/ws/2004/09/mex/.
+    </bibl>
 	<bibl id="XML-Signature" key="XML-Signature" href="http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/">
 	  <titleref>XML-Signature Syntax and Processing</titleref>,
 	  D. Eastlake, J. Reagle, and D. Solo, Editors. The Internet
@@ -2039,7 +2047,7 @@
                         <td>Updated "Changes in this Version" section (Appendix C)
                         </td>
                     </tr>
-                     <tr>
+                    <tr>
                        	<td>20061012</td>
                        	<td>DBO</td>
                        	<td>Revisited action items: <loc href="http://www.w3.org/2006/07/12-ws-policy-minutes.html#action15">15</loc> 
@@ -2047,6 +2055,13 @@
                        	     <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3720">3720</loc>                 	
                        	</td>
                     </tr>
+                    <tr>
+                        <td>20061019</td>
+                        <td>PY</td>
+                        <td>Completed action item:
+                            <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/57">57</loc> PaulC's comments.
+                        </td>
+                    </tr>
                 </tbody>
             </table>
         </inform-div1>

Index: ws-policy-attachment.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-attachment.xml,v
retrieving revision 1.51
retrieving revision 1.52
diff -u -d -r1.51 -r1.52
--- ws-policy-attachment.xml	13 Oct 2006 20:29:44 -0000	1.51
+++ ws-policy-attachment.xml	19 Oct 2006 19:24:38 -0000	1.52
@@ -439,7 +439,7 @@
 	assumed to be located at
 	<code>http://www.example.com/policies</code>.  Per Section
 	<xspecref href="&framework.latest;/#Policy_Identification">3.2
-	Policy Identification</xspecref> of &framework.title; [<bibref ref="WS-Policy"/>], the URIs used for these <termref def="policy_expression">policy expressions</termref>
+	Policy Identification</xspecref> of &framework.title; [<bibref ref="WS-Policy"/>], the IRIs used for these <termref def="policy_expression">policy expressions</termref>
 	in the remainder of this document are
 	<code>http://www.example.com/policies#RmPolicy</code> and
 	<code>http://www.example.com/policies#X509EndpointPolicy</code>,
@@ -588,7 +588,7 @@
 <p>This mechanism allows <termref def="policy">policies</termref> to be associated with a <termref def="policy_subject">policy
 subject</termref> independent of that subject's definition and/or representation
 through the use of a <el>wsp:PolicyAttachment</el>
-gelement.</p>
+element.</p>
 <p>This element has three components: the <termref def="policy_scope">policy scope</termref> of the
 attachment, the <termref def="policy_expression">policy expressions</termref> being bound, and optional security
 information. The <termref def="policy_scope">policy scope</termref> of the attachment is defined using one
@@ -2869,6 +2869,13 @@
           <td>PY</td>
             <td>Updated "Changes in this Version" section (Appendix D)</td>
       </tr>
+      <tr>
+          <td>20061019</td>
+          <td>PY</td>
+          <td>Completed action item:
+            <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/57">57</loc> PaulC's comments.
+          </td>
+      </tr>
 </tbody>
 </table>
 </inform-div1>

Received on Thursday, 19 October 2006 19:24:51 UTC