W3C home > Mailing lists > Public > whatwg@whatwg.org > March 2008

[whatwg] Geolocation API Proposal

From: Benjamin West <bewest@gmail.com>
Date: Wed, 19 Mar 2008 19:44:02 -0800
Message-ID: <8ad71be30803192044r6b1f4f6ah36aae246e8398ec4@mail.gmail.com>
On Fri, Mar 7, 2008 at 1:03 AM, Aaron Boodman <aa at google.com> wrote:
> I've posted this to the W3C WebAPI mailing list as well. Still looking
>  forward to feedback on the actual content of the proposal, in either
>  place.
>
>  Thanks,
>
>  - a
>

What use cases are drive this proposal?
If the use case is for user agents to describe their geographical
location to applications, then one possible solution is to wield web
architecture, and use an HTTP header.
User agents might send something like:

    X-Agent-Lat: 1234123
    X-Agent-Lon: -2132362

This frames the problem in terms of an application being interested in
the properties of the client, instead of the client needing to know
about properties of the client so they can eventualy send a request to
an application with the same information.

That said, if the client does need to know, it might be easier to
simply give user script the ability to sniff and edit outbound headers,
with which you can build the proposed API.

Most of the features in you proposal seem to deal with geocoding, and
I've ignored that here.  The notion of sensitivity to time was
interesting, but I suspect HTTP headers would be adequate for that as
well.

Would a solution like this satisfy the requirements necessary for the
use cases that drive your proposal?

-Ben
Received on Wednesday, 19 March 2008 20:44:02 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:40 UTC