Content modeling & FOAF — this is really very good stuff — you should read these then subscribe to Paul’s blog
Paul’s experiments with FOAF and Doctor Who
“I chose the first ever episode of the show, from 1963. This featured four main characters, and thanks to the workshop from Yves and the others, I had an inkling of an understanding of how to create FOAF profiles. The results can be seen here (best viewed if you use a Firefox plugin like Tabulator). So far so good. I then linked each character to the other, using the simple ‘knows’ relationship. Finally, to get my linked open data brownie points, I linked each character to its DBpedia equivalent, using the OWL ’same as’ relationship.” Modeling Doctor Who is going to be cool esp if Paul looks at the different incarnations of the Doctor (different actors + different version).
Part three of Paul’s investigation into fictional content modeling and FOAF
One thing that has come up in the discussions, though, is that there’s perhaps two elements to what I’m trying to achieve. The first is to link existing ontologies and, if needed, build a new one, to help describe the narrative content of ’stories’ within the context of television and radio programmes. The second is to experiment (and for me to learn) with existing ontologies, again, linking them up, to build dynamic and interesting webpages that work on linked data principles.
SUDS an ontology (an extension to FOAF) for Soap operas [author stream presentation]
Celia Romaniuk’s presentation on SUDS and it’s application to Eastenders.
Visualising radio — I can’t but applaud the team and I love the technology but does the idea make sense? I’m not so sure…
… a bit like ‘enhanced podcast’ (you know podcasts with pictures) because my iPod lives in my pocket as far as I’m concerned the images are just a waste of bandwidth; likewise visual radio. That said it’s well worth checking out.
Visual radio launch announced [BBC Radio Labs]
Snippets of information delivered over http to visualise the Chris Moyles show.
Visualising Radio, pushing, not pulling [whomwah.com]
A bit of technical background from Duncan. “So, the big news here is that we are pushing and not pulling. Ordinarily, you would request a webpage using your browser and a some data would be returned. The only way that you would then subsequently see any changes to that data, would be if you requested it again, or if something on that page requested it for you, maybe via polling.”
These are just great…
In Search of Cultural Identifiers [BBC – Radio Labs]
Getting this stuff right is really the first job in any web project. Identify the objects you want to talk about and model the relations between those objects. The key point is to ensure the things you model map to user’s mental models of the world. User centric design starts here and if you choose to model and expose things that users can’t easily comprehend no amount of product requirements or personaes or storyboards will help you out. For want of a better label we A&M types often refer to this work as ‘cultural identifiers’. One identifier, one URL, one page per cultural artifact, all interlinked. It’s something that Wikipedia does better than anyone. One page per concept, one concept per page. bbc.co.uk could be a much more pleasant place to be if we can build something similar for the BBC.
Teaching a Six Year Old About Triples [Lost Boy]
“I suggested to him that we try drawing it out. I thought that this might help him get a better mental picture. I explained to him that we could try writing down the characters names and start drawing lines between them to illustrate the relationships. He got it straight away.” This is brilliant and shows just how intuitive RDF is.
Wikipedia over DNS [DgL]
“I had written some code to take wikipedia articles and summarise them. I wanted to offer this for use in various places, now the obvious way to offer it is just a web service (via REST, SOAP, etc), but that’s boring and I had a cunning plan. Why not offer it over DNS – it is basically a huge associative array and DNS is designed for this stuff. So I wrote a little nameserver which returns the results as TXT records. There are some obvious limitations for example responses are limited to around 430 bytes (it only does UDP). It has advantages too, it gets cached at your nameserver and it is also faster than HTTP (no need to setup a TCP session).” Such a cool idea and lovely URLs too.