BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Sabre//Sabre VObject 4.5.8//EN
CALSCALE:GREGORIAN
LAST-MODIFIED:20260219T063508Z
BEGIN:VTIMEZONE
TZID:Asia/Tokyo
X-MICROSOFT-CDO-TZID:20
BEGIN:STANDARD
DTSTART:20241117T021500
TZOFFSETFROM:+0900
TZOFFSETTO:+0900
TZNAME:JST
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
UID:22b75ecd-a861-4818-8eb5-1c40cba52c13
DTSTAMP:20260219T063508Z
SUMMARY:Geolocation and Privacy
DTSTART;TZID=Asia/Tokyo:20251112T111500
DTEND;TZID=Asia/Tokyo:20251112T121500
DESCRIPTION:https://www.w3.org/events/meetings/22b75ecd-a861-4818-8eb5-1c40
 cba52c13/\n\nA discussion on geolocation and privacy.\n\n[Approximate Geol
 ocation](https://github.com/explainers-by-googlers/approximate-geolocation
 /blob/main/README.md) proposes to give sites the ability to request obfusc
 ated position estimates. Obfuscation protects user privacy by making it mo
 re difficult for sites to recover the user's true location. We'll review I
 ETF GEOPRIV recommendations for location obfuscation and discuss how obfus
 cation was implemented for Mozilla's Geode add-on.\n\nWe'll recap the hist
 ory of geolocation on the web platform. What were the influences that resu
 lted in Geolocation API's privacy model? How did the Geofencing and Geoloc
 ation Sensor proposals approach location privacy? How do current proposals
  address privacy concerns?\n\nOpen discussion on the future of location pr
 ivacy on the web.\n\n**Goal(s):**\nReview geolocation privacy consideratio
 ns\, feedback on current proposals\n\nAgenda\n\n**Materials:**\n- [Session
  proposal on GitHub](https://github.com/w3c/tpac2025-breakouts/issues/29)
STATUS:CONFIRMED
CREATED:20251028T073721Z
LAST-MODIFIED:20260219T063508Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Floor 5 - 505
CATEGORIES:TPAC 2025,Breakout Sessions
END:VEVENT
END:VCALENDAR