- From: Frederick Hirsch via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 07 Apr 2010 16:30:02 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/privacy-reqs In directory hutz:/tmp/cvs-serv13215 Modified Files: Overview.html Log Message: get rid of code elements in bullet list. Index: Overview.html =================================================================== RCS file: /sources/public/2009/dap/privacy-reqs/Overview.html,v retrieving revision 1.11 retrieving revision 1.12 diff -u -d -r1.11 -r1.12 --- Overview.html 7 Apr 2010 16:27:46 -0000 1.11 +++ Overview.html 7 Apr 2010 16:30:00 -0000 1.12 @@ -125,17 +125,17 @@ 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> - <li><p><code><a href="#privacy-minimization">Minimization</a>:</code>Limiting the amount and level of detail of data collected through Device APIs</p></li> - <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 + <li><p><a href="#privacy-notice">Notice</a>:Informing users about the data collected through Device APIs</p></li> + <li><p><a href="#privacy-consent">Consent</a>:Obtaining user agreement to sharing data through Device APIs</p></li> + <li><p><a href="#privacy-minimization">Minimization</a>:Limiting the amount and level of detail of data collected through Device APIs</p></li> + <li><p><a href="#privacy-control">Control</a>:Allowing users to control access to their data once they have consented to having it collected through Device APIs</p></li> + <li><p><a href="#privacy-access">Access</a>:Providing users with access to information about the data that has been collected about them through Device APIs</p></li> + <li><p><a href="#privacy-retention">Retention</a>:Limiting how long applications retain data that was collected through Device APIs</p></li> + <li><p><a href="#privacy-secondary-use">Secondary + Use</a>: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> + <li><p><a href="#privacy-sharing">Sharing</a>:Limiting applications from sharing data collected through Device APIs with third parties</p></li> </ul> <p>These elements will each need to be approached in different ways. Approaches include specific requirements
Received on Wednesday, 7 April 2010 16:30:06 UTC