- From: Asir Vedamuthu via cvs-syncmail <cvsmail@w3.org>
- Date: Sun, 20 May 2007 17:58:16 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy In directory hutz:/tmp/cvs-serv10328 Modified Files: ws-policy-guidelines.html ws-policy-guidelines.xml Log Message: Added an ed note in Section 5.1 Assertions and Their Target Use that there is an open issue against Good Practice G2. Index: ws-policy-guidelines.html =================================================================== RCS file: /sources/public/2006/ws/policy/ws-policy-guidelines.html,v retrieving revision 1.60 retrieving revision 1.61 diff -u -d -r1.60 -r1.61 --- ws-policy-guidelines.html 20 May 2007 17:34:21 -0000 1.60 +++ ws-policy-guidelines.html 20 May 2007 17:58:14 -0000 1.61 @@ -139,9 +139,9 @@ 5.5.1 <a href="#doc-ignorable-assertions">Assertions and Ignorable Behavior</a><br> 5.5.2 <a href="#XML-ignorable-assertions">XML Outline for Ignorable </a><br> 5.6 <a href="#optional-policy-assertion">Designating Optional Behaviors</a><br> - 5.6.1 <a href="#d3e757">Optional behavior in Compact authoring</a><br> - 5.6.2 <a href="#d3e797">Optional behavior at runtime</a><br> - 5.6.2.1 <a href="#d3e842">Example</a><br> + 5.6.1 <a href="#d3e766">Optional behavior in Compact authoring</a><br> + 5.6.2 <a href="#d3e806">Optional behavior at runtime</a><br> + 5.6.2.1 <a href="#d3e851">Example</a><br> 5.7 <a href="#levels-of-abstraction">Considerations for Policy Attachment in WSDL </a><br> 5.8 <a href="#interrelated-domains">Interrelated domains</a><br> 6. <a href="#versioning-policy-assertions">Versioning Policy Assertions</a><br> @@ -419,7 +419,14 @@ practice 2: Semantics Independent of Attachment Mechanisms</span></p><p class="practice"> The semantics of a policy assertion should not depend on the - attachment mechanism used.</p></div></div><div class="div2"> + attachment mechanism used.</p></div><table border="1" summary="Editorial note"><tr><td align="left" valign="top" width="50%"><b>Editorial note</b></td><td align="right" valign="top" width="50%"> </td></tr><tr><td colspan="2" align="left" valign="top">April 25th 07, editors + <a href="http://www.w3.org/2007/04/25-ws-policy-eds-minutes.html#item03">decided</a> to add G2 - + "An assertion author should define + policy assertions for behaviors that are relevant to compatibility tests, + such as web service protocols that manifest on the wire." - to Section 5.1. + May 9th 07, an issue was opened against G2 - issue + <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4566">4566</a>. + </td></tr></table></div><div class="div2"> <h3><a name="compact-full" id="compact-full"></a>5.2 Authoring Styles </h3><p>WS-Policy supports two different authoring styles, compact form and normal form. A compact form is one in which an expression consists of three constructs: an attribute to decorate an assertion (to indicate @@ -817,7 +824,7 @@ to indicate ignorable behavior. </p></div></div></div><div class="div2"> <h3><a name="optional-policy-assertion" id="optional-policy-assertion"></a>5.6 Designating Optional Behaviors</h3><div class="div3"> -<h4><a name="d3e757" id="d3e757"></a>5.6.1 Optional behavior in Compact authoring</h4><p>Optional behaviors represent behaviors that may be engaged by a consumer. When using the +<h4><a name="d3e766" id="d3e766"></a>5.6.1 Optional behavior in Compact authoring</h4><p>Optional behaviors represent behaviors that may be engaged by a consumer. When using the compact authoring form for assertions, such behaviors are marked by using <code>wsp:Optional</code> attribute with a value of "true". (In order to simplify reference to such assertions, @@ -848,7 +855,7 @@ it has an Endpoint Policy Subject and must be attached to a wsdl:binding or wsdl:port. The assertion may be optional when attached to these subjects, allowing use of wsp:Optional. </pre></div></div></div><div class="div3"> -<h4><a name="d3e797" id="d3e797"></a>5.6.2 Optional behavior at runtime</h4><p>Since optional behaviors indicate optionality for +<h4><a name="d3e806" id="d3e806"></a>5.6.2 Optional behavior at runtime</h4><p>Since optional behaviors indicate optionality for both the provider and the consumer, behaviors that must always be engaged by a consumer must not be marked as "optional" with a value "true" since this would allow the @@ -903,7 +910,7 @@ </p><div class="boxedtext"><p><a name="bp-indicate-optional-assertion-use" id="bp-indicate-optional-assertion-use"></a><span class="practicelab">Good practice 20: Indicate use of an Optional Assertion</span></p><p class="practice">When a given behavior may be optional, it must be possible for both message participants to determine that the assertion is selected by both parties, either out of band or as reflected by the message content.</p></div><div class="div4"> -<h5><a name="d3e842" id="d3e842"></a>5.6.2.1 Example</h5><p> +<h5><a name="d3e851" id="d3e851"></a>5.6.2.1 Example</h5><p> The <cite><a href="#WS-Policy-Primer">Web Services Policy Primer</a></cite> document contains an example that outlines the use of <cite><a href="#MTOM">MTOM</a></cite> as an optional behavior that can be engaged by a consumer. @@ -1670,4 +1677,6 @@ </td></tr><tr><td rowspan="1" colspan="1">20070520</td><td rowspan="1" colspan="1">ASV</td><td rowspan="1" colspan="1">Added an ed note that Section <a href="#Ignorable"><b>5.5 Designating Ignorable Behavior</b></a> looks incomplete. </td></tr><tr><td rowspan="1" colspan="1">20070520</td><td rowspan="1" colspan="1">ASV</td><td rowspan="1" colspan="1">Fixed typos. + </td></tr><tr><td rowspan="1" colspan="1">20070520</td><td rowspan="1" colspan="1">ASV</td><td rowspan="1" colspan="1">Added an ed note in Section <a href="#assertion-target"><b>5.1 Assertions and Their Target Use</b></a> that + there is an open issue against Good Practice G2. </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.75 retrieving revision 1.76 diff -u -d -r1.75 -r1.76 --- ws-policy-guidelines.xml 20 May 2007 17:34:21 -0000 1.75 +++ ws-policy-guidelines.xml 20 May 2007 17:58:14 -0000 1.76 @@ -481,6 +481,17 @@ The semantics of a policy assertion should not depend on the attachment mechanism used.</quote> </p> + + <ednote> + <edtext>April 25th 07, editors + <loc href="http://www.w3.org/2007/04/25-ws-policy-eds-minutes.html#item03">decided</loc> to add G2 - + "An assertion author should define + policy assertions for behaviors that are relevant to compatibility tests, + such as web service protocols that manifest on the wire." - to Section 5.1. + May 9th 07, an issue was opened against G2 - issue + <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4566">4566</loc>. + </edtext> + </ednote> </div2> <div2 id="compact-full"> @@ -2543,6 +2554,13 @@ <td>ASV</td> <td>Fixed typos. </td> + </tr> + <tr> + <td>20070520</td> + <td>ASV</td> + <td>Added an ed note in Section <specref ref="assertion-target"/> that + there is an open issue against Good Practice G2. + </td> </tr> </tbody> </table>
Received on Sunday, 20 May 2007 17:58:19 UTC