Geo-location in the Mobile Web Dave Raggett, W3C & JustSystems - - PowerPoint PPT Presentation
Geo-location in the Mobile Web Dave Raggett, W3C & JustSystems W3C Track @ WWW2008, Beijing, 23 April 2008 1 Contact: dsr@w3.org Overview Privacy, trust and legal considerations Location sensing technologies Deployment choices
1
W3C Track @ WWW2008, Beijing, 23 April 2008 Contact: dsr@w3.org
2
3
– 1996 Telecommunications Act, seen by FCC as
– but overturned by courts in U.S.West vs FCC
– Subsequent to introduce laws to require opt-in have
– 2003 CTIA proposes “consumer code” for self-
– E911 requiring location of emergency callers
Taken from http://www.isoc.org/briefings/015/
4
– Article 9 of Directive on Privacy and Electronic
– Subscribers must be able, without charge, to
– But it is up to each EU member country to
– EU E-112 regulations mandating location of
5
– 1989 Ministry of Posts and Telecommunications
– Requires opt-in and defines clear standard for
– 2003 the Diet passes Personal Data Protection Law – Clear legal and regulatory standards has boosted
6
wants the location for
reduced accuracy
trustworthy loki.com is requesting your exact location:
–
Would you like to allow or deny this request?
–
Would you like to remember this decision for future requests?
–
Would you like to manage sites?
7
– The click through dialogue offers poor usability – Users may have little knowledge of the track record
– Some sites may have been vetted by operator
– Ask a friend or trusted authority – Wisdom of crowds
8
Internet website website website User Security Policy Engine Policies &
Policies &
policies when application requests access to restricted capabilities
remote TMS
to TMS
matching user's preferences
Trust Management Service (TMS) Client
Browser Security Policy Engine Server
9
– A-GPS reduces power consumption and boosts
– Doesn't work well indoors or high rise urban areas
– U-TDOA which measures time of arrival at each
– Bluetooth, Infrared, WiFi neighborhood, Barcodes,
10
– Typically pre-installed
– User installable, digitally signed by device vendor
– Browser detects markup extension – Location passed via HTTP to web server – No need for client-side scripting
– Not yet available, but great for mashups
11
– maps with turn by turn directions
– location based advertising
12
– Use QRCode to add
– Location-based search
13
– based on location and
– select to get coupons
14
15
– find loved ones
– track employees
Turn off your phone to stop being tracked
16
– GPX (XML-based) and several proprietary formats
– Widely used for J2ME applications
17
– GPS, E-TDOA, WiFi neighbourhood, ... – Only a limited fraction of deployed devices – This limits the customer base at any time
– TDOA, U-TDOA, Cell ID, ... – This makes such techniques easier to deploy
18
– Server is needed in some way to compute location
– via client device – direct to websites, but controlled how?
– not all devices will include GPS support – doesn't work well in shadow of tall buildings – doesn't work in enclosed urban environments
19
– obvious choice and widely supported for GPS
– Lower accuracy for altitude in most cases – Bearing determined from location tracking
– postal addresses in USA, UK, France, ...
20
– simple opt-in consent dialogues are insufficient!
– details to be announced
– used by browser to determine when to send
21
This talk is available at http://www.w3.org/2008/Talks/0423-dsr-lbs/slides.pdf
22
– Browser asks user for consent to send location – Browser sends HTTP GET with params
http://server/location.cgi?datum=AAA&unit=BBB&lat=XXX&lon=YYY May use additional HTTP headers, e.g. x-jphone-geocode
<form action="location:gps" method="post"> <input type="submit" value="data" /> <input type="hidden" name="url" value="http://www.example.com/example/example" /> <input type="hidden" name="param1" value="1234" /> <input type="hidden" name="param2" value="data" /> </form> Multiple approaches and lack of concensus on details