W3C home > Mailing lists > Public > public-geolocation@w3.org > May 2009

Re: Additional security and privacy considerations?

From: Greg Bolsinga <bolsinga@apple.com>
Date: Wed, 27 May 2009 09:08:13 -0700
To: Doug Turner <doug.turner@gmail.com>
Message-Id: <58F4A9E5-15B4-43B2-8F37-D41E6899AE40@apple.com>
Cc: Thomas Roessler <tlr@w3.org>, Andrei Popescu <andreip@google.com>, Rigo Wenning <rigo@w3.org>, public-geolocation <public-geolocation@w3.org>
On May 27, 2009, at 7:58 AM, Doug Turner wrote:

> After thinking about this a bit more....
>
> I believe adding text, normative or not, that talks about a  
> fictional UI will add confusion.  I can imagine questions like "how  
> come this UA didn't follow the w3c spec when it concerns UI?" As  
> Greg said, "This spec is about getting a location, not how it is  
> implemented." We should instead cite this thread as part of the  
> considerations and drop having any recommended UI design related to  
> points 1, 2, and 3 in this specification.

+1. I must agree again. Having additional optional (or non-normative,  
a term I learned reading this thread) items in a spec seems to diverge  
from "keep it simple".

It's already a simple (and even too complex, see my previous thread  
about dropping getCurrentLocation(), PositionOptions.timeout and  
PositionOptions.maximumAge) API to get one's location. There can be  
other specifications about privacy considerations and this location API.

Thanks,
-- Greg
Received on Wednesday, 27 May 2009 16:08:55 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 22 March 2012 18:13:43 GMT