W3C home > Mailing lists > Public > public-dap-commits@w3.org > June 2010

2009/dap/policy Profile.html,1.15,1.16

From: Dominique Hazael-Massieux via cvs-syncmail <cvsmail@w3.org>
Date: Mon, 21 Jun 2010 14:14:01 +0000
To: public-dap-commits@w3.org
Message-Id: <E1OQhlB-0004lm-D5@lionel-hutz.w3.org>
Update of /sources/public/2009/dap/policy
In directory hutz:/tmp/cvs-serv18320

Modified Files:
	Profile.html 
Log Message:
minor tweaks


Index: Profile.html
===================================================================
RCS file: /sources/public/2009/dap/policy/Profile.html,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -d -r1.15 -r1.16
--- Profile.html	21 Jun 2010 13:45:04 -0000	1.15
+++ Profile.html	21 Jun 2010 14:13:59 -0000	1.16
@@ -57,7 +57,7 @@
 	    <li>String</li> <li>IRI</li>
 	  </ul> <p> Each <a href="#modifier-function">modifier
 	  function</a> defines its result type, and how the
-	  function's effect depends on the type of the input. </p>
+	  function’s effect depends on the type of the input. </p>
 	  <p> Each <a href="#matching-function">matching
 	  function</a> defines how it depends on the type of its
 	  input. </p> <p> Where a modifier function or matching
@@ -114,7 +114,7 @@
 	  undetermined. </p>
     <p> In the second case, there is no
 	  modifierfunc. </p>
-    <p>The value to match (matchfunc's
+    <p>The value to match (matchfunc’s
 	  second input) is a sequence of literal text and other
 	  attribute references implicitly combined using string
 	  concatenation. Thus its type is bag containing a single
@@ -266,7 +266,7 @@
 	  <p>Where the implementation supports deployment of a
 	  fragment of policy to add to the existing security
 	  policy framework or to replace a part of it, the
-	  <code>policy document</code> is the unit of addition or
+	  policy document is the unit of addition or
 	  replacement. A policy document can be either a
 	  <code>policy</code> or a <code>policy-set</code>. </p>
 		</section> <!-- policy-document -->
@@ -388,10 +388,10 @@
 	  combined. </p> <p>The algorithms are described in the
 	  following subsections. The term “child” is used
 	  to mean the child rules in the policy
-	  when applying the policy's rule-combining
+	  when applying the policy’s rule-combining
 	  algorithm, or the child policies and
 	  policy sets in the policy set when
-	  applying the policy set's policy-combining
+	  applying the policy set’s policy-combining
 	  algorithm. </p>
 	  <section id="deny-overrides-combining-algorithm">
 	    <h4>Deny-Overrides Combining Algorithm</h4>
@@ -813,7 +813,7 @@
               <td>string</td> 
 	  <td>"tls-ev"</td> <td>As "tls", and, additionally, the
 	  site certificate has an extended validation field and
-	  the browser's internal policy allows that information to
+	  the browser’s internal policy allows that information to
 	  be passed to the security framework.</td> </tr> <tr>
 	  <td>uri</td> <td>URI</td> <td colspan="2">The URI used
 	  to access the document that embeds or refers to the
@@ -861,7 +861,7 @@
 	  ****)</td> <td>URI</td> <td>The IRI identifier of the
 	  requested Feature converted to URI as per RFC3987
 	  [[!IRI]].</td> <td>This uses the same naming scheme as
-	  in a widget's <code>feature</code> element. Determined for all
+	  in a widget’s <code>feature</code> element. Determined for all
 	  applicable application execution phases.</td> </tr>
       <tr>
         <td id="device-cap">device-cap</td> <td>string</td> <td>Device
@@ -1009,7 +1009,7 @@
   <h2>Acknowledgements</h2>
     <p>
     The editors would like to extend special thanks to Nokia, OMTP BONDI,
-    and PhoneGap for providing the foundation of the working group's
+    and PhoneGap for providing the foundation of the working group’s
     requirements discussion.
     </p>
 </section>
Received on Monday, 21 June 2010 14:14:02 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 21 June 2010 14:14:02 GMT