W3C home > Mailing lists > Public > public-dap-commits@w3.org > May 2013

dap commit: update 'Security and privacy considerations' sections as per PING's feedback

From: Mercurial notifier <cvsmail@w3.org>
Date: Tue, 21 May 2013 09:04:24 +0000
Message-Id: <E1UeiUa-000611-RL@mcbain.w3.org>
To: public-dap-commits@w3.org
changeset:   419:7bca576bd37a
user:        Anssi Kostiainen <anssi.kostiainen@intel.com>
date:        Tue May 21 12:02:22 2013 +0300
files:       light/Overview.src.html proximity/Overview.src.html
description:
update 'Security and privacy considerations' sections as per PING's feedback


diff -r 86141a82d02c -r 7bca576bd37a light/Overview.src.html
--- a/light/Overview.src.html	Mon May 20 22:43:48 2013 +0200
+++ b/light/Overview.src.html	Tue May 21 12:02:22 2013 +0300
@@ -113,9 +113,40 @@
       </p>
     </section>
     
-    <section>
+    <section class="informative">
       <h2>Security and privacy considerations</h2>
       <p>
+        Privacy threats can arise when this specification is used in
+        combination with other functionality or when used over time,
+        specifically with the risk of correlation of data and user
+        identification through fingerprinting. Web application developers
+        using these JavaScript APIs should consider how this information might
+        be correlated with other information and the privacy risks that might
+        be created. The potential risks of collection  of such data over a
+        longer period of time should also be considered.
+      </p>
+      <p>
+        Variations in implementation light level values as well as event firing
+        rates offer the possibility of fingerprinting to identify users.
+        Browser implementations may reduce the risk by only using the less
+        precise <a>LightLevelState</a> of 'dim', 'normal', and 'bright' and limiting
+        event rates available to web application developers.
+      </p>
+      <p>
+        If the same JavasScript code using the API can be used simultaneously in
+        different window contexts on the same device it may be possible for
+        that code to correlate the user across those two contexts, creating
+        unanticipated tracking mechanisms.
+      </p>
+      <p>
+        Browser implementations should consider providing the user an
+        indication of when the sensor is used and allowing the user to disable
+        sensing.
+      </p>
+      <p>
+        Web application developers that use this specification should perform a
+        privacy assessment of their application taking all aspects of their
+        application into consideration.
       </p>
     </section>
     
diff -r 86141a82d02c -r 7bca576bd37a proximity/Overview.src.html
--- a/proximity/Overview.src.html	Mon May 20 22:43:48 2013 +0200
+++ b/proximity/Overview.src.html	Tue May 21 12:02:22 2013 +0300
@@ -146,9 +146,40 @@
       </p>
     </section>
     
-    <section>
+    <section class="informative">
       <h2>Security and privacy considerations</h2>
       <p>
+        Privacy threats can arise when this specification is used in
+        combination with other functionality or when used over time,
+        specifically with the risk of correlation of data and user
+        identification through fingerprinting. Web application developers
+        using these JavaScript APIs should consider how this information might
+        be correlated with other information and the privacy risks that might
+        be created. The potential risks of collection  of such data over a
+        longer period of time should also be considered.
+      </p>
+      <p>
+        Variations in implementation limits of minimum and maximum sensing
+        distance as well as event firing rates offer the possibility of
+        fingerprinting to identify users. Browser implementations may reduce
+        the risk by limiting the granularity and event rates available to web
+        application developers.
+      </p>
+      <p>
+        If the same JavasScript code using the API can be used simultaneously in
+        different window contexts on the same device it may be possible for
+        that code to correlate the user across those two contexts, creating
+        unanticipated tracking mechanisms.
+      </p>
+      <p>
+        Browser implementations should consider providing the user an
+        indication of when the sensor is used and allowing the user to disable
+        sensing.
+      </p>
+      <p>
+        Web application developers that use this specification should perform a
+        privacy assessment of their application taking all aspects of their
+        application into consideration.
       </p>
     </section>
     
Received on Tuesday, 21 May 2013 09:04:26 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:52:34 UTC