Various proposals over the years have been made for a Geolocation API in
HTML5. Since the W3C has now started work on a Geolocation API
specification, I do not intend to add such an API to HTML5.
If you are interested in this work I recommend following this mailing
list:
and do you send it to third party servers? should doubleclick be able
to automatically target their ads based on precise location?
If the container page/site is able to access location via any of these
mechanisms, there is little to nothing that the user-agent can do to prent that
site from
Perhaps you could do something similar with the HTTP mechanism, but I
don't know how, exactly.
Another issue with the HTTP headers approach is that it doesn't seem
like a natural fit for offline-enabled web apps that want to use the
location info offline.
Right. I am not advocating the HTTP
On 3/21/08, Shyam Habarakada [EMAIL PROTECTED] wrote:
If the container page/site is able to access location via any of these
mechanisms, there is little to nothing that the user-agent can do to prent
that site from forwarding the information to an ad provider. In other words,
the privacy
On Fri, Mar 7, 2008 at 1:03 AM, Aaron Boodman [EMAIL PROTECTED] 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
On Mar 19, 2008, at 8:44 PM, Benjamin West wrote:
On Fri, Mar 7, 2008 at 1:03 AM, Aaron Boodman [EMAIL PROTECTED] 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
Given that location may change with time, Position should (must?) also include
the Time at which the particular value was produced. Optionally, it would also
be good to have the Position describe 'how' the location was determined (GPS,
cell-tower triangulation, etc.)
shyam
-Original
Hi Vlad, thanks for the reply.
On Mon, Mar 17, 2008 at 9:31 PM, Vladimir Vukicevic [EMAIL PROTECTED] wrote:
So, some feedback on the proposal... overall, I think that this API should
be kept as simple as possible. To that end, I would suggest:
I agree with the sentiment :)
- remove
Hi Aaron,
On Mar 7, 2008, at 1:03 AM, Aaron Boodman 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.
I agree with the previously stated comments that this probably doesn't
belong in
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
Dnia 05-03-2008, Śr o godzinie 23:36 -0800, Aaron Boodman pisze:
Hi all,
We're adding an API to Google Gears that will allow an application to
obtain (with permission) the user's current location.
Here's our current design:
http://code.google.com/p/google-gears/wiki/LocationAPI
We
On Thu, Mar 6, 2008 at 8:14 AM, Krzysztof Żelechowski
[EMAIL PROTECTED] wrote:
The intersection of this interface with HTML is empty
and it will always be because it does not hook on anything to declare.
It qualifies as a browser extension.
How is it different than the HTML5 database API?
Dnia 06-03-2008, Cz o godzinie 08:30 -0800, Aaron Boodman pisze:
On Thu, Mar 6, 2008 at 8:14 AM, Krzysztof Żelechowski
[EMAIL PROTECTED] wrote:
The intersection of this interface with HTML is empty
and it will always be because it does not hook on anything to declare.
It qualifies as a
Aaron Boodman wrote:
On Thu, Mar 6, 2008 at 8:14 AM, Krzysztof Żelechowski
[EMAIL PROTECTED] wrote:
The intersection of this interface with HTML is empty and it will
always be because it does not hook on anything to declare.
It qualifies as a browser extension.
How is it different
2008/3/6 Aaron Boodman [EMAIL PROTECTED]:
On Thu, Mar 6, 2008 at 8:14 AM, Krzysztof Żelechowski
[EMAIL PROTECTED] wrote:
The intersection of this interface with HTML is empty
and it will always be because it does not hook on anything to declare.
It qualifies as a browser extension.
2008/3/6 Brian Smith [EMAIL PROTECTED]:
It isn't. See
http://blog.mozilla.com/rob-sayre/2008/02/19/bloaty-parts-of-the-whatwg-
html5-specification-that-should-be-removed/
In particular, see Ian Hickson's comment. He already acknoledged that
this stuff doesn't belong in the HTML
Aaron Boodman wrote:
2008/3/6 Brian Smith [EMAIL PROTECTED]:
It isn't. See
http://blog.mozilla.com/rob-sayre/2008/02/19/bloaty-parts-of-the-whatwg-
html5-specification-that-should-be-removed/
In particular, see Ian Hickson's comment. He already acknoledged that
this stuff doesn't
2008/3/6 Aaron Boodman [EMAIL PROTECTED]:
How is it different than the HTML5 database API?
It's not. Neither belongs in an HTML specification, but a charismatic
leader should be able to overcome this obstacle.
--
Robert Sayre
Hi all,
We're adding an API to Google Gears that will allow an application to
obtain (with permission) the user's current location.
Here's our current design:
http://code.google.com/p/google-gears/wiki/LocationAPI
We think there's a lot of potential for interesting applications with
an API
19 matches
Mail list logo
