- From: David Orchard via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 08 Aug 2006 23:05:13 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv11452
Modified Files:
ws-policy-framework.xml ws-policy-framework.html
Log Message:
Action item 15, as early as possible in the doc, use the definition that are defined in the doc. http://www.w3.org/2006/07/12-ws-policy-minutes.html#action15
Index: ws-policy-framework.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-framework.xml,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -d -r1.17 -r1.18
--- ws-policy-framework.xml 8 Aug 2006 22:44:28 -0000 1.17
+++ ws-policy-framework.xml 8 Aug 2006 23:05:10 -0000 1.18
@@ -83,9 +83,13 @@
model for the expression of these properties as
policies.</p>
- <p>&framework.title; defines a policy to be a collection of policy
- alternatives, where each policy alternative is a
- collection of policy assertions. Some policy assertions
+ <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>
+ Some policy assertions
specify traditional requirements and capabilities that
will ultimately manifest on the wire (e.g., authentication
scheme, transport protocol selection). Other policy
@@ -95,8 +99,18 @@
language to allow both kinds of assertions to be reasoned
about in a consistent manner.</p>
- <p>&framework.title; does not specify how policies are discovered
- or attached to a Web service. Other specifications are
+<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
+ (e.g., an endpoint, message, resource, interaction) with which a
+ <termref def="policy">policy</termref> can be associated. </termdef>
+
+ Other specifications are
free to define technology-specific mechanisms for
associating policy with various entities and
resources. &attachment.title; [<bibref ref="WS-PolicyAttachment"/>]
@@ -147,9 +161,13 @@
<ulist>
<item>
- <p>An XML Infoset called a <emph>policy
- expression</emph> that contains domain-specific, Web
- Service policy information.</p></item>
+ <p>
+ An XML Infoset called a <termref def="policy_expression">policy
+ expression</termref> that contains domain-specific, Web
+ Service policy information. <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></p></item>
+
<item><p>A core set of constructs to indicate how
choices and/or combinations of domain-specific policy
assertions apply in a Web services
@@ -326,16 +344,7 @@
</p>
<p>We introduce the following terms that are used throughout this document:</p>
-<p><termdef id='policy' term='policy'>A <term>policy</term> is a collection of <termref def='policy_alternative'>policy alternatives</termref>.</termdef></p>
-<p><termdef id='policy_alternative' term='policy alternative'>A <term>policy alternative</term> is a collection of <termref def='policy_assertion'>policy assertions</termref>.</termdef></p>
-<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></p>
-<p><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></p>
-<p><termdef id='policy_assertion_parameter' term='policy assertion parameter'>A <term>policy assertion parameter</term> qualifies the behavior indicated by a <termref def='policy_assertion'>policy assertion</termref>.</termdef></p>
-<p><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></p>
-<p><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></p>
-<p><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></p>
-<p><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>
-<p><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></p>
+<p>EdNote: script will insert termdefs here</p>
</div2>
</div1>
<div1 id="Policy_Model">
@@ -360,7 +369,11 @@
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. Assertions of
+ 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
a given type <rfc2119>MUST</rfc2119> be consistently
interpreted independent of their <termref
def='policy_subject'>policy subjects</termref>.</p>
@@ -376,11 +389,14 @@
algorithms to qualify the specific behavior of a security
binding assertion. </p>
- <p>The XML Infoset of an assertion <rfc2119>MAY</rfc2119> contain a non-empty <emph
+ <p>The XML Infoset of a <termref def="policy_assertion">policy assertion</termref> <rfc2119>MAY</rfc2119> contain a non-empty <emph
role="infoset-property">attributes</emph> property and/or a non-empty <emph
role="infoset-property">children</emph>
property. Such content <rfc2119>MAY</rfc2119> be used to parameterize the
- behavior indicated by the assertion. For example, an
+ behavior indicated by the assertion.
+ <termdef id='policy_assertion_parameter' term='policy assertion parameter'>A <term>policy assertion parameter</term>
+ qualifies the behavior indicated by a <termref def='policy_assertion'>policy assertion</termref>.</termdef>
+ For example, an
assertion identifying support for a specific reliable
messaging mechanism might include an attribute information
item to indicate how long an endpoint will wait before
@@ -409,9 +425,10 @@
<p>The vocabulary of a policy alternative is the set of
all <termref def='policy_assertion_type'>policy assertion
- types</termref> within the alternative. The <termref def='policy_vocabulary'>vocabulary of
- a policy</termref> is the set of all assertion types used in all the
- policy alternatives in the policy. An assertion whose type
+ types</termref> within the alternative.
+ <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>
+ An assertion whose type
is part of the policy's vocabulary but is not included in
an alternative is explicitly prohibited by the
alternative.</p>
@@ -1448,7 +1465,7 @@
<th rowspan="1" colspan="1">Author</th>
<th rowspan="1" colspan="1">Description</th>
</tr>
- <!-- template do not use, script has been developed
+ <!-- template
<tr>
<td>200505</td>
<td></td>
@@ -1479,6 +1496,13 @@
namespace URI versioning policy</loc> adopted by the WG.
</td>
</tr>
+ <tr>
+ <td>20060808</td>
+ <td>DBO</td>
+ <td>Completed 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.
+ </td>
+ </tr>
</tbody>
</table>
</inform-div1>
Index: ws-policy-framework.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-framework.html,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -d -r1.14 -r1.15
--- ws-policy-framework.html 28 Jul 2006 06:34:26 -0000 1.14
+++ ws-policy-framework.html 8 Aug 2006 23:05:10 -0000 1.15
@@ -1,6 +1,5 @@
-<!DOCTYPE html
- PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en-US"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Web Services Policy 1.5 - Framework</title><style type="text/css">
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
+<html lang="en-US"><head><META http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Web Services Policy 1.5 - Framework</title><style type="text/css">
code { font-family: monospace; }
div.constraint,
@@ -48,29 +47,52 @@
div.exampleWrapper { margin: 4px }
div.exampleHeader { font-weight: bold;
[...1487 lines suppressed...]
+ <td rowspan="1" colspan="1">Incorporated the
<a href="http://lists.w3.org/Archives/Public/public-ws-policy/2006Jul/0107.html">XML
namespace URI versioning policy</a> adopted by the WG.
- </td></tr></tbody></table><br></div></div></body></html>
\ No newline at end of file
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">20060808</td>
+ <td rowspan="1" colspan="1">DBO</td>
+ <td rowspan="1" colspan="1">Completed action items: <a href="http://www.w3.org/2006/07/12-ws-policy-minutes.html#action15">15</a>
+ as early as possible in the doc, use the definition that are defined in the doc.
+ </td>
+ </tr>
+ </tbody>
+ </table><br>
+ </div>
+ </div>
+</body></html>
\ No newline at end of file
Received on Tuesday, 8 August 2006 23:05:24 UTC