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

RE: DOM based API

From: Alec Berntson <alecb@windows.microsoft.com>
Date: Fri, 6 Jun 2008 11:07:19 -0700
To: Andrei Popescu <andreip@google.com>, Maciej Stachowiak <mjs@apple.com>
CC: Mark Baker <distobj@acm.org>, "public-geolocation@w3.org" <public-geolocation@w3.org>, "public-webapi@w3.org" <public-webapi@w3.org>
Message-ID: <D8939A2F7A8C124ABE6075E08C52CDCA03F7925A@TK5-EXMBX-W603v.wingroup.windeploy.ntdev.microsoft.com>

  I am new to this WG, but I have been playing with location for a while now. I think Andrei's current set of use cases is pretty well distilled, but I'll throw these out there:

One Shot
  Any application where you just need a location 'seed'
     Get directions from 'here' (opposite of find POI)
     Fill in forms with your current address (good use of reverse geocoding)
     Metadata for any sort of submission (geocode a blog post, email, etc)
     Social networking - play games with people around you (doesn't have to be continuously updated to get the game started)

Position monitoring
  Continuously updating local information (traffic, weather, etc)


-----Original Message-----
From: public-geolocation-request@w3.org [mailto:public-geolocation-request@w3.org] On Behalf Of Andrei Popescu
Sent: Friday, June 06, 2008 10:09 AM
To: Maciej Stachowiak
Cc: Mark Baker; public-geolocation@w3.org; public-webapi@w3.org
Subject: Re: DOM based API

On Fri, Jun 6, 2008 at 5:58 PM, Maciej Stachowiak <mjs@apple.com> wrote:
> On Jun 6, 2008, at 7:55 AM, Mark Baker wrote:
>> On Thu, Jun 5, 2008 at 4:20 PM, Andrei Popescu <andreip@google.com> wrote:
>>> Hello,
>>> I am interested in working on a specification of a DOM API that allows
>>> Web pages to access the user's geolocation information (e.g. latitude
>>> and longitude).
>> I'm very glad to see somebody mention using the DOM API for this kind
>> of information, right off the bat.  I'm a big believer in reuse, and
>> feel that this API is an obvious candidate for reusing the DOM, i.e.
>> providing a "Location" Javascript object that's also a DOM Document.
> I don't understand why you would want the "Location" object to be a DOM
> Document. (It needs a better name, by the way, so it doesn't conflict with
> the Location object that is window.location.) And I don't think that is what
> Andrei had in mind, as I understand it, he just wants an API that aligns
> well with the DOM, not necessarily one that makes non-markup information
> appear to be part of a Document.

That's right, what I meant is that I agree with the fact that this API
should align with existing standards, not that the Location object
itself should be a DOM Document. Anyway, I think we should start with
the use cases first? I'm planning to add a little more detail to that
section of the draft early next week and any feedback on this topic
would be very welcome.

Received on Saturday, 7 June 2008 16:32:40 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:16:27 UTC