- From: David Orchard via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 12 Sep 2006 19:11:00 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv15076
Modified Files:
ws-policy-framework.xml ws-policy-framework.html
Log Message:
Ed action item http://www.w3.org/2005/06/tracker/wspolicyeds/actions/6
Index: ws-policy-framework.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-framework.xml,v
retrieving revision 1.36
retrieving revision 1.37
diff -u -d -r1.36 -r1.37
--- ws-policy-framework.xml 10 Sep 2006 19:17:20 -0000 1.36
+++ ws-policy-framework.xml 12 Sep 2006 19:10:57 -0000 1.37
@@ -344,12 +344,12 @@
<p>A <termref def='policy_assertion'>policy
assertion</termref> identifies a behavior that is a
- requirement (or capability) of a <termref def='policy_subject'>policy
+ requirement or capability of a <termref def='policy_subject'>policy
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 strongly typed by the domain authors
+ <p>Assertions are typed by the domain authors
that define them. The <termref
def='policy_assertion_type'>policy assertion
type</termref> is identified only by the XML Infoset <emph
@@ -368,8 +368,7 @@
<p>Domain authors <rfc2119>MAY</rfc2119> define that an assertion contains a
<termref def='policy_expression'>policy
expression</termref> as one of its <emph
- role="infoset-property">children</emph>. Policy
- expression nesting is used by domain authors to further
+ role="infoset-property">children</emph>. <termref def="nested_policy_expression">Nested policy expression(s)</termref> are used by domain authors to further
qualify one or more specific aspects of the original
assertion. For example, security policy domain authors may
define an assertion describing a set of security
@@ -391,8 +390,8 @@
<p>Domain authors should be cognizant of the processing
requirements when defining complex assertions containing
- additional assertion content or nested policy
- expressions. Specifically, domain authors are encouraged
+ <termref def="policy_assertion_parameter">policy assertion parameters</termref> or <termref def="nested_policy_expression">nested policy
+ expressions</termref>. Specifically, domain authors are encouraged
to consider when the identity of the root Element
Information Item alone is enough to convey the requirement
or capability.</p>
@@ -569,8 +568,8 @@
</glist>
<p>If an <termref def='policy_assertion'>assertion</termref> in the
-normal form of a policy expression contains a nested policy
-expression, the nested policy expression <rfc2119>MUST</rfc2119>
+normal form of a policy expression contains a <termref def="nested_policy_expression">nested policy
+expression</termref>, the nested policy expression <rfc2119>MUST</rfc2119>
contain at most one policy alternative.</p>
<p>To simplify processing and improve interoperability, the normal
@@ -760,9 +759,9 @@
<head>Policy Assertion Nesting</head>
<p>Any <termref def='policy_assertion'>policy assertion</termref>
-<rfc2119>MAY</rfc2119> contain a nested <termref
-def='policy_expression'>policy expression</termref>. The schema
-outline for a nested policy expression is:</p>
+<rfc2119>MAY</rfc2119> contain a <termref
+def='policy_expression'>policy expression</termref>. <termdef id="nested_policy_expression" term="nested policy expression">A <term>nested policy expression</term> is a <termref def='policy_assertion'>policy assertion</termref> that is a descendent of a <termref def='policy_assertion'>policy assertion</termref>.</termdef> The schema
+outline for a <termref def="nested_policy_expression">nested policy expression</termref> is:</p>
<eg xml:space="preserve"><<emph>Assertion</emph> …>
…
@@ -1673,7 +1672,7 @@
</td>
</tr>
<tr>
- <td>200609006</td>
+ <td>20060906</td>
<td>DBO</td>
<td>Completed partial resolution for issue
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3590">3590</loc>.
@@ -1691,7 +1690,13 @@
Better describe policy language capabilities in the Introduction.
</td>
</tr>
-
+ <tr>
+ <td>20060912</td>
+ <td>DBO</td>
+ <td>Completed action item:
+ <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/6">6</loc>.
+ </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.31
retrieving revision 1.32
diff -u -d -r1.31 -r1.32
--- ws-policy-framework.html 10 Sep 2006 19:17:20 -0000 1.31
+++ ws-policy-framework.html 12 Sep 2006 19:10:57 -0000 1.32
@@ -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,24 +47,43 @@
div.exampleWrapper { margin: 4px }
div.exampleHeader { font-weight: bold;
[...1697 lines suppressed...]
for issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3607">3607</a>.
Better describe policy language capabilities in the Introduction.
- </td></tr></tbody></table><br></div></div></body></html>
\ No newline at end of file
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">20060912</td>
+ <td rowspan="1" colspan="1">DBO</td>
+ <td rowspan="1" colspan="1">Completed action item:
+ <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/6">6</a>.
+ </td>
+ </tr>
+ </tbody>
+ </table><br>
+ </div>
+ </div>
+</body></html>
\ No newline at end of file
Received on Tuesday, 12 September 2006 19:11:11 UTC