No standard e-book format for consumers after nearly five years. VHS-vs.-Beta times ten. That's the Open eBook Forum for you.
OeBF delays have cost publishers many millions of dollar in sales to readers put off by the format wars. Everyone has suffered, from Random House to self-publishers.
TeleRead's Web log will continue its analysis of the OeBF debacle and also suggest some solutions, in no particular order. The OeBF has attracted some very bright and well-meaning people even if they come with clashing interests. How to get humans and formats in harmony or at least reduce the conflicts?
The good news is that the OeBF's work has been far from wasted. Formats such as Mobipocket, not just Microsoft Reader, the starting point in some ways, already offer Open eBook features galore.
Alas, however, this isn't enough for the world to enjoy the consumer-level compatibility that Microsoft executives Dick Bass and Steve Stone promised in 1998 when they unveiled their vision for the e-books and the OeBF.
Today we address, among other format-related problems, a Catch 22 about which too many e-book techies are complacent. Major publishers are insisting on Digital Rights Management to protect their e-books. And yet when they rely on proprietary encryption to safeguard books using the Open eBook Publishing Structure, the OeB format is no longer "open."
What to do? Below, slightly edited, is a recent message from Jon Noring, co-founder of Windspun Technologies, to the eBook Community list. Noring, himself active in the OeBF, is list moderator. After his comments, we'll offer a TeleRead perspective. Time for some open-mindedness from OeBF, especially when the group holds its annual meeting May 29 in Los Angeles?
* * *
The wrapper for a native OEBPS Publication can certainly include DRM, and all the components can be based on "truly open standards" (as in published, non-proprietary, freely usable, maintained by non-profit organizations representing a broad range of industry stakeholders). For example, the rights control language can be based on XrML, which OeBF is now considering. The encryption algorithms can be based on some open standard.
Interestingly, the recent decompiling of the LIT format illustrates nicely how an OEBPS Publication wrapper may work. If you look at the LIT format, LIT simply wraps (just like a zip file--LIT uses a well-known compression algorithm) a multi-file set which is a slightly digested OEBPS Publication. Technically speaking (ignoring legal/financial hurdles), it is now possible for anyone to build a LIT rendering system for any platform. Reading LIT on Linux? On Mac? On BeOS? On ZippyOS? It is certainly possible to do (whether it makes sense to do so, or if Microsoft will let you, is another issue, but irrelevant to the discussion at hand).
Regarding the DRM topic, the subtle fallout of the LIT decompilation, which hopefully publishers should realize by now, is that 1) security by obscurity does not work, and 2) it is likely impossible to design an ebook format to be read on non-proprietary hardware/OS platforms which is completely immune to cracking.
These two observations have the net effect of virtually removing (albeit not completely) one argument against native OEBPS as a distribution format: that because it (including a DRM-capable wrapper) is based on "truly open standards," it will not be able to provide a level of protection anywhere near that of "proprietary" standards such as LIT and PDF. That is, both Microsoft and Adobe will find it more difficult to argue to publishers that their proprietary format solutions for ebook distribution are substantially "safer" than the truly open-standards approach. Obviously, right now Microsoft and Adobe cannot tell publishers that their e-book formats are truly safe because they aren't.
So how about the OEBPS 1.2 alternative? No, it would not be perfect. It's still in its infancy, and certainly can be improved. I have my own laundry list of items which need fixing and improving. However, as it stands now, OEBPS is essentially ready for primetime. If one adds MathML and SVG capability to OEBPS, we have a quite powerful e-book distribution format which should adequately represent nearly all ink-on-paper books published today (OEBPS by itself is also very good, but MathML and SVG add a lot of advanced capabilities--SVG is a pretty good replacement for both PDF and Flash). The ball is now in the court of those who design OEBPS presentation systems to take advantage of these advanced capabilities.
* * *
The TeleRead take: Jon Noring's comments nicely jibe with TeleRead's advocacy of open standards. While Korean-style viewers, accommodating many formats, could be a good interum solution and probably more, a standard e-book format is the real way to go. Notice Jon's observation that his approach would "adequately represent nearly all ink-on-paper books published today"? Future versions of the format, obviously, could be far, far more than "adequate." But let's get started now.
The Noring approach is especially sensible about encryption. Full protection of content is impossible. Meanwhile, how about all the millions lost in the formats war amid the accompanying reliance on encryption systems based on proprietary technology? We're talking about far more money than from potential piracy losses. So why not a rational open-standards approach to encryption--which, by the way, would also mean that the algorithms could be subjected to more intensive review by many programmers with different perspectives, as opposed to those benefiting just from the feedback of corporate colleagues? Such a plan could at least discourage casual piracy--while, hopefully, also providing for protection systems to allow for fair use. Forget about perfected encryption systems. Remember, paper books have no protection systems in places, and scanning and page-flipping techniques will get better and better. Worse, anything that can be displayed on screen or printed is vulnerable in the end to pirates.
With the right mechanisms in place, however, readers could endlessly swap files while authors and publishers received fair compensation based on a privacy-respecting tracking mechanism (perhaps using concepts similar to those for anonymous digital cash). Payments could come from a national digital library fund, local schools and libraries and consumers directly (since we couldn't afford to cover all books). Simply put, this TeleRead-style approach could reduce the incentive for piracy while allowing good publishers to do quite well, thank you.