<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.gmailquote
{mso-style-name:gmail_quote;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>That’s a good point. I think you’re right that the “navigator”
object might make more sense:<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>// Example<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>var location = navigator.getLocation()<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>alert(location.latitude+’, ‘+location.longitude);<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>thoughts?<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Steve Runyon
[mailto:s.runyon@gmail.com] <br>
<b>Sent:</b> Wednesday, February 21, 2007 4:27 PM<br>
<b>To:</b> Ryan Sarver<br>
<b>Subject:</b> Re: [whatwg] Geolocation in the browser<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal>You couldn't use window.location because that's already
used: "the location object represents information about the URL of
any currently open window or of a specific frame" (Danny Goodman,
JavaScript Bible 4e, p 486). How about the navigator object? <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><br>
<br>
<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span class=gmailquote>On 2/21/07, <b>Ryan Sarver</b> <<a
href="mailto:rsarver@skyhookwireless.com">rsarver@skyhookwireless.com</a>>
wrote:</span> <o:p></o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>David,<br>
<br>
The ICBM standard is for geotagging the actual content whereas we are talking
about a standard that lets the content know the location of the User or device
so that the website can be location-aware. <br>
<br>
I want to use as much of the existing standards, but have more questions about
where it should exist in ecosystem and how servers and webpages would expect to
see it and use it.<br>
<br>
-----Original Message-----<br>
From: David Latapie [mailto:<a href="mailto:david@empyree.org">david@empyree.org</a>]<br>
Sent: Wednesday, February 21, 2007 3:56 PM<br>
To: Ryan Sarver<br>
Cc: <a href="mailto:whatwg@lists.whatwg.org">whatwg@lists.whatwg.org </a><br>
Subject: Re: [whatwg] Geolocation in the browser<br>
<br>
On Wed, 21 Feb 2007 15:31:11 -0500, Ryan Sarver wrote:<br>
> - would it make sense to also expose it in the request headers?
This<br>
> way the server receives it on the first request as opposed to through <br>
> the client after the initial page request<br>
><br>
><br>
><br>
> User-Geolocation: 43.338018, -71.817930<br>
<br>
Surely you've heard of ICBM<br>
(<meta name="ICBM" content="46.025507, 14.300186" />)<br>
<br>
Could elaborate on what you like and dislike on this?<br>
--<br>
</david_latapie>
U+0F00<br>
<a href="http://blog.empyree.org/en">http://blog.empyree.org/en</a> (English)<br>
<a href="http://blog.empyree.org/fr">http://blog.empyree.org/fr</a> (Français)<br>
<a href="http://blog.empyree.org/sl">http://blog.empyree.org/sl</a> (Slovensko)<br>
<br>
<o:p></o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>