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

Aaron Boodman

Re: skeleton Geolocation API - Error codes (Monday, 4 August)

Alec Berntson

Wording (Friday, 29 August)
[public-geolocation] <none> (Friday, 29 August)

Andrei Popescu

(no subject) (Friday, 29 August)
Re: next steps ... (Thursday, 28 August)
Re: skeleton Geolocation API - Error codes (Monday, 18 August)
Re: skeleton Geolocation API - Error codes (Monday, 18 August)
Re: spec bug: Orphaned reference to "typedef sequence<DOMString> StringArray" <eom> (Monday, 18 August)
Re: skeleton Geolocation API - Error codes (Friday, 15 August)
Re: skeleton Geolocation API - Error codes (Monday, 11 August)
Re: skeleton Geolocation API - Error codes (Friday, 8 August)
Re: Draft Charter (Monday, 4 August)
Re: skeleton Geolocation API - Error codes (Monday, 4 August)
Re: skeleton Geolocation API - Error codes (Monday, 4 August)
Re: skeleton Geolocation API - Error codes (Monday, 4 August)

Chris Butler

RE: Suggest adding proximity alarm interface (Wednesday, 27 August)
RE: skeleton Geolocation API - Error codes (Monday, 11 August)

Doug Turner

Re: Remarks on GeoLocation Spec (Thursday, 28 August)
Re: skeleton Geolocation API - Error codes (Monday, 11 August)
Re: skeleton Geolocation API - Error codes (Monday, 4 August)
Re: skeleton Geolocation API - Error codes (Monday, 4 August)

Eric Tune

Suggest adding proximity alarm interface (Monday, 25 August)

Innovimax SARL

Remarks on GeoLocation Spec (Thursday, 28 August)

Matt Womer

Re: next steps ... (Thursday, 28 August)
Re: Draft Charter (Wednesday, 6 August)

Shyam Habarakada

RE: next steps ... (Thursday, 28 August)
next steps ... (Thursday, 28 August)
Re: skeleton Geolocation API - Error codes (Monday, 18 August)
spec bug: Orphaned reference to "typedef sequence<DOMString> StringArray" <eom> (Monday, 18 August)
RE: skeleton Geolocation API - Error codes (Monday, 4 August)

Last message date: Friday, 29 August 2008 15:19:49 UTC