- From: Frederick Hirsch via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 15 Mar 2010 18:55:36 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/policy-reqs
In directory hutz:/tmp/cvs-serv8325
Modified Files:
Overview.html
Log Message:
Restructure and integrate new material from John Morris
Index: Overview.html
===================================================================
RCS file: /sources/public/2009/dap/policy-reqs/Overview.html,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -d -r1.21 -r1.22
--- Overview.html 10 Mar 2010 17:18:31 -0000 1.21
+++ Overview.html 15 Mar 2010 18:55:34 -0000 1.22
@@ -20,9 +20,9 @@
<section id='abstract'>
This document includes common use cases and security, privacy
and policy requirements for device APIs.
- </section>
+ </section> <!-- abstract -->
- <section class='informative'>
+ <section id='introduction'>
<h2>Introduction</h2>
<p>
This document is an editors draft and currently does not
[...1159 lines suppressed...]
- <p></p>
+ <h2>Access Control Requirements</h2>
<ul>
<li>Access control decisions may be made at both the
granularity of Features
@@ -880,12 +1011,8 @@
( see <a href="http://www.w3.org/2009/dap/track/issues/21">ISSUE-21 - OPEN</a> ) Is access control at the feature level required or is access control
at the device capability level adequate?
</p>
- </section>
- <section class='informative'>
- <h3>Rationale</h3>
- <p>
- </p>
- </section>
+ </section> <!-- access control requirements -->
+</section> <!-- requirements -->
</section>
<section>
<h2>Out of Scope</h2>
Received on Monday, 15 March 2010 18:55:39 UTC