- From: Frederick Hirsch via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 07 Apr 2010 16:27:48 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/privacy-reqs
In directory hutz:/tmp/cvs-serv13084
Modified Files:
Overview.html
Log Message:
link from table headers to sections, make consistent. Attempt to fix
validation errors.
Index: Overview.html
===================================================================
RCS file: /sources/public/2009/dap/privacy-reqs/Overview.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -d -r1.10 -r1.11
--- Overview.html 7 Apr 2010 16:17:43 -0000 1.10
+++ Overview.html 7 Apr 2010 16:27:46 -0000 1.11
@@ -119,7 +119,11 @@
<section>
<h2>Privacy Principles relevant to APIs</h2>
- <p>Privacy protections are frequently understood as a set of principles or elements (one such set is described in [[PRIVACY-ISSUES-GEO]]). The core elements of privacy that are relevant to Device APIs, user agents that support the APIs, and applications that use the APIs are as follows:
+ <p>Privacy protections are frequently understood as a set of
+ principles or elements (one such set is described in
+ [[PRIVACY-ISSUES-GEO]]). The core elements of privacy that are
+ relevant to Device APIs, user agents that support the APIs, and
+ applications that use the APIs are as follows: </p>
<ul>
<li><p><code><a href="#privacy-notice">Notice</a>:</code>Informing users about the data collected through Device APIs</p></li>
<li><p><code><a href="#privacy-consent">Consent</a>:</code>Obtaining user agreement to sharing data through Device APIs</p></li>
@@ -127,10 +131,12 @@
<li><p><code><a href="#privacy-control">Control</a>:</code>Allowing users to control access to their data once they have consented to having it collected through Device APIs</p></li>
<li><p><code><a href="#privacy-access">Access</a>:</code>Providing users with access to information about the data that has been collected about them through Device APIs</p></li>
<li><p><code><a href="#privacy-retention">Retention</a>:</code>Limiting how long applications retain data that was collected through Device APIs</p></li>
- <li><p><code><a href="#privacy-secondary-use">Secondary Use</a>:</code>Limiting applications from using data collected through Device APIs for purposes other than the purpose for which it was collected</li></p>
+ <li><p><code><a href="#privacy-secondary-use">Secondary
+ Use</a>:</code>Limiting applications from using data
+ collected through Device APIs for purposes other than the
+ purpose for which it was collected</p></li>
<li><p><code><a href="#privacy-sharing">Sharing</a>:</code>Limiting applications from sharing data collected through Device APIs with third parties</p></li>
- </ul>
- </p>
+ </ul>
<p>These elements will each need to be approached in different ways. Approaches include specific requirements
on individual APIs, conveying user expectations together with
@@ -143,8 +149,9 @@
<table class="simple">
<tr>
<th>Privacy Element</th>
- <th>Requirements for API Definitions</th>
- <th>Requirements for user expectations conveyed with data</th>
+ <th><a href="#privacy-requirements">Requirements for API Definitions</a></th>
+ <th><a href="#privacy-user-expectations">Requirements
+ related to User Expectations of Data Use</a></th>
<th>Best practices for developers</th>
</tr>
<tr>
@@ -199,8 +206,9 @@
<p> The privacy requirements for individual APIs are provided in the next section. The requirements described in this document are intended
- to be applicable to device APIs both in the context of widgets and web applications.</p>
- </p>
+ to be applicable to device APIs both in the context of
+ widgets and web applications.</p>
+
</section>
<div class="issue"><p>The breakdown described above foreshadows the idea of providing API hooks that allow users to attach their expectations/preferences/policies about privacy to the data they share through the APIs. Attaching policy rules to the data that get shared can provide a legal basis for enhancing the control users have
over their data once they are shared; but doing so create the
@@ -223,7 +231,7 @@
</section> <!-- introduction -->
<section id="privacy-requirements">
-<h3>Privacy Requirements for APIs</h3>
+<h3>Requirements for API Definitions</h3>
<p class="issue">For most of the privacy elements that apply to APIs (except for minimization), the WG has not discussed what the specific requirements should be. Therefore most of the sections below simply list what requirements could address.</p>
@@ -376,7 +384,6 @@
important aspect of sharing.</p>
</section> <!-- sharing -->
-
</section>
<section class='appendix'>
<h2>Acknowledgements</h2>
Received on Wednesday, 7 April 2010 16:27:50 UTC