public-geolocation@w3.org from June 2008 by author

Aaron Boodman

• Re: skeleton Geolocation API (Sunday, 29 June)
• Re: skeleton Geolocation API (Sunday, 29 June)
• Re: skeleton Geolocation API (Friday, 27 June)
• Re: skeleton Geolocation API (Friday, 27 June)
• Re: skeleton Geolocation API (Thursday, 26 June)
• Re: skeleton Geolocation API (Thursday, 26 June)
• Re: skeleton Geolocation API (Thursday, 26 June)
• Re: skeleton Geolocation API (Thursday, 26 June)
• Re: skeleton Geolocation API (Thursday, 26 June)
• Re: what is a position? (Thursday, 26 June)
• Re: what is a position? (Thursday, 26 June)
• Re: skeleton Geolocation API (Tuesday, 24 June)
• Re: skeleton Geolocation API (Saturday, 21 June)
• Re: skeleton Geolocation API (Saturday, 21 June)
• Re: Geolocation API (Thursday, 12 June)

Aaron Straup Cope

• Re: skeleton Geolocation API (Sunday, 29 June)
• Re: Geolocation: Security and Privacy (Thursday, 12 June)

Alan McNamara

• The Geolocation API must provide location data in terms of a pair of latitude and longitude coordinates. (Wednesday, 25 June)

Alec Berntson

• Privacy in the Geolocation Spec (Tuesday, 24 June)
• RE: Geolocation API (Friday, 13 June)
• RE: Geolocation API (Thursday, 12 June)
• RE: Geolocation: Security and Privacy (Wednesday, 11 June)
• RE: Geolocation: Security and Privacy (Tuesday, 10 June)
• RE: Geolocation: Security and Privacy (Tuesday, 10 June)
• RE: Geolocation: Security and Privacy (Tuesday, 10 June)
• RE: Geolocation: Security and Privacy (Monday, 9 June)
• RE: Geolocation: Security and Privacy (Monday, 9 June)
• RE: Geolocation: Security and Privacy (Monday, 9 June)
• RE: Geolocation API (Monday, 9 June)
• Geolocation: Security and Privacy (Friday, 6 June)
• RE: DOM based API (Friday, 6 June)

Andrei Popescu

• Re: skeleton Geolocation API (Friday, 27 June)
• Re: skeleton Geolocation API (Friday, 27 June)
• Re: skeleton Geolocation API (Friday, 27 June)
• Re: skeleton Geolocation API (Friday, 27 June)
• Re: skeleton Geolocation API (Thursday, 26 June)
• Re: The Geolocation API must provide location data in terms of a pair of latitude and longitude coordinates. (Wednesday, 25 June)
• Re: Position.address property vs. a ReverseGeoCode( .. ) method? (Wednesday, 25 June)
• Re: skeleton Geolocation API (Monday, 23 June)
• Re: skeleton Geolocation API (Monday, 23 June)
• Re: skeleton Geolocation API (Monday, 23 June)
• Re: skeleton Geolocation API (Monday, 23 June)
• Re: skeleton Geolocation API (Monday, 23 June)
• skeleton Geolocation API (Friday, 20 June)
• Editor draft updated (Friday, 13 June)
• Re: Geolocation API (Thursday, 12 June)
• Re: Geolocation API (Thursday, 12 June)
• Re: Geolocation API (Thursday, 12 June)
• Re: Geolocation API (Thursday, 12 June)
• Re: Geolocation API (Monday, 9 June)
• Re: DOM based API (Friday, 6 June)
• Re: DOM based API (Friday, 6 June)
• Geolocation API (Thursday, 5 June)

Anne van Kesteren

• Re: Geolocation API (Monday, 9 June)
• Re: DOM based API (Friday, 6 June)

Arun Ranganathan

• Re: Draft Charter (Thursday, 26 June)

Charles McCathieNevile

• Re: what is a position? (Wednesday, 25 June)
• Re: Draft Charter (Wednesday, 25 June)

Chris Butler

• RE: skeleton Geolocation API (Thursday, 26 June)
• RE: value semantics (Wednesday, 25 June)
• RE: The Geolocation API must provide location data in terms of a pair of latitude and longitude coordinates. (Wednesday, 25 June)
• RE: The Geolocation API must provide location data in terms of a pair of latitude and longitude coordinates. (Wednesday, 25 June)
• RE: skeleton Geolocation API (Saturday, 21 June)
• onChange and raw position vs. error-corrected position (Saturday, 21 June)
• RE: Geolocation: Security and Privacy (Tuesday, 10 June)
• RE: Geolocation: Security and Privacy (Tuesday, 10 June)
• RE: Geolocation: Security and Privacy (Sunday, 8 June)

Chris Prince

• Re: skeleton Geolocation API (Thursday, 26 June)
• Re: skeleton Geolocation API (Thursday, 26 June)
• Re: skeleton Geolocation API (Thursday, 26 June)
• Re: DOM based API (Monday, 9 June)

Chris Wilson

• RE: Draft Charter (Monday, 23 June)
• Re: Draft Charter (Monday, 23 June)

Dave Burke

• Re: skeleton Geolocation API (Friday, 27 June)
• Re: Geolocation: Security and Privacy (Thursday, 12 June)
• Re: DOM based API (Monday, 9 June)

Doug Schepers

• Re: Draft Charter (Friday, 20 June)
• Re: DOM based API (Monday, 9 June)
• Re: Geolocation: Security and Privacy (Monday, 9 June)
• Re: DOM based API (Friday, 6 June)

Doug Turner

• Re: skeleton Geolocation API (Thursday, 26 June)
• Re: skeleton Geolocation API (Thursday, 26 June)
• Re: skeleton Geolocation API (Saturday, 21 June)
• Re: skeleton Geolocation API (Saturday, 21 June)
• Re: skeleton Geolocation API (Saturday, 21 June)
• Re: skeleton Geolocation API (Saturday, 21 June)
• Re: Geolocation API (Friday, 13 June)
• Re: Geolocation: Security and Privacy (Wednesday, 11 June)
• Re: Geolocation: Security and Privacy (Wednesday, 11 June)
• Re: DOM based API (Friday, 6 June)

Erik Wilde

• Re: skeleton Geolocation API (Sunday, 29 June)
• Re: skeleton Geolocation API (Sunday, 29 June)
• Re: DOM based API (Sunday, 29 June)
• Re: skeleton Geolocation API (Sunday, 29 June)
• Re: skeleton Geolocation API (Saturday, 28 June)
• Re: skeleton Geolocation API (Saturday, 28 June)
• Re: skeleton Geolocation API (Friday, 27 June)
• Re: skeleton Geolocation API (Thursday, 26 June)
• Re: GPS recommended minimum (Thursday, 26 June)
• value semantics (Wednesday, 25 June)
• Re: The Geolocation API must provide location data in terms of a pair of latitude and longitude coordinates. (Wednesday, 25 June)
• Re: Privacy in the Geolocation Spec (Wednesday, 25 June)
• Re: The Geolocation API must provide location data in terms of a pair of latitude and longitude coordinates. (Wednesday, 25 June)
• Re: The Geolocation API must provide location data in terms of a pair of latitude and longitude coordinates. (Wednesday, 25 June)
• Re: Draft Charter (Monday, 23 June)
• what is a position? (Sunday, 22 June)
• Re: Draft Charter (Friday, 20 June)

Ian Hickson

• Re: Privacy in the Geolocation Spec (Tuesday, 24 June)
• Re: Draft Charter (Monday, 23 June)
• Re: Draft Charter (Saturday, 21 June)
• Re: Draft Charter (Friday, 20 June)
• Re: DOM based API (Monday, 9 June)

Jon Ferraiolo

• Re: The Geolocation API must provide location data in terms of a pair of latitude and longitude coordinates. (Wednesday, 25 June)
• Re: Privacy in the Geolocation Spec (Tuesday, 24 June)
• Re: Geolocation API (Friday, 13 June)
• RE: Geolocation API (Friday, 13 June)

Kai Hendry

• Re: GPS recommended minimum (Thursday, 26 June)
• GPS recommended minimum (Thursday, 26 June)

Karl Dubost

• Re: what is a position? (Thursday, 26 June)
• Re: Geolocation: Security and Privacy (Thursday, 12 June)
• Re: Geolocation: Security and Privacy (Thursday, 12 June)

Kartikaya Gupta

• Re: skeleton Geolocation API (Friday, 27 June)
• Re: skeleton Geolocation API (Friday, 27 June)
• Re: skeleton Geolocation API (Saturday, 21 June)
• RE: Geolocation: Security and Privacy (Wednesday, 11 June)

lists.geolocation@stakface.com

• Re: Geolocation API (Friday, 6 June)

Maciej Stachowiak

• Re: Draft Charter (Monday, 23 June)
• Re: Draft Charter (Saturday, 21 June)
• Re: DOM based API (Monday, 9 June)
• Re: DOM based API (Monday, 9 June)
• Re: DOM based API (Sunday, 8 June)
• Re: Charter question on form of API, was Re: DOM based API (Friday, 6 June)
• Re: DOM based API (Friday, 6 June)
• Re: DOM based API (Friday, 6 June)
• Re: DOM based API (Friday, 6 June)

Mark Baker

• Re: DOM based API (Saturday, 28 June)
• Re: DOM based API (Saturday, 28 June)
• Re: DOM based API (Monday, 9 June)
• Re: DOM based API (Monday, 9 June)
• Re: Geolocation API (Monday, 9 June)
• Re: DOM based API (Monday, 9 June)
• Re: DOM based API (Monday, 9 June)
• Re: DOM based API (Friday, 6 June)
• Re: DOM based API (Friday, 6 June)
• DOM based API (Friday, 6 June)

Matt Womer

• Re: The Geolocation API must provide location data in terms of a pair of latitude and longitude coordinates. (Wednesday, 25 June)
• Re: Draft Charter (Wednesday, 25 June)
• Re: Draft Charter (Friday, 20 June)
• Draft Charter (Friday, 20 June)
• Re: Where we are (Friday, 6 June)
• Charter question on form of API, was Re: DOM based API (Friday, 6 June)
• Where we are (Friday, 6 June)

Michael(tm) Smith

• Re: skeleton Geolocation API (Saturday, 21 June)
• Re: DOM based API (Friday, 6 June)
• Re: Charter question on form of API, was Re: DOM based API (Friday, 6 June)

Nick Brachet

• Re: Position.address property vs. a ReverseGeoCode( .. ) method? (Wednesday, 25 June)
• Re: skeleton Geolocation API (Tuesday, 24 June)
• Re: skeleton Geolocation API (Saturday, 21 June)

Ryan Sarver

• Re: skeleton Geolocation API (Sunday, 29 June)
• Re: Draft Charter (Saturday, 21 June)
• Re: skeleton Geolocation API (Saturday, 21 June)
• Re: Geolocation: Security and Privacy (Wednesday, 11 June)
• Re: Geolocation API (Wednesday, 11 June)

Shyam Habarakada

• RE: skeleton Geolocation API (Thursday, 26 June)
• RE: Position.address property vs. a ReverseGeoCode( .. ) method? (Wednesday, 25 June)
• Position.address property vs. a ReverseGeoCode( .. ) method? (Tuesday, 24 June)
• RE: Geolocation API (Thursday, 12 June)
• RE: Geolocation API (Saturday, 7 June)

timeless

• Re: skeleton Geolocation API (Friday, 27 June)
• Re: skeleton Geolocation API (Friday, 27 June)
• Re: what is a position? (Thursday, 26 June)
• Re: what is a position? (Thursday, 26 June)
• Re: skeleton Geolocation API (Tuesday, 24 June)
• Re: Geolocation: Security and Privacy (Wednesday, 11 June)
• Re: Geolocation: Security and Privacy (Tuesday, 10 June)
• Re: Geolocation: Security and Privacy (Sunday, 8 June)

Will_Wilbrink@mapinfo.com

• Re: The Geolocation API must provide location data in terms of a pair of latitude and longitude coordinates. (Wednesday, 25 June)

Last message date: Sunday, 29 June 2008 22:09:39 UTC