Fall2010 producer summit_openpbs_final


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • PBS API differentiators: Brand Power, More Content, Higher Quality Content
  • The recently launched iPad application and PBS.org redesign as well as the upcoming iPhone app and updated COVE CMS are built on the COVE and Merlin APIs.
  • Imagine how speedy the COVE CMS and COVE portal will be once they are built on the APIs
  • Partnered with Apigee (formerly known as Sonoa) to build out a robust unified API strategy centered around a developer portal. This portal will allow us to streamline the intake process for new developers and applications. We are consolidating the Merlin and COVE APIs as well as the DTV API, station finder, shop
  • The API is just the beginning.
  • Sharing of knowledge. Sharing of code. Sharing of ideas. Sharing of applications Collaboration on code, best methods, new technologies, more efficient workflows Transparency into the development process, new features, priorities Control over content, release of content, windowing remains unchanged but reach is further.
  • Through new and emerging devices and technologies Give content new reach
  • Fall2010 producer summit_openpbs_final

    1. 1. open.PBS.API & open.PBS Producer Product Summit Dec. 9, 2010 Tom Crenshaw Technical Product Manager
    2. 2. API 101 (Review) Twitter API getTweet?user=novapbs Shop PBS API getDVD?type=NOVA
    3. 3. open.PBS.API COVE Video Portals PMP Widgets Unified CMS Mobile Devices Custom Players Merlin Station Finder DTV Social Media Web Content Producer Site Anything! What Can Be Built on PBS APIs? Kids Video
    4. 4. New Product Releases on PBS APIs iPad App PBS.org Redesign iPhone App
    5. 5. <ul><li>COVE API </li></ul><ul><li>68,000 requests per day </li></ul><ul><li>99.999% uptime </li></ul><ul><li>< 499 ms response time </li></ul>API Success Exec Time Building sites on top of an API results in faster, more reliable, easier to maintain and more consistent sites for our visitors
    6. 6. <ul><li>PBS Interactive </li></ul><ul><ul><li>API will support the entire infrastructure of PBS sites and apps </li></ul></ul><ul><ul><li>Product owners can quickly build products with fewer dev resources </li></ul></ul><ul><li>PBS Producers and Stations </li></ul><ul><ul><li>Gain easier access to content, local and national </li></ul></ul><ul><ul><li>Better able to service the needs of their web users </li></ul></ul><ul><ul><li>Quickly prototype and build applications </li></ul></ul>open.PBS.API Target Audience <ul><li>Public </li></ul><ul><ul><li>Engages the community </li></ul></ul><ul><ul><li>Promotes viral distribution of public media content </li></ul></ul><ul><ul><li>Build excitement around brand and the potential </li></ul></ul><ul><li>PBS Strategic Partners </li></ul><ul><ul><li>Makes partner integration much easier for both parties </li></ul></ul><ul><ul><li>Generates new opportunities </li></ul></ul>
    7. 7. What’s next for open.PBS.API? <ul><li>Unified PBS API strategy consolidates the various PBS APIs into a single API (open.PBS.API) </li></ul><ul><li>Upcoming launch of developer portal to manage the API </li></ul>
    8. 8. The Start of Something Bigger!!
    9. 9. *Not the official logo of openPBS *
    10. 10. <ul><li>SHARING </li></ul><ul><li>… of knowledge, ideas, code, applications </li></ul><ul><li>COLLABORATION </li></ul><ul><li>… among projects, best practices, stations, producers </li></ul><ul><li>TRANSPARENCY </li></ul><ul><li>… of development process, roadmap, priorities </li></ul><ul><li>CONTROL </li></ul><ul><li>… of content type, windowing, distribution… </li></ul>What does open.PBS mean?
    11. 11. <ul><li>Develop a Great Cookie </li></ul><ul><li>Share it worldwide (publish the recipe, produce pre-mixed batter, sell baked cookies) </li></ul><ul><li>The world consumes and reproduces the Great Cookie </li></ul><ul><li>Rachael Ray tweaks recipe to make Great Cookie 2.0 </li></ul><ul><li>Revision broadcast worldwide </li></ul><ul><li>The world adopts and improves upon Great Cookie 2.0 … and so on </li></ul>Open Sourcing a Cookie
    12. 12. <ul><li>FIREFOX </li></ul><ul><ul><li>Netscape opens their source code in 1998 </li></ul></ul><ul><ul><li>Mozilla Foundation creates Firefox browser </li></ul></ul><ul><ul><li>Plug-in architecture lets anyone extend functionality </li></ul></ul><ul><li>APACHE </li></ul><ul><ul><li>HTTP server that can be modified by anyone </li></ul></ul><ul><li>WIKIPEDIA </li></ul><ul><ul><li>Community based open content </li></ul></ul>Other Open Source Examples
    13. 13. PBS Needs to Change the Game <ul><li>The marketplace is changing faster than internal resources are growing. </li></ul><ul><ul><li>Content is moving beyond the browser. </li></ul></ul><ul><ul><li>The web is becoming more decentralized. </li></ul></ul><ul><ul><li>Digital media is beginning to blend people, objects, and locations. </li></ul></ul><ul><ul><li>There is value in the app economy. </li></ul></ul>Through collaboration we can build better products faster and cheaper.
    14. 14. How We Change the Game <ul><li>Ensure PBS content is relevant to new and existing audiences. </li></ul><ul><li>Serve the audience anytime, anywhere, on any platform. </li></ul><ul><li>Create an ecosystem of applications built and maintained by a community of developers. </li></ul><ul><li>Leverage the long-tail to support the head. </li></ul>
    15. 15. It Begins With Opening Apps
    16. 16. open.PBS Vision PBS will create, promote, and support an internal and external community of volunteer technologists to innovate on top of our content and services. PBS will draw upon the successes, and failures of those external technologists to improve our internal product development. In turn, PBS will adapt to the dynamic environment and thrive in the app economy.
    17. 17. What This Means For You <ul><li>Increased voice in project features. </li></ul><ul><li>Access to projects contributed by others to open.PBS. </li></ul><ul><li>Quicker time to market for PBS applications. </li></ul><ul><li>More transparent change management. </li></ul><ul><li>Uniform content management, i.e. delivery windows managed through COVE. </li></ul>
    18. 18. Roadmap July Aug. Sept. <ul><li>COVE API design research </li></ul><ul><li>thePlatform integration with COVE API </li></ul><ul><li>API Production Deployment </li></ul><ul><li>COVE CMS 2.0 ALPHA using COVE API </li></ul><ul><li>PBS.org launches powered by Merlin API </li></ul><ul><li>TV Schedules API used in iPad, iPhone and PBS.org </li></ul>Oct. Nov. Dec. <ul><li>Support for iPad and iPhone Apps </li></ul><ul><li>open.pbs.org landing page </li></ul><ul><li>openapi.pbs.org developer portal </li></ul>Q1 2011 <ul><li>COVE CMS 2.0 launched using openPBS.API </li></ul><ul><li>Video Portal transition to openPBS.API </li></ul><ul><li>open.PBS.API developer portal soft launch </li></ul><ul><li>Launch code repository for open.PBS </li></ul><ul><li>Merlin data included in openPBS.API </li></ul>Q2 2011 & Beyond <ul><li>open.pbs.org community site launched </li></ul><ul><li>PBS applications released under open source license </li></ul><ul><li>Developer community outreach </li></ul><ul><li>COVE Batch Ingest API </li></ul>
    19. 19. Questions?
    20. 20. Contact me: <ul><li>Email: </li></ul><ul><ul><li>[email_address] </li></ul></ul><ul><ul><li>[email_address] </li></ul></ul><ul><li>AIM: crenshawtw </li></ul><ul><li>Twitter: @tomatpbs </li></ul><ul><li>http://open.pbs.org/ </li></ul>