- From: Nilsson, Claes1 <Claes1.Nilsson@sonyericsson.com>
- Date: Thu, 27 Jan 2011 16:28:52 +0100
- To: "public-device-apis@w3.org" <public-device-apis@w3.org>
FYI, Geolocation WG has also noted the "Do Not Track headers". Claes -----Original Message----- From: public-geolocation-request@w3.org [mailto:public-geolocation-request@w3.org] On Behalf Of Richard L. Barnes Sent: den 24 januari 2011 22:49 To: public-geolocation Subject: Privacy rules along with data The blogosphere is abuzz today talking about Do Not Track headers [1][2][3]. The idea of this HTTP header is to signal to an advertising server that the user's browser information should not be stored or used for customized marketing. In the context of this group, I wanted to note that the idea of DNT is essentially the same as the idea of carrying rules with location objects that we discussed here a while back. In both cases, when the user provides sensitive information (tracking data, location) to a third party, that information comes along with rules for how the user would like the information to be used (don't track, don't retain). Perhaps this is an approach that we should revisit in our v2 discussions, for the geolocation API as well as general browsing? (Or perhaps for DAP in general?) --Richard [1] <http://www.engadget.com/2011/01/24/chrome-and-firefox-adding-new-opt-out-features-to-prevent-third/> [2] <http://firstpersoncookie.wordpress.com/2011/01/23/more-choice-and-control-over-online-tracking/> [3] <https://bugzilla.mozilla.org/show_bug.cgi?id=628197>
Received on Thursday, 27 January 2011 15:29:48 UTC