APIs and URLs for Social TV
•
8 likes•9,230 views
This document summarizes a presentation given by Dan Brickley on requirements for linked social TV. The three key requirements discussed are: 1) Allowing metadata to flow widely between content and platforms, 2) Identifying content with URLs, and 3) Opening APIs to control TVs and link devices. Examples of prototypes that were discussed include using QR codes and second screen apps on tablets to link TV content. The presentation argues that linking content with URLs is foundational for social TV and that standard protocols are needed for second screen functionality.
Recommended
More Related Content
What's hot
What's hot (19)
Similar to APIs and URLs for Social TV
Similar to APIs and URLs for Social TV (20)
More from Dan Brickley
More from Dan Brickley (20)
Recently uploaded
Recently uploaded (20)
APIs and URLs for Social TV
- 1. APIs and URLs for Social TV Dan Brickley <danbri@danbri.org> NoTube Project & Vrije Universiteit, Amsterdam with Libby Miller, Mo McRoberts, Vicky Buser a joint W3C position paper from NoTube & Project Baird W3C Web & TV Workshop, Berlin, Feb 2011 Wednesday, 9 February 2011
- 2. Today • From me... • 3 requirements from Linked Social TV • Via motivating scenarios & examples • Suggestions for W3C next steps • A few words from a like-minded special guest (Matt Hammond of BBC) • Coffee! Wednesday, 9 February 2011
- 3. (who am I?) • In W3C community since 1997 • Joined W3C team to help start Semantic Web project, RDF specs and groups • 2006/7 Libby’s ‘Widget / social’ team at Joost.com startup - TV re-built in the Web • NoTube project, also recently co-chaired W3C SocialWeb Incubator Group Wednesday, 9 February 2011
- 4. The 3 Requirements Achievable, inter-dependent and foundational • Let metadata flow widely - advertising content, rather than be a hidden asset • Identify and link content with useful URLs(*) • Open APIs to control TV and link devices * CRIDs are great, but people share HTTP URLs see also CRID resolver demo services.notu.be Wednesday, 9 February 2011
- 5. Scenario-led analysis TV - not as a device, but as a part of people’s lives World Wide Web - not just a technology component but as a linked information network... ...and as something that connects billions of people Wednesday, 9 February 2011
- 6. Wednesday, 9 February 2011
- 7. Wednesday, 9 February 2011
- 8. Wednesday, 9 February 2011
- 9. ... and we noticed • Nobody says, “I want to see recommendations from other people who bought the same TV as me” • Nobody says, “I want to learn a new interface and controller for every device I use” • Or “I wish watching TV was more like using a computer.” Wednesday, 9 February 2011
- 10. Prototypes and demos From Widgets to APIs and the second screen (and third, fourth, and fifth...) (and sometimes no screens at all...) Wednesday, 9 February 2011
- 11. Wednesday, 9 February 2011
- 12. Wednesday, 9 February 2011
- 13. Wednesday, 9 February 2011
- 14. Experiments with pairing protocols eg. QR Codes (“xmpp:bob.notube@gmail.com/tv1234”) Wednesday, 9 February 2011
- 15. 2nd screen archive browser on a tablet computer Wednesday, 9 February 2011
- 16. Custom 2nd screen apps (OAuth/Twitter for ‘social’) Wednesday, 9 February 2011
- 17. Wednesday, 9 February 2011
- 18. (scope: can a table be a ‘remote control’?) Wednesday, 9 February 2011
- 19. (scope: is a projector a ‘TV’?) Wednesday, 9 February 2011
- 20. Observations • Second screen APIs have huge potential • Standard protocols needed (HTTP, XMPP?) • Useless without content identifiers, free-flow of metadata • “Social TV” is happening online anyway (even if people didn’t care to connect their TV’s ethernet cable) Wednesday, 9 February 2011
- 21. Linked TV data Connecting Archive.org films via Wikipedia to IMDB, Rotten Tomatoes, Facebook and to other users... (24 hour collab with Kingsley Idehen) Wednesday, 9 February 2011
- 22. We linked Archive.org video URLs to Wikipedia/DBpedia URLs We can visualize and navigate content using info from Wikipedia. Now, whenever Wikipedia is improved, so is Archive.org. And not just the “content” but related entities... Wednesday, 9 February 2011
- 23. Microsoft Pivot Viewer - laptop as 2nd screen “Show films by distributor, in the 1940s” Wednesday, 9 February 2011
- 24. (via Pivot embedded in OpenLink’s RDF/SPARQL db) Wednesday, 9 February 2011
- 25. Each entity of interest gets an URL, a page, some descriptive metadata... ...and more links by URL Wednesday, 9 February 2011
- 26. Wednesday, 9 February 2011
- 27. Wednesday, 9 February 2011
- 28. URLs + public metadata: RDFa in IMDB and RottenTomatoes HTML Aggregated by Facebook Wednesday, 9 February 2011
- 29. Conclusions & next steps • This is not rocket science: URLs make the Web • URL links are a foundation for Social TV • Linking documents is easier than linking devices • Protocol work deserves a Working Group • Best Practices Note: collect via Interest Group Wednesday, 9 February 2011
- 30. And speaking of remotes... (see Matt’s slides here) Wednesday, 9 February 2011
- 31. Wednesday, 9 February 2011
- 32. Last week’s examples • Al Jazeera’s Egyptian Twitter coverage • Linking content with URIs (these last slides not used...) Wednesday, 9 February 2011
- 33. Livestation streaming app embeds a Twitter client Wednesday, 9 February 2011
- 34. I posted a screenshot of Al Jazeera quoting someone talking about Egypt: “I’m not rich or poor, not muslim or christian, white or black, I’m neither from the north or south. I am EGYPTIAN!” Wednesday, 9 February 2011
- 35. ...he noticed, and was happy, and shared this back with @AJEnglish Wednesday, 9 February 2011