- From: Prasad Yendluri via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 22 Jan 2007 20:06:47 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv24035
Modified Files:
ws-policy-framework.xml
Log Message:
Completed AI 128, to implement resolution of issue 4203
Index: ws-policy-framework.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-framework.xml,v
retrieving revision 1.104
retrieving revision 1.105
diff -u -d -r1.104 -r1.105
--- ws-policy-framework.xml 22 Jan 2007 19:41:40 -0000 1.104
+++ ws-policy-framework.xml 22 Jan 2007 20:06:45 -0000 1.105
@@ -100,21 +100,22 @@
language to allow both kinds of assertions to be expressed and evaluated
in a consistent manner.</p>
-<p>&framework.title; does not specify policy discovery or
- policy attachments. A <termref def="policy_expression">policy attachment</termref> is a mechanism for associating
- policy with one or more policy scopes, where a <termref def="policy_scope">policy scope</termref> is a collection of
- policy subjects to which a policy may apply. A <termref def="policy_subject">policy subject</termref> is an entity
+ <p>&framework.title; does not cover discovery of policy, policy scopes and subjects,
+ or their respective attachment mechanisms.
+ A <termref def="policy_expression">policy attachment</termref> is a mechanism for associating
+ policy with one or more policy scopes. A <termref def="policy_scope">policy scope</termref> is
+ a collection of policy subjects to which a policy applies.
+ A <termref def="policy_subject">policy subject</termref> is an entity
(e.g., an endpoint, message, resource, interaction) with which a
- policy can be associated. Other specifications are
- free to define technology-specific mechanisms for
- associating policy with various entities and
- resources. &attachment.title; [<bibref ref="WS-PolicyAttachment"/>]
- defines such mechanisms, especially for associating policy
- with arbitrary XML elements [<bibref ref='XML10'/>], WSDL artifacts [<bibref ref="WSDL11" />, <bibref
- ref="WSDL20" />], and UDDI
- elements [<bibref
- ref="UDDIAPI20" />, <bibref ref="UDDIDataStructure20"
- />, <bibref ref="UDDI30" />].</p>
+ policy can be associated. &attachment.title; [<bibref ref="WS-PolicyAttachment"/>]
+ defines such policy attachment mechanisms, especially for associating policy
+ with arbitrary XML elements [<bibref ref='XML10'/>], WSDL artifacts [<bibref ref="WSDL11" />,
+ <bibref ref="WSDL20" />], and UDDI elements [<bibref ref="UDDIAPI20" />,
+ <bibref ref="UDDIDataStructure20"/>, <bibref ref="UDDI30" />].
+ Other specifications are free to define either extensions to the mechanisms
+ defined in &attachment.title; [<bibref ref="WS-PolicyAttachment"/>], or additional
+ mechanisms not covered by &attachment.title; [<bibref ref="WS-PolicyAttachment"/>],
+ for purposes of associating policy with policy scopes and subjects.</p>
<div2 id="Example">
@@ -2421,6 +2422,13 @@
<loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/125">125</loc>
Resolution for issue <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4177">4177</loc></td>
</tr>
+ <tr>
+ <td>20070122</td>
+ <td>PY</td>
+ <td>Completed action item:
+ <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/128">128</loc>
+ Resolution for issue <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4203">4203</loc></td>
+ </tr>
</tbody>
</table>
</inform-div1>
Received on Monday, 22 January 2007 20:06:50 UTC