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

2006/ws/policy ws-policy-guidelines.html,1.7,1.8

From: Umit Yalsinap via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 01 Nov 2006 02:40:44 +0000
To: public-ws-policy-eds@w3.org
Message-Id: <E1Gf620-0007Pf-MJ@lionel-hutz.w3.org>

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

Modified Files:
	ws-policy-guidelines.html 
Log Message:
Fixed a reference

Index: ws-policy-guidelines.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-guidelines.html,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -d -r1.7 -r1.8
--- ws-policy-guidelines.html	1 Nov 2006 02:32:16 -0000	1.7
+++ ws-policy-guidelines.html	1 Nov 2006 02:40:42 -0000	1.8
@@ -658,9 +658,9 @@
             semantics if the incoming messages also utilized the
             behavior. This is especially important if the assertion is
             applicable to more than one specific policy subject. One
-            approach that is currently taken by WS-RM Policy <cite><a href="#WS-RM">Web Services Reliable Messaging</a></cite> is to introduce both message and endpoint
+            approach that is currently taken by WS-RM Policy [<cite><a href="#WS-RM-Policy">Web Services Reliable Messaging Policy</a></cite>] is to introduce both message and endpoint
             policy subjects for one of its assertions and require the
-            use of endpoint policy subject when message level subject
+            use of endpoint policy subject when message policy subject
             is used via attachment. </p></li></ul></li><li><p>Optional assertion authors should explicitly state
           how the behavior that is enabled by the assertion would be
           engaged when they are designing their assertion, whether by
Received on Wednesday, 1 November 2006 02:46:07 GMT

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