{"id":200,"date":"2005-06-03T17:07:48","date_gmt":"2005-06-03T17:07:48","guid":{"rendered":"\/ifbookblog\/?p=200"},"modified":"2005-06-03T17:07:48","modified_gmt":"2005-06-03T17:07:48","slug":"remixing_the_news","status":"publish","type":"post","link":"https:\/\/futureofthebook.org\/blog\/2005\/06\/03\/remixing_the_news\/","title":{"rendered":"remixing the news"},"content":{"rendered":"<p>There&#8217;s been an explosion of creative tinkering since the BBC opened up its API (applications programming interface) last month. An API is a window into a site&#8217;s code and content allowing techie types to build new applications with BBC material. It&#8217;s really worth going over to the <a href=\"http:\/\/backstage.bbc.co.uk\/prototypes\/\">BBC Backstage blog<\/a> to take a look at the first batch of prototypes and demos. The majority are clever splicings of BBC data &#8211; news, traffic reports, images etc. &#8211; with <a href=\"http:\/\/maps.google.com\">Google Maps<\/a> (everyone&#8217;s favorite lately), not unlike <a href=\"http:\/\/www.chicagocrime.org\">chicagocrime.org<\/a>. Other notable examples: an <a href=\"http:\/\/backstage.bbc.co.uk\/prototypes\/archives\/2005\/04\/bbc_complaints.html\">RSS feed of BBC complaints<\/a>; a feature that allows you to <a href=\"http:\/\/backstage.bbc.co.uk\/prototypes\/archives\/2005\/05\/bbc_shared_tags.html\">tag articles<\/a> and read tags left by other readers; and a nice <a href=\"http:\/\/www.justinflavin.com\/tagsoup\/tagsoupfinance.php\">&#8220;tag soup&#8221;<\/a> visualization of financial news.<\/p>\n<blockquote><p><b>Correction: A <a href=\"\/blog\/archives\/2005\/06\/remixing_the_ne.html#c497\">reader<\/a> kindly pointed out that BBC Backstage hasn&#8217;t actually released APIs yet (though they intend to soon). The projects I&#8217;ve referenced use BBC feeds, or have scraped content directly from the BBC site. APIs are to follow soon (more info <a href=\"http:\/\/backstage.bbc.co.uk\/data\/Data\">here<\/a>). When they do, the scaping process will become much cleaner. For now, the BBC welcomes projects that &#8220;use our stuff to build your stuff&#8221; the rough-and-tumble way, and is happy to showcase them on the Backstage site.<\/b><\/p><\/blockquote>\n<p>The API is becoming a powerful tool for creative reinvention of the web. Back in April, I <a href=\"\/blog\/archives\/2005\/04\/web_30_all_cons.html\">wrote<\/a> about <a href=\"http:\/\/dangillmor.typepad.com\/dan_gillmor_on_grassroots\/2005\/04\/web_20_try_30.html\">Dan Gillmor&#8217;s piece<\/a> on &#8220;Web 3.0&#8221;.. Web 1.0 was the early web, a place you went to read &#8211; a series of interconnected brochures. Web 2.0 is the &#8220;read-write&#8221; web &#8211; it&#8217;s a place you go to interact. Web 3.0 is where we start weaving the disparate pieces into new forms. APIs let you do this. You take one application and design a new front end that shows your point of view. Or you take two applications and mix them together, creating something new and illuminating. Right now, Web 2.0 is pretty well in place. The tools for self-expression and interaction are pretty accessible &#8211; email, chat, blogs, etc. But the weaving tools required for 3.0 are available only to advanced users. We&#8217;ll see if that changes.<br \/>\nHere are grabs from four of the map prototypes at BBC Backstage:<br \/>\n<a href=\"http:\/\/backstage.bbc.co.uk\/prototypes\/archives\/2005\/05\/traffic_maps.html\">Traffic Maps:<\/a><br \/>\n<img loading=\"lazy\" decoding=\"async\" alt=\"BBC traffic map.jpg\" img border=\"1;\" src=\"\/blog\/archives\/BBC traffic map.jpg\" width=\"384\" height=\"335\" \/><br \/>\n<a href=\"http:\/\/backstage.bbc.co.uk\/prototypes\/archives\/2005\/05\/map_of_bbc_lond.html\"><br \/>\nMap of BBC London Jam Cams:<\/a><br \/>\n<img loading=\"lazy\" decoding=\"async\" alt=\"BBC traffic cam map.jpg\" img border=\"1;\" src=\"\/blog\/archives\/BBC traffic cam map.jpg\" width=\"466\" height=\"253\" \/><br \/>\n<a href=\"http:\/\/backstage.bbc.co.uk\/prototypes\/archives\/2005\/05\/photo_mapping.html\"><br \/>\nPhoto Mapping:<\/a><br \/>\n<img loading=\"lazy\" decoding=\"async\" alt=\"BBC photo map.jpg\" img border=\"1;\" src=\"\/blog\/archives\/BBC photo map.jpg\" width=\"369\" height=\"367\" \/><br \/>\n<a href=\"http:\/\/backstage.bbc.co.uk\/prototypes\/archives\/2005\/05\/a_map_of_the_ne.html\"><br \/>\nMap of the News:<\/a><br \/>\n<img loading=\"lazy\" decoding=\"async\" alt=\"BBC news map cricket.jpg\" img border=\"1;\" src=\"\/blog\/archives\/BBC news map cricket.jpg\" width=\"450\" height=\"340\" \/><br \/>\nFor more analysis, check out this <a href=\"http:\/\/radar.oreilly.com\/archives\/2005\/05\/google_maps_and.html\">article on O&#8217;Reilly Radar<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>There&#8217;s been an explosion of creative tinkering since the BBC opened up its API (applications programming interface) last month. An API is a window into a site&#8217;s code and content allowing techie types to build new applications with BBC material. It&#8217;s really worth going over to the BBC Backstage blog to take a look at [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1547,1591],"tags":[2481],"class_list":["post-200","post","type-post","status-publish","format-standard","hentry","category-publishing-broadcast-and-the-press","category-remix","tag-google-googlemaps-bbc-bbcbackstage-api-web-online-internet-web3-0-gilmor-hack-remix"],"_links":{"self":[{"href":"https:\/\/futureofthebook.org\/blog\/wp-json\/wp\/v2\/posts\/200","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/futureofthebook.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/futureofthebook.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/futureofthebook.org\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/futureofthebook.org\/blog\/wp-json\/wp\/v2\/comments?post=200"}],"version-history":[{"count":0,"href":"https:\/\/futureofthebook.org\/blog\/wp-json\/wp\/v2\/posts\/200\/revisions"}],"wp:attachment":[{"href":"https:\/\/futureofthebook.org\/blog\/wp-json\/wp\/v2\/media?parent=200"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/futureofthebook.org\/blog\/wp-json\/wp\/v2\/categories?post=200"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/futureofthebook.org\/blog\/wp-json\/wp\/v2\/tags?post=200"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}