- From: Asir Vedamuthu via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 06 Mar 2007 19:13:44 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv3605
Modified Files:
ws-policy-guidelines.html ws-policy-guidelines.xml
Log Message:
Implemented partial resolution for issue 3987. Related editorial action is 153.
Index: ws-policy-guidelines.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-guidelines.html,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -d -r1.28 -r1.29
--- ws-policy-guidelines.html 21 Feb 2007 22:55:54 -0000 1.28
+++ ws-policy-guidelines.html 6 Mar 2007 19:13:41 -0000 1.29
@@ -89,12 +89,12 @@
4.4.2 <a href="#nested-assertions">Nested Assertions</a><br>
4.4.3 <a href="#which-one-to-use">Considerations for choosing parameters vs nesting</a><br>
4.5 <a href="#optional-policy-assertion">Designating Optional Behaviors</a><br>
- 4.5.1 <a href="#d3e510">Optional behavior in Compact authoring</a><br>
- 4.5.2 <a href="#d3e518">Optional behavior at runtime</a><br>
+ 4.5.1 <a href="#d3e512">Optional behavior in Compact authoring</a><br>
+ 4.5.2 <a href="#d3e520">Optional behavior at runtime</a><br>
4.6 <a href="#typing-assertions">Typing Assertions</a><br>
4.7 <a href="#levels-of-abstraction">Levels of Abstraction in WSDL </a><br>
4.8 <a href="#interrelated-domains">Interrelated domains</a><br>
-5. <a href="#lifecycle">Lifecycle of Assertions</a><br>
+5. <a href="#versioning-policy-assertions">Versioning Policy Assertions</a><br>
5.1 <a href="#Referencing_Policy_Expressions">Referencing Policy Expressions</a><br>
5.2 <a href="#extending-assertions"> Evolution of Assertions (Versioning and Compatibility)</a><br>
6. <a href="#best-practices-attachment">Applying Best Practices for Policy Attachment</a><br>
@@ -307,7 +307,7 @@
to evolve their services capabilities over time. If
forward compatibility is a concern in order to accommodate
compatibility with different and potentially new clients,
- providers should refer to <a href="#lifecycle"><b>5. Lifecycle of Assertions</b></a> and
+ providers should refer to and
<cite><a href="#WS-Policy-Primer">Web Services Policy Primer</a></cite> that describes service and
policy assertion evolution.
</p></div></div></div><div class="div1">
@@ -332,10 +332,7 @@
to combine individual assertions may also need to be considered.
</p><p>The number of different subjects to which an assertion
can be attached is also a factor when defining an
- assertion. Determining the appropriate policy subjects can sometimes
- involve understanding the requirements of wide range of client configurations, from
- stand alone client applications to "active" web service
- requesters that are capable of modifying their own configurations dynamically.
+ assertion. For attaching to WSDL subjects see <a href="#levels-of-abstraction"><b>4.7 Levels of Abstraction in WSDL </b></a> for more detail.
</p><p> Once the range of policy subjects is identified, there are choices for ways of
attaching multiple instances of a simple policy
assertion to multiple subjects. One way is to utilize
@@ -679,7 +676,7 @@
to the WS-Policy framework.
</p></div></div><div class="div2">
<h3><a name="optional-policy-assertion" id="optional-policy-assertion"></a>4.5 Designating Optional Behaviors</h3><div class="div3">
-<h4><a name="d3e510" id="d3e510"></a>4.5.1 Optional behavior in Compact authoring</h4><p>Optional behaviors represent behaviors which may be engaged by a consumer. When using the
+<h4><a name="d3e512" id="d3e512"></a>4.5.1 Optional behavior in Compact authoring</h4><p>Optional behaviors represent behaviors which may be engaged by a consumer. When using the
compact authoring form for assertions, behaviors are marked by
using <code>wsp:Optional</code> attribute that has a value,
"true". During the process of normalization, the runtime
@@ -690,7 +687,7 @@
runtime behavior. In order to simplify reference to such
assertions, we just use the term optional assertions in this section.
</p></div><div class="div3">
-<h4><a name="d3e518" id="d3e518"></a>4.5.2 Optional behavior at runtime</h4><p>The <cite><a href="#WS-Policy-Primer">Web Services Policy Primer</a></cite> document contains an
+<h4><a name="d3e520" id="d3e520"></a>4.5.2 Optional behavior at runtime</h4><p>The <cite><a href="#WS-Policy-Primer">Web Services Policy Primer</a></cite> document contains an
example that proposes the use of <cite><a href="#MTOM">MTOM</a></cite> as an
optional behavior that can be engaged by a consumer. The
primer proposes that an assertion that identifies the use of
@@ -773,7 +770,8 @@
aware of the possible evolution of their assertions and how
this would impact the semantics of the assertion overtime. A namespace
associated with the assertion may be used to indicate a
- specific version of an assertion but this has its limitations. See Lifecycle material <a href="#lifecycle"><b>5. Lifecycle of Assertions</b></a> for more detail.
+ specific version of an assertion but this has its limitations.
+ See section <a href="#versioning-policy-assertions"><b>5. Versioning Policy Assertions</b></a> for more detail.
</p><p>The typing must be done in combination with the scoping
of the semantics to a policy subject. WS-PolicyAttachment provides a means of associating an
assertion with arbitrary subjects, regardless of their
@@ -888,8 +886,8 @@
assertions and should also make sure that when adding assertions those new assertions are consistent
with pre-existing assertions of any
interrelated domain. </p></div></div><div class="div1">
-<h2><a name="lifecycle" id="lifecycle"></a>5. Lifecycle of Assertions</h2><p>Assertion Authors need to consider not just the expression of the current set of requirements but
- how they anticipate new assertions being added to the set. There are three aspects that govern an assertions lifecycle:</p><ul><li><p> Assertion Extensibility </p></li><li><p> Policy Language Extensibility </p><p>Over time, the Policy WG or third parties can version or extend the Policy Language with new
+<h2><a name="versioning-policy-assertions" id="versioning-policy-assertions"></a>5. Versioning Policy Assertions</h2><p>Assertion Authors need to consider not just the expression of the current set of requirements but
+ how they anticipate new assertions being added to the set. There are three aspects to versioning policy assetions:</p><ul><li><p> Assertion Extensibility </p></li><li><p> Policy Language Extensibility </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.
</p><p> Assertion Authors should review the WS-Policy Primer <cite><a href="#WS-Policy-Primer">Web Services Policy Primer</a></cite>
and the specifications <cite><a href="#WS-Policy">Web Services Policy Framework</a></cite> <cite><a href="#WS-PolicyAttachment">Web Services Policy Attachment</a></cite>
@@ -1343,4 +1341,14 @@
as noted in message
<a href="http://lists.w3.org/Archives/Public/public-ws-policy/2007Jan/0217.html">217</a>.
Changes correspond to editor's action
- <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/152">152</a>.</td></tr></tbody></table><br></div></div></body></html>
\ No newline at end of file
+ <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/152">152</a>.</td></tr><tr><td rowspan="1" colspan="1">20070221</td><td rowspan="1" colspan="1">MH</td><td rowspan="1" colspan="1"> Partial implementation for issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4072">4072</a>
+ in response to editor's action
+ <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/154">154 </a>.
+ NOTE ALSO- I needed to put back in the "prefix" entity defintion [line7] to get the build to work.
+ </td></tr><tr><td rowspan="1" colspan="1">20070306</td><td rowspan="1" colspan="1">ASV</td><td rowspan="1" colspan="1"> Implemented partial
+ <a href="http://www.w3.org/2007/01/31-ws-policy-minutes.html#item10">resolution</a> for issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3987">3987</a>.
+ Related editorial action is
+ <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/153">153</a>.
+ </td></tr></tbody></table><br></div></div></body></html>
\ No newline at end of file
Index: ws-policy-guidelines.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-guidelines.xml,v
retrieving revision 1.37
retrieving revision 1.38
diff -u -d -r1.37 -r1.38
--- ws-policy-guidelines.xml 22 Feb 2007 17:25:28 -0000 1.37
+++ ws-policy-guidelines.xml 6 Mar 2007 19:13:42 -0000 1.38
@@ -1017,7 +1017,8 @@
aware of the possible evolution of their assertions and how
this would impact the semantics of the assertion overtime. A namespace
associated with the assertion may be used to indicate a
- specific version of an assertion but this has its limitations. See Lifecycle material <specref ref="lifecycle"/> for more detail.
+ specific version of an assertion but this has its limitations.
+ See section <specref ref="versioning-policy-assertions"/> for more detail.
</p>
<p>The typing must be done in combination with the scoping
of the semantics to a policy subject. WS-PolicyAttachment provides a means of associating an
@@ -1189,10 +1190,10 @@
interrelated domain. </p>
</div2>
</div1>
- <div1 id="lifecycle">
- <head>Lifecycle of Assertions</head>
+ <div1 id="versioning-policy-assertions">
+ <head>Versioning Policy Assertions</head>
<p>Assertion Authors need to consider not just the expression of the current set of requirements but
- how they anticipate new assertions being added to the set. There are three aspects that govern an assertions lifecycle:</p>
+ how they anticipate new assertions being added to the set. There are three aspects to versioning policy assetions:</p>
<ulist>
<item>
<p> Assertion Extensibility </p>
@@ -1989,7 +1990,17 @@
<loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/154">154 </loc>.
NOTE ALSO- I needed to put back in the "prefix" entity defintion [line7] to get the build to work.
</td>
- </tr>
+ </tr>
+ <tr>
+ <td>20070306</td>
+ <td>ASV</td>
+ <td> Implemented partial
+ <loc href="http://www.w3.org/2007/01/31-ws-policy-minutes.html#item10">resolution</loc> for issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3987">3987</loc>.
+ Related editorial action is
+ <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/153">153</loc>.
+ </td>
+ </tr>
</tbody>
</table>
</inform-div1>
Received on Tuesday, 6 March 2007 19:14:18 UTC