Turn on ye ole Javascript to add ratings in this low-budg app.

Title:

Get Me Rewrite! Developing APIs and the Changing Face of News

Your vote:
Yes No
Organizer:
Jacob Harris, The New York Times
Description:
In the past year, several major media producers have rolled out APIs to open up and remix their content. This panel assembles several noted developers of media APIs to discuss their experiences with the process: the technical hurdles, the internal arguments, the surprising ways in which people have discovered new ways of looking at the news.
Questions
Answered:
  1. What are some notable media APIs?
  2. Why should your newspaper/magazine/etc. create APIs?
  3. What are some common considerations for creating an API?
  4. How do you moderate access, prevent abuse, and protect intellectual property?
  5. What new revenue models are possible with APIs?
  6. What are the most surprising things we've seen people do with our APIs?
  7. What's the fastest and cheapest ways for a newspaper to get started?
  8. What about user-generated content? How does that mesh with standard editorial workflows?
  9. What sort of APIs should you offer? What data formats are required?
  10. What things are coming next for APIs from the big media companies?
Panelists:
John Donovan (daylife.com), Jacob Harris, moderator (The New York Times), Dan Jacobson (NPR), Brad Stenger (Wired)
Level:
Intermediate
Category:
Content
Type:
Panel
Event:
SXSW Interactive 2009
on 8/8/08
yes, yes and yes again. This is a must see.
on 8/8/08
I'm in - we love the NYT.
on 30/8/08
Does "internal arguments" refer to verbal (or fist!) fights between people on the development team during development, or to strategy-phase rationales for releasing an API in the first place?
on 4/5/09
Very interesting discussion, thank you
Developed for SXSW by Lindsey Simon