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

>
>
> But we also have two open issues that should be closed before we go  
> to last call:
>
> 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 still don't like having this attribute and would be quite content to  
have it just be dropped.  If we don't great agreement on doing that, i  
would be okay with "useLowPower".


> 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).
>
> There hasn't really been any discussion on this issue. Are there any  
> objections to moving the "heading" and "speed" attributes out of the  
> Coordinates interface and into a new Velocity interface?


How about dropping them from V1, and consider them, as a new Velocity  
interface w/ associated option flags, for V2?

Doug