- From: Maryann Hondo via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 13 Jun 2007 19:16:22 +0000
- To: public-ws-policy-eds@w3.org
Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv10299
Modified Files:
ws-policy-guidelines.xml
Log Message:
edits to close AI 292, 293
Index: ws-policy-guidelines.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-guidelines.xml,v
retrieving revision 1.89
retrieving revision 1.90
diff -u -d -r1.89 -r1.90
--- ws-policy-guidelines.xml 1 Jun 2007 19:01:27 -0000 1.89
+++ ws-policy-guidelines.xml 13 Jun 2007 19:16:19 -0000 1.90
@@ -650,15 +650,41 @@
<p>Web Services Policy language allows Assertion Authors to invent
their own XML dialects to represent policy assertions. The policy language relies only
on the policy assertion XML element QName. This QName is unique and identifies the
- behavior represented by a policy assertion. Assertion Authors have the option to
+ behavior represented by a policy assertion. Assertion Authors have the option to
represent an assertion parameter as a child element (by leveraging natural XML nesting)
or an attribute of an assertion. The general guidelines on when to use XML elements
- versus attributes apply is. Use a unique QName to identify a distinct behavior and provide
- an XML outline (plus an XML schema document) to specify the syntax of an assertion. </p>
+ versus attributes apply is: Use a unique QName to identify a distinct behavior </p>
- <p role="practice" id="bp-unique-qnames"><quote>Use Unique QNames</quote>
- <quote>Assertion Authors should use a unique QName to identify a distinct behavior.</quote>
+ <p role="practice" id="bp-unique-qnames"><quote>Use Unique QNames</quote>
+ <quote>Assertion Authors should use a unique QName to identify a distinct behavior.</quote> </p>
+ <p> and provide
+ an XML outline (plus an XML schema document) to specify the syntax of an assertion. </p>
+ <p role="practice" id="XMLOutline"> <quote>Provide an XML Outline</quote> >
+ <quote> An assertion description should provide an XML outline plus an XML schema to specify the
+ syntax of the assertion.
+ </quote>
+ </p>
+ <p> An example of this method (below) is given in the Web Services Reliable Messaging Policy document. [<bibref ref="WS-RM-Policy"/>]
</p>
+ <example>
+ <eg>
+ <wsrmp:RMAssertion [wsp:Optional="true"]? ...>
+ <wsp:Policy >
+ [ <wsrmp:SequenceSTR/> |
+ <wsrmp:SequenceTransportSecurity/> ] ?
+ <wsrmp:DeliveryAssurance/>
+ <wsp:Policy >
+ [ <wsrmp:ExactlyOnce/> |
+ <wsrmp:AtLeastOnce/> |
+ <wsrmp:AtMostOnce/> ]
+ <wsrmp:InOrder/> ?
+ </wsp:Policy>
+ </wsrmp:DeliveryAssurance> ] ?
+ </wsp:Policy>
+ </wsrmp:RMAssertion/>
+ </eg>
+ </example>
+
<p>The syntax of an assertion can be represented using an XML outline (plus an XML schema
document). If the assertion has a nested policy expression then the assertion XML
outline can enumerate the nested assertions that are allowed. An example is the following:
@@ -687,19 +713,7 @@
assertion.
</quote>
</p>
- <p role="practice" id="XMLOutline"> <quote>Provide an XML Outline</quote> >
- <quote> An assertion description should provide an XML outline plus an XML schema to specify the
- syntax of the assertion.
- </quote>
- </p>
-
- <example>
- <eg>
- <wsrmp:RMAssertion [wsp:Optional="true"]? ...>
- ...
- </wsrmp:RMAssertion/>
- </eg>
- </example>
+
</div3>
<div3 id="self-describing">
@@ -2671,7 +2685,15 @@
<loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/310">310</loc> and
<loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/311">311</loc>.
</td>
- </tr>
+ </tr>
+ <tr>
+ <td>200706013</td>
+ <td>MH</td>
+ <td>Implemented Resolution in Editors' actions
+ <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/292">292</loc> and
+ <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/293">293</loc>.
+ </td>
+ </tr>
</tbody>
</table>
</inform-div1>
Received on Wednesday, 13 June 2007 19:16:31 UTC