- From: Andrei Popescu <andreip@google.com>
- Date: Mon, 16 Mar 2009 16:50:17 +0000
- To: public-geolocation <public-geolocation@w3.org>
Hi, I have uploaded the first editor's draft for the Geolocation API v2 (or level 2): http://dev.w3.org/geo/api/spec-source-v2.html The main change is the addition of the Address interface. Following the evidence presented in the thread at http://lists.w3.org/Archives/Public/public-geolocation/2009Feb/0000.html I concluded that the scheme based on a simplified RFC4119 is the best choice so far. It is also reasonably close to the proposal made by Alec Berntson. One thing we have not discussed is the extension to the PositionOptions interface. Alec proposed something similar to the following: interface PositionOptions { (...) const unsigned short COORDS_REQUIRED = 0; // default const unsigned short ADDRESS_REQUIRED = 1; const unsigned short EITHER = 2; readonly unsigned short positionType; } Where: COORDS_ONLY = The API only returns position objects when coords has data, address can be null ADDRESS_ONLY = The API only returns position objects when address has data, coords can be null EITHER = The API returns a position object whenever there is data for either address or coords data. Should we also have BOTH_REQUIRED as a fourth option? Thanks, Andrei
Received on Monday, 16 March 2009 16:50:54 UTC