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

2006/ws/policy ws-policy-framework.html,1.40,1.41

From: Prasad Yendluri via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 27 Sep 2006 22:48:06 +0000
To: public-ws-policy-eds@w3.org
Message-Id: <E1GSiCE-0002ay-6l@lionel-hutz.w3.org>

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

Modified Files:
	ws-policy-framework.html 
Log Message:
Completed action item: 46 resolution for issue 3752 - Clarify restrictions of ID type usage (http://www.w3.org/Bugs/Public/show_bug.cgi?id=3752)

Index: ws-policy-framework.html
===================================================================
RCS file: /sources/public/2006/ws/policy/ws-policy-framework.html,v
retrieving revision 1.40
retrieving revision 1.41
diff -u -d -r1.40 -r1.41
--- ws-policy-framework.html	26 Sep 2006 07:50:17 -0000	1.40
+++ ws-policy-framework.html	27 Sep 2006 22:48:04 -0000	1.41
@@ -451,7 +451,7 @@
 	    security, transactions) semantics and are expected to be
 	    defined in separate, domain-specific specifications.</p>
 
-	    <p>Assertions are typed by the domain authors
+	    <p>Assertions are typed by the authors
 	    that define them. The <a title="policy assertion type" href="#policy_assertion_type">policy assertion
 	    type</a> is identified only by the XML Infoset <strong>[namespace name]</strong> and <strong>[local name]</strong> properties (that
 	    is, the qualified name or QName) of the root Element
@@ -463,11 +463,11 @@
 	    a given type <span class="rfc2119">MUST</span> be consistently
 	    interpreted independent of their <a title="policy subject" href="#policy_subject">policy subjects</a>.</p>
 
-	    <p>Domain authors <span class="rfc2119">MAY</span> define that an assertion contains a
+	    <p>Authors <span class="rfc2119">MAY</span> define that an assertion contains a
 	    <a title="policy expression" href="#policy_expression">policy
-	        expression</a> (as defined in <a href="#rPolicy_Expression"><b>4. Policy Expression</b></a>) as one of its <strong>[children]</strong>.  <a title="nested policy expression" href="#nested_policy_expression">Nested policy expression(s)</a> are used by domain authors to further
+	        expression</a> (as defined in <a href="#rPolicy_Expression"><b>4. Policy Expression</b></a>) as one of its <strong>[children]</strong>.  <a title="nested policy expression" href="#nested_policy_expression">Nested policy expression(s)</a> are used by authors to further
 	    qualify one or more specific aspects of the original
-	    assertion. For example, security policy domain authors may
+	    assertion. For example, security policy authors may
 	    define an assertion describing a set of security
 	    algorithms to qualify the specific behavior of a security
 	    binding assertion. </p>
@@ -484,10 +484,10 @@
 	    item to indicate how long an endpoint will wait before
 	    sending an acknowledgement. </p>
 
-	    <p>Domain authors should be cognizant of the processing
+	    <p>Authors should be cognizant of the processing
 	    requirements when defining complex assertions containing
 	    <a title="policy assertion parameter" href="#policy_assertion_parameter">policy assertion parameters</a> or <a title="nested policy expression" href="#nested_policy_expression">nested policy
-	    expressions</a>. Specifically, domain authors are encouraged
+	    expressions</a>. Specifically, authors are encouraged
 	    to consider when the identity of the root Element
 	    Information Item alone is enough to convey the requirement
 	    or capability.</p>
@@ -519,7 +519,7 @@
 	    thus aspects such as the order in which behaviors
 	    (indicated by assertions) are applied to a <a title="policy subject" href="#policy_subject">subject</a> are
 	        beyond the scope of this specification.
-	        However, domain authors can write assertions that control the order in which behaviours are applied.</p>
+	        However, authors can write assertions that control the order in which behaviours are applied.</p>
 
 	    <p>A policy alternative <span class="rfc2119">MAY</span> contain multiple assertions of
 	    the same type. Mechanisms for determining the aggregate
@@ -719,10 +719,11 @@
 
 <dt class="label"><code class="attr">/wsp:Policy/(@wsu:Id | @xml:id)</code> </dt>
 <dd><p>The identity of the policy expression as an <code>ID</code> within the
-enclosing XML document. If omitted, there is no implied value. To
-refer to this policy expression, an IRI-reference
-&nbsp;<span class="rfc2119">MAY</span> be formed using this value per Section 4.2 of
-    WS-Security [<cite><a href="#WS-Security">WS-Security 2004</a></cite>] when @wsu:Id is used.</p>
+enclosing XML document. If omitted, there is no implied value. 
+The constraints of the XML 1.0 [<cite><a href="#XML10">XML 1.0</a></cite>] ID type MUST be met.
+To refer to this policy expression, an IRI-reference
+<span class="rfc2119">MAY</span> be formed using this value per Section 4.2 of
+WS-Security [<cite><a href="#WS-Security">WS-Security 2004</a></cite>] when @wsu:Id is used.</p>
     <p>The use of <code>xml:id</code> attribute in conjunction with Canonical XML 1.0 is 
     inappropriate as described in Appendix C of xml:id Version 1.0 [<cite><a href="#XMLID">XML ID</a></cite>] 
     and thus this combination must be avoided (see [<cite><a href="#C14NNOTE">C14N 1.0 Note</a></cite>]). For example, 
@@ -908,7 +909,6 @@
 with straight vines.</p>
 
 <p>For example, consider the following policy expression with 
-
 nested policy expressions in a compact form:</p>
 <div class="exampleInner"><pre>(01) &lt;wsp:Policy
 &nbsp; &nbsp; &nbsp; &nbsp; xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"
@@ -2044,12 +2044,30 @@
                     <tr>
                         <td rowspan="1" colspan="1">20060926</td>
                         <td rowspan="1" colspan="1">ASV</td>
-                        <td rowspan="1" colspan="1">Implemented the 
-                            <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/30">resolution</a> 
-                            for issue 
+                        <td rowspan="1" colspan="1">Implemented the action item:
+                            <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/30">30</a> 
+                            resolution for issue 
                             <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3549">3549</a>.                	
                         </td>
                     </tr>
+                     <tr>
+                        <td rowspan="1" colspan="1">20060927</td>
+                        <td rowspan="1" colspan="1">MH</td>
+                        <td rowspan="1" colspan="1">Completed action item:
+                            <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/02">02</a> 
+                            resolution for issue 
+                            <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3706">3706</a> - changing "domain authors" to "authors".                	
+                        </td>
+                    </tr>
+                    <tr>
+                        <td rowspan="1" colspan="1">20060927</td>
+                        <td rowspan="1" colspan="1">PY</td>
+                        <td rowspan="1" colspan="1">Completed action item:
+                            <a href="http://www.w3.org/2005/06/tracker/wspolicyeds/actions/46">46</a> 
+                            resolution for issue 
+                            <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3752">3752</a> - Clarify restrictions of ID type usage.                	
+                        </td>
+                    </tr>
                 </tbody>
             </table><br>
         </div>
Received on Wednesday, 27 September 2006 22:48:17 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:27:49 UTC