• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
BookServer: A Web of Books
 

BookServer: A Web of Books

on

  • 4,495 views

Description of the origins and development of the BookServer architecture and the Open Publication Distribution System (OPDS). Why OPDS Catalogs can help build a web of books. Discussion of the ...

Description of the origins and development of the BookServer architecture and the Open Publication Distribution System (OPDS). Why OPDS Catalogs can help build a web of books. Discussion of the challenges ahead.

Statistics

Views

Total Views
4,495
Views on SlideShare
4,226
Embed Views
269

Actions

Likes
5
Downloads
42
Comments
0

4 Embeds 269

http://wp.kzakza.com 208
http://kzakza.wordpress.com 39
http://www.slideshare.net 20
url_unknown 2

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

CC Attribution License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel

BookServer: A Web of Books BookServer: A Web of Books Presentation Transcript

  • BookServer: A web of books Peter Brantley Internet Archive NISO . BNC . 2010
  • I. Opportunity and Vision
  • Motivating issues Entering the digital fold, a tangled landscape: 1. finding the book 2. format of the book 3. acquiring the book
  • Finding the book  Web search? (Google, Bing, etc)  Publisher website? (Tor.com ... )  The local library? (borrowing/lending)  Online bookstore? (Amazon, Indigo, B&N)  Indie bookstore? (Vroman’s, Powell’s)  Alt. vendor? (Smashwords, Kobo)
  • Format of the book  Highly structured display (pdf)  Downloadable book package (epub, mobi)  Web- or “cloud”-based (Google Editions)  Non-standard enhanced book (Blio)  Not really available at all (ill)
  • Acquiring the book Reading systems –  Amazon Kindles, Sony Readers, B&N nook  IBIS Reader, Aldiko, Stanza, Kobo  Standard desktops and laptops  Game consoles (Wii)  Apple iPad
  • “ripping hair out” + Device + Format + Discovery + Acquisition + Installation ( + DRM ) = Confusion. http://www.flickr.com/photos/dan4th/2295925353/
  • What readers want What readers want to have .. Be able to find the books they want, in the formats that they can use, for the device that they have, and not have it be painful.
  • Book distributors What publishers, libraries, bookstores want - Make books available for discovery, with accurate descriptive information, at as many different places as possible, under the sales / use terms permitted.
  • Even the Feds
  • For the United States Even the U.S. Dept of Justice is an advocate: “[book] data provided should be available in multiple, standard, open formats supported by a wide variety of different applications, devices, and screens.”
  • Wanted: Web of Books
  • BookServer: A future for books Creating a new architecture using common, open standards that permits people to find, buy, acquire, and read books from any source, on any device, using many different ebook applications.
  • The Heritage: Lexcyle’s Stanza
  • Relation: Library catalogs Library 2.0 Gang (02/09): Google books and libraries “Open Catalogue Crawling Protocol” Google, DLF, Talis, and others Atom vs Sitemap discussions
  • Stages of support IDPF Board Tools of Change (NYC, Feb 2009) Web Expo 2.0 (SF, Apr 2009)
  • OPDS “Catalog” launch “The Open Publication Distribution System (OPDS) is a generalization of the Atom [XML] approach used by Stanza's online catalog. ... I believe this effort has the potential to be a critical enabler to the growth in access to, and adoption of, digital books.” - Bill McCoy, Adobe, 04.09
  • Getting the terms right 1. “BookServer” is the architecture. 2. “OPDS” is the technical specification. 3. “Catalogs” are made using OPDS. 4. “Atom” is the XML scheme for OPDS.
  • Based on Atom Because OPDS is based on a commonly used XML standard, called Atom, OPDS Catalogs can be read by –  web browsers  news readers (rss)  mobile applications
  • Catalogs scale Because Catalogs are easy to make –  Any web site can run a bookstore/library.  Libraries, bookstores, publishers can play.  Search engines can serve as book gateways.  Aggregators can harvest multiple catalogs.
  • Distribution format Because Catalogs contain simple data describing books and their availability – Catalogs can also be used for B2B, to distribute data to partners for “harvest” instead of using complicated standards. (Future: “real time web” notifications.)
  • Journals good to go
  • Delivering article level
  • What’s in this thing? Catalogs provide manifests –  List of the titles available  Information about each title  Formats the title is available in  Ways the title can be acquired
  • How it works A reader ... 1. Browses a Catalog of titles - 2. selects a title for more information - 3. makes a purchase/borrow decision - 4. obtains book (PayPal, Amazon, Google) - 5. installs and reads the book.
  • A good catalog ... For best user experience:  Intelligent hierarchy  Flexible search  Extensive faceting  Human touch
  • Made easily Catalogs can be derived from basic bibliographic metadata. Such as: ONIX, MARC, (ahem) spreadsheets (Internally OPDS Catalogs use simple Dublin Core metadata.)
  • Why not ONIX? ONIX (and BISG “BookDROP”) are:  Designed for a different use cases  Complex standard with many options  Not widely used beyond publishing  Not understood by web browsers  Established; change is difficult
  • Catalogs are emergent Because we use open standards for describing data, it is possible to link bibliographic book data more easily.
  • Linking books Catalogs can tie together – § Book reviews § Reading lists § Annotations § Fan fiction
  • Make Books Apparent A workshop sponsored by the Internet Archive October 19-20, Fort Mason, San Francisco, CA With the assistance (among many others):  O’Reilly Media http://oreilly.com/  Threepress http://threepress.org/  Feedbooks http://feedbooks.com/  Book Oven http://bookoven.com/
  •  Adobe  Ingram Digital  Aldiko  Inkmesh  (Amazon) Lexcycle  O’Reilly Media  Applewood Books  OLPC  Book Oven  Pixel Qi  Feedbooks  Kobo Books  Floss Manuals  Threepress  HumanWare  Voyager Japan Interested parties (03.2010)
  • Part II: Meeting the challenge
  • Building the ecosystem For this to work, we need: 1. Good (independent!) reading systems 2. Books, journals, magazines, and more 3. $ Publishers must contribute frontlist Revenue nexus: 4. Mobile reading systems 5. Aggregators (incl. search)
  • We’re in draft
  • We have issues!
  • Issues – I Aggregation Two roles for OPDS: 1. simple publication 2. catalog aggregation Aggregating resembles metasearch: out of many sources must come order.
  • Issues – II Metadata Matching title <> reader is not trivial. FRBR, recommending, clustering - and then there is plain old GIGO
  • Issues – III Identifiers OMG. Where does one start? - Author, work, and subjects. Data from publishers (book and journal); libraries, trade organizations and assns.
  • Issues – IV.a Territorial Rights Publishers carve up markets into territories, geographic and language-based. One publisher might have UK, AU, NZ rights, whilst another might possess U.S. rights. Spanish publishers typically retain worldwide spanish-language rights.
  • Issues – IV.b Territorial Rights Territorial rights make zero sense for digital editions (n.b. language might). Publishers must obtain non-geographic rights for electronic text versions. (Regional DVD codes is a sad analogy).
  • Issues – V Search OPDS defines search via OpenSearch. OpenSearch ver status is “under development” and not really “owned” by anyone (origin: A9). Could benefit from support and enhancement.
  • Issues – VI Faceting On a small screen device, faceting must be a normative discovery user interface form. What is baked in? – Top-20. Classics. New. What is algorithmically derived, on the fly? How can one do this against aggregations?
  • Issues – VII Bookshelves Users should be able to define and maintain their own book lists in OPDS format. Ideally, these should be portable across book hosting services.
  • Issues – VIII DRM Bad word, but many publishers still reliant. Best market solution: Adobe ACS4 Pay per transaction model. Desperate need for open source solution. (Perhaps premised on “social-DRM” spec.)
  • Issues – IX Vending Not a trivial problem. Need an abstracted selling API. Application elicits essential purchaser data, then handles transaction “under the covers” Paypal, Google Checkout, Amazon Checkout
  • Issues – X Lending Internet Archive would like to lend books (directly, not via a third-party). Is every lending a renting? (no ... !) Is there digital first-sale? (yes ... !) Options: ACS4, streaming (cloud)
  • Issues – XI Hello World! Currently no way for new OPDS Catalogs to announce themselves to the world. We have discussed a “ping server” to aid the auto-aggregation of Catalogs. This remains a manual notification process.
  • Join in! OpenPub on Google Code: http://code.google.com/p/openpub/wiki/OPDS
  • Ask the question
  • thanks! peter brantley internet archive san francisco ca @naypinya (twitter) peter @archive.org