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

Re: New attribute suggestion

From: Andrei Popescu <andreip@google.com>
Date: Wed, 3 Dec 2008 15:09:31 +0000
Message-ID: <708552fb0812030709x1d6b9f3ctbd365d05e05fe837@mail.gmail.com>
To: Moon-Sang Lee <sang0627.lee@samsung.com>
Cc: Doug Turner <doug.turner@gmail.com>, public-geolocation@w3.org

Hi,

2008/12/3 Moon-Sang Lee <sang0627.lee@samsung.com>:
>
>
> Hi Doug,
>
>
>
> Thanks for your comment, and I want to mention several things regarding your
> comment.
>
> First of all, as you've shown with a AJAX code, logging feature can be
> implemented in application(script) level. (i.e. I also mentioned it in the
> last paragraph of my original email.) I think this is not about
> possible-impossible problem but about the scope of Geolocation API. If we
> provide the logging feature with Geolocation API, it helps programmers make
> their web applications easy.
>

The use cases you presented are certainly valid but I don't think that
adding the functionality you suggest is in the scope of this API. To
me, this is clearly application logic that can be implemented using
several existing Web APIs. For offline storing of location waypoints,
one can use HTML5's Database API (or even cookies) and periodically do
batch uploads to a server using XHR (as Doug also suggested).

> In addition, we can reduce the logging latency and network traffic if we use
> the extended API. Let's assume  that a network server tells me where I am.
> (i.e. My host device does not have a GPS module or uses a network server for
> position accuracy.) When the logging feature is implemented in application
> level, there should be two network requests, one for acquiring the current
> position and the other for logging the current position. However, we can
> send only one request for both of acquiring and logging the current position
> if the Geolocation API provides remote logging.
>

But that's only the case if the server that gives you location is the
same as the server that does the logging. However, this will probably
be pretty rare in practice. And anyway, if the logging and location
server are one and the same, then you can do the logging
automatically, without the need for any extra arguments in the
Geolocation API, right?

> There are various web browsers, particularly, in mobile devices. And, each
> browser has its own plug-in structure. If we want to log our tracks of
> position into a host storage, we should use browser plug-ins and many
> different plug-ins should be distributed in accordance with the browser we
> use. In a worst case, a fine web page for a browser 'I' would not work on a
> browser 'F' since the 'F' supports only partial of such plug-ins.
>

Right, but I am not sure I understand how adding some extra attributes
to this API would affect this situation.

> I think attributes which seem primitive need to be included in
> standardizing.
>

Agreed. However, in this case these attributes are not 'primitive'.
The functionality they would add can already be implemented using
other standard Web APIs.

Many thanks,
Andrei
Received on Wednesday, 3 December 2008 15:10:12 GMT

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