Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Terry Jones TOC 2011 slides


Published on

Slides from "The Future of Publishing is Writable" talk by Terry Jones of Fluidinfo at the O'Reilly TOC conference, New York, Feb 15 2011.

Published in: Technology
  • Be the first to comment

Terry Jones TOC 2011 slides

  1. The Futureof Publishing is Writable Terry Jones @terrycojones
  2. A talk in four acts I. working with information II. A writable book API III. Hugh & Brian IV. Food for thought
  3. Act IWorking with information
  4. Information in the wild Think as generally as possible about publishing: not just print, not just digital Information publication and communication in natural systems Books as a special case
  5. disparity &
  6. Post-it notes are blank But it wasn’t always so
  7. An asynchronousinformation storeWith a wonderfuluser interface!
  8. Cross-building communication via Post-it notes
  9. unanticipated
  11. terry/rating 89 books/title The Sound & The Fury books/author William Faulknerterry/i-own books/ISBN 0075536668terry/read tim/current-page 224no owner! $18 $19alexlines/opinion One of his classics!
  12. With an openly writable object for everything augment personalize search filter share organize
  13. Image credits• Disparity• Matilda• Bookmark• Topless• Message• Portcullis• Toilet• Hand• Cross building communication• Dog• Switch• Locks• Unanticipated• Silo• Bulletin board• Twitter bird• Encyclopedia
  14. books/title The Sound & The Furyterry/rating 9 books/author William Faulknerterry/i-own books/ISBN 0075536668terry/read .... tim/current-page 224 andy/current-page 17no owner! $19 $18alexlines/opinion One of his classics!
  15. Flui!nfoAn object for everythingPermissions at the level of the tagDomain names on dataUniversal metadata engineA bit like Wikipedia, but for data
  16. Act IIa writable book API
  17. Act IIIHugh & Brian
  18. Book APIs & Containers The line between book and Internet will disappear Hugh McGuire Context first Brian O’Leary
  19. Book APIs “The inevitability of truly connected books and why publishers need APIs.”The line between book and Internet will disappearHugh McGuire
  20. Book APIs “An API is ... what smart web companies build so that other innovative companies and developers can build tools and services on top of their underlying databases and services.”The line between book and Internet will disappearHugh McGuire
  21. Book APIs “We are a long, long way from publishers thinking of themselves as API providers -- as the API for the books they publish. But we’ve seen countless times that value grows when data is opened up (sometimes selectively) to the world ... That is where book publishing is going. Eventually.”The line between book and Internet will disappearHugh McGuire
  22. Book APIs “I don’t know exactly what an API for books would look like, nor do I know exactly what it means. I dont know what smart things people will start to do when books are truly of the Internet. But I do know that it will happen, and the ‘Future of Publishing’ has something to do with this. The current world of ebooks is just a transition to a digitally connected book publishing ecosystem that won’t look anything like the book world we live in now.”The line between book and Internet will disappearHugh McGuire
  23. Context, containers & APIs “the current workflow hierarchy – container first, limiting content and context – is already outdated.  To compete digitally, we must start with context and preserve its connection to content ... We must start to open up access, making it possible for readers to discover and consume our content within and across digital realms.”Context FirstBrian O’Leary
  24. Context, containers & APIs “In a limited market, our editors became skilled in making decisions about what would be published.  Now, in an era of abundance, editors have inherited a new and fundamentally different role: figuring out how ‘what is published’ will be discovered. To serve that new role, we must reverse our publishing paradigm.  We need to start with context and develop and maintain rich, linked, digital content.”Context FirstBrian O’Leary
  25. Context, containers & APIs “In a digital realm, true content solutions are increasingly built with open APIs, something containers are pretty bad at.  APIs provide users with a roadmap that lets them customize their content consumption. Open up your API, I contend, or someone else will. Many current audiences (and all future ones) live in an open and accessible environment.  They expect to be able to look under the hood, mix and match chunks of content and create, seamlessly, something of their own.”Context FirstBrian O’Leary
  26. Context, containers & APIs “Stories like this one ... have led me to see piracy as the consequence of a bad API. 16 years olds expect access, or they invent it. The future of content involves giving readers access to the rules, tools and opportunities of contextually rich content, so that they can engage with it on their own terms. And whether they say it just like this or not, readers WANT good APIs.”Context FirstBrian O’Leary
  27. Context, containers & APIs “Context can’t be just a preference or an afterthought any more.  Early and deep tagging is a search reality.  In structural terms, our content fits search conventions, or it will not be referenced. And in contextual terms, our content needs to be deeply and consistently tagged, or it will face an increasingly tough time being found. We can’t afford to build context into content after the fact.”Context FirstBrian O’Leary
  28. Act IVFood for thought
  29. Bullets!The awkwardness is (ubiquitous) in thedigital world tooThe solution is not another applicationInstead: openly-writable storage (cf thenatural world & concepts)Data vs metadata: a dead-end in informationarchitecture; non-existent in the real world
  30. Bullets!Evolution trumps ontology (in informationarchitecture)Asynchronous data protocolsPersonalization & customization: should bein our hands, not on our behalfOpenly writable objects change many things(e.g. information organization)
  31. A little math(Read-only) containers < APIs (Brian)
  32. A little math(Read-only) containers < APIs (Brian)APIs < writable APIs (Terry)
  33. A little math(Read-only) containers < APIs (Brian)APIs < writable APIs (Terry)
  34. A little math(Read-only) containers < APIs (Brian)APIs < writable APIs (Terry)Writable API = Writable container (Peace on earth?)
  35. The Futureof Publishing is Writable Terry Jones @terrycojones
  36. Flui!nfo Inc. NYC start-up Fantastic set of investors making the world writable
  37. Image creditsIgnite bullets