W3C home > Mailing lists > Public > public-geolocation@w3.org > June 2008

Re: skeleton Geolocation API

From: Aaron Boodman <aa@google.com>
Date: Thu, 26 Jun 2008 17:08:54 -0700
Message-ID: <278fd46c0806261708h100b0cebo2fabf2c17333ec8a@mail.gmail.com>
To: "Erik Wilde" <dret@berkeley.edu>
Cc: public-geolocation@w3c.org, "Andrei Popescu" <andreip@google.com>

On Thu, Jun 26, 2008 at 4:35 PM, Erik Wilde <dret@berkeley.edu> wrote:
> i still think that http://dev.w3.org/geo/api/spec-source.html#position is
> just too limited in its model of location. a location can be a lat/long pair
> of coordinates, but it also can be something else, like the identification
> of a city or a state or some other place-oriented location concept.

I'm not sure how this would work.

We are trying to implement a way for web applications to get the
current position of the user. Having the user actually specify this
seems useful to some subset of users, but having it be automatic seems
better for most users.

Automatically generating a URI like this seems like it would be a lot
of work, and greatly increase the specification size. And it probably
requires reverse geocoding. And I don't see that it buys any
additional privacy over just chopping digits off the coordinates.

- a
Received on Friday, 27 June 2008 00:09:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 22 March 2012 18:13:39 GMT