- From: Frederick Hirsch via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 15 Mar 2010 22:37:43 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/policy-reqs
In directory hutz:/tmp/cvs-serv22388
Modified Files:
Overview.html
Log Message:
additional fixes
Index: Overview.html
===================================================================
RCS file: /sources/public/2009/dap/policy-reqs/Overview.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -d -r1.23 -r1.24
--- Overview.html 15 Mar 2010 22:21:38 -0000 1.23
+++ Overview.html 15 Mar 2010 22:37:41 -0000 1.24
@@ -555,7 +555,6 @@
</section>
<section>
<h3>Example: Voice search</h3>
-<p>
<dl><dt>Application</dt>
<dd>Uses the Capture API for a voice search service.
</dd>
@@ -563,7 +562,6 @@
<dd>Voice searches are retained for 90 days for use (for
example) in optimizing search results.</dd>
</dl>
-</p>
</section>
</section>
<section>
@@ -571,10 +569,9 @@
<p>Policies describe uses of user data beyond the service
requested by the user that caused the API call. Secondary uses might
be immediate or time-shifted -- and there are different levels of
-privacy concern for immediate vs. delayed secondary uses.
+privacy concern for immediate vs. delayed secondary uses.</p>
<section>
<h3>Example: Event reminders</h3>
-<p>
<dl><dt>Application</dt>
<dd>Uses the Calendar API to allow users to set reminders for
upcoming events, and serves contextual ads when users set reminders
@@ -584,11 +581,9 @@
<dt>Policy</dt>
<dd>Reminder information is used to target contextual ads.</dd>
</dl>
-</p>
</section>
<section>
<h3>Example: Event reminders with ads</h3>
-<p>
<dl><dt>Application</dt>
<dd>Uses the Calendar API to allow users to set reminders for
upcoming events, and serves ads based on the content of all of the
@@ -599,7 +594,6 @@
targeting purposes. (The ad targeting profile would be a time-shifted
or delayed secondary use.)</dd>
</dl>
-</p>
</section>
</section>
@@ -610,7 +604,6 @@
</p>
<section>
<h3>Example: Integrate address book contacts with social network</h3>
-<p>
<dl><dt>Application</dt>
<dd>Uses the Contacts API to upload address book contacts to a
social network.
@@ -619,18 +612,15 @@
<dd>Discloses names and email addresses from the address book
to the social networking service, but not to any other third party.</dd>
</dl>
-</p>
</section>
<section>
<h3>Example: Integrate address book contacts with social network and
Third Party credit checking service</h3>
-<p>
<dl><dt>Application</dt>
<dd>Uses the Contacts API to upload address book contacts to a
social network, and shares them with a third-party service that
performs credit checks based on social network data (see, e.g.,
- http://www.cdt.org/blogs/erica-newland/keeping-friends-close-and-friends-good-credit-scores-closer)
-.
+ http://www.cdt.org/blogs/erica-newland/keeping-friends-close-and-friends-good-credit-scores-closer).
</dd>
<dt>Policy</dt>
<dd>Discloses all contact information from the address book to
@@ -898,8 +888,6 @@
<h2>Requirements</h2>
<section id='user-control-rqmts'>
<h3>User Control Requirements</h3>
- <p>
- </p>
<ul>
<li>The security framework MUST NOT require User Agents to present modal dialogs to prompt users for security
decisions</li>
Received on Monday, 15 March 2010 22:37:45 UTC