Frequently Asked Questions - to be updated shortly

What is URIplay?

URIplay is a name service for media content, giving each file a URI and a simple description. Think of it as DNS for media. The service is not intended to be used directly by viewers. Like DNS, it works behind the scenes to make things easier.

What problem does it solve?

It helps users to immediately find the right version of a media file. This is necessary because media distribution has become very complex. A single piece of media is often available through numerous routes, including:

Live off-air
From recordings
'On-demand' services

The routes available to the user depend on the specification of one's equipment and software. Is it cable, satellite, antenna? Is the user in time to watch/ listen to the repeat? Did the DVR record it? Does the user have HDTV? Surround sound? If yes, great, but what type?

The rights owners add extra complexity for the viewer by attempting to restrict content availability. They control access according to where the viewer is located, which service the viewer uses to find content, and when the viewer wants to watch it.

URIplay summarises all this information so that user's software and hardware can make the choices itself.

So, what does URIplay do?

URIplay helps media software and hardware answer two questions:

What is the name of a media file?
I want to tell someone about the show I'm watching/ listening to, but what reliable name can I use?
Where can I find a media file?
I know a reliable name, but where can I find a copy that will work with my hardware and my software?

We are developing a spec for the URIplay RDF ontology.

Can't search engines already do this?

Not very well. There are several problems:

It's complex.
Search engines typically require a person to choose the result, then navigate through to the actual media file. We want online media to be as simple as channel surfing on a TV set or radio.
Data is missing.
Technical and legal restrictions mean that search engines rarely list a wide range of locations where a media file can be obtained.
Only some content works.
Simple show/ season/ episode names (like 'West.Wing.s02e21') are common. These are sufficient for long-running shows, but not much good for a one-off, or a regular show like the news. What about video blogs, podcasts, or short films? Some of the richness of TV, radio, and wider media experiences is lost with this scheme.

How will you make this happen?

With a little help from our friends. This needs to be a community effort, owned by a broad group of interested parties.

We will:

Suggest a small new XML vocabulary, and an API for running URIplay services.
Set up a first server that receives and outputs URIplay data.
Import a small set of information.
Participate in a broad community that runs the service.

We will not:

Control data—data we receive will be made available under a licence that has the minimum possible restrictions.
Run the only server—this service is designed to encourage splitting data across many servers, controlled by many organisations.
Own intellectual property—code will be released under an open source licence, and we will not file patents.
Do other bad stuff—this list is not exhaustive. We won't do anything else that the community considers inappropriate.

We need help with:

Developing the XML vocabulary and rules
Marshalling data
Moderating and editing data
Adding support for URIplay to applications
Releasing copyrighted data
Running servers

How does URIplay relate to existing standards?

We build on existing standards to a feasible extent. We employ XML and RDF, reusing existing vocabularies as much as possible. The URIplay vocabulary is inspired by TV Anytime and XMLTV, although we have found that neither alone can be used as a starting point.

Is this just for video, or will you cover other media?

Video is the first priority. We believe that is a broad enough problem to tackle first. We'll provide a format that can work for audio and other media that one can 'play'; also, other types of media might come later.

Who is behind URIplay?

A first version is being developed by MetaBroadcast, a London-based start-up that develops video distribution software. This phase of work is being supported financially by BBC.

We're keen to involve as many people as possible. We're very open to suggestions and offers of assistance, and have already been in contact with a wide range of organisations and individuals. To get in touch or contribute to the project, come join our Google Group.

How much progress has been made?

The ideas for URIplay were formed in writing on Chris's blog, following discussions with Ashok over many years. We hope there's something in the air, and that other people have been thinking along the same lines.

Chris summarised a vision of Simple Social Broadcasting, then laid out some of the ideas behind URIplay, and delivered a presentation at the unfestival track of the Edinburgh International Television Festival in August 2007.

In autumn 2007 BBC offered us financial support to develop these ideas into a full prototype. Lee Denison came onboard as a full-time software engineer. Lee and Chris have formed MetaBroadcast to develop a first version of URIplay, alongside several other projects.

What are the future plans?

We will update this site as the project progresses, and aim to release a first working service in March 2009.