- From: Philippe Le Hegaret via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 11 Jul 2006 19:20:40 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv20993/policy
Modified Files:
ws-policy-attachment.xml ws-policy-framework.xml
Log Message:
Id are case-insentives if the HTML is interpreted as HTML 4.01
Index: ws-policy-framework.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-framework.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- ws-policy-framework.xml 9 Jun 2006 16:46:28 -0000 1.2
+++ ws-policy-framework.xml 11 Jul 2006 19:20:38 -0000 1.3
@@ -302,7 +302,7 @@
<p>This section defines an abstract model for policies and for operations upon policies.</p>
<p>This abstract model is independent of how it is represented as an XML Infoset. </p>
- <div2 id="Policy_Assertion">
+ <div2 id="rPolicy_Assertion">
<head>Policy Assertion</head>
<p>A <termref def='policy_assertion'>policy
@@ -354,7 +354,7 @@
(capability).</p>
</div2>
- <div2 id="Policy_Alternative">
+ <div2 id="rPolicy_Alternative">
<head>Policy Alternative</head>
<p>A <termref def='policy_alternative'>policy
@@ -388,7 +388,7 @@
of this document.</p>
</div2>
- <div2 id="Policy">
+ <div2 id="rPolicy">
<head>Policy</head>
<p>At the abstract level a <termref
@@ -460,7 +460,7 @@
backward-compatible manner.</p>
</div2>
</div1>
- <div1 id="Policy_Expression">
+ <div1 id="rPolicy_Expression">
<head>Policy Expression</head>
<p>To convey policy in an interoperable form, a <termref def='policy_expression'>policy
@@ -865,7 +865,7 @@
<def>
<p>In line with the previous statements that policy assertions within
a policy alternative and policy alternatives within a policy are not
-ordered (see <specref ref="Policy_Alternative"/> and <specref ref="Policy"/>, respectively), <el>wsp:All</el> and
+ordered (see <specref ref="rPolicy_Alternative"/> and <specref ref="rPolicy"/>, respectively), <el>wsp:All</el> and
<el>wsp:ExactlyOne</el> are commutative. For example,</p>
<eg xml:space="preserve"><wsp:All> <emph><!-- assertion 1 --> <!-- assertion 2 --> </emph></wsp:All></eg>
@@ -1103,7 +1103,7 @@
<div2 id="Policy_Intersection">
<head>Policy Intersection</head>
<p>Policy intersection is useful when two or more parties express <termref def='policy'>policy</termref> and want to limit the <termref def='policy_alternative'>policy alternatives</termref> to those that are mutually compatible. For example, when a requester and a provider express requirements on a message exchange, intersection identifies compatible policy alternatives (if any) included in both requester and provider policies. Intersection is a commutative, associative function that takes two policies and returns a policy.</p>
-<p>Because the set of behaviors indicated by a <termref def='policy_alternative'>policy alternative</termref> depends on the domain-specific semantics of the collected assertions, determining whether two policy alternatives are compatible generally involves domain-specific processing. As a first approximation, an algorithm is defined herein that approximates compatibility in a domain-independent manner; specifically, for two policy alternatives to be compatible, they must at least have the same vocabulary (see Section <specref ref="Policy_Alternative"/>).</p>
+<p>Because the set of behaviors indicated by a <termref def='policy_alternative'>policy alternative</termref> depends on the domain-specific semantics of the collected assertions, determining whether two policy alternatives are compatible generally involves domain-specific processing. As a first approximation, an algorithm is defined herein that approximates compatibility in a domain-independent manner; specifically, for two policy alternatives to be compatible, they must at least have the same vocabulary (see Section <specref ref="rPolicy_Alternative"/>).</p>
<ulist>
<item><p>Two <termref def='policy_assertion'>policy assertions</termref> are compatible if they have the same <termref def='policy_assertion_type'>type</termref> and</p></item>
<item><p>If either assertion contains a nested <termref def='policy_expression'>policy expression</termref>, the two assertions are compatible if they both have a nested policy expression and the alternative in the nested policy expression of one is compatible with the alternative in the nested policy expression of the other.</p></item>
Index: ws-policy-attachment.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-attachment.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- ws-policy-attachment.xml 31 May 2006 17:20:37 -0000 1.1
+++ ws-policy-attachment.xml 11 Jul 2006 19:20:38 -0000 1.2
@@ -346,7 +346,7 @@
ref='Table3'/>, respectively.</p>
</div2>
</div1>
- <div1 id='PolicyAttachment'>
+ <div1 id='rPolicyAttachment'>
<head>Policy Attachment</head>
<p>This section defines two general-purpose mechanisms for
@@ -360,7 +360,7 @@
<p>In addition it defines the processing rules for scenarios
where multiple policies are attached to a policy subject.</p>
- <div2 id='EffectivePolicy'>
+ <div2 id='rEffectivePolicy'>
<head>Effective Policy</head>
<p><termref def='policy'>Policies</termref> will often be
associated with a particular <termref
@@ -709,7 +709,7 @@
<item><p><el>wsdl11:service</el></p></item>
</ulist>
<p>This element <rfc2119>MAY</rfc2119> have <termref def='element_policy'>element policy</termref> as per
-Section <specref ref='PolicyAttachment'/>, and if present
+Section <specref ref='rPolicyAttachment'/>, and if present
<rfc2119>MUST</rfc2119> be merged into the <termref def='effective_policy'>effective policy</termref> of the
WSDL service policy subject.</p>
<p>Policy attached to the service
@@ -725,7 +725,7 @@
<item><p><el>wsdl11:port</el></p></item>
<item><p><el>wsdl11:portType</el></p></item>
<item><p><el>wsdl11:binding</el></p></item>
-</ulist><p>These elements <rfc2119>MAY</rfc2119> have <termref def='element_policy'>element policy</termref> as per Section <specref ref='PolicyAttachment'/>. The <termref def='policy_scope'>policy scope</termref> implied by each of these elements contains the endpoint policy subject representing the deployed endpoint.</p>
+</ulist><p>These elements <rfc2119>MAY</rfc2119> have <termref def='element_policy'>element policy</termref> as per Section <specref ref='rPolicyAttachment'/>. The <termref def='policy_scope'>policy scope</termref> implied by each of these elements contains the endpoint policy subject representing the deployed endpoint.</p>
<p>Since the <el>wsdl11:portType</el> may be used by more than one
binding, it is <rfc2119>RECOMMENDED</rfc2119> that only policies
@@ -749,7 +749,7 @@
<ulist>
<item><p><el>wsdl11:portType/wsdl11:operation</el></p></item>
<item><p><el>wsdl11:binding/wsdl11:operation</el></p></item>
-</ulist><p>These elements <rfc2119>MAY</rfc2119> have <termref def='element_policy'>element policy</termref> as per Section <specref ref='PolicyAttachment'/>. </p>
+</ulist><p>These elements <rfc2119>MAY</rfc2119> have <termref def='element_policy'>element policy</termref> as per Section <specref ref='rPolicyAttachment'/>. </p>
<p>The <termref def='policy_scope'>policy scope</termref> implied by each of these elements contains the
operation policy subject representing the specific operation of the
@@ -784,7 +784,7 @@
<item><p><el>wsdl11:binding/wsdl11:operation/wsdl11:output</el></p></item>
<item><p><el>wsdl11:binding/wsdl11:operation/wsdl11:fault</el></p></item>
</ulist>
-<p>These elements <rfc2119>MAY</rfc2119> have <termref def='element_policy'>element policy</termref> as per Section <specref ref='PolicyAttachment'/>.</p>
+<p>These elements <rfc2119>MAY</rfc2119> have <termref def='element_policy'>element policy</termref> as per Section <specref ref='rPolicyAttachment'/>.</p>
<p>The <termref def='policy_scope'>policy scope</termref> implied by these elements contains the message
policy subject representing the specific input, output, or fault
@@ -1007,7 +1007,7 @@
itself.</p>
<p>Each of these entities <rfc2119>MAY</rfc2119> have an <termref def='element_policy'>element
-policy</termref> per Section <specref ref='PolicyAttachment'/>. The remainder of
+policy</termref> per Section <specref ref='rPolicyAttachment'/>. The remainder of
this section defines how that <termref def='element_policy'>element policy</termref> is interpreted to
calculate the <termref def='effective_policy'>effective policy</termref>.</p>
@@ -1019,7 +1019,7 @@
</ulist>
<p>This element <rfc2119>MAY</rfc2119> have <termref def='element_policy'>element policy</termref> as per
-Section <specref ref='PolicyAttachment'/>, and if present
+Section <specref ref='rPolicyAttachment'/>, and if present
<rfc2119>MUST</rfc2119> be merged into the <termref def='effective_policy'>effective policy</termref> of the
UDDI businessEntity Subject.</p>
@@ -1038,7 +1038,7 @@
<p>This element <rfc2119>MAY</rfc2119> have <termref
def='element_policy'>element policy</termref> as per Section <specref
-ref='PolicyAttachment'/>, and if present <rfc2119>MUST</rfc2119> be
+ref='rPolicyAttachment'/>, and if present <rfc2119>MUST</rfc2119> be
merged into the <termref def='effective_policy'>effective
policy</termref> of the UDDI businessService Subject.</p>
@@ -1056,7 +1056,7 @@
</ulist>
<p>These elements <rfc2119>MAY</rfc2119> have <termref def='element_policy'>element policy</termref> as per
-Section <specref ref='PolicyAttachment'/>. The <termref def='policy_scope'>policy scope</termref> implied by
+Section <specref ref='rPolicyAttachment'/>. The <termref def='policy_scope'>policy scope</termref> implied by
each of these elements contains the endpoint policy subject
representing the deployed endpoint.</p>
Received on Tuesday, 11 July 2006 19:20:52 UTC