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

2006/ws/policy ws-policy-primer.xml,1.70,1.71

From: Prasad Yendluri via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 12 Sep 2007 19:11:05 +0000
To: public-ws-policy-eds@w3.org
Message-Id: <E1IVXcA-0005mO-0I@lionel-hutz.w3.org>

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

Modified Files:
	ws-policy-primer.xml 
Log Message:
Implemented the resolution for issue 5036. Editors' action 355. 

Index: ws-policy-primer.xml
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-primer.xml,v
retrieving revision 1.70
retrieving revision 1.71
diff -u -d -r1.70 -r1.71
--- ws-policy-primer.xml	23 Aug 2007 01:53:04 -0000	1.70
+++ ws-policy-primer.xml	12 Sep 2007 19:11:03 -0000	1.71
@@ -157,8 +157,8 @@
           determine the compatibility of policies, to name and reference policies and to associate
           policies with Web service metadata constructs such as service, endpoint and operation. Web
           Services Policy is a simple language that has four elements - <code>Policy, All</code>,
-            <code>ExactlyOne</code> and <code>PolicyReference</code> - and one attribute -
-            <code>wsp:Optional</code>.</p>
+            <code>ExactlyOne</code> and <code>PolicyReference</code> - and two attributes -
+          <code>wsp:Optional</code> and <code>wsp:Ignorable</code>.</p>
       </div2>
       <div2 id="simple-message">
         <head>Simple Message</head>
@@ -212,7 +212,7 @@
         <p>
           The policy expression in the above example consists of a Policy main  
           element and a child element wsam:Addressing. Child elements of  
-          the Policy element are policy assertions. Company-X attaches the above  
+          the Policy element that are not from the Policy namespace are policy assertions. Company-X attaches the above  
           policy expression to a WSDL binding description.
           </p>
         <example>
@@ -501,7 +501,7 @@
         <p>As described in the sections above and in Section <specref ref="strict-lax-policy-intersection"/>, 
         the WS-Policy 1.5 specification defines two 
         attributes that can be used to mark an assertion: wsp:Optional and wsp:Ignorable.</p>
-        <p>The WS-Policy Framework allows a policy assertion to be marked with both "optional" 
+        <p>The WS-Policy Framework allows a policy assertion to be marked with both "Optional" 
         and "Ignorable" attributes simultaneously. The presence of "@wsp:optional=true" on an assertion 
         is a syntactic compact form for two alternatives in normal form, one with the assertion 
         and the other without the assertion. Hence syntactically marking an assertion "A" with both the 
@@ -617,7 +617,7 @@
         </p>
         <p>A policy expression may be identified by an IRI and referenced for re-use as a standalone
           policy or within another policy expression. There are three mechanisms to identify a policy
-          expression: the <code>wsu:Id</code> <code>xml:id</code> and <code>Name</code> attributes. A
+          expression: the <code>wsu:Id</code>, <code>xml:id</code> and <code>Name</code> attributes. A
             <code>PolicyReference</code> element can be used to reference a policy expression
           identified using either of these mechanisms.</p>
         <example>
@@ -706,12 +706,12 @@
           assertions from different domains are used in a policy expression,
           complex expressions will emerge. Naming parts of complex expressions for
           reuse and building more complex policies through referencing enables
-          building more complicated policy scenerios easily. This approach enables
+          building more complicated policy scenarios easily. This approach enables
           the association of additional policy subjects to identified policy
           expressions.  It also promotes manageability of the expressions as they
-          are uniquely identified and allows profiles for common scenerios to be
+          are uniquely identified and allows profiles for common scenarios to be
           developed. Note that when a named expression has assertions that
-          contains parametrized expressions, care must be given to ensure that the
+          contains parameterized expressions, care must be given to ensure that the
           parameterized content is statically available to enable reuse.</p>
       </div2>
       <div2 id="attaching-policy-expressions-to-wsdl">
@@ -782,7 +782,7 @@
         <head>Policy Automates Web Services Interaction</head>
         <p>As you have seen, Web Services Policy is a simple language that has four elements -
             <code>Policy, All</code>, <code>ExactlyOne</code> and <code>PolicyReference</code> - and
-          one attribute - <code>wsp:Optional</code>. In practice, service providers, like Company-X,
+          two attributes - <code>wsp:Optional</code> and <code>wsp:Ignorable</code>. In practice, service providers, like Company-X,
           use policy expressions to represent combinations of capabilities and requirements. Web
           service developers use policy-aware clients that understand policy expressions
           and engage the behaviors represented by providers automatically. A sizable amount of
@@ -949,8 +949,8 @@
           policy expression in the normal form. As you can see, the compact form is less verbose
           than the normal form. The normal form represents a policy as a collection of policy
           alternatives. Each of the <code>All</code> operators is a policy alternative. There are
-          four policy alternatives in the normal form. These alternatives map to bullets (a) through
-          (d) above.</p>
+          four policy alternatives in the normal form. These alternatives map to list items (1) through
+          (4) above.</p>
         <example>
           <head>Company-X’s Policy Expression in Normal Form</head>
           <eg xml:space="preserve">&lt;Policy&gt;
@@ -994,7 +994,7 @@
           this section, let us look at the policy data model.</p>
         <p>Company-X uses a policy to convey the conditions for an interaction. Policy-aware clients,
           like the one used by the developer in our example (as explained earlier in <specref
-            ref="basic-concepts-policy-expression"/>), view policy as an unordered collection of
+            ref="basic-concepts-policy-expression"/>), view a policy as an unordered collection of
           zero or more policy alternatives. A policy alternative is an unordered collection of zero
           or more policy assertions. A policy alternative represents a collection of behaviors or
           requirements or conditions for an interaction. In simple words, each policy alternative
@@ -1136,7 +1136,7 @@
         <div3 id="strict-lax-policy-intersection">
           <head>Strict and Lax Policy Intersection</head>
           <p>
-            The previous sections outlined how the normal-form of a policy expression relate to the policy data model and how the 
+            The previous sections outlined how the normal-form of a policy expression relates to the policy data model and how the 
             compatibility of requester and provider policies may be determined.  
             This section outlines how ignorable assertions may impact the process of determining compatibility.
           </p>
@@ -1657,7 +1657,7 @@
         
         <div2 id="versioning-policy-framework"><head>Policy Framework</head>
           <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". 
+          ExactlyOne or All will be treated as an assertion. The default value for wsp:Optional is "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>
           <example><head>Policy containing 1.5 and 1.6 Policies.</head>
@@ -1905,7 +1905,7 @@
               <code>wsam</code>
             </td>
             <td>
-              <code>http://www.w3.org/2007/05/addressing/metadata</code>
+              <code>http://www.w3.org/TR/2007/REC-ws-addr-metadata-20070904/</code>
             </td>
             <td>[<bibref ref="WS-AddressingMetadata"/>]</td>
           </tr>
@@ -2007,11 +2007,11 @@
             href="http://www.w3.org/TR/ws-addr-core/">latest version of Web Services Addressing 1.0
             - Core</loc> is available at http://www.w3.org/TR/ws-addr-core. </bibl>
         <bibl key="WS-Addressing Metadata" id="WS-AddressingMetadata"
-          href="http://www.w3.org/TR/2007/PR-ws-addr-metadata-20070731/">
+          href="http://www.w3.org/TR/2007/REC-ws-addr-metadata-20070904/">
           <titleref>Web Services Addressing 1.0 - Metadata</titleref>, M. Gudgin, M. Hadley, T.
           Rogers and Ü. Yalçinalp, Editors. World Wide Web Consortium, 31 July 2007. This is a work in progress. This version of
           the Web Services Addressing 1.0 - Metadata is
-          http://www.w3.org/TR/2007/PR-ws-addr-metadata-20070731/. The <loc
+          http://www.w3.org/TR/2007/REC-ws-addr-metadata-20070904/. The <loc
             href="http://www.w3.org/TR/ws-addr-metadata">latest version of Web Services Addressing 1.0 -
             Metadata</loc> is available at http://www.w3.org/TR/ws-addr-metadata. </bibl>
         <bibl id="WS-Atomic" key="Web Services Atomic Transaction" href="http://schemas.xmlsoap.org/ws/2004/10/wsat/">
@@ -2556,7 +2556,15 @@
           <td>20070806</td>
           <td>FS</td>
           <td>Updated references for draft publication.</td>
-         </tr>   
+         </tr>
+          <tr>
+            <td>20070912</td>
+            <td>PY</td>
+            <td>Implemented the resolution for issue 
+              <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=5036">5036</loc>. Editors' action 
+              <loc href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/355">355</loc>.
+            </td>
+          </tr>   
         </tbody>
       </table>
     </inform-div1>
Received on Wednesday, 12 September 2007 19:11:08 GMT

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