In addition to KQED’s Quest Explorations is there anyone else out there Geotagging their stories within public broadcasting? More importantly, is there any kind of a national initiative to get stations / webcasters to start doing this?
I’ve have testing the ability to map KJZZ’s news stories here:
using, for example, the following rss feed:
http://kjzz.org/search/georss?keyword=immigration&size=5
http://kjzz.org/search/rss?keyword=immigration&size=5
I’ve also started testing this with Yahoo Pipes.
It would be interesting to see what a world map would look like if NPR was geotagging their stories, or what a national map would look like if we aggregated stories from public broadcasting stations across the country.
Are there other stations doing this, or considering doing this, with their stories? If so, should there a dialog between stations about aggregating stories and about the possibilties and best practices for mapping stories?
Is there some kind of national initiative for at stations across the system to start serving their content in this way. Is there support for Andy Carvin’s Election 2.0 Task Force where he says:
we must promote open standards for aggregating content – consistent tagging protocols at the station level, heavy use of RSS to pull content together, distributed content modules that can exist simultaneously on local and national websites, etc – to allow all us to mix and mashup these resources so they can surface at the local and national level.
What are your thoughts and experiences?
A Standard REST API for Public Broadcasting? ...
I am intrigured by Andy Carvin’s suggestion of forming an Election 2.0 Task Force where:
Additionally, Craig Rosa’s comment about microformats had me thinking… how does the taxononomy/lexicon for describing objects using microformats inform how we might structure a database of web resources? While I know PBCore is noble and vast and everything, it’s primary goal is to be used for digital asset management – not for web sites (please let me know if I am wrong in my thinking about this). Are there content management systems out there which use microformats as a naming standard for metadata right out of the box? And how would this help facilitate a consistent “tagging protocol?” Also, in looking for how we might do this, I wonder if RSS is only the tip of the iceberg. Does this also mean a standard API for searching (and retrieving) RSS… if so, does this imply a standard REST protocol for querying a station web site and getting information back? I did a quick search for “common api standard REST” and came up with this modest proposal: Atom Will Change the World which contains a sprinkling of all the best buzzwords: Atom, GeoRSS, Dublin Core, etc. etc. But what it also says is that Atom is not only a syndication format, it’s also a publishing protocol:
This article goes on to say:
and that Atom
Shoot! Should I, as a webmaster at a public radio station, be implementing Atom feeds and moving towards an ideal of a standard API? And is the API already out there? Should I be learning about the Atom publishing protocol?