BEA Show Notes, Day 1, Lynn's Take
Books as Algorithms, books as APIs and reading as a shared experience
By
Lynn Rosen
Facebook
Facebook
Twitter
Twitter
LinkedIn
LinkedIn
Email
Email
0 Comments
Comments
Hugh McGuire of PressBooks, thinks of books not as works under glass but as something different, and envisions building books as structured data. He mentions important things ebooks should do.
- Every book should have a persistent URL - a good identifier.
- Every book should live as structured data online.
- The URL should make ONIX-like top level metadata available through an open API.
- Should pull info back into the URL: reviews, annotations, comments, etc. The activity of reading is generating data about reading. (Talk about meta!)
- The book should aggregate the conversation about the book.
- Allow porous access to the book (like the New York Times pay wall.)
- Allow/enable links from one book to another.
- Have real-time analytics in the back end.
- Expose the table of contents, index, tables, images to web so readers can find it.
Writer/designer Craig Mod quotes newspaper industry expert Joshua Benton, saying the perception of incoming disrupters is that they are low quality and not worth paying attention to. These disrupters come in when technology enables new players to compete with incumbents on terms the incumbents aren’t used to or comfortable with. Sounds like it might apply to the book publishing industry!
0 Comments
View Comments
E
Lynn Rosen
Author's page
Related Content
Comments