- From: Doug Turner <doug.turner@gmail.com>
- Date: Fri, 3 Apr 2009 07:37:41 -0700
- To: Doug Turner <doug.turner@gmail.com>
- Cc: Andrei Popescu <andreip@google.com>, Lars Erik Bolstad <lbolstad@opera.com>, Max Froumentin <maxfro@opera.com>, public-geolocation@w3.org
Also, we need an issue for removing: readonly attribute double heading; readonly attribute double speed; From the Coordinates interface. In V2, these might also be reflected in a Address interface. On Apr 3, 2009, at 7:30 AM, Doug Turner wrote: > Please add another issue for the useLowPower/highAccuracy flag > name. I would like to see this resolved before last call. > > > On Apr 3, 2009, at 6:45 AM, Andrei Popescu wrote: > >> On Fri, Apr 3, 2009 at 2:43 PM, Andrei Popescu <andreip@google.com> >> wrote: >>> On Fri, Apr 3, 2009 at 1:54 PM, Andrei Popescu >>> <andreip@google.com> wrote: >>>> On Fri, Apr 3, 2009 at 1:20 PM, Lars Erik Bolstad <lbolstad@opera.com >>>> > wrote: >>>>> It is overdue. >>>>> >>>>> In order for us to proceed to last call we need to close all >>>>> open issues, of >>>>> which there are currently three: >>>>> http://www.w3.org/2008/geolocation/track/issues/open >>>>> >>>>> ISSUE-2: Should the Geolocation API include privacy information? >>>>> This should be closed. We have concluded that the API will not >>>>> include >>>>> privacy information. We should focus on ISSUE-5 instead. >>>>> >>>> >>>> Agreed. >>>> >>>>> ISSUE-3: Exposing civic addresses in the API >>>>> This is for "version 2" of the spec and should not hold up our >>>>> transition to >>>>> last call for "version 1". >>>>> >>>> >>>> Agreed. >>>> >>>>> ISSUE-5: What should the Recommendation state about security and >>>>> privacy >>>>> considerations? >>>>> Andrei, could you maybe put your latest draft wording into the >>>>> editor's >>>>> draft. I think it looks good. >>>>> >>>> >>>> Ok, will ping the list once I'm done. >>>> >>> >>> Done. I have also did >> >> s/did/made :) >> >> Andrei >
Received on Friday, 3 April 2009 14:38:22 UTC