Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.

Book as URL

88 755 vues

Publié le

A short presentation of 10 proposals of what a Book as URL should be. Presented at the 2013 IDPF conference at Book Expo America, part of the opening session: "The Evolving Digital Book: 4 Visionary Perspectives"

Publié dans : Formation, Business, Technologie

Book as URL

  1. 1. Book as URL--hugh mcguire--pressbooks.com@hughmcguire
  2. 2. A proposal:10 Recommendations?Dreams?Ideas?forthe Book as URL
  3. 3. 1. Every book should have apersistent URL, something like:http://publisher.com/isbn/title-by-author
  4. 4. 2. Every book should live as structureddata online.
  5. 5. 3. Every book should make ONIX-like top-level metadata available through anopen API, eg:- cover image- title- author- descriptions (one line, 50 words, unlimited)- keywords- pub date- BISG categories- etc.
  6. 6. so far so good...actually HarperCollins, Pearson, andRandom House have apis that dothis kind of stuff ...
  7. 7. 4. Every book URL should pull in additional"external" metadata -- through APIs fromexternal services, eg:- reviews from "official" sources + review URL- reviews from readers (goodreads, facebook,twitter)- data from libraries/librarians- external "about the book" URLs (wikipedia etc)- external "about the author" URLs (wikipedia,authors web site, etc.)
  8. 8. 5. The book should aggregate theconversation about the book:- pull in highlights & comments from openannotation systems (eg Readmill … andothers who open their data up)… ideallylinked to the occurrence in the text.
  9. 9. 6. Allow porous web access to thebook:- modelled on NYTimes paywall (and GoogleBooks) ... allow links into the content itself, andreaders the ability to read X% before paying.
  10. 10. 7. Enable linking from one book toanother book- even more ideally, with links to the text inthose books(which can be built if those books haveAPIs).
  11. 11. 8. Real time analytics in the back-end- what is popular & with whom
  12. 12. 9. Expose all Tables of Contents andIndexes (in structured format) to theweb- while we are at it, expose: lists of tables,figures, images- and expose those tables, figures, imagesas well
  13. 13. 10. Provide API access to all of this
  14. 14. Is this hard?
  15. 15. Not if you use a good web-based contentmanagement system/repository
  16. 16. Not if you use a good web-based contentmanagement system/repository(Ideally an open source one,like PressBooks!)
  17. 17. hugh mcguire--pressbooks.comhugh@pressbooks.com@hughmcguire@pressbooks