- From: David Orchard via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 12 Oct 2006 23:05:28 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv12485
Modified Files:
ws-policy-framework.xml
Log Message:
bug 3722, define terms where used.
Index: ws-policy-framework.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-framework.xml,v
retrieving revision 1.69
retrieving revision 1.70
diff -u -d -r1.69 -r1.70
--- ws-policy-framework.xml 12 Oct 2006 20:17:27 -0000 1.69
+++ ws-policy-framework.xml 12 Oct 2006 23:05:25 -0000 1.70
@@ -80,15 +80,11 @@
entities in a Web services-based system.
</p>
- <p><termdef id='policy' term='policy'>A <term>policy</term> is a collection of
- <termref def='policy_alternative'>policy alternatives</termref>, </termdef>
- where <termdef id='policy_alternative' term='policy alternative'>a <term>policy alternative</term>
- is a collection of <termref def='policy_assertion'>policy assertions</termref>.</termdef>
- <termdef id='policy_assertion' term='policy assertion'>A <term>policy assertion</term>
- represents an individual requirement, capability, or other property of a behavior.</termdef>
- <termdef id='policy_expression' term='policy expression'>A <term>policy expression</term>
- is an XML Infoset representation of a <termref def='policy'>policy</termref>,
- either in a normal form or in an equivalent compact form.</termdef> Some policy assertions
+ <p>A policy is a collection of policy alternatives,
+ where a policy alternative is a collection of policy assertions.
+ A policy assertion represents an individual requirement, capability, or other property of a behavior. A policy expression
+ is an XML Infoset representation of a policy,
+ either in a normal form or in an equivalent compact form. Some policy assertions
specify traditional requirements and capabilities that
will ultimately manifest on the wire (e.g., authentication
scheme, transport protocol selection). Other policy
@@ -99,17 +95,11 @@
in a consistent manner.</p>
<p>&framework.title; does not specify policy discovery or
- <termref def="policy_attachment">policy attachment</termref>.
- <termdef id="policy_attachment" term="policy attachment">A
- <term>policy attachment</term> is a mechanism for associating
- <termref def="policy">policy</termref> with one or more <termref def="policy_scope">policy scopes</termref>.</termdef>
- <termdef id="policy_scope" term="policy scope">A <term>policy scope</term> is a collection of
- <termref def="policy_subject">policy subjects</termref> to which a policy may apply.</termdef>
- <termdef id="policy_subject" term="policy subject">A <term>policy subject</term> is an entity
+ policy attachments. A policy attachment is a mechanism for associating
+ policy with one or more policy scopes, where a policy scope is a collection of
+ policy subjects to which a policy may apply. A policy subject is an entity
(e.g., an endpoint, message, resource, interaction) with which a
- <termref def="policy">policy</termref> can be associated. </termdef>
-
- Other specifications are
+ 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"/>]
@@ -347,26 +337,26 @@
<p>The descriptions below use XML Infoset terminology for convenience of description. However, this abstract model itself is independent of how it is represented as an XML Infoset. </p>
<div2 id="rPolicy_Assertion">
<head>Policy Assertion</head>
-
- <p>A <termref def='policy_assertion'>policy
+
+
+ <p><termdef id='policy_assertion' term='policy assertion'>A <term>policy assertion</term>
+ represents an individual requirement, capability, or other property of a behavior.</termdef> A <termref def='policy_assertion'>policy
assertion</termref> identifies a behavior that is a
requirement or capability of a <termref def='policy_subject'>policy
- subject</termref>. Assertions indicate domain-specific (e.g.,
+ subject</termref>. Assertions indicate domain-specific (e.g.,
security, transactions) semantics and are expected to be
defined in separate, domain-specific specifications.</p>
<p>Assertions are typed by the authors
- that define them. The <termref
+ that define them. <termdef id='policy_assertion_type' term='policy assertion type'>A <term>policy assertion type</term>
+ represents a class of <termref def='policy_assertion'>policy assertions</termref> and implies a
+ schema for the assertion and assertion-specific semantics.</termdef> The <termref
def='policy_assertion_type'>policy assertion
type</termref> is identified only by the XML Infoset <emph
role="infoset-property">namespace name</emph> and <emph
role="infoset-property">local name</emph> properties (that
is, the qualified name or QName) of the root Element
- Information Item representing the assertion.
- <termdef id='policy_assertion_type' term='policy assertion type'>A <term>policy assertion type</term>
- represents a class of <termref def='policy_assertion'>policy assertions</termref> and implies a
- schema for the assertion and assertion-specific semantics.</termdef>
- Assertions of
+ Information Item representing the assertion. Assertions of
a given type <rfc2119>MUST</rfc2119> be consistently
interpreted independent of their <termref
def='policy_subject'>policy subjects</termref>.</p>
@@ -406,22 +396,19 @@
</div2>
<div2 id="rPolicy_Alternative">
<head>Policy Alternative</head>
-
- <p>A <termref def='policy_alternative'>policy
- alternative</termref> is a logical construct which
- represents a potentially empty collection of <termref
- def='policy_assertion'>policy assertions</termref>. An
+
+
+ <p><termdef id='policy_alternative' term='policy alternative'>A <term>policy alternative</term>
+ is a potentially empty collection of <termref def='policy_assertion'>policy assertions</termref>.</termdef> An
alternative with zero assertions indicates no
behaviors. An alternative with one or more assertions
indicates behaviors implied by those, and only those
- assertions. </p>
-
- <p> <termdef id='policy_vocabulary' term='policy vocabulary'>A <term>policy vocabulary</term> is the set of all
+ assertions. <termdef id='policy_vocabulary' term='policy vocabulary'>A <term>policy vocabulary</term> is the set of all
<termref def='policy_assertion_type'>policy assertion types</termref> used in a policy.</termdef>
<termdef id="policy_alternative_vocabulary" term="policy alternative vocabulary">A <term>policy alternative vocabulary</term> is the set of
all <termref def='policy_assertion_type'>policy assertion
types</termref> within the <termref def='policy_alternative'>policy
- alternative</termref></termdef>.
+ alternative</termref>.</termdef>
When an assertion whose type is part of the policy's vocabulary is not included
in a policy alternative, the policy alternative without the assertion type
indicates that the assertion will not be applied in the context of the attached
@@ -444,10 +431,8 @@
<div2 id="rPolicy">
<head>Policy</head>
- <p>A <termref
- def='policy'>policy</termref> is a potentially empty
- collection of <termref def='policy_alternative'>policy
- alternatives</termref>. A policy with zero alternatives
+ <p><termdef id='policy' term='policy'>A <term>policy</term> is a potentially empty collection of
+ <termref def='policy_alternative'>policy alternatives</termref>. </termdef> A policy with zero alternatives
contains no choices; a policy with one or more
alternatives indicates choice in requirements or
capabilities within the policy. </p>
@@ -470,7 +455,9 @@
<p>Applied in the Web services based system, <termref
def='policy'>policy</termref> is used to convey conditions
on an interaction between entities (requester application,
- provider service, Web infrastructure component, etc). Any entity in a
+ provider service, Web infrastructure component, etc). <termdef id="policy_subject" term="policy subject">A <term>policy subject</term> is an entity
+ (e.g., an endpoint, message, resource, interaction) with which a
+ <termref def="policy">policy</termref> can be associated. </termdef> Any entity in a
Web services based system may expose a policy to convey conditions under
which it functions. Satisfying assertions in the policy usually results
in behavior that reflects these conditions. For example, if two entities
@@ -513,9 +500,9 @@
<div1 id="rPolicy_Expression">
<head>Policy Expression</head>
<p>This section describes how to convey policy in an interoperable form,
- using the XML Infoset representation of a policy. This XML Infoset representation
- of a policy is known as a <termref def='policy_expression'>policy
- expression</termref>. Other subsections below describe
+ using the XML Infoset representation of a policy. <termdef id='policy_expression' term='policy expression'>A <term>policy expression</term>
+ is an XML Infoset representation of a <termref def='policy'>policy</termref>,
+ either in a normal form or in an equivalent compact form.</termdef> Other subsections below describe
several important aspects related to policy expression, namely
(i) Normal form of a policy expression (ii) Compact form of a policy expression
(iii) Identification of policy expressions and (iv) Policy intersection.
@@ -637,7 +624,12 @@
used to refer to a policy from other XML documents using a <termref
def='policy_attachment'>policy attachment</termref> mechanism such as
those defined in WS-PolicyAttachment [<bibref
-ref="WS-PolicyAttachment"/>]. </p></def>
+ref="WS-PolicyAttachment"/>]. <termdef id="policy_attachment" term="policy attachment">A
+ <term>policy attachment</term> is a mechanism for associating
+ <termref def="policy">policy</termref> with one or more <termref def="policy_scope">policy scopes</termref>.</termdef>
+ <termdef id="policy_scope" term="policy scope">A <term>policy scope</term> is a collection of
+ <termref def="policy_subject">policy subjects</termref> to which a policy may apply.</termdef>
+ </p></def>
</gitem>
<gitem>
<label><att>/wsp:Policy/(@wsu:Id | @xml:id)</att></label>
@@ -2047,6 +2039,14 @@
<td>Updated "Changes in this Version" section (Appendix C)
</td>
</tr>
+ <tr>
+ <td>20061012</td>
+ <td>DBO</td>
+ <td>Revisited action items: <loc href="http://www.w3.org/2006/07/12-ws-policy-minutes.html#action15">15</loc>
+ as early as possible in the doc, use the definition that are defined in the doc. Opened as Bug
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3720">3720</loc>
+ </td>
+ </tr>
</tbody>
</table>
</inform-div1>
Received on Thursday, 12 October 2006 23:08:02 UTC