By Bill Rosenblatt
The 2017 ePub Summit in Brussels this month was the venue for the beta launch and first live demos of the Readium LCP DRM technology for ePub-formatted e-books. I’ve discussed aspects of the genesis and design of Readium LCP elsewhere: here is a summary that I presented at last year’s ePub Summit in Bordeaux. Readium LCP is designed to integrate with the Readium open source code library for ePub reading systems, although Readium can integrate with other DRMs, and in fact there are Readium implementations that support multiple DRMs at the same time.
Readium LCP started, to a large extent, with a conversation that I had in 2012 with Bill McCoy, then Executive Director of IDPF, the standards body that oversaw the ePub format (now part of W3C). He was concerned with various aspects of Adobe ACS, the de facto standard DRM (outside of the Apple and Amazon ecosystems), including Adobe’s lack of commitment to supporting the new version of ePub (ePub 3), and he wanted to motivate alternatives.
Here is an early snapshot of the project. I was involved in various aspects of it, including the licensing, compliance, and robustness frameworks as well as the initial requirements. Five years later, some of the design principles and goals have changed, but the basic idea of providing a simple, low-cost, and vendor-neutral DRM for ePub has remained.
Readium LCP has blossomed into a vibrant, cooperative, open-source development effort involving several companies. Among others: De Marque of Canada built server software; TEA and Mantano of France developed e-reading clients; and Feedbooks (France) and DRM Inside (South Korea) contributed key design elements. DRM Inside also built its own server and client implementations, and ePagine of Netherlands/Belgium/France contributed on the server side. (Please complain to me if I left you out.)
The code (C++ on the client side; Go on the server side) is available in Github repositories and is almost entirely BSD-licensed open source. Anyone can implement Readium LCP, although it’s necessary to do a few things to participate in the Readium LCP interoperable ecosystem: sign a license agreement, pass a compliance test, and (on the client side) agree to harden your code to make it resistant to reverse engineering and key discovery. Licensees get access to the small library of hardened binary code and the digital certificates that provide security and are necessary to integrate with other components.
The ecosystem is set up so that any licensed e-reader should be able to read e-books from any licensed server. In fact, such interoperability was demonstrated yesterday in Brussels, as DRM Inside’s implementations were shown to be interoperable with those of De Marque, TEA, and Mantano.
The non-profit, Paris-based European Digital Reading Lab (EDRLab), which was established in 2015, administers the licensing and compliance testing. It will charge a modest initial license fee and flat annual fees that depend only on organization size and not on transaction volume or size of catalog. The only dependence on any commercial vendors is that the digital certificates are supplied by a division of Deutsche Telekom.
At the ePub Summit, it became clear that the biggest initial “bowling pin” (niche market) for Readium LCP is library ebook lending. The library community likes the lack of transaction costs for Readium LCP, the lack of dependence on a single DRM vendor, and growing community of companies building software and services around the technology.
(The French library community particularly likes a feature of Readium LCP that makes it desirable in France: public libraries limit the number of lending transactions that a user can make at a given time. When you “borrow” an ebook, you can ask to extend the lending period; the library may grant the extension if there is no waiting list for the title. If the library uses the Adobe DRM, the extension counts as another lending transaction that counts towards the user’s limit, but with Readium LCP, it doesn’t.)
The library lending demo in Brussels was a cooperative one among many entities: several publishers (Dutch and French) contributed ebook titles; the ebook distributor Eden Livres housed the ebooks and their metadata; Dilicom, a French library/publisher joint venture, served as a pipeline of e-book data to library e-lending platforms; and ePagine provided an e-lending platform for the demo. Lirtuel, an e-lending system for Francophone Belgium, will use the platform to serve its based of 100,000 users (the name is a clever portmanteau word for “Lire,” to read, and “Virtuel”). Dilicom also showed a mockup of an e-lending system for the Paris area public library system PNB (Prêt Numérique en Bibliothèque), which may launch a Readium LCP-based e-lending system soon.
Participants in the Brussels conference said that Readium LCP is the first and only DRM technology whose designers solicited input specifically from the library community. While Readium LCP may have some success with retail e-book services as well, library e-lending looks like a strong initial market for this newly hatched DRM technology. Despite doubts that some publishers and distributors have about DRM for retail e-books, DRM for library e-book lending is here to stay for the foreseeable future.
Thanks to copyright-and-technology expert Bill Rosenblatt, owner of GiantSteps Media Technologies Strategies, for permission to reproduce the above article from his blog, Copyright and Technology. The above opinions are his, not necessarily TeleRead’s. In fact, I myself think the Publishing@W3C, the new incarnation of the IDPF within the World Wide Web Consortium, should care a lot more about watermarking and other anti-piracy measures that better respect the rights of ebook users than DRM does. For library use? The issues are different. I do appreciate the added flexibility that LCP brings for borrowers. Not to mention sharp reduction in costs—for all users, not just library ones—compared to using Adobe DRM.
In commenting, please take extra care to be civil. For years, in the interest of dialogue and mutual enlightenment, I’ve wanted to see more of the pro-DRM side in TeleRead even though I myself am on the anti side (at least in regard to “retail sales”). I am grateful to Bill for obliging. – DR
I’d be interested in reading more about ReadiumJS and how it might support open source content. I was very impressed with Ibis Reader when it was available and would like to see more web-based readers to pick up where Ibis Reader left off. These might support LCP if only to afford a single point of contact for those who are reading both OER and commercial titles.
Hi I’m a writer who is self-publishing. I want to put this kind of DRM on my ebook but don’t know how someone like me will go about doing so when it’s available. People who are anti-DRM don’t usually address situations like mine where there is a huge potential for piracy to the point where I could end up selling very few copies of my book if I didn’t have protection. And I don’t know if social DRM would do much considering most of my market is in African countries.
Would the LCP also be able to handle other content type (ie. PDF)
Readium will never take off unless there is a stand-alone program for Windows. Just having a plugin for Chrome is not going to cut it.