12. Some simple requirements
Vital Permanent URIs
Vital Deterministic behavior
– A file is available
– It contains the right version
– The file plays
– The quality is high enough
Really Nice Reliable titles, descriptions
and links between episodes
13. Why can’t we just blame the broadcasters?
they don’t own all the rights they care about context
Photo from: Photo from:
http://www.flickr.com/photos/hereinvannuys/1879221392/ http://www.flickr.com/photos/yakanama/276195587/
14. Why can’t we just blame the broadcasters?
Or,
information
friction
Photo from:
http://www.flickr.com/photos/philandpam/1622589139/
17. Good news #2: data exists
Wikipedia Title, synopsis, cast etc
Link
Broadcaster Content URL
websites
TX time
Schedule Transmission times
TX time
Off air data Series linkage
18. What we are doing
1 simple design
• XML Data Format (also RDF)
• API
2 first implementation
3 some crawlers
19. What we are not doing
http://www.flickr.com/photos/mattlogelin/360329081/
21. a little more detail po
URIplay
“show” Brand
“episode” Episode
“bag of frames” Version Broadcast
“bag of bits” Encoding
“uri” Location Policy
22. The API: Main types of URI
http://uriplay.org/$brand(/$episode(/$version(/$encoding)))/
e.g., http://uriplay.org/holby-city/s10e16/
http://broadcast.uriplay.org/$broadcaster/$w3_datetime/
e.g., http://broadcast.uriplay.org/five.tv/2007-02-16T20:00/
http://policy.uriplay.org/$distributor/$identifier/
e.g., http://policy.uriplay.org/bbc.co.uk/iplayer-streaming/
http://api.uriplay.org/lookup/?uri=$uri
23. We’re a service describing resources
Reinvent nothing means:
Big design choice: should we
use RDF?
24. In plain old XML
<Brand>
<title>Yes Minister</title>
<Episode>
http://uriplay.org/yesminister/s01e01/
</Episode>
<Episode>
http://uriplay.org/yesminister/s01e02/
</Episode>
</Brand>
28. RDF: travels of a data source provider
What we like: What we don’t like:
It’s Flexible Flexible = Complex
Inference built in Must Compute
Deductive Extension
Statements must be
It’s Declarative Interpreted
29. What we learned
There is abig difference between an aggregator
and a data source
For a data source:
1 Encode the ontology as application logic and data
model
2 Use views to separate definitive truths from
application details
3 Keep it simple
30.
31. where we’re heading
bbc.co.uk apps
link
discovery.com maker
aggregator
TV
nav
uriplay.org
tagging
wikipedia.com
?
apple.com
33. What do the public and you get out of us doing this?
Easier to choose what you
want
Don't have to care about codecs, etc.
Devices and web services interop
well
We benefit too – you get to play, get
your hands dirty, make stuff with this
that we couldn't
We help a free software project –
we hope it'll help us.
CC licence http://flickr.com/photos/hddod/865542747/
34. Getting involved
Right now we’re finalizing the
first version and design
In two weeks prime time
data time
End of May see it, use it
35. Lets talk more
http://uriplay.org/
http://groups.google.com/group/uriplay/
chris@metabroadcast.com
lee@metabroadcast.com
george.wright@bbc.co.uk
