2006/ws/policy ws-policy-framework.xml,1.65,1.66

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

Modified Files:
	ws-policy-framework.xml 
Log Message:
replaced security policy example as per issue 3753- editor action 45

Index: ws-policy-framework.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-framework.xml,v
retrieving revision 1.65
retrieving revision 1.66
diff -u -d -r1.65 -r1.66
--- ws-policy-framework.xml	7 Oct 2006 22:30:55 -0000	1.65
+++ ws-policy-framework.xml	9 Oct 2006 13:18:23 -0000	1.66
@@ -130,27 +130,33 @@
             <example id="ex-wsp-use-security-assertations">
                 <head>Use of Web Services Policy with security policy assertions.</head>
                 <eg xml:space="preserve">
+                
 (01) &lt;wsp:Policy
         xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"
         xmlns:wsp="&nsuri;" &gt;
-(02)   &lt;wsp:ExactlyOne&gt;
-(03)     &lt;sp:Basic256Rsa15 /&gt;
-(04)     &lt;sp:TripleDesRsa15 /&gt;
-(05)   &lt;/wsp:ExactlyOne&gt;
-(06) &lt;/wsp:Policy&gt;</eg>
-            </example>
-            
-            <p>Lines (01-06) represent a
-                policy for the algorithm suite required for performing
-                cryptographic operations with symmetric or asymmetric
-                key-based security tokens.</p>
+(02)   &lt;wsp:ExactlyOne&gt;
+(03)     &lt;sp:wsp:All&gt;
+(04)        &lt;sp:SignedParts/&gt;
+(05)           &lt;sp:Body/&gt;
+(06)        &lt;/sp:SignedParts/&gt;
+(07)     &lt;/wsp:All&gt;
+(08)     &lt;sp:wsp:All&gt;
+(09)        &lt;sp:EncryptedParts/&gt;
+(10)           &lt;sp:Body/&gt;
+(11)        &lt;/sp:EncryptedParts/&gt;
+(12)     &lt;/wsp:All&gt;
+(13)   &lt;/wsp:ExactlyOne&gt;
+(14) &lt;/wsp:Policy&gt;</eg> 
+            </example>     
+            <p>Lines (03-06) represent one
+                policy alternative for signing a message body.</p>
             
-            <p>Lines (02-05) illustrate the <el>ExactlyOne</el> policy
+            <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
                 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 uses
-                one of the algorithm suite assertions (Lines 03-04)
-                specified.</p>        
+                above would be that an invocation of a Web service will either sign or encrypt the message body.</p>           
+           
         </div2>
 	</div1>
 	<div1 id='Notation_Terminlogy'>
@@ -589,25 +595,27 @@
 <p>To simplify processing and improve interoperability, the normal
     form of a policy expression <rfc2119>SHOULD</rfc2119> be used where practical.</p>
 
-	      <p>For example, the following is the normal form of the policy expression example introduced earlier (see <specref ref='ex-wsp-use-security-assertations' />).</p>
+	      <p>For example, the following is the normal form of a policy expression.</p>
 <eg xml:space="preserve">(01) &lt;wsp:Policy
         xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"
         xmlns:wsp="&nsuri;" &gt;
 (02)   &lt;wsp:ExactlyOne&gt;
-(03)     &lt;wsp:All&gt;
-(04)       &lt;sp:Basic256Rsa15 /&gt;
-(05)     &lt;/wsp:All&gt;
-(06)     &lt;wsp:All&gt;
-(07)       &lt;sp:TripleDesRsa15 /&gt;
-(08)     &lt;/wsp:All&gt;
-(09)   &lt;/wsp:ExactlyOne&gt;
-(10) &lt;/wsp:Policy&gt;</eg>
+(03)     &lt;sp:wsp:All&gt;
+(04)        &lt;sp:SignedParts/&gt;
+(05)           &lt;sp:Body/&gt;
+(06)        &lt;/sp:SignedParts/&gt;
+(07)     &lt;/wsp:All&gt;
+(08)     &lt;sp:wsp:All&gt;
+(09)        &lt;sp:EncryptedParts/&gt;
+(10)           &lt;sp:Body/&gt;
+(11)        &lt;/sp:EncryptedParts/&gt;
+(12)     &lt;/wsp:All&gt;
+(13)   &lt;/wsp:ExactlyOne&gt;
+(14) &lt;/wsp:Policy&gt;</eg>
 
-<p>Lines (03-05) and Lines (06-08) express the two alternatives in the
-policy. If the first alternative is selected, only the Basic 256 RSA
-15 algorithm suite [<bibref ref="WS-SecurityPolicy"/>] is supported;
-conversely, if the second alternative is selected, only the 3DES RSA
-15 algorithm suite is supported. </p>
+<p>Lines (03-07) and Lines (08-11) express the two alternatives in the
+policy. If the first alternative is selected, the message body needs to be signed [<bibref ref="WS-SecurityPolicy"/>] is supported;
+conversely, if the second alternative is selected, the message body needs to be encrypted. </p>
 	  </div2>
 <div2 id="Policy_Identification">
 <head>Policy Identification</head>
@@ -2021,6 +2029,13 @@
                             <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/19">19</loc> Add an intro paragraph that introduces the material in section 4.3.3.
                         </td>
                     </tr>
+                    <tr>
+                        <td>20061008</td>
+                        <td>MH</td>
+                        <td>Completed action item:
+                            <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/45">45</loc> Replace security policy example 1.1. as per issue 3753.
+                        </td>
+                    </tr>
                 </tbody>
             </table>
         </inform-div1>

Received on Monday, 9 October 2006 13:18:32 UTC