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

Re: Intended usage notification

From: Doug Turner <doug.turner@gmail.com>
Date: Sun, 12 Apr 2009 20:26:03 -0700
Cc: public-geolocation@w3.org
Message-Id: <271410AC-0E9F-432F-B816-A23F7E4BAA4F@gmail.com>
To: Henning Schulzrinne <hgs@cs.columbia.edu>

sorry, Henning is right.  I only speak for myself and +1 what greg  
said, what andrei said, what Ian said, and what Max said.

On Apr 12, 2009, at 8:21 PM, Henning Schulzrinne wrote:

> I think it would be more honest to state that *you* believe this,  
> not some regal *we*; not everybody agrees. You make certain  
> assumptions that not everybody shares. Everybody is entitled to  
> their opinion, but it would help the discussion if you extended the  
> same courtesy to others.
> On Apr 12, 2009, at 10:58 PM, Doug Turner wrote:
>> On Apr 12, 2009, at 3:39 PM, Greg Bolsinga wrote:
>>> On Apr 12, 2009, at 3:23 PM, Nick Doty wrote:
>>>> Hmm, wouldn't it be pretty tacky for users to have to click  
>>>> through a generic Javascript alert in order to make sure they had  
>>>> contextual information for the separate dialogue for revealing  
>>>> location information?
>>> That's subjective. But the developer can create an entire web page  
>>> that explains things before it uses GeoLocation.
>>>> I think we have an opportunity to make it easy for web site  
>>>> designers to do the right thing and disclose this information in  
>>>> a standardized way.  If we rely on each web site designer going  
>>>> out of their way to accomplish this (with a Javascript alert or  
>>>> varying levels of conspicuous disclosure), I fear that we'll end  
>>>> up  in a situation where most users are making the decision  
>>>> whether or not to disclose their location without knowing the  
>>>> relevant information, beyond the URI.  In other words, I'd like  
>>>> to solve the problem for everyone, not just for me.
>>> IMHO, all this API is about is getting the location. It's not  
>>> about UI for this feature. That's properly left up to the UA and  
>>> the code on the sites using the API.
>> Nick,
>> I think you have raised an interesting idea about disclosing intent  
>> of usage through this device API.  However, over this thread we  
>> have shown that it does more harm that it helps, especially when  
>> you consider untrustworthy sites.
>> Thanks for raising the idea, however I do not think any UA should  
>> implement an API in such a way.
>> Doug Turner
Received on Monday, 13 April 2009 03:26:44 UTC

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