W3C home > Mailing lists > Public > public-ws-policy-eds@w3.org > May 2007

2006/ws/policy ws-policy-primer.xml,1.56,1.57

From: David Orchard via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 02 May 2007 21:51:39 +0000
To: public-ws-policy-eds@w3.org
Message-Id: <E1HjMjb-0008Ud-NU@lionel-hutz.w3.org>

Update of /sources/public/2006/ws/policy
In directory hutz:/tmp/cvs-serv32599

Modified Files:
	ws-policy-primer.xml 
Log Message:
synch up

Index: ws-policy-primer.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-primer.xml,v
retrieving revision 1.56
retrieving revision 1.57
diff -u -d -r1.56 -r1.57
--- ws-policy-primer.xml	2 May 2007 21:09:41 -0000	1.56
+++ ws-policy-primer.xml	2 May 2007 21:51:36 -0000	1.57
@@ -1377,6 +1377,9 @@
       
       <div2 id="extensibility-and-versioning">
         <head>Extensibility and Versioning</head>
+        <div3 id="ext-vers-policylanguage">
+<head>Policy Language</head>
+
         <p>Web Services Policy language is an extensible language by design. The
           <code>Policy</code>, <code>ExactlyOne</code>, <code>All</code>
           and <code>wsp:PolicyReference</code> elements are extensible. The <code>Policy</code>
@@ -1389,11 +1392,14 @@
           elements as policy assertions. The child elements of <code>wsp:PolicyReference</code> are ignored. 
           </p>
         <p>The <code>PolicyReference</code> element allows element and attribute extensibility.</p>
-        <p>Web Services Policy language enables simple versioning practices that allow requesters to
-          continue the use of any older policy alternatives in a backward compatible manner. This
-          allows service providers, like Company-X, to deploy new behaviors using additional policy
+        </div3>
+        <div3>
+<head>Policy Expressions</head>
+        <p>Services that use the Web Services Policy language for policy expression enable simple versioning practices that allow requesters to
+          continue the use of older policy alternatives in a backward compatible manner. This
+          versioning practice allows service providers, like Company-X, to deploy new behaviors using additional (or new) policy
           assertions without breaking compatibility with clients that rely on any older policy
-          alternatives.</p>
+          alternatives.  We use two examples below to illustrate how versioning might be done.</p>
         <p>The example below represents a Company-X version 1 policy expression. This expression
           requires the use of addressing and transport-level security for protecting messages. </p>
         <example>
@@ -1452,6 +1458,7 @@
           known WSDL constructs and allows Web service developers to fill in code for custom or
           unknown constructs in the WSDL.
         </p>
+        </div3>
       <div3 id="ignorable-and-versioning">
         <head>Ignorable and Versioning</head>
         <p>
@@ -2432,4 +2439,4 @@
       </table>
     </inform-div1>
   </back>
-</spec>
+</spec>
\ No newline at end of file
Received on Wednesday, 2 May 2007 21:51:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:21:02 GMT