- From: Frederick Hirsch via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 31 Jan 2007 20:24:42 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy In directory hutz:/tmp/cvs-serv14249 Modified Files: ws-policy-guidelines.xml Log Message: Implement amendment in message 217 with minor editorial modifications for readability of entire sentence. This should complete editors action 152. Index: ws-policy-guidelines.xml =================================================================== RCS file: /sources/public/2006/ws/policy/ws-policy-guidelines.xml,v retrieving revision 1.33 retrieving revision 1.34 diff -u -d -r1.33 -r1.34 --- ws-policy-guidelines.xml 31 Jan 2007 20:15:13 -0000 1.33 +++ ws-policy-guidelines.xml 31 Jan 2007 20:24:40 -0000 1.34 @@ -1175,7 +1175,7 @@ </div2> <div2 id="interrelated-domains"> <head>Interrelated domains</head> - <p>Domain authors need to be clear about how assertions defined in + <p>Assertion authors need to be clear about how assertions defined in their domain may fit with assertions for interrelated domains. A classic example of such an interrelated domain is security, because security tends to @@ -1185,9 +1185,9 @@ related to the interrelated security domain [<bibref ref="WS-SecurityPolicy"/>] in Web Services Reliable Messaging Policy Assertions [<bibref ref="WS-RM-Policy"/>]. </p> - <p>Care should be taken to not duplicate existing - assertions and also to make sure that new assertions are consistent - with pre-existing assertions, when adding assertions related to an + <p>Assertion authors should not duplicate existing + assertions and should also make sure that when adding assertions those new assertions are consistent + with pre-existing assertions of any interrelated domain. </p> </div2> </div1>
Received on Wednesday, 31 January 2007 20:24:46 UTC