W3C home > Mailing lists > Public > public-ws-policy-eds@w3.org > November 2006

2006/ws/policy ws-policy-guidelines.xml,1.17,1.18

From: Frederick Hirsch via cvs-syncmail <cvsmail@w3.org>
Date: Thu, 30 Nov 2006 04:45:02 +0000
To: public-ws-policy-eds@w3.org
Message-Id: <E1GpdnC-0006hy-En@lionel-hutz.w3.org>

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

Modified Files:
	ws-policy-guidelines.xml 
Log Message:
Additional edit to fix versioning examples and additional editorial bug as noted in Asir;s action 90 part 2

Index: ws-policy-guidelines.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-guidelines.xml,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -d -r1.17 -r1.18
--- ws-policy-guidelines.xml	30 Nov 2006 04:04:19 -0000	1.17
+++ ws-policy-guidelines.xml	30 Nov 2006 04:44:59 -0000	1.18
@@ -1201,12 +1201,8 @@
         			</p>
 			</div2>
 			<div2 id="extending-assertions">
-					<head> Factors in Extending Assertions within a Domain </head>
-					<p> Extensibility affects the policy subjects and attachment semantics. </p>
-			</div2>
-			<div2 id="assertion-evolution">
-					<head>Evolution of Assertions (Versioning and Compatibility)</head>
-					<p>4.4.7. Over time, there may be multiple equivalent behaviors emerging in the Web
+					<head> Evolution of Assertions (Versioning and Compatibility)</head>
+					<p>Over time, there may be multiple equivalent behaviors emerging in the Web
            			Service interaction space. Examples of such multiple equivalent behaviors are WSS: SOAP Message Security 1.0
            			vs. 1.1 and WS-Addressing August 2004 version vs. WS-Addressing W3C Recommendation
            			[<bibref ref="WS-Addressing"/>]. These equivalent behaviors
@@ -1215,17 +1211,22 @@
            			policy expression in the example below requires the use of
            			WSS: SOAP Message Security 1.0. </p> 
            			<example>
-           			<head>Example 4-2. Message-level Security and WSS: SOAP Message Security 1.0 </head>
-					<p>ADD THE EXAMPLE HERE </p>
-					</example>
-					<p>The policy expression in the example below requires the use of WSS: SOAP Message Security 1.1. These are multiple
-           			equivalent behaviors and are represented using distinct policy assertions. </p>
-					<example>
-						<head>Example 4-3. Message-level Security and WSS: SOAP Message Security 1.1</head>
-						<p>ADD THE EXAMPLE HERE </p>
-					</example>
-					<p>Best practice: use independent assertions for modeling multiple equivalent behaviors. </p>
-					<!-- EDS TO DO reconcile from Primer. GET THE REST FROM DAVE and Umit -->
+           				<head>Message-level Security and WSS: SOAP Message Security 1.0</head>
+           						<eg xml:space="preserve">&lt;Policy&gt;
+           							&lt;sp:Wss10&gt;&hellip;&lt;/sp:Wss10&gt;
+           							&lt;/Policy&gt;</eg>
+           					</example>
+           					<p>The policy expression in the example below requires the use of WSS: SOAP Message
+           						Security 1.1. These are multiple equivalent behaviors and are represented using distinct
+           						policy assertions.</p>
+           					<example>
+           						<head>Message-level Security and WSS: SOAP Message Security 1.1</head>
+           						<eg xml:space="preserve">&lt;Policy&gt;
+           							&lt;sp:Wss11&gt;&hellip;&lt;/sp:Wss11&gt;
+           							&lt;/Policy&gt;</eg>
+           					</example>
+           					<p>Best practice: use independent assertions for modeling multiple equivalent
+           						behaviors.</p>
 			</div2>	      
 		</div1>
 		
Received on Thursday, 30 November 2006 04:45:10 GMT

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