Adjust privacy note for POS Kiosk
authorIan Jacobs <ij@w3.org>
Tue, 31 Mar 2015 12:53:11 -0500
changeset 135 23df61549861
parent 134 c23eadff2889
child 136 a9d13d3816a9
Adjust privacy note for POS Kiosk

- I think “shouldn’t be able to be tracked” may be too strong; I think
we want to ensure Cory can exercise control.
latest/use-cases/index.html
--- a/latest/use-cases/index.html	Tue Mar 31 12:47:28 2015 -0500
+++ b/latest/use-cases/index.html	Tue Mar 31 12:53:11 2015 -0500
@@ -746,7 +746,7 @@
 General feedback is requested related to the general structure of the
 use case snippets below. Are they focused enough to convey each topic listed?
 Is there information that should be added to each use case in general? Would
-more elaborate use cases be helpful. Would an attempt to minimize each existing
+more elaborate use cases be helpful? Would an attempt to minimize each existing
 use further be helpful in scanning the document more quickly?
     </p>
 
@@ -791,9 +791,8 @@
 success of this work.
           </dd>
           <dt>Privacy</dt>
-          <dd>
-Cory shouldn't be able to be tracked by the merchant unless he uses a loyalty
-card to pay.
+          <dd>Cory should exercise control over how much he wants the merchant
+	    to be able to track his activities. Programs like loyalty cards will likely involve agreement to more data with the merchant.
           </dd>
         </dl>