<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet title="XSL_formatting" type="text/xsl" href="/blogs/shared/nolsol.xsl"?>

<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>

<title>
BBC Internet Blog
 - 
Michael Smethurst
</title>
<link>https://bbcbreakingnews.pages.dev/blogs/bbcinternet/</link>
<description>Staff from the BBC&apos;s online and technology teams talk about BBC Online, BBC iPlayer, and the BBC&apos;s digital and mobile services. The blog is reactively moderated. Posts are normally closed for comment after three months. Your host is Eliza Kessler. </description>
<language>en</language>
<copyright>Copyright 2012</copyright>
<lastBuildDate>Thu, 10 Sep 2009 17:13:02 +0000</lastBuildDate>
<generator>http://www.sixapart.com/movabletype/?v=4.33-en</generator>
<docs>http://blogs.law.harvard.edu/tech/rss</docs> 


<item>
	<title>A skim-read introduction to linked data</title>
	<description><![CDATA[<p><strong>Editor's note: If you've ever been embarrassed about your knowledge, or lack of knowledge, about the Semantic Web, RDF or Linked Data (I'm at the front of this particular queue) then have a look at the slide-show on the Radio Labs blog. (PM)</strong></p>

<p><a href="http://www.meetup.com/londonwebstandards/calendar/10791931/">Last night</a> me and <a href="http://moustaki.org/">Yves</a> gave a presentation to the <a href="http://www.londonwebstandards.org/">London Web Standards</a> group on <a href="http://linkeddata.org/">Linked Data</a>. We promised to put the slides online...</p>

<p><em>Go to the Radio Labs blog to read the rest of <a href="https://bbcbreakingnews.pages.dev/blogs/radiolabs/2009/09/a_skimread_introduction_to_lin.shtml">A skim-read introduction to linked data, to view the slide show and to leave your comments. </a></em></p>]]></description>
         <dc:creator>Michael Smethurst 
Michael Smethurst
</dc:creator>
	<link>https://bbcbreakingnews.pages.dev/blogs/bbcinternet/2009/09/a_skimread_introduction_to_lin.html</link>
	<guid>https://bbcbreakingnews.pages.dev/blogs/bbcinternet/2009/09/a_skimread_introduction_to_lin.html</guid>
	<category>open standards</category>
	<pubDate>Thu, 10 Sep 2009 17:13:02 +0000</pubDate>
</item>

<item>
	<title>Designing for your least able user</title>
	<description><![CDATA[<blockquote>To use a tortuous analogy a well designed website should be like a cubist painting: the spaces between things are as important as the things themselves - where things in this case means pages and spaces means links. Sorry!...</blockquote>

<p><img style="visibility:hidden;width:0px;height:0px;" border=0 width=0 height=0 src="http://counters.gigya.com/wildfire/IMP/CXNID=2000002.0NXC/bT*xJmx*PTEyMzcyOTY1MjU2OTImcHQ9MTIzNzI5NzMwNzYzMSZwPTEwMTkxJmQ9Jmc9MiZ*PSZvPWQ3ZDMwMmY3NDZiNjRjOTdiNDkzMmUyNTZjZjY1NDVi.gif" /><div style="width:425px;text-align:left" id="__ss_1152901"><a style="font:14px Helvetica,Arial,Sans-serif;display:block;margin:12px 0 3px 0;text-decoration:underline;" href="http://www.slideshare.net/fantasticlife/designing-for-your-least-able-user?type=presentation" title="Designing For Your Least Able User">Designing For Your Least Able User</a><object style="margin:0px" width="425" height="355"><param name="movie" value="http://static.slideshare.net/swf/ssplayer2.swf?doc=designingforyourleastableuser-090316150101-phpapp02&stripped_title=designing-for-your-least-able-user" /><param name="allowFullScreen" value="true"/><param name="allowScriptAccess" value="always"/><embed src="http://static.slideshare.net/swf/ssplayer2.swf?doc=designingforyourleastableuser-090316150101-phpapp02&stripped_title=designing-for-your-least-able-user" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="425" height="355"></embed></object><div style="font-size:11px;font-family:tahoma,arial;height:26px;padding-top:2px;">View more <a style="text-decoration:underline;" href="http://www.slideshare.net/">presentations</a> from <a style="text-decoration:underline;" href="http://www.slideshare.net/fantasticlife">fantasticlife</a>.</div></div></p>

<p><em>Michael Smethurst is Information Architect, Audio & Music Interactive, BBC FM&T.</em></p>

<p><a href="https://bbcbreakingnews.pages.dev/blogs/radiolabs/2009/03/designing_for_your_least_able.shtml">Read more</a> (and there is a lot more!) and <a href="https://bbcbreakingnews.pages.dev/blogs/radiolabs/2009/03/designing_for_your_least_able.shtml#P77314119">comment</a> at BBC Radio labs blog.</p>]]></description>
         <dc:creator>Michael Smethurst 
Michael Smethurst
</dc:creator>
	<link>https://bbcbreakingnews.pages.dev/blogs/bbcinternet/2009/03/designing_for_your_least_able.html</link>
	<guid>https://bbcbreakingnews.pages.dev/blogs/bbcinternet/2009/03/designing_for_your_least_able.html</guid>
	<category>accessibility</category>
	<pubDate>Wed, 18 Mar 2009 11:36:40 +0000</pubDate>
</item>

<item>
	<title>How we make websites</title>
	<description><![CDATA[<p>For the past few months I've been touting a presentation around the BBC entitled 'How we make websites'. It's a compendium of everything our team has learned from long years developing <a href="https://bbcbreakingnews.pages.dev/programmes">/programmes</a>, the recent work on <a href="https://bbcbreakingnews.pages.dev/music/beta">/music </a>and the currently in development /events.</p>

<p>As a warning there's very little original thinking in here. For those familiar with the concept of <a href="http://www.w3.org/TR/mobile-bp/">one web</a>, the importance of <a href="http://www.w3.org/Provider/Style/URI">persistent URIs</a>, <a href="http://www.w3.org/Provider/Style/URI">REST</a>, <a href="http://en.wikipedia.org/wiki/Domain-driven_design">Domain Driven Design </a>and <a href="http://linkeddata.org/">Linked Open Data </a>it'll probably be old news. Possibly it's interesting to see all these threads tied up in one place!?! Maybe it's interesting to see them all from a user experience point of view?!? Anyway, as ever, it's built on the <a href="http://roy.gbiv.com/">thinking</a> <a href="http://www.domainlanguage.com/about/ericevans.html">and</a> <a href="http://tomheath.com/home/html">achievements</a> <a href="http://moustaki.org/">of</a> <a href="http://twitter.com/hellomatty">many</a> <a href="http://twitter.com/onpause">clever</a> <a href="http://twitter.com/onpause">people</a> <a href="http://www.aelius.com/njh/">over</a> <a href="http://www.metade.org/">many</a> <a href="https://bbcbreakingnews.pages.dev/blogs/bbcinternet/jamie_tetlow/">years</a> <a href="http://whomwah.com/">who</a> <a href="http://twitter.com/rjolly">are</a> <a href="http://jonathan.tweed.name/">too</a> <a href="http://www.hackdiary.com/">numerous</a> <a href="http://www.plasticbag.org/">to</a> <a href="http://interconnected.org/home/">mention</a> <a href="http://www.cookinrelaxin.com/">here</a>. Although obviously I'll make an exception for Paul Clifford and <a href="http://dig.csail.mit.edu/breadcrumbs/node/215">TimBL.</a> :)</p>

<p><img alt="DomainDrivenDesign.jpg" src="https://bbcbreakingnews.pages.dev/blogs/bbcinternet/img/DomainDrivenDesign.jpg" width="429" height="321" /></p>

<p>The presentation is <a href="http://www.slideshare.net/fantasticlife/how-we-make-websites-presentation?type=presentation">here</a> and the (slightly) expanded text is <a href="https://bbcbreakingnews.pages.dev/blogs/radiolabs/2009/01/how_we_make_websites.shtml">below</a> for the sake of accessibility and Google.</p>

<p><em>Read more and comment <a href="https://bbcbreakingnews.pages.dev/blogs/radiolabs/2009/01/how_we_make_websites.shtml">at BBC Radio Labs.</a></em></p>

<p><em>Michael Smethurst is Information Architect, A&Mi, BBC Future Media & Technology</em><br />
</p>]]></description>
         <dc:creator>Michael Smethurst 
Michael Smethurst
</dc:creator>
	<link>https://bbcbreakingnews.pages.dev/blogs/bbcinternet/2009/01/how_we_make_websites.html</link>
	<guid>https://bbcbreakingnews.pages.dev/blogs/bbcinternet/2009/01/how_we_make_websites.html</guid>
	<category>BBC Online</category>
	<pubDate>Sat, 31 Jan 2009 18:57:02 +0000</pubDate>
</item>

<item>
	<title>In search of Cultural Identifiers</title>
	<description><![CDATA[<p><a href="http://flickr.com/photos/candiedwomanire/1651870/"><img alt="books.jpg" src="https://bbcbreakingnews.pages.dev/blogs/bbcinternet/img/books.jpg" width="420" height="315" /></a>Image: "<a href="http://flickr.com/photos/candiedwomanire/1651870/">A Rainbow of Books</a>" by <a href="http://flickr.com/photos/candiedwomanire/">Dawn Indigo</a> on flickr.</p>

<p>Late last year we got quite excited about <a href="http://openlibrary.org/">Open Library</a>. Using the open word always seems to tick our boxes. We chatted about the prospect of a comprehensive, coherent <a href="https://bbcbreakingnews.pages.dev/arts/books/">BBC books site </a>heavily interlinked with <a href="https://bbcbreakingnews.pages.dev/arts/books/">BBC programmes</a>. Every <a href="https://bbcbreakingnews.pages.dev/programmes/b00gftgp">dramatisation of a novel</a>, every <a href="https://bbcbreakingnews.pages.dev/programmes/b006qp7q">poetry reading</a>, every <a href="https://bbcbreakingnews.pages.dev/programmes/b00ghrlb">author interview</a> and <a href="https://bbcbreakingnews.pages.dev/programmes/b00fkgnl">profile</a>, every <a href="https://bbcbreakingnews.pages.dev/programmes/b00gdz3w">play</a> linked to / from programmes. The prospect of new user journeys from programme episode to book to author to poem and back to episode still seems enticing. We started to wonder if we could use Open Library as the backbone of this new service in the same way we use <a href="http://musicbrainz.org/">MusicBrainz</a> open data as the backbone of <a href="https://bbcbreakingnews.pages.dev/music/beta">/music</a>.</p>

<p>Unfortunately when we looked more closely an obvious problem came to light. </p>

<p><strike>Open Libary is based on<a href="http://www.amazon.com/"> Amazon </a>book data and Amazon is based on products. </strike></p>

<p>Correction 16.01.09: OpenLibrary is NOT based on Amazon data (see <a href="https://bbcbreakingnews.pages.dev/blogs/radiolabs/2009/01/in_search_of_cultural_identifi.shtml#comment8">Tim's comment</a>). For now it models books in a similar fashion to Amazon (as publications/products not cultural artifacts). <a href="http://openlibrary.org/about/frbrization">OpenLibrary are looking to enhance this model to allow grouping of publications into works</a> which is fantastic news. If you can <a href="http://openlibrary.org/about/help">contribute code or knowledge</a> I'd encourage you to do so.</p>

<p>And the BBC isn't all that interested in products. Neither are users.</p>

<p><em>Read more and comment at <a href="https://bbcbreakingnews.pages.dev/blogs/radiolabs/2009/01/in_search_of_cultural_identifi.shtml">BBC Radio Labs blog</a>.</em></p>

<p><em>Michael Smethurst is Information Architect, A&Mi, BBC Future Media & Technology</em></p>]]></description>
         <dc:creator>Michael Smethurst 
Michael Smethurst
</dc:creator>
	<link>https://bbcbreakingnews.pages.dev/blogs/bbcinternet/2009/01/in_search_of_cultural_identifi.html</link>
	<guid>https://bbcbreakingnews.pages.dev/blogs/bbcinternet/2009/01/in_search_of_cultural_identifi.html</guid>
	<category>innovation</category>
	<pubDate>Wed, 14 Jan 2009 13:46:24 +0000</pubDate>
</item>

<item>
	<title>Taking the Proms to the semantic web in 10% time</title>
	<description><![CDATA[<p><a href="https://bbcbreakingnews.pages.dev/blogs/radiolabs/2008/09/taking_the_proms_to_the_semant.shtml"><img alt="henry_wood_proms.jpg" src="https://bbcbreakingnews.pages.dev/blogs/bbcinternet/img/henry_wood_proms.jpg" width="200" height="309" style="" /></a>A few weeks back, I had the good fortune to be handed a dump of a mysql database stuffed to the gills with historical <a href="https://bbcbreakingnews.pages.dev/proms/2008/">Proms</a> data. It's got every Prom from <a href="http://bbc-hackday.dyndns.org:2840/seasons/1895">1895</a> to <a href="http://bbc-hackday.dyndns.org:2840/seasons/2007">2007</a> (and (you'd hope) 2008 at some point).</p>

<p>I've started to wrap a <a href="http://www.rubyonrails.org/">Ruby on Rails</a> app around it and the results can be seen <a href="http://bbc-hackday.dyndns.org:2840/">here</a>. For now, it's pretty basic with lots of gaps left to fill - but the intention is to link it to <a href="http://musicbrainz.org/">MusicBrainz</a> / <a href="http://dbpedia.org/About">DBpedia</a> and to publish the results into the <a href="http://esw.w3.org/topic/SweoIG/TaskForces/CommunityProjects/LinkingOpenData">Linking Open Data cloud</a>.</p>

<p><em><a href="https://bbcbreakingnews.pages.dev/blogs/radiolabs/2008/09/taking_the_proms_to_the_semant.shtml">Read more and comment</a> at the BBC Radio Labs blog.</em></p>

<p><em>Michael Smethurst is Information Architect, FM&T for BBC Audio & Music Interactive.</em></p>]]></description>
         <dc:creator>Michael Smethurst 
Michael Smethurst
</dc:creator>
	<link>https://bbcbreakingnews.pages.dev/blogs/bbcinternet/2008/09/taking_the_proms_to_the_semant.html</link>
	<guid>https://bbcbreakingnews.pages.dev/blogs/bbcinternet/2008/09/taking_the_proms_to_the_semant.html</guid>
	<category>Music</category>
	<pubDate>Fri, 05 Sep 2008 12:28:33 +0000</pubDate>
</item>

<item>
	<title>Microformats, RDFa &amp; RDF</title>
	<description><![CDATA[<p>My original post on <a href="https://bbcbreakingnews.pages.dev/blogs/radiolabs/2008/06/removing_microformats_from_bbc.shtml">removing microformats from /programmes</a> seems to have kicked off <a href="http://ejohn.org/blog/bbc-removing-microformat-support/">quite a debate</a>. Unfortunately, some of this seems to have resulted in RDFa people criticising microformats and vice versa. Which wasn't really the intention.</p>

<p><em><a href="https://bbcbreakingnews.pages.dev/blogs/radiolabs/2008/06/microformats_and_rdfa_and_rdf.shtml">Read more and comment at the BBC Radio Labs blog.</a></em></p>

<p><em>Michael Smedhurst is an Information Architect at BBC Audio & Music Interactive.</em></p>]]></description>
         <dc:creator>Michael Smethurst 
Michael Smethurst
</dc:creator>
	<link>https://bbcbreakingnews.pages.dev/blogs/bbcinternet/2008/06/microformats_and_rdfa_and_rdf.html</link>
	<guid>https://bbcbreakingnews.pages.dev/blogs/bbcinternet/2008/06/microformats_and_rdfa_and_rdf.html</guid>
	<category>open standards</category>
	<pubDate>Wed, 25 Jun 2008 11:35:43 +0000</pubDate>
</item>

<item>
	<title>Removing Microformats</title>
	<description><![CDATA[<p><a href="https://bbcbreakingnews.pages.dev/blogs/radiolabs/2008/06/removing_microformats_from_bbc.shtml"><img alt="bbc_programmes_hcalendar.png" src="https://bbcbreakingnews.pages.dev/blogs/bbcinternet/img/bbc_programmes_hcalendar.png" width="120" height="158"  /></a>Since <a href="https://bbcbreakingnews.pages.dev/programmes">/programmes</a> first <a href="https://bbcbreakingnews.pages.dev/blogs/bbcinternet/2007/11/a_page_for_every_programme_1.html">went live</a> we've been working to ensure that programme data was accessible to people and <a href="https://bbcbreakingnews.pages.dev/blogs/radiolabs/2008/05/helping_machines_play_with_pro.shtml">machines</a> alike. The API design was baked in at the application design stage. Similarly we've worked on adding <a href="/go/blogs/radiolabs/2008/06/removing_microformats_from_bbc.shtml/ext/_auto/-/http://microformats.org/">microformats</a> to HTML pages as a lightweight API. All <a href="https://bbcbreakingnews.pages.dev/radio1/programmes/schedules/2008/06/23">broadcasts</a> use the <a href="/go/blogs/radiolabs/2008/06/removing_microformats_from_bbc.shtml/ext/_auto/-/http://microformats.org/wiki/hcalendar">hCalendar</a> microformat to add start times, end times, broadcast channels etc.</p>

<p>Unfortunately there have been a <a href="/go/blogs/radiolabs/2008/06/removing_microformats_from_bbc.shtml/ext/_auto/-/http://www.webstandards.org/2007/04/27/haccessibility/">number of concerns</a> over hCalendar's use of the <a href="/go/blogs/radiolabs/2008/06/removing_microformats_from_bbc.shtml/ext/_auto/-/http://microformats.org/wiki/abbr-design-pattern">abbreviation design pattern</a>. This uses the HTML abbreviation element to add machine data to pages. Our concerns were:<ul><li>the effect on blind users using screen readers with abbreviation expansion turned on where abbreviations designed for machines would be read out</li><li>the effect on partially sighted users using screen readers where tool tips of abbreviations designed for machines would be read out</li><li>the effect of incomprehensible tooltips on users with cognitive disabilities</li><li>the potential fencing off of abbreviations to domains that need them (travel - <a href="/go/blogs/radiolabs/2008/06/removing_microformats_from_bbc.shtml/ext/_auto/-/http://en.wikipedia.org/wiki/IATA_airport_code">airport codes</a>, finance - <a href="/go/blogs/radiolabs/2008/06/removing_microformats_from_bbc.shtml/ext/_auto/-/http://en.wikipedia.org/wiki/Ticker_symbol">ticker symbols</a> etc)</li></ul><br />
    <br />
<p><em><a href="https://bbcbreakingnews.pages.dev/blogs/radiolabs/2008/06/removing_microformats_from_bbc.shtml">Read more and comment at the Radio Labs blog.</a></em></p></p>

<p><em>Michael Smethurst is an Information Architect at BBC Audio & Music Interactive.</em></p>]]></description>
         <dc:creator>Michael Smethurst 
Michael Smethurst
</dc:creator>
	<link>https://bbcbreakingnews.pages.dev/blogs/bbcinternet/2008/06/removing_microformats.html</link>
	<guid>https://bbcbreakingnews.pages.dev/blogs/bbcinternet/2008/06/removing_microformats.html</guid>
	<category>accessibility</category>
	<pubDate>Tue, 24 Jun 2008 10:24:06 +0000</pubDate>
</item>


</channel>
</rss>

 
