- From: Frederick Hirsch via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 17 Mar 2010 15:35:17 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/privacy-reqs In directory hutz:/tmp/cvs-serv31801 Modified Files: Overview.html Log Message: add relevant material on implicit consent to consent section Index: Overview.html =================================================================== RCS file: /sources/public/2009/dap/privacy-reqs/Overview.html,v retrieving revision 1.1 retrieving revision 1.2 diff -u -d -r1.1 -r1.2 --- Overview.html 17 Mar 2010 15:02:19 -0000 1.1 +++ Overview.html 17 Mar 2010 15:35:15 -0000 1.2 @@ -139,10 +139,27 @@ "express," "affirmative," "implied," "implicit," or something else); how that consent is obtained; whether that consent should be remembered by the UA</p> - -<p>See <a href="#user-control-principle">User Control over -Decisions</a> for a general discussion about requirements for -obtaining user consent.</p> +<p> + The semantics of some APIs are defined such that user + interaction is essential to make use of the API. An example is + a camera API that enables the user to take a photograph, but + is defined to require the user to press a shutter key to take + the photograph. Another example + is an API that produces a message template, but requires the + user to press "send" to actually send the message. + </p><p> + Such user actions constitute implicit consent, since the user + has a choice to perform them and doing so implies consent to + use the associated Device Capabilities. Such implicit consent + eliminates the need for a security access dialog for that + action since it is implicit in the application semantics. + </p><p> + Device APIs may also be defined such that implicit consent is not + implied. Examples are a camera API that takes a photograph without + user involvement, or a messaging API that sends a message without the + user pressing "send". In these cases policy and/or + user dialogs may be required. + </p> </section> <!-- consent --> <section id="privacy-minimization">
Received on Wednesday, 17 March 2010 15:35:21 UTC