public-geolocation@w3.org from March 2009 by author

Alec Berntson

• RE: Geolication API level 2 - editor's draft (Wednesday, 25 March)
• RE: Civic Address for V2 (Monday, 9 March)
• RE: Civic Address for V2 (Tuesday, 3 March)
• RE: Civic Address for V2 (Tuesday, 3 March)
• RE: Civic Address for V2 (Monday, 2 March)
• RE: Civic Address for V2 (Monday, 2 March)

Alissa Cooper

• Re: Intended usage notification (Tuesday, 31 March)
• Re: geolocation privacy statement strawman (Saturday, 28 March)
• Re: Intended usage notification (Saturday, 28 March)

Allan Thomson (althomso)

• RE: renaming enableHighAccuracy (Tuesday, 31 March)
• RE: api comments (Tuesday, 31 March)
• RE: api comments (Monday, 30 March)
• api comments (Monday, 30 March)
• RE: Geolication API level 2 - editor's draft (Monday, 30 March)
• RE: Geolication API level 2 - editor's draft (Monday, 30 March)
• RE: Geolication API level 2 - editor's draft (Friday, 20 March)
• RE: Geolication API level 2 - editor's draft (Friday, 20 March)

Andrei Popescu

• renaming enableHighAccuracy (Tuesday, 31 March)
• Re: api comments (Tuesday, 31 March)
• Re: PositionOptions.timeout & UserAgent permission (Monday, 30 March)
• Re: geolocation privacy statement strawman (Monday, 30 March)
• Re: ISSUE-4 (privacy-geopriv): GEOPRIV WG proposal for privacy within the API (Friday, 27 March)
• Re: Intended usage notification (Thursday, 26 March)
• Re: ISSUE-4 (privacy-geopriv): GEOPRIV WG proposal for privacy within the API (Thursday, 26 March)
• Re: ISSUE-2 (privacy): Should the Geolocation API include privacy information? (Thursday, 26 March)
• Re: ISSUE-2 (privacy): Should the Geolocation API include privacy information? (Thursday, 26 March)
• Re: geolocation privacy statement strawman (Wednesday, 25 March)
• Re: ISSUE-2 (privacy): Should the Geolocation API include privacy information? (Wednesday, 25 March)
• Re: Geolication API level 2 - editor's draft (Wednesday, 25 March)
• Re: Geolication API level 2 - editor's draft (Wednesday, 25 March)
• Re: geolocation privacy statement strawman (Wednesday, 25 March)
• Re: PositionOptions.timeout & UserAgent permission (Friday, 20 March)
• Re: Geolication API level 2 - editor's draft (Friday, 20 March)
• Re: PositionOptions.timeout & UserAgent permission (Thursday, 19 March)
• Re: PositionOptions.timeout & UserAgent permission (Wednesday, 18 March)
• Re: More on TimeOut, MaximumAge and EnableHighAccuracy (Tuesday, 17 March)
• Re: PositionOptions.timeout & UserAgent permission (Tuesday, 17 March)
• Geolication API level 2 - editor's draft (Monday, 16 March)
• Re: PositionOptions.timeout & UserAgent permission (Monday, 16 March)
• Re: Civic Address for V2 (Tuesday, 10 March)
• Re: geolocation privacy statement strawman (Tuesday, 10 March)
• Re: Civic Address for V2 (Tuesday, 10 March)
• Re: Civic Address for V2 (Friday, 6 March)
• Re: Civic Address for V2 (Tuesday, 3 March)
• Re: Civic Address for V2 (Tuesday, 3 March)
• Re: Civic Address for V2 (Tuesday, 3 March)
• Re: Civic Address for V2 (Tuesday, 3 March)
• delivering test cases (Tuesday, 3 March)
• Re: Civic Address for V2 (Tuesday, 3 March)
• Re: Civic Address for V2 (Tuesday, 3 March)
• Re: Civic Address for V2 (Monday, 2 March)
• Re: Civic Address for V2 (Monday, 2 March)

Angel Machín

• Re: delivering test cases (Thursday, 26 March)
• Re: geolocation privacy statement strawman (Wednesday, 25 March)
• Re: FYI: GEOPRIV meeting on thursday (Wednesday, 25 March)
• Test suite (Tuesday, 10 March)

Charles McCathieNevile

• Re: Civic Address for V2 (Wednesday, 4 March)

Dirk Segers

• RE: geolocation privacy statement strawman (Wednesday, 25 March)

Doug Turner

• Re: renaming enableHighAccuracy (Tuesday, 31 March)
• Re: api comments (Tuesday, 31 March)
• Re: api comments (Monday, 30 March)
• Re: Geolication API level 2 - editor's draft (Monday, 30 March)
• Re: Intended usage notification (Thursday, 26 March)
• Re: Intended usage notification (Thursday, 26 March)
• Re: ISSUE-4 (privacy-geopriv): GEOPRIV WG proposal for privacy within the API (Thursday, 26 March)
• Re: delivering test cases (Thursday, 26 March)
• Re: ISSUE-2 (privacy): Should the Geolocation API include privacy information? (Thursday, 26 March)
• Re: ISSUE-2 (privacy): Should the Geolocation API include privacy information? (Wednesday, 25 March)
• Re: Geolication API level 2 - editor's draft (Wednesday, 25 March)
• Re: Civic Address for V2 (Monday, 23 March)
• Re: Geolication API level 2 - editor's draft (Friday, 20 March)
• Re: PositionOptions.timeout & UserAgent permission (Wednesday, 18 March)
• Re: PositionOptions.timeout & UserAgent permission (Wednesday, 18 March)
• Re: PositionOptions.timeout & UserAgent permission (Wednesday, 18 March)
• Re: PositionOptions.timeout & UserAgent permission (Sunday, 15 March)
• Re: Civic Address for V2 (Tuesday, 10 March)
• Re: geolocation privacy statement strawman (Tuesday, 10 March)
• Re: Civic Address for V2 (Monday, 9 March)
• Re: geolocation privacy statement strawman (Monday, 9 March)
• Re: geolocation privacy statement strawman (Monday, 9 March)
• Re: geolocation privacy statement strawman (Friday, 6 March)
• geolocation privacy statement strawman (Friday, 6 March)
• Re: Civic Address for V2 (Tuesday, 3 March)
• Re: Civic Address for V2 (Tuesday, 3 March)
• Re: Civic Address for V2 (Tuesday, 3 March)
• Re: Civic Address for V2 (Tuesday, 3 March)
• Re: Civic Address for V2 (Tuesday, 3 March)

Erik Wilde

• privacy issues (Tuesday, 17 March)
• NYT article on location and privacy (Wednesday, 11 March)
• Re: Civic Address for V2 (Monday, 9 March)

Geolocation Working Group Issue Tracker

• ISSUE-5 (privacy-text): What should the Recommendation state about security and privacy considerations? (Thursday, 26 March)
• ISSUE-4 (privacy-geopriv): GEOPRIV WG proposal for privacy within the API (Thursday, 26 March)
• ISSUE-3 (civic-addressing): Exposing civic addresses in the API (Wednesday, 25 March)
• ISSUE-2 (privacy): Should the Geolocation API include privacy information? (Wednesday, 25 March)

Greg Bolsinga

• Re: geolocation privacy statement strawman (Saturday, 28 March)
• Re: Intended usage notification (Thursday, 26 March)
• Re: geolocation privacy statement strawman (Wednesday, 25 March)
• Re: PositionOptions.timeout & UserAgent permission (Thursday, 19 March)
• Re: PositionOptions.timeout & UserAgent permission (Thursday, 19 March)
• More on TimeOut, MaximumAge and EnableHighAccuracy (Tuesday, 17 March)
• Re: PositionOptions.timeout & UserAgent permission (Tuesday, 17 March)
• Re: PositionOptions.timeout & UserAgent permission (Sunday, 15 March)
• PositionOptions.timeout & UserAgent permission (Sunday, 15 March)

Henning Schulzrinne

• Re: ISSUE-3 (civic-addressing): Exposing civic addresses in the API (Thursday, 26 March)
• Re: Civic Address for V2 (Monday, 23 March)
• Re: Civic Address for V2 (Tuesday, 10 March)
• Re: Civic Address for V2 (Monday, 9 March)
• Re: geolocation privacy statement strawman (Monday, 9 March)
• Re: geolocation privacy statement strawman (Friday, 6 March)
• Re: Civic Address for V2 (Wednesday, 4 March)
• Re: Civic Address for V2 (Tuesday, 3 March)
• Re: Civic Address for V2 (Tuesday, 3 March)
• Re: Civic Address for V2 (Monday, 2 March)
• Re: Civic Address for V2 (Saturday, 28 February)

Ian Hickson

• Re: Intended usage notification (Saturday, 28 March)
• RE: Intended usage notification (Thursday, 26 March)
• RE: Intended usage notification (Thursday, 26 March)
• Re: Civic Address for V2 (Tuesday, 3 March)
• Re: Civic Address for V2 (Tuesday, 3 March)
• Re: Civic Address for V2 (Tuesday, 3 March)
• Re: Civic Address for V2 (Tuesday, 3 March)
• Re: Civic Address for V2 (Tuesday, 3 March)

John Morris

• Re: ISSUE-4 (privacy-geopriv): GEOPRIV WG proposal for privacy within the API (Thursday, 26 March)
• Re: ISSUE-2 (privacy): Should the Geolocation API include privacy information? (Thursday, 26 March)
• Re: ISSUE-3 (civic-addressing): Exposing civic addresses in the API (Thursday, 26 March)

Kai Hendry

• Re: delivering test cases (Tuesday, 31 March)

Kruessel, Steffen

• RE: Civic Address for V2 (Monday, 2 March)

Lars Erik Bolstad

• Opera Geolocation build (Thursday, 26 March)

Marc Linsner

• Re: Civic Address for V2 (Friday, 6 March)
• Re: Civic Address for V2 (Tuesday, 3 March)
• Re: Civic Address for V2 (Tuesday, 3 March)
• Re: Civic Address for V2 (Tuesday, 3 March)
• Re: Civic Address for V2 (Monday, 2 March)

Matt Womer

• Re: ISSUE-4 (privacy-geopriv): GEOPRIV WG proposal for privacy within the API (Thursday, 26 March)
• Re: ISSUE-2 (privacy): Should the Geolocation API include privacy information? (Thursday, 26 March)
• Tracker and other tools (Thursday, 26 March)
• Re: ISSUE-3 (civic-addressing): Exposing civic addresses in the API (Thursday, 26 March)
• Re: ISSUE-2 (privacy): Should the Geolocation API include privacy information? (Wednesday, 25 March)
• Re: FYI: GEOPRIV meeting on thursday (Tuesday, 24 March)

Max Froumentin

• Re: Intended usage notification (Friday, 27 March)

Michael(tm) Smith

• Re: Civic Address for V2 (Wednesday, 4 March)
• Re: Civic Address for V2 (Wednesday, 4 March)
• Re: Civic Address for V2 (Wednesday, 4 March)
• Re: delivering test cases (Wednesday, 4 March)

Perry Tancredi

• RE: Civic Address for V2 (Tuesday, 3 March)
• RE: Civic Address for V2 (Tuesday, 3 March)

Richard Barnes

• Re: renaming enableHighAccuracy (Tuesday, 31 March)
• Re: api comments (Tuesday, 31 March)
• Re: Geolication API level 2 - editor's draft (Thursday, 26 March)
• Re: Civic Address for V2 (Monday, 23 March)
• FYI: GEOPRIV meeting on thursday (Saturday, 21 March)
• Re: Civic Address for V2 (Friday, 20 March)
• Re: Civic Address for V2 (Tuesday, 3 March)
• Re: Civic Address for V2 (Tuesday, 3 March)
• Re: Civic Address for V2 (Tuesday, 3 March)
• Re: Civic Address for V2 (Tuesday, 3 March)
• Re: Civic Address for V2 (Tuesday, 3 March)
• Re: Civic Address for V2 (Sunday, 1 March)

Taqi Jaffri

• RE: renaming enableHighAccuracy (Tuesday, 31 March)

Thomson, Martin

• RE: renaming enableHighAccuracy (Tuesday, 31 March)
• RE: Intended usage notification (Thursday, 26 March)
• RE: Intended usage notification (Thursday, 26 March)
• RE: ISSUE-5 (privacy-text): What should the Recommendation state about security and privacy considerations? (Thursday, 26 March)
• Intended usage notification (Thursday, 26 March)
• RE: PositionOptions.timeout & UserAgent permission (Monday, 16 March)
• RE: Civic Address for V2 (Tuesday, 10 March)
• RE: geolocation privacy statement strawman (Monday, 9 March)

Last message date: Tuesday, 31 March 2009 23:16:50 UTC