- From: Asir Vedamuthu via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 23 Mar 2007 00:33:27 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv23506
Modified Files:
ws-policy-primer.html ws-policy-primer.xml
Log Message:
Deleted residual text in 4. Versioning Policy Language:
s/The possible extensibility points with their current extensibility - including some outstanding issues related to extensibility - are:/The possible extensibility points are:/
s/PolicyReference: any attribute and a proposal to add any element/PolicyReference: any attribute and any element/.
Index: ws-policy-primer.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-primer.html,v
retrieving revision 1.47
retrieving revision 1.48
diff -u -d -r1.47 -r1.48
--- ws-policy-primer.html 22 Mar 2007 05:42:14 -0000 1.47
+++ ws-policy-primer.html 23 Mar 2007 00:33:25 -0000 1.48
@@ -1131,7 +1131,7 @@
</td></tr></table>
</p><p>Over time, the Policy WG or third parties can version or extend the Policy Language with new or modified constructs. These constructs may be compatible or incompatible with previous versions. Some of the possible new constructs that have been mentioned previously are: new operators, operator cardinality, policy identification, compact syntax, Policy Inclusion, security, referencing, attachment points, alternative
priority, effective dating, negotiation. </p><p>WS-Policy provides extensibility points on 6 elements with a combination of attribute and/or element extensibility.
- The possible extensibility points with their current extensibility - including some outstanding issues related to extensibility - are:</p><ol class="enumar"><li><p>Policy: element from ##other namespace and any attribute</p></li><li><p>PolicyReference: any attribute and a proposal to add any element ExactlyOne, All: element from ##other namespace, no attribute extensibility</p></li><li><p>PolicyAttachment: element from ##other namespace and any attribute</p></li><li><p>AppliesTo: any element and any attribute</p></li></ol><div class="div2">
+ The possible extensibility points are:</p><ol class="enumar"><li><p>Policy: element from ##other namespace and any attribute</p></li><li><p>PolicyReference: any attribute and any element</p></li><li><p>ExactlyOne, All: element from ##other namespace, no attribute extensibility</p></li><li><p>PolicyAttachment: element from ##other namespace and any attribute</p></li><li><p>AppliesTo: any element and any attribute</p></li></ol><div class="div2">
<h3><a name="versioning-policy-framework" id="versioning-policy-framework"></a>4.1 Policy Framework</h3><p>WS-Policy Framework 1.5 specifies that any child element that is not known inside a Policy,
ExactlyOne or All will be treated as an assertion. The default value for wsp:Optional="false".
After normalization, such an element will be inside an ExactlyOne/All operator. </p><p>Let us show an example with a hypothetical new operator that is a Choice with a minOccurs and a maxOccurs attributes, ala XSD:Choice, in a new namespace. We use the wsp16 prefix to indicate a hypothetical Policy Language 1.6 that is intended to be compatible with Policy Language 1.5:</p><div class="exampleOuter">
@@ -1543,4 +1543,6 @@
for <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4300">issue 4300</a>.
Editors' action
<a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/190">190</a>.
- </td></tr><tr><td rowspan="1" colspan="1">20070321</td><td rowspan="1" colspan="1">ASV</td><td rowspan="1" colspan="1">Updated section <a href="#change-description"><b>E. Changes in this Version of the Document</b></a>. </td></tr><tr><td rowspan="1" colspan="1">20070321</td><td rowspan="1" colspan="1">ASV</td><td rowspan="1" colspan="1">Formatted the example in <a href="#ignorable-and-versioning"><b>3.8.1 Ignorable and Versioning</b></a>. </td></tr></tbody></table><br></div></div></body></html>
\ No newline at end of file
+ </td></tr><tr><td rowspan="1" colspan="1">20070321</td><td rowspan="1" colspan="1">ASV</td><td rowspan="1" colspan="1">Updated section <a href="#change-description"><b>E. Changes in this Version of the Document</b></a>. </td></tr><tr><td rowspan="1" colspan="1">20070321</td><td rowspan="1" colspan="1">ASV</td><td rowspan="1" colspan="1">Formatted the example in <a href="#ignorable-and-versioning"><b>3.8.1 Ignorable and Versioning</b></a>. </td></tr><tr><td rowspan="1" colspan="1">20070322</td><td rowspan="1" colspan="1">ASV</td><td rowspan="1" colspan="1"><p>Deleted residual text in <a href="#versioning-policy-language"><b>4. Versioning Policy Language</b></a>:</p>
+ <p>s/The possible extensibility points with their current extensibility - including some outstanding issues related to extensibility - are:/The possible extensibility points are:/</p>
+ <p>s/PolicyReference: any attribute and a proposal to add any element/PolicyReference: any attribute and any element/.</p></td></tr></tbody></table><br></div></div></body></html>
\ No newline at end of file
Index: ws-policy-primer.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-primer.xml,v
retrieving revision 1.46
retrieving revision 1.47
diff -u -d -r1.46 -r1.47
--- ws-policy-primer.xml 22 Mar 2007 07:11:39 -0000 1.46
+++ ws-policy-primer.xml 23 Mar 2007 00:33:25 -0000 1.47
@@ -1554,10 +1554,11 @@
<p>Over time, the Policy WG or third parties can version or extend the Policy Language with new or modified constructs. These constructs may be compatible or incompatible with previous versions. Some of the possible new constructs that have been mentioned previously are: new operators, operator cardinality, policy identification, compact syntax, Policy Inclusion, security, referencing, attachment points, alternative
priority, effective dating, negotiation. </p>
<p>WS-Policy provides extensibility points on 6 elements with a combination of attribute and/or element extensibility.
- The possible extensibility points with their current extensibility - including some outstanding issues related to extensibility - are:</p>
+ The possible extensibility points are:</p>
<olist>
<item><p>Policy: element from ##other namespace and any attribute</p></item>
- <item><p>PolicyReference: any attribute and a proposal to add any element ExactlyOne, All: element from ##other namespace, no attribute extensibility</p></item>
+ <item><p>PolicyReference: any attribute and any element</p></item>
+ <item><p>ExactlyOne, All: element from ##other namespace, no attribute extensibility</p></item>
<item><p>PolicyAttachment: element from ##other namespace and any attribute</p></item>
<item><p>AppliesTo: any element and any attribute</p></item>
</olist>
@@ -2367,7 +2368,14 @@
<td>20070321</td>
<td>ASV</td>
<td>Formatted the example in <specref ref="ignorable-and-versioning"/>. </td>
- </tr>
+ </tr>
+ <tr>
+ <td>20070322</td>
+ <td>ASV</td>
+ <td><p>Deleted residual text in <specref ref="versioning-policy-language"/>:</p>
+ <p>s/The possible extensibility points with their current extensibility - including some outstanding issues related to extensibility - are:/The possible extensibility points are:/</p>
+ <p>s/PolicyReference: any attribute and a proposal to add any element/PolicyReference: any attribute and any element/.</p></td>
+ </tr>
</tbody>
</table>
</inform-div1>
Received on Friday, 23 March 2007 00:33:29 UTC