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

Re: skeleton Geolocation API

From: Aaron Boodman <aa@google.com>
Date: Sun, 29 Jun 2008 13:15:21 -0700
Message-ID: <278fd46c0806291315l34daabd9v7af064879b9fd8fc@mail.gmail.com>
To: "Erik Wilde" <dret@berkeley.edu>
Cc: public-geolocation@w3c.org, straup@gmail.com

On Sun, Jun 29, 2008 at 11:11 AM, Erik Wilde <dret@berkeley.edu> wrote:
>> At a minimum, that would allow people to identify what system is being
>> used for Plain Old Points (tm) and in the hand-waving future leave some
>> wiggle room for the kinds of things that Erik mentions and stuff no one has
>> imagined yet.
>
> i like the general idea. this would also allow contexts in which no lat/long
> information is given at all. for each context, there would have to be a
> definition which parts of a position (lat/log, elevation, uri, bearing,
> speed) can/must be present, and how they are defined. if it is done that
> way, there would have to be at least three context identifiers for wgs84
> coordinates, though, because elevation should at least be supported for
> plain wg84, egm96, and barometric values.

I think it is better for the web if we choose one way to interpret the
API. Interop is hard to achieve when the developer has to be ready for
many different measurement systems.

- a
Received on Sunday, 29 June 2008 20:16:05 GMT

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