The community-developed LCP software is used by public libraries (mostly in Europe) to lend ebooks to patrons fora limited period of time, say one month.
What NoDRM allows is for that lending period to be broken, so that patrons (readers) can read the ebook they have borrowed forma public library indefinitely.
The practical consequence is that copyright owners (authors, publishers., etc) would in most cases cease to make ebooks available for lending.
In some cases Readium LCP is also used by ebook vendors (retailers), mostly small European ones, as an alternative to Adobe's RMSDK, but the LCP platform is constructed such that if you buy the ebook from one vendor that you can read it on the app of any other vendor using Readium LCP, even if their authentication server is different (Adobe always requires authentication through a central Adobe server, meaning the end user needs an account both with Adobe AND the vendor/library, something not required with Readium LCP). IT is the most interpoerable system available in the publishing ecosystem
In fact the EU in part funded the development of the Readium LCP system through the European Digital Reading Lab (EDRL),a non-profit community-driven organisation, who are the complainant in this case.
I find it quite disheartening that nobody (or at least very few people in this thread) have looked who the complainant(s) actually are, i.e. the European Digital Reading Lab (EDRL) and (indirectly) the Readium foundation, both of which are community–driven non-profit organisation, operating on very modest budgets.
The Readium LCP software system (as distinct from the Readium the reading applications) was created a community effort to offer readers a user-friendly alternative to proprietary DRM systems. IT plays a particularly strong role in libraries ebook lending where it’s rule it is to ensure that a loan is just that a loan.
I understand the misgivings some have about the DMCA, copyright law and associated copyright protections, and the capitalist system in general. However, please set these aside for a moment and look at the situation from the perspective of readers, authors and others.
Readium LCP is fundamentally a trust system. It relies on copyright holders and that is not just large media companies, but small independent publishers, authors, agents and similar.
The largest consumer publisher (Penguin Random House) is but less than 1/100th the size of Apple or Amazon. Also the earning of an average author in the UK is in the neighborhood of a mere £7,00 per year.
If beg everyone to consider what the practical ramifications would be of destroying trust in a community-driven platform hat spent years to generate.
It means library lending of ebooks would cease entirely or revert to the old system such as Adobe’s RMSDK (reader mobile software development kit) with all the usability issues so familiar to anyone who does software development in the publishing ecosystem.
Aside: the acronym LCP originally stood for “lightweight content protection system” it is “lightweight” by design. For “marketing" reasons (or what I call “trust building”) it was later changed to stand for “licensed content protection”.
Also note that this is a discussion about consumer publishing “trade publishing in the vernacular of the industry) which is distinct from academic publishing (scientific journals, textbooks, etc.) a market dominated by Elsevier, Springer Nature and similar where Readium LCP is hardly used.
Disclaimer: Yes, I personally engage in weekly Readium engineering calls, but neither me not my organisation use or contribute to Readium LCP. WE use and contribute to the general Readium ebook reading software. I can attest that Readium comes with all the issues and problems of a community-driven open software system, but please recognise it for what it is, a community-driven , not-for profit effort.
Jellybooks is looking for an experienced JavaScript and front-end developer with experience designing for diverse accessibility requirements.
This is a remote position but the candidate must be a UK-resident for tax purposes with the right to work in the UK, because this position is supported by public funds.
We are unable to sponsor a work visa or support relocation to the UK.
What NoDRM allows is for that lending period to be broken, so that patrons (readers) can read the ebook they have borrowed forma public library indefinitely.
The practical consequence is that copyright owners (authors, publishers., etc) would in most cases cease to make ebooks available for lending.
In some cases Readium LCP is also used by ebook vendors (retailers), mostly small European ones, as an alternative to Adobe's RMSDK, but the LCP platform is constructed such that if you buy the ebook from one vendor that you can read it on the app of any other vendor using Readium LCP, even if their authentication server is different (Adobe always requires authentication through a central Adobe server, meaning the end user needs an account both with Adobe AND the vendor/library, something not required with Readium LCP). IT is the most interpoerable system available in the publishing ecosystem