W3C home > Mailing lists > Public > public-geolocation@w3.org > March 2010

RE: enableHighAccuracy as a privacy feature

From: Thomson, Martin <Martin.Thomson@andrew.com>
Date: Thu, 25 Mar 2010 00:40:10 +0800
To: Dominique Hazael-Massieux <dom@w3.org>, Doug Turner <dougt@dougt.org>
CC: public-geolocation <public-geolocation@w3.org>
Message-ID: <8B0A9FCBB9832F43971E38010638454F03E24ED194@SISPE7MB1.commscope.com>
For one, your proposal places control over privacy in the wrong hands - those of the entity least interested in that characteristic.

This attribute is largely meaningless and therefore useless.  A way to negotiate accuracy, as a three-way negotiation, is probably something that I hope will be considered for the next version.


p.s. ...By three way negotiation, I mean that:
 1. the site has a set of minimum or desired quality requirements
 2. the browser/system has a set of constraints, such accuracy or timeliness limitations 
 3. the user has a set of privacy constraints
Currently, this negotiation is hampered by the narrow bandwidth offered for communicating between these parties.

> -----Original Message-----
> From: public-geolocation-request@w3.org [mailto:public-geolocation-
> request@w3.org] On Behalf Of Dominique Hazael-Massieux
> Sent: Wednesday, 24 March 2010 9:22 AM
> To: Doug Turner
> Cc: public-geolocation
> Subject: Re: enableHighAccuracy as a privacy feature
> Le mercredi 24 mars 2010 à 09:17 -0700, Doug Turner a écrit :
> > In the API, we do not have a way to negotiate accuracy.  I do not
> > think that we should add yet another meaning to this already poorly
> > named attribute.
> Could you maybe be a bit more specific? e.g. what are there use cases
> where the proposed additional behavior would create problems?
> Dom

Received on Wednesday, 24 March 2010 16:39:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:50:59 UTC