- From: Dominique Hazael-Massieux via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 01 Mar 2010 14:18:56 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/policy-reqs
In directory hutz:/tmp/cvs-serv11552
Modified Files:
Overview.html
Log Message:
tweaking
Index: Overview.html
===================================================================
RCS file: /sources/public/2009/dap/policy-reqs/Overview.html,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -d -r1.13 -r1.14
--- Overview.html 1 Mar 2010 14:17:42 -0000 1.13
+++ Overview.html 1 Mar 2010 14:18:54 -0000 1.14
@@ -369,7 +369,7 @@
<section>
<h3>Appropriateness</h3>
<p>When making a decision about sharing or not some private data, the user needs to understand how these data will be used by the requester.</p>
- <p class="issue">Should the APIs have a hook to convey the intended usage of the data? If so, how can this information be conveyed without misleading the user in the trustiness of that information?</p>
+ <p class="issue">Should the APIs have a hook to convey the intended usage of the data? If they do, should it be a required parameter? And how can this information be conveyed without misleading the user in the trustiness of that information?</p>
</section>
<section>
Received on Monday, 1 March 2010 14:18:58 UTC