W3C home > Mailing lists > Public > public-pling@w3.org > July 2009

Re: Geolocation Last Call

From: Lorrie Faith Cranor <lorrie@cs.cmu.edu>
Date: Fri, 10 Jul 2009 12:30:04 -0400
Cc: ashok.malhotra@oracle.com, Renato Iannella <renato@nicta.com.au>
Message-Id: <107B7572-6401-4FA2-82C7-1B6F1A57D71E@cs.cmu.edu>
To: MCrompton@iispartners.com, public-pling@w3.org
I agree with these concerns too. And it is not obvious how to build  
"easy to use and control." We have a research project at CMU where we  
are working on this and have made some headway (see http:// 
locaccino.org - feel free to try it and send me your feedback), but  
it's not a completely solved problem by any means.

Lorrie

--
Lorrie Faith Cranor • lorrie@cmu.edu • http://lorrie.cranor.org/
Associate Professor, Computer Science and Engineering & Public Policy
CyLab Usable Privacy and Security Laboratory • http://cups.cs.cmu.edu/
Carnegie Mellon University, 5000 Forbes Ave., Pittsburgh, PA 15213



On Jul 9, 2009, at 11:52 PM, Malcolm Crompton wrote:

> I agree, strongly.  The lack of sophistication in thinking around  
> location
> based services & privacy is sometimes breathtaking.  It is neither  
> 'anything
> goes' nor 'never disclose'.  It has to be much more nuanced than  
> that.  A
> person on the lookout for a chance date is in a vastly different  
> position
> from the person who is the secret negotiator going to the secret  
> meeting to
> lock down the multi-million dollar deal.  AND the technology is  
> NEVER going
> to be able to tell the difference, especially because it could in  
> fact be
> the same person at different times in the same day.
>
> And that is before we bring in policing, national security and  
> emergency
> rescue...
>
> Informed, easy to use control with the right default settings (just  
> ask the
> behavioural economists et al) is going to be the only solution.
>
> Regards
>
> Malcolm Crompton
>
> Managing Director
> Information Integrity Solutions Pty Ltd
> ABN 78 107 611 898
>
> T:  +61 407 014 450
>
> MCrompton@iispartners.com
> www.iispartners.com
>
>
>
> -----Original Message-----
> From: public-pling-request@w3.org [mailto:public-pling- 
> request@w3.org] On
> Behalf Of ashok malhotra
> Sent: Friday, July 10, 2009 11:25 AM
> To: Renato Iannella
> Cc: public-pling@w3.org
> Subject: Re: Geolocation Last Call
>
> I, too, was worried when I read Section 4.  It punts all the privacy
> APIs to the implementations.
> All the best, Ashok
>
>
> Renato Iannella wrote:
>> After reading Section 4 of the Working Draft [1], I am more worried
>> than before.
>>
>> It does not engender any confidence, even by using the term
>> "consideration", for the safety and awareness of the end user's  
>> privacy.
>>
>> Perhaps we now need a PLING Note on "Best Practices for Privacy
>> Awareness" ?
>>
>>
>> Renato
>>
>> [1] http://www.w3.org/TR/geolocation-API/
>>
>>
>> On 8 Jul 2009, at 23:09, Thomas Roessler wrote:
>>
>>> No explicit request for review by PLING, but I think it would be  
>>> fine
>>> for this IG to tell them that you want to do a review -- if that is
>>> indeed the case.
>>> --
>>> Thomas Roessler, W3C  <tlr@w3.org <mailto:tlr@w3.org>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Begin forwarded message:
>>>
>>>> *From: *Angel Machín <angel.machin@gmail.com
>>>> <mailto:angel.machin@gmail.com>>
>>>> *Date: *8 July 2009 14:58:29 CEDT
>>>> *To: *janina@rednote.net <mailto:janina@rednote.net>,
>>>> art.barstow@nokia.com <mailto:art.barstow@nokia.com>,
>>>> chaals@opera.com <mailto:chaals@opera.com>,
>>>> Mary_Ellen_Zurko@notesdev.ibm.com
>>>> <mailto:Mary_Ellen_Zurko@notesdev.ibm.com>, tlr@w3.org
>>>> <mailto:tlr@w3.org>, dom@w3.org <mailto:dom@w3.org>, dsr@w3.org
>>>> <mailto:dsr@w3.org>,  chris@w3.org <mailto:chris@w3.org>,
>>>> daniel.appelquist@vodafone.com
>>>> <mailto:daniel.appelquist@vodafone.com>,
>>>> dahl@conversational-technologies.com
>>>> <mailto:dahl@conversational-technologies.com>, rbarnes@bbn.com
>>>> <mailto:rbarnes@bbn.com>, acooper@cdt.org <mailto:acooper@cdt.org>,
>>>> bondi@omtp.org <mailto:bondi@omtp.org>, jferrai@us.ibm.com
>>>> <mailto:jferrai@us.ibm.com>, Lars Erik Bolstad <lbolstad@opera.com
>>>> <mailto:lbolstad@opera.com>>,  Matt Womer <mdw@w3.org
>>>> <mailto:mdw@w3.org>>, chairs@w3.org <mailto:chairs@w3.org>
>>>> *Subject: **Geolocation Last Call*
>>>>
>>>> Hello Chairs,
>>>>
>>>> On behalf of Lars Erik Bolstad, the other co-chair of this WG,  
>>>> and I:
>>>>
>>>> The Geolocation Working Group has published the Geolocation API
>>>> Specification as a Last Call Working Draft on 7 July 2009:
>>>> http://www.w3.org/TR/geolocation-API/
>>>>
>>>> Feedback on this document would be appreciated through 31 July 2009
>>>> via mail to public-geolocation@w3.org
>>>> <mailto:public-geolocation@w3.org>.
>>>>
>>>> In particular we are requesting review from the Web Application WG,
>>>> Device APIs, Web Security Context, Ubiquitous Web Applications,  
>>>> Mobile
>>>> Web Best Practices, Hypertext Coordination, Protocols and Formats
>>>> Working Group and also GEOPRIV, BONDI and OpenAJAX Alliance.
>>>>
>>>> The Group made the decision to go to Last Call:
>>>> http://lists.w3.org/Archives/Public/public-geolocation/2009Jun/0161.html
>>>>
>>>> No patent disclosures have been made for this specification.
>>>>
>>>> Thanks,
>>>>
>>>> Angel Machin
>>>> Geolocation WG co-Chair
>>>>
>>>
>>
>> Cheers...  Renato Iannella
>> NICTA
>>
>
>
>
>
Received on Friday, 10 July 2009 16:31:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 10 July 2009 16:31:25 GMT