<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="http://feeds.feedburner.com/~d/styles/rss2full.xsl" type="text/xsl" media="screen"?><?xml-stylesheet href="http://feeds.feedburner.com/~d/styles/itemcontent.css" type="text/css" media="screen"?><!-- generator="wordpress/2.0.10" --><rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>The geoURI scheme</title>
	<link>http://geouri.org</link>
	<description>a Uniform Resource Identifier for geographic locations</description>
	<pubDate>Fri, 06 Jul 2007 08:45:30 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.10</generator>
	<language>en</language>
			<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/geouri" type="application/rss+xml" /><feedburner:browserFriendly></feedburner:browserFriendly><item>
		<title>Internet Draft updated to version 01</title>
		<link>http://geouri.org/2007/07/06/internet-draft-updated-to-version-01/</link>
		<comments>http://geouri.org/2007/07/06/internet-draft-updated-to-version-01/#comments</comments>
		<pubDate>Fri, 06 Jul 2007 08:38:56 +0000</pubDate>
		<dc:creator>alex</dc:creator>
		
		<category>Drafting</category>
<category>ietf</category><category>internet draft</category><category>standardization</category>
		<guid isPermaLink="false">http://geouri.org/2007/07/06/internet-draft-updated-to-version-01/</guid>
		<description><![CDATA[The Internet Draft specifying the &#8220;geo:&#8221; URI has been updated, the new version is already available from the IETF draft archives.
The new version 01 (which is the second version after 00) removes the &#8220;query&#8221; part of the URI, as this was pretty much underspecified in the initial version, and has proven to be rather controversial. [...]]]></description>
			<content:encoded><![CDATA[<p>The <a href="http://www.ietf.org/internet-drafts/draft-mayrhofer-geo-uri-01.txt" onclick="javascript:urchinTracker ('/outbound/article/www.ietf.org');">Internet Draft specifying the &#8220;geo:&#8221; URI</a> has been updated, the new version is already available from the <a href="http://tools.ietf.org/html/draft-mayrhofer-geo-uri-01" onclick="javascript:urchinTracker ('/outbound/article/tools.ietf.org');">IETF draft archives</a>.</p>
<p>The new version 01 (which is the second version after 00) removes the &#8220;query&#8221; part of the URI, as this was pretty much underspecified in the initial version, and has proven to be rather controversial. Since it does not actually identify the spatial location, but provides meta information (like location classification &#038; type, preferred map scale) we decided to remove it from the specification.</p>
<p>Please note that this is work in progress, which also means that any feedback is appreciated.
</p>
]]></content:encoded>
			<wfw:commentRss>http://geouri.org/2007/07/06/internet-draft-updated-to-version-01/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Presentation at IETF 68, Prague</title>
		<link>http://geouri.org/2007/03/21/presentation-at-ietf-68-prague/</link>
		<comments>http://geouri.org/2007/03/21/presentation-at-ietf-68-prague/#comments</comments>
		<pubDate>Wed, 21 Mar 2007 14:53:19 +0000</pubDate>
		<dc:creator>alex</dc:creator>
		
		<category>Drafting</category>
<category>geo</category><category>geouri</category><category>ietf</category><category>ietf68</category><category>presentation</category>
		<guid isPermaLink="false">http://geouri.org/2007/03/21/presentation-at-ietf-68-prague/</guid>
		<description><![CDATA[The Internet Engineering Task Force is currently hosting it&#8217;s 68th meeting in the Hilton Hotel, Prague, Czech Republic.
The geo: URI proposal is on the agenda of tomorrows session of the Geographic Location/Privacy working group:

GEOPRIV WG meeting
March 22, 2007, 9:00 - 11:30
IETF 68, Hilton Hotel Prague, Room &#8220;Congress I&#8221;

According to the agenda, the presentation of the [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://geouri.org/wp-content/uploads/2007/03/geo-uri-ietf68.pdf" ><img align="right" id="image11" alt="IETF68 slides" src="http://geouri.org/wp-content/uploads/2007/03/ietf-slides.png" /></a>The <a href="http://www.ietf.org/" onclick="javascript:urchinTracker ('/outbound/article/www.ietf.org');">Internet Engineering Task Force</a> is currently hosting it&#8217;s 68th meeting in the <a href="http://geouri.org/geo:50.09318,14.43892,203" >Hilton Hotel, Prague, Czech Republic</a>.</p>
<p>The <a href="/2007/02/24/internet-draft-about-geo-uri-published/">geo: URI proposal</a> is on the agenda of tomorrows session of the <a href="http://www.ietf.org/html.charters/geopriv-charter.html" onclick="javascript:urchinTracker ('/outbound/article/www.ietf.org');">Geographic Location/Privacy working group</a>:</p>
<ul>
<li><strong>GEOPRIV WG meeting</strong></li>
<li>March 22, 2007, 9:00 - 11:30</li>
<li>IETF 68, Hilton Hotel Prague, Room &#8220;Congress I&#8221;</li>
</ul>
<p>According to the <a href="http://www3.ietf.org/proceedings/07mar/agenda/geopriv.txt" onclick="javascript:urchinTracker ('/outbound/article/www3.ietf.org');">agenda</a>, the presentation of the &#8220;geo&#8221; URI scheme is scheduled for about <strong>10:55</strong>.</p>
<p>For remote participation, session audio will be available via the <a href="http://videolab.uoregon.edu/events/ietf/ietf68.html" onclick="javascript:urchinTracker ('/outbound/article/videolab.uoregon.edu');">IETF audio streaming effort</a> (Channel 1), a supplemental Jabber discussion room at <a href="http://geouri.org/xmpp:geopriv@jabber.ietf.org" >geopriv@jabber.ietf.org</a> can be used as a backchannel for remote participants to ask questions and provide feedback.</p>
<p><a href="http://geouri.org/wp-content/uploads/2007/03/geo-uri-ietf68.pdf"id="p12"  >Slides of the presentation</a>
</p>
]]></content:encoded>
			<wfw:commentRss>http://geouri.org/2007/03/21/presentation-at-ietf-68-prague/feed/</wfw:commentRss>
		</item>
		<item>
		<title>“geo:” URI JavaScript parser</title>
		<link>http://geouri.org/2007/03/12/geo-uri-javascript-parser/</link>
		<comments>http://geouri.org/2007/03/12/geo-uri-javascript-parser/#comments</comments>
		<pubDate>Mon, 12 Mar 2007 15:19:01 +0000</pubDate>
		<dc:creator>Christian</dc:creator>
		
		<category>Applications</category>
<category>geouri</category><category>Gutenkarte</category><category>JavaScript</category><category>jQuery</category><category>Mashup</category><category>Parser</category>
		<guid isPermaLink="false">http://geouri.org/2007/03/12/geo-uri-javascript-parser/</guid>
		<description><![CDATA[As another proof of concept I wrote a little &#8220;geo:&#8221; URI JavaScript parser.
Basically it scans all anchors in a given text for &#8220;geo:&#8221; links, extracts location and meta information (e.g. coordinates and corresponding text), places them on a map and appends the map to the text.
I choose to go with a Google Map because I [...]]]></description>
			<content:encoded><![CDATA[<p>As another proof of concept I wrote a little &#8220;geo:&#8221; URI JavaScript parser.<br />
Basically it scans all anchors in a given text for &#8220;geo:&#8221; links, extracts location and meta information (e.g. coordinates and corresponding text), places them on a map and appends the map to the text.</p>
<p>I choose to go with a Google Map because I already knew the API, so it was the easiest way. Of course one could modify the script to use any other mapping API&#8217;s, create a KML or even transfer the data to a GIS application. If I can free some time in the next weeks I&#8217;ll spice the script a little up, some more user defined parameters (e.g. map dimension, marker symbols) and the interpretation of query arguments would be nice though.</p>
<p>See a quick example <a href="http://www.spanring.eu/geouri/"title="geoURI JavaScript parser example"  onclick="javascript:urchinTracker ('/outbound/article/www.spanring.eu');">here</a>: the locations of a few cultural venues are marked with &#8220;geo:&#8221; anchors, scanned by the script and dynamically shown in the map below.</p>
<p>However, if you&#8217;re interested you can download the JavaScript file <a href="http://www.spanring.eu/geouri/lib/geouriparser.js"title="geoURI JavaScript parser"  onclick="javascript:urchinTracker ('/outbound/article/www.spanring.eu');">here</a>. You&#8217;ll need a copy of <a href="http://jquery.com/"title="jQuery"  onclick="javascript:urchinTracker ('/outbound/article/jquery.com');">jQuery</a> (I used version 1.1.2) and a valid Google Maps key for your domain too. Then just add the corresponding 3 script elements (Google key, jQuery and geouriparser.js) into the head of your document and let the script find and display the geoURIs in your text.</p>
<p>The idea is heavily inspired by <a href="http://gutenkarte.org/"title="Gutenkarte"  onclick="javascript:urchinTracker ('/outbound/article/gutenkarte.org');">Gutenkarte</a>, a presentation of <a href="http://labs.metacarta.com/"title="MetaCarta Labs"  onclick="javascript:urchinTracker ('/outbound/article/labs.metacarta.com');">MetaCarta Labs</a> I remembered from last year&#8217;s Where 2.0 conference. Gutenkarte is based on MetaCarta&#8217;s Geoparser API, which is of course far more complex than my few lines JavaSrcipt code.
</p>
]]></content:encoded>
			<wfw:commentRss>http://geouri.org/2007/03/12/geo-uri-javascript-parser/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Firefox extension handles “geo:” URI</title>
		<link>http://geouri.org/2007/02/26/firefox-extension-handles-geo-uri/</link>
		<comments>http://geouri.org/2007/02/26/firefox-extension-handles-geo-uri/#comments</comments>
		<pubDate>Mon, 26 Feb 2007 15:52:38 +0000</pubDate>
		<dc:creator>alex</dc:creator>
		
		<category>Applications</category>
<category>extension</category><category>firefox</category><category>geo</category><category>geouri</category><category>mapping</category><category>plugin</category><category>spatial</category>
		<guid isPermaLink="false">http://geouri.org/2007/02/26/firefox-extension-handles-geo-uri/</guid>
		<description><![CDATA[The first version of a firefox extension to handle geo-URIs is now available. The plugin uses a proxy to forward &#8216;geo:&#8217; requests to a mapping service (currently Google Maps, we&#8217;re planning to make this configurable RSN).

(click screenshot to install)
The extension should be compatible with Firefox 1.5 and above - You might need to allow software [...]]]></description>
			<content:encoded><![CDATA[<p>The first version of a <a href='http://www.mozilla.com/'>firefox</a> extension to handle geo-URIs is now available. The plugin uses a proxy to forward &#8216;geo:&#8217; requests to a mapping service (currently Google Maps, we&#8217;re planning to make this configurable RSN).</p>
<p><a href='http://p.geouri.org/download/geoURI-0.0.1.xpi'><img src='/wp-content/uploads/2007/02/geo-firefox-plugin.jpg'></a><br />
<em>(click screenshot to install)</em></p>
<p><a href='http://p.geouri.org/download/geoURI-0.0.1.xpi'>The extension</a> should be compatible with Firefox 1.5 and above - You might need to allow software installations from &#8220;p.geouri.org&#8221;, and firefox will need to be restarted.</p>
<p>After installation, clicking on the following link should bring up a map of Vienna&#8217;s city centre:</p>
<p><a href='geo:48.208333,16.372778'>geo:48.208333,16.372778</a></p>
<p>As usual, feedback is appreciated - please note that this extension is currently at a &#8220;proof of concept&#8221; level, subsequent versions will provide more choice of mapping services via a configuration option. The extension should detect new versions automatically as we release them.
</p>
]]></content:encoded>
			<wfw:commentRss>http://geouri.org/2007/02/26/firefox-extension-handles-geo-uri/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Internet Draft about “geo” URI published</title>
		<link>http://geouri.org/2007/02/24/internet-draft-about-geo-uri-published/</link>
		<comments>http://geouri.org/2007/02/24/internet-draft-about-geo-uri-published/#comments</comments>
		<pubDate>Sat, 24 Feb 2007 09:42:22 +0000</pubDate>
		<dc:creator>alex</dc:creator>
		
		<category>Drafting</category>
<category>draft</category><category>geo</category><category>geouri</category><category>ietf</category><category>ietf68</category><category>internet draft</category><category>spatial</category><category>uri</category>
		<guid isPermaLink="false">http://geouri.org/2007/02/24/internet-draft-about-geo-uri-published/</guid>
		<description><![CDATA[The first version of the geo-URI specification is now available as an Internet Draft on the IETF web site (announcement). An Internet Draft is the first step towards publication of a specification as an RFC.
The draft specifies syntax, format and semantics of the &#8220;geo&#8221; URI - it also requests registration of the respective Uniform Resource [...]]]></description>
			<content:encoded><![CDATA[<p>The first version of the geo-URI specification is now available as an <a href='http://www.ietf.org/internet-drafts/draft-mayrhofer-geo-uri-00.txt'>Internet Draft</a> on the <a href='http://www.ietf.org/'>IETF</a> web site (<a href='http://www1.ietf.org/mail-archive/web/i-d-announce/current/msg13979.html'>announcement</a>). An Internet Draft is the first step towards publication of a specification as an RFC.</p>
<p>The draft specifies syntax, format and semantics of the &#8220;geo&#8221; URI - it also requests registration of the respective Uniform Resource Identifier scheme (&#8221;geo:&#8221;) from <a href='http://www.iana.org/'>IANA</a>.</p>
<p>The draft will be presented during the session of the GEOPRIV (&#8221;<em>geographic location and privacy</em>&#8220;) working group on the <a href='https://datatracker.ietf.org/public/meeting_agenda_html.cgi?meeting_num=68'>68th IETF meeting</a>, taking place March 18-23, 2007 in Prague. The GEOPRIV session is currently scheduled for Tuesday, March 20, 0900 - 1130. Audio streaming will be available from <a href='http://videolab.uoregon.edu/events/ietf/'>here</a>.</p>
<p>Comments and feedback on the <a href='http://www.ietf.org/internet-drafts/draft-mayrhofer-geo-uri-00.txt'>Internet Draft</a> is appreciated.</p>
]]></content:encoded>
			<wfw:commentRss>http://geouri.org/2007/02/24/internet-draft-about-geo-uri-published/feed/</wfw:commentRss>
		</item>
		<item>
		<title>geoURI primer</title>
		<link>http://geouri.org/2007/02/17/geo-uri-primer/</link>
		<comments>http://geouri.org/2007/02/17/geo-uri-primer/#comments</comments>
		<pubDate>Sat, 17 Feb 2007 15:28:11 +0000</pubDate>
		<dc:creator>alex</dc:creator>
		
		<category>Drafting</category>
<category>geo</category><category>geographic</category><category>iana</category><category>ietf</category><category>internet draft</category><category>mapping</category><category>spatial</category><category>uri</category>
		<guid isPermaLink="false">http://geouri.org/2007/02/17/geo-uri-primer/</guid>
		<description><![CDATA[More and more protocols and data formats are being extended by methods to add geographic information. However, all of those options are tied to that specific protocol or data format.
A dedicated Uniform Resource Identifier (URI) scheme for geographic locations would be independent from any protocol, usable by any software/data format that can handle generich URIs. [...]]]></description>
			<content:encoded><![CDATA[<p>More and more protocols and data formats are being extended by methods to add geographic information. However, all of those options are tied to that specific protocol or data format.</p>
<p>A dedicated Uniform Resource Identifier (URI) scheme for geographic locations would be independent from any protocol, usable by any software/data format that can handle generich URIs. Like a &#8220;mailto:&#8221; URI launches your favourite mail application today, a &#8220;geo:&#8221; URI could soon launch your favourite mapping service, or queue that location for a navigation device.</p>
<p>Making the format as simple as possible allows to jot down &#8220;geo:&#8221; URIs, like you jot down email addresses today. An example for a simple &#8220;geo:&#8221; URI (<a href="http://en.wikipedia.org/wiki/St._Stephen%27s_Cathedral%2C_Vienna" onclick="javascript:urchinTracker ('/outbound/article/en.wikipedia.org');">St. Stephen&#8217;s Cathedral, Vienna, Austria</a>) could look like:</p>
<p><a href="geo:48.208333,16.372778">geo:48.208333,16.372778</a><br />
(you browser will not be able to handle this Link yet, of course)</p>
<p>This blog is about the development of the &#8220;geo:&#8221; URI scheme. The first goal is the publication of an Internet Draft withing the <a href="http://www.ietf.org/" onclick="javascript:urchinTracker ('/outbound/article/www.ietf.org');">IETF</a>, probably progressing it to a RFC, and having the URI scheme registered with <a href="http://www.iana.org/" onclick="javascript:urchinTracker ('/outbound/article/www.iana.org');">IANA</a>.
</p>
]]></content:encoded>
			<wfw:commentRss>http://geouri.org/2007/02/17/geo-uri-primer/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
