<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"	>
<channel>
	<title>Comments on: Geotagging Public Broadcasting</title>
	<atom:link href="http://johntynan.com/archives/26/feed" rel="self" type="application/rss+xml" />
	<link>http://johntynan.com/archives/26</link>
	<description>A friendly journal for introspection, wonder and bliss.</description>
	<lastBuildDate>Sun, 20 Feb 2011 17:09:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: A Standard REST API for Public Broadcasting? :: John Tynan&#8217;s Fifteen Minute Break</title>
		<link>http://johntynan.com/archives/26/comment-page-1#comment-4655</link>
		<dc:creator>A Standard REST API for Public Broadcasting? :: John Tynan&#8217;s Fifteen Minute Break</dc:creator>
		<pubDate>Mon, 19 Nov 2007 03:22:42 +0000</pubDate>
		<guid isPermaLink="false">http://johntynan.com/archives/26#comment-4655</guid>
		<description>[...] Craig Rosa&#8217;s comment about microformats had me thinking&#8230; how does the taxononomy/lexicon for [...]</description>
		<content:encoded><![CDATA[<p>[...] Craig Rosa&#8217;s comment about microformats had me thinking&#8230; how does the taxononomy/lexicon for [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Tynan</title>
		<link>http://johntynan.com/archives/26/comment-page-1#comment-3138</link>
		<dc:creator>John Tynan</dc:creator>
		<pubDate>Fri, 10 Aug 2007 23:57:10 +0000</pubDate>
		<guid isPermaLink="false">http://johntynan.com/archives/26#comment-3138</guid>
		<description>Andy,  do you think NPR will start to include Latitude / Longitude as part of the metadata associated with each story?  

Any stop-gap measures that you all can put in place for the immediate present? 

Do you see how something like this would be useful for things like national elections, etc.?

Now, if we could get buy in from all reporters at the station level, and from stations throughout the network to include location information as part of their rss feed...</description>
		<content:encoded><![CDATA[<p>Andy,  do you think NPR will start to include Latitude / Longitude as part of the metadata associated with each story?  </p>
<p>Any stop-gap measures that you all can put in place for the immediate present? </p>
<p>Do you see how something like this would be useful for things like national elections, etc.?</p>
<p>Now, if we could get buy in from all reporters at the station level, and from stations throughout the network to include location information as part of their rss feed&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: andy carvin</title>
		<link>http://johntynan.com/archives/26/comment-page-1#comment-3053</link>
		<dc:creator>andy carvin</dc:creator>
		<pubDate>Tue, 07 Aug 2007 17:20:58 +0000</pubDate>
		<guid isPermaLink="false">http://johntynan.com/archives/26#comment-3053</guid>
		<description>Here&#039;s a crude attempt at mapping NPR world news stories using Pipes. As you&#039;ll see, it puts some stories in the right location, but not others.

http://pipes.yahoo.com/pipes/pipe.info?_id=2DJyowdF3BGYEvETzKky6g</description>
		<content:encoded><![CDATA[<p>Here&#8217;s a crude attempt at mapping NPR world news stories using Pipes. As you&#8217;ll see, it puts some stories in the right location, but not others.</p>
<p><a href="http://pipes.yahoo.com/pipes/pipe.info?_id=2DJyowdF3BGYEvETzKky6g" rel="nofollow">http://pipes.yahoo.com/pipes/pipe.info?_id=2DJyowdF3BGYEvETzKky6g</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: andy carvin</title>
		<link>http://johntynan.com/archives/26/comment-page-1#comment-3052</link>
		<dc:creator>andy carvin</dc:creator>
		<pubDate>Tue, 07 Aug 2007 16:43:32 +0000</pubDate>
		<guid isPermaLink="false">http://johntynan.com/archives/26#comment-3052</guid>
		<description>I still haven&#039;t had a chance to fully explore yahoo pipes, but I&#039;m wondering if its &quot;content analysis&quot; tool could be used to determine the location of a story, then place it on a map. I know this wouldn&#039;t always work well - like a story about a soldier&#039;s homecoming from Iraq to Iowa could be displayed as taking place in Iraq even though it&#039;s in Iowa - but it might be an interesting way to experiment and see how content would get displayed.</description>
		<content:encoded><![CDATA[<p>I still haven&#8217;t had a chance to fully explore yahoo pipes, but I&#8217;m wondering if its &#8220;content analysis&#8221; tool could be used to determine the location of a story, then place it on a map. I know this wouldn&#8217;t always work well &#8211; like a story about a soldier&#8217;s homecoming from Iraq to Iowa could be displayed as taking place in Iraq even though it&#8217;s in Iowa &#8211; but it might be an interesting way to experiment and see how content would get displayed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Olson</title>
		<link>http://johntynan.com/archives/26/comment-page-1#comment-1271</link>
		<dc:creator>Tim Olson</dc:creator>
		<pubDate>Wed, 09 May 2007 06:44:45 +0000</pubDate>
		<guid isPermaLink="false">http://johntynan.com/archives/26#comment-1271</guid>
		<description>As recording devices increasingly record GPS location at point of capture, it will be interesting to see the applications and uses that develop as we make the data available.

Tim Olson
KQED</description>
		<content:encoded><![CDATA[<p>As recording devices increasingly record GPS location at point of capture, it will be interesting to see the applications and uses that develop as we make the data available.</p>
<p>Tim Olson<br />
KQED</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Tynan</title>
		<link>http://johntynan.com/archives/26/comment-page-1#comment-1262</link>
		<dc:creator>John Tynan</dc:creator>
		<pubDate>Tue, 08 May 2007 23:46:02 +0000</pubDate>
		<guid isPermaLink="false">http://johntynan.com/archives/26#comment-1262</guid>
		<description>Here&#039;s a reply from Paul Burrows at WGBH:

The quick answer would be to use the *coverage* and *coverageType*  metadata fields, specifically using *spatial coverage*.  Geophysical  enumerations, rather than place names, could be folded into this  field, like they are with Dublin Core.

On Dublin Core&#039;s web page...
http://dublincore.org/documents/dces/

They state under the &quot;Term Name coverage&quot;...
&quot;Spatial topic may be a named place or a location specified by its  geographic coordinates.&quot;

This method can be considered a legitimate use of *spatial coverage*  within PBCore.

Paul Burrows</description>
		<content:encoded><![CDATA[<p>Here&#8217;s a reply from Paul Burrows at WGBH:</p>
<p>The quick answer would be to use the *coverage* and *coverageType*  metadata fields, specifically using *spatial coverage*.  Geophysical  enumerations, rather than place names, could be folded into this  field, like they are with Dublin Core.</p>
<p>On Dublin Core&#8217;s web page&#8230;<br />
<a href="http://dublincore.org/documents/dces/" rel="nofollow">http://dublincore.org/documents/dces/</a></p>
<p>They state under the &#8220;Term Name coverage&#8221;&#8230;<br />
&#8220;Spatial topic may be a named place or a location specified by its  geographic coordinates.&#8221;</p>
<p>This method can be considered a legitimate use of *spatial coverage*  within PBCore.</p>
<p>Paul Burrows</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Tynan</title>
		<link>http://johntynan.com/archives/26/comment-page-1#comment-1256</link>
		<dc:creator>John Tynan</dc:creator>
		<pubDate>Tue, 08 May 2007 22:03:29 +0000</pubDate>
		<guid isPermaLink="false">http://johntynan.com/archives/26#comment-1256</guid>
		<description>Hi Craig!

Thanks for the comment!  I appreciate your mentioning microformats, lending your support to this idea and clarifying its relevancy to our mission as broadcasters.

I have not heard about geotagging as part of PubCore, I&#039;ll post the question to the pubcore listserv and let you know.

Let&#039;s keep in touch about this over time.

Best regards,

John T.</description>
		<content:encoded><![CDATA[<p>Hi Craig!</p>
<p>Thanks for the comment!  I appreciate your mentioning microformats, lending your support to this idea and clarifying its relevancy to our mission as broadcasters.</p>
<p>I have not heard about geotagging as part of PubCore, I&#8217;ll post the question to the pubcore listserv and let you know.</p>
<p>Let&#8217;s keep in touch about this over time.</p>
<p>Best regards,</p>
<p>John T.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Craig Rosa</title>
		<link>http://johntynan.com/archives/26/comment-page-1#comment-1248</link>
		<dc:creator>Craig Rosa</dc:creator>
		<pubDate>Tue, 08 May 2007 16:59:01 +0000</pubDate>
		<guid isPermaLink="false">http://johntynan.com/archives/26#comment-1248</guid>
		<description>Hi John:

Craig from QUEST here. I appreciate you bringing up the topic of geotagging public media stories. I think it has huge potential.

We too have begun adding geotags to our QUEST RSS video feed for iTunes and other RSS readers. Similar to what you&#039;ve done with your feed above.

We&#039;ve adopted the georss standard, which makes it really simple:

http://www.georss.org

Another intriguing possibility is to just mark up existing/ongoing content with geo info via microformats:

http://microformats.org/wiki/geo

If the big question of the last couple years on the web was about personalization (the &quot;who?&quot;) then the next big question is about localization (the &quot;where?&quot;), And who better to provide  news and stories about local issues than public media? Community is about place, and we can only serve our community better by making place a factor in our web services.

Has there been any discussion of geo information regarding PBCore? I didn&#039;t immediately see it in the spec. 

p.s. Also, just a quick point of clarification, all of the TV and Radio stories for QUEST are geotagged and presented on a Google map on the QUEST home page as well:

http://www.kqed.org/quest</description>
		<content:encoded><![CDATA[<p>Hi John:</p>
<p>Craig from QUEST here. I appreciate you bringing up the topic of geotagging public media stories. I think it has huge potential.</p>
<p>We too have begun adding geotags to our QUEST RSS video feed for iTunes and other RSS readers. Similar to what you&#8217;ve done with your feed above.</p>
<p>We&#8217;ve adopted the georss standard, which makes it really simple:</p>
<p><a href="http://www.georss.org" rel="nofollow">http://www.georss.org</a></p>
<p>Another intriguing possibility is to just mark up existing/ongoing content with geo info via microformats:</p>
<p><a href="http://microformats.org/wiki/geo" rel="nofollow">http://microformats.org/wiki/geo</a></p>
<p>If the big question of the last couple years on the web was about personalization (the &#8220;who?&#8221;) then the next big question is about localization (the &#8220;where?&#8221;), And who better to provide  news and stories about local issues than public media? Community is about place, and we can only serve our community better by making place a factor in our web services.</p>
<p>Has there been any discussion of geo information regarding PBCore? I didn&#8217;t immediately see it in the spec. </p>
<p>p.s. Also, just a quick point of clarification, all of the TV and Radio stories for QUEST are geotagged and presented on a Google map on the QUEST home page as well:</p>
<p><a href="http://www.kqed.org/quest" rel="nofollow">http://www.kqed.org/quest</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.493 seconds -->

