W3C home > Mailing lists > Public > public-geolocation@w3.org > June 2009

Re: updated editor's draft of the Geolocation API specification

From: Greg Bolsinga <bolsinga@apple.com>
Date: Mon, 8 Jun 2009 19:26:46 -0700
Cc: Andrei Popescu <andreip@google.com>, public-geolocation <public-geolocation@w3.org>
Message-Id: <04FFD545-07A7-4B74-ABF8-6D172E9930C0@apple.com>
To: Lars Erik Bolstad <lbolstad@opera.com>
On Jun 8, 2009, at 2:29 PM, Lars Erik Bolstad wrote:
> ISSUE-6: enableHighAccuracy, "Is enableHighAccuracy the right naming  
> for this attribute? Should we have it at all?"
> We seemed to have consensus on renaming it, with a few members in  
> favour of dropping it completely.
> Allan Thomson proposed to replace it with "reducedPowerHint", along  
> with a definition:
> http://lists.w3.org/Archives/Public/public-geolocation/2009Apr/0034.html
> Is anyone against resolving ISSUE-6 by replacing enableHighAccuracy  
> and its definition with Allan's proposal?

I describe "enableHighAccuracy" as a hint to people myself. I don't  
have an opinion if it should change.

> ISSUE-7: heading & speed, "Should heading & speed be moved out of  
> the Coordinates interface?"
> Given that Geolocation API v2 will have support for address, should  
> 'heading' and 'speed' attributes be moved out of the Coordinates  
> interface? They could go to a separate interface (e.g. Velocity) so  
> that implementation can return any combination of (coords, velocity,  
> address).


I have no opinion on this.

FWIW, iPhone 3.0 announced today (and out June 17) will support both  
of these names.

-- Greg
Received on Tuesday, 9 June 2009 02:27:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 22 March 2012 18:13:44 GMT