<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 http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<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;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.gmailquote
{mso-style-name:gmail_quote;}
span.q
{mso-style-name:q;}
span.EmailStyle20
{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'>Steve, good points…<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'>It’s also important to remember that this functionality
would be an opt-in system – unlike your cell phone :) The prototype that
we are working on would allow the browser to point to a COM port where it could
find a GPS device or any NMEA-compatible device or software. It would then read
the NMEA stream over the COM port and use that to deliver the user’s
location to the website via the DOM.<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'>Our software positions you based on WiFi triangulation and can
emulate a GPS device by streaming NMEA over a virtual COM port so that the
user wouldn’t need to have a dedicated GPS antennae.<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:48 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>Makes sense to me. And while the privacy issues that
others have brought up are real, it does seem doable to make it
user-configurable. Perhaps the first time the user hits a site that wants
to know where they are they have the more-or-less standard "disallow/allow
this time/always allow" options? <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>And as with cell phones (which in the US at least
must include location info when the user dials 911 for help), there should
be reasonable guarantees that intelligence agencies and law enforcement can't
activate the locator unbeknownst to the user without a search warrant. <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>
<div>
<div>
<p><span style='font-size:11.0pt;color:#1F497D'>That's a good point. I think
you're right that the "navigator" object might make more sense:</span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'>// Example</span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'>var location =
navigator.getLocation()</span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'>alert(location.latitude+',
'+location.longitude);</span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'>thoughts?</span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p><b><span style='font-size:10.0pt'>From:</span></b><span style='font-size:
10.0pt'> Steve Runyon [mailto:<a href="mailto:s.runyon@gmail.com"
target="_blank">s.runyon@gmail.com </a>] <br>
<b>Sent:</b> Wednesday, February 21, 2007 4:27 PM<br>
<b>To:</b> Ryan Sarver<br>
<span class=q><b>Subject:</b> Re: [whatwg] Geolocation in the browser</span></span><o:p></o:p></p>
</div>
<p> <o:p></o:p></p>
<div>
<p>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><br>
<br>
<o:p></o:p></p>
</div>
<div>
<p>On 2/21/07, <b>Ryan Sarver</b> <<a
href="mailto:rsarver@skyhookwireless.com" target="_blank">rsarver@skyhookwireless.com</a>>
wrote: <o:p></o:p></p>
<p 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" target="_blank">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" target="_blank">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" target="_blank">http://blog.empyree.org/en</a>
(English)<br>
<a href="http://blog.empyree.org/fr" target="_blank">http://blog.empyree.org/fr</a>
(Français)<br>
<a href="http://blog.empyree.org/sl" target="_blank">http://blog.empyree.org/sl</a>
(Slovensko)<o:p></o:p></p>
</div>
<p> <o:p></o:p></p>
</div>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>