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

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 UTC