- From: Frederick Hirsch via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 15 Mar 2010 22:21:40 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/policy-reqs In directory hutz:/tmp/cvs-serv17764 Modified Files: Overview.html Log Message: fix link, validation errors Index: Overview.html =================================================================== RCS file: /sources/public/2009/dap/policy-reqs/Overview.html,v retrieving revision 1.22 retrieving revision 1.23 diff -u -d -r1.22 -r1.23 --- Overview.html 15 Mar 2010 18:55:34 -0000 1.22 +++ Overview.html 15 Mar 2010 22:21:38 -0000 1.23 @@ -215,7 +215,7 @@ how that consent is obtained; whether that consent should be remembered by the UA</p> -<p>See <a href="#user-control-over-decisions">User Control over +<p>See <a href="#user-control-principle">User Control over Decisions</a> for a general discussion about requirements for obtaining user consent.</p> </section> <!-- consent --> @@ -572,7 +572,6 @@ 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. -</p> <section> <h3>Example: Event reminders</h3> <p> @@ -637,7 +636,6 @@ <dd>Discloses all contact information from the address book to the social networking service and the credit check service.</dd> </dl> -</p> </section> </section> </section>
Received on Monday, 15 March 2010 22:21:42 UTC