Re: skeleton Geolocation API

Hi all,

Thanks for the feedback! I've updated the draft editor spec:

- Removed the reverse geocoding.
- Removed locationResolvers property.
- Attempted to clarify the definition of the getCurrentPosition() and
watchPosition().
- Mentioned that we default to WGS84 for the coordinate system and
added an issue about supporting other geodetic systems.
- Added links to the mailing list discussions around "enableHighAccuracy".

I'd be very grateful if you could have another look and let me know
what you think, especially if there are any fundamental changes that
are still needed (things around the overall API design, things that
should be addressed or should be left out, etc).

Many thanks,
Andrei

Received on Thursday, 26 June 2008 21:09:23 UTC