- From: Maryann Hondo via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 09 Oct 2006 03:07:38 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv26343
Modified Files:
ws-policy-attachment.xml
Log Message:
updated to address use of the term subject for editor action1, f2f action 10
Index: ws-policy-attachment.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-attachment.xml,v
retrieving revision 1.47
retrieving revision 1.48
diff -u -d -r1.47 -r1.48
--- ws-policy-attachment.xml 3 Oct 2006 05:31:05 -0000 1.47
+++ ws-policy-attachment.xml 9 Oct 2006 03:07:35 -0000 1.48
@@ -465,7 +465,7 @@
associated with a particular <termref def="policy_subject">policy subject</termref> using multiple
<termref def="policy_attachment">policy
attachments</termref>. For example, there may be attachments
- at different points in a WSDL description that apply to a
+ at different points in a WSDL description that apply to one policy
subject, and other attachments may be made by UDDI and other
mechanisms.</p>
<p>When multiple attachments are made, <termdef id="effective_policy" term="effective policy">the
@@ -482,7 +482,7 @@
children of a wrapper <el>wsp:Policy</el>
element.</termdef> The resulting policy expression is considered to
represent the combined policy of all of the attachments to
- that subject.</p>
+ that policy subject.</p>
<p>Such calculated policy expressions have no meaningful IRI of their own. </p>
</div2>
<div2 id="PolicyAttachmentMechanisms">
@@ -498,12 +498,9 @@
</div2>
<div2 id="XMLElementAttachement">
<head>XML Element Attachment</head>
-<p>It is often desirable to associate policies with the XML
- elements describing a subject; this allows description formats
- such as WSDL to be easily used with the Web Services Policy
- Framework (see Section <specref ref="AttachingPolicyUsingWSDL1.1"/> for the specific details
+<p>It is often desirable to associate policies with Web services policy subjects represented as XML elements (i.e., WSDL 1.1 elements - Section <specref ref="AttachingPolicyUsingWSDL1.1"/> for the specific details
of WSDL attachment).</p>
-<p>The precise
+<p>Since policy assertions are strongly typed by the authors, the precise
semantics of how element policy is to be processed once
discovered is domain-specific; however, implementations are
likely to follow the precedent specified in the section below
@@ -786,7 +783,7 @@
<termref def="policy_attachment">Policy attachments</termref> in WSDL 1.1 can be used to associate <termref def="policy">policies</termref>
with four different types of <termref def="policy_subject">policy subject</termref>, identified as the service
policy subject, the endpoint policy subject, the operation policy
-subject, and the message policy subject. These subjects should be
+subject, and the message policy subject. These policy subjects should be
considered as nested, due to the hierarchical nature of WSDL. </p>
<p>When attaching a <termref def="policy">policy</termref> to a WSDL element, a <termref def="policy_scope">policy scope</termref> is
implied for that attachment. The <termref def="policy_scope">policy scope</termref> only contains the <termref def="policy_subject">policy
@@ -794,7 +791,7 @@
children of that element. Therefore, it is
<rfc2119>RECOMMENDED</rfc2119> that each <termref def="policy_assertion">policy assertion</termref> contained
within a WSDL element's <termref def="element_policy">element policy</termref> should have the correct
-semantic such that the subject for that assertion is that WSDL
+semantic such that the policy subject for that assertion is that WSDL
element. For example, assertions that describe behaviours regarding
the manipulation of messages should only be contained within policies
attached to WSDL message elements.</p>
@@ -1851,7 +1848,7 @@
the children of that entity. This <termref def="policy">policy</termref> is the entity's <termref def="element_policy">element
policy</termref>.</p>
<p>Each <termref def="policy_assertion">policy assertion</termref> contained within a UDDI entity's <termref def="element_policy">element
-policy</termref> should have the correct semantic such that the subject for that
+policy</termref> should have the correct semantic such that the policy subject for that
assertion is that UDDI entity. For example, assertions that describe
behaviours regarding a service provider should only be contained
within policies attached to a businessEntity structure.</p>
@@ -2857,6 +2854,15 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3712">3712</loc>:wsp:PolicyReference can be used in any place where you can use wsp:Policy
</td>
</tr>
+<tr>
+<td>20061008</td>
+<td>MH</td>
+<td>Implemented the
+ <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/1">resolution</loc>
+ for issue
+ <loc href="http://www.w3.org/2006/07/13-ws-policy-minutes.html#action10">summary of Action 10 from F2F</loc> replaced "subject" instances with "policy subject"
+ </td>
+</tr>
</tbody>
</table>
</inform-div1>
Received on Monday, 9 October 2006 03:07:44 UTC