W3C home > Mailing lists > Public > public-geolocation@w3.org > November 2010

RE: Geolocation provide API

From: Thomson, Martin <Martin.Thomson@andrew.com>
Date: Thu, 18 Nov 2010 08:35:10 +0800
To: Doug Turner <dougt@dougt.org>
CC: "public-geolocation@w3.org Group WG" <public-geolocation@w3.org>
Message-ID: <8B0A9FCBB9832F43971E38010638454F03F33EA4FC@SISPE7MB1.commscope.com>
On 2010-11-18 at 11:23:46, Doug Turner wrote:
> Recall, the basic idea is to allow sites to set
> up their own location provider so that places like universities,
> hospitals, can provide wifi positioning inside of their campuses.  

That's an admirable goal.  I'm interested in how you reached the conclusion that Geolocation API changes are part of the solution.  That's not a conclusion that I would have reached.

It helps to examine the reasons that a locally operator provider is useful.  Is it accuracy alone that you care about?  Is it the case that the local provider is better capable of providing more accurate location?

If that's the case, then provider selection is still better handled by something other than the site serving pages.  For instance, you could configure multiple providers in the browser.  If the global provider indicates a location within a campus, the browser could activate the more accurate provider for that campus.  

By the same token, you could use automatically discovered network services (i.e., RFC5985/5986).

--Martin
Received on Thursday, 18 November 2010 00:35:57 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:51:01 UTC