Posts Tagged ‘David Rogers’

Keep It Simple, Smarty: How the BBC Is Expanding Their Linked Data Platform

At the Semantic Technology and Business Conference last June in San Francisco, David Rogers of the BBC was on-hand to educate attendees on the origins and progress of the BBC’s impressive Linked Data Platform. In his presentation, Rogers — who serves as Senior Technical Architect for BBC Future Media (News & Knowledge) — explained how the news giant’s use of semantic technologies has evolved since they first turned to Linked Data to better report on the 2010 World Cup. Currently, the BBC Linked Data Platform works with content across the company, including news, sports, music, location, and learning.

Rogers started things off with a little history. Leading up to the 2010 World Cup, the BBC wanted to create a sports website, and they found that RDF triplestores were the best way to connect and organize their player, team, and tournament information. Pleased with what they’d accomplished, the BBC amped things up a few notches for the 2012 Olympics. Everything got scaled up, their data became more dynamic, and all while relying on the simplest metadata possible. Before the Olympics, the BBC Sports website had information on 300 athletes. By the end, 1,100 athletes were covered semantically, allowing the BBC’s vast pool of reporters to all draw upon the same data and interlink their content in an easily discoverable manner. Read more

RDF Tree: An Updated Approach

Last week David Rogers wrote about RDF tree. He said, “I want to make RDF data more developer-friendly. When you show a typical developer RDF, where they have previously been used to simple JSON or XML structures, they find the format confusing, and hard to code with. This is primarily because the data is a graph, and graphs don’t fit well with the tree structures of JSON and XML. I have seen this problem tackled through the use of libraries that can parse and interpret the graph data, and present an easier interface to the developer. Whilst these have been useful, I still think there are some fundamental problems. JSON-LD also offers a solution to this problem, but is not sufficiently lightweight for environments where data structures change and develop regularly. I compare my approach with JSON-LD at the end of the post.” Read more