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

2009/dap/policy-reqs Overview.html,1.39,1.40

From: Frederick Hirsch via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 16 Jun 2010 19:22:54 +0000
To: public-dap-commits@w3.org
Message-Id: <E1OOyCM-0003gX-Mn@lionel-hutz.w3.org>
Update of /sources/public/2009/dap/policy-reqs
In directory hutz:/tmp/cvs-serv14151

Modified Files:
	Overview.html 
Log Message:
duh.


Index: Overview.html
===================================================================
RCS file: /sources/public/2009/dap/policy-reqs/Overview.html,v
retrieving revision 1.39
retrieving revision 1.40
diff -u -d -r1.39 -r1.40
--- Overview.html	16 Jun 2010 19:20:26 -0000	1.39
+++ Overview.html	16 Jun 2010 19:22:52 -0000	1.40
@@ -693,7 +693,6 @@
 
 </section>
 
-</section>
       <section id="framework">
 <h2>Security Framework</h2>
       <section id="framework-rqmts">
@@ -701,12 +700,11 @@
       <section id="policy-integrity-requirements">
         <h2>Policy Integrity Requirements</h2>
 <p>It should be possible for policy to be integrity protected during
-various points in its life-cycle.
+various points in its life-cycle.</p>
 <ul>
   <li>It MUST be possible to provide integrity protection and
     source authentication for policy.</li>
 </ul>
-</p>
 </section>
         <ul>
           <li>The DAP security framework MUST NOT preclude different
@@ -748,7 +746,6 @@
     </p>
   </section> <!-- access control requirements -->
 </section> <!-- requirements -->
-</section>
 <section>
       <h3>Examples of statements or rules that may be expressed in a policy</h3>
       <p>
Received on Wednesday, 16 June 2010 19:22:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 16 June 2010 19:22:56 GMT