- From: Frederick Hirsch via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 17 Mar 2010 13:05:31 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/policy-reqs
In directory hutz:/tmp/cvs-serv21108
Modified Files:
Overview.html
Log Message:
update conformance target section, create new categories section
Index: Overview.html
===================================================================
RCS file: /sources/public/2009/dap/policy-reqs/Overview.html,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -d -r1.29 -r1.30
--- Overview.html 17 Mar 2010 11:01:02 -0000 1.29
+++ Overview.html 17 Mar 2010 13:05:29 -0000 1.30
@@ -132,11 +132,14 @@
</section> <!-- definitions -->
<section id='targets'>
<h2>Conformance Targets</h2>
- <section>
- <h3>Privacy Conformance Targets</h3>
-
-<p>There are four privacy conformance targets to whom privacy compliance might apply:
-</p>
+<p>There are two conformance targets referred to in this document:</p>
+<ul>
+<li><p><code>User Agent</code></li>
+<li><p><code>Application/Content</code></li>
+</ul>
+</section>
+<section id="privacy-categorization">
+<h3>Privacy Requirement Categorization</h3>
<ul>
<li><p><code>UA-Functionality</code>: Requirements for functionality provided strictly by user
agents (without relation to any policy information provided by an
@@ -172,7 +175,7 @@
as [[PRIVACY-ISSUES-GEO]] points out, most sites implementing the API
are not complying).</p>
</section>
-</section>
+
<section id='privacy-areas'>
<h3>Privacy Areas</h3>
<p>Privacy considerations are important to Device APIs, since misuse of
Received on Wednesday, 17 March 2010 13:05:33 UTC