The Open Publication Standard for E-Books 2.0

This summer we've seen a quite a few interesting moves made by ebook technology leaders and there have been hints about the best of what's yet to come this fall, such as new devices from Amazon and Palm. The most important development, I dare say, is one that's been totally overlooked by the media, averse as they are to technical acronyms. This week, the voting members of the International Digital Publishing Forum (aka. the IDPF, which includes E-Reads) made the OPS 2.0 (Open Publication Standard) official. The OPS specifications are the next generation standards for ebook production. The good news for publishers is that this should reduce production costs in the long run, which will in turn be good for consumers because publishers will be able to afford to convert more titles. And, if the developers of ebook software, like MobiPocket, Sony, Adobe, Microsoft, etc., all implement the new specifications fully, then the new standardized files (better known as the ".epub" format) should be the document format of choice for our collective ebook future. I say "should," because it's still not a sure bet.

The biggest hurdles the ".epub" format has faced since the spec was first drafted are getting three specific groups to have interest in using it. The first group is the software companies responsible for digital-rights-managed ebook readers. There's no point producing ".epub" files if hardly anyone can use them yet. Publishers, such as E-Reads, want to be able to produce our books in the standard ".epub" format and then send them off to retailers, who will either sell the unencrypted ".epub" files, or encrypt them by using automated processes to convert them into any DRM format the consumer needs, such as Sony's Reader format, but, as things are right now, it's a rare piece of software that can already read or export ".epub" files, so retailers aren't very interested yet and they're still asking for MS Lit, PDF, Mobi, etc. In fact, only the recently released Adobe's Digital Editions software is really set up to use ".epub" files properly and many other reader applications have yet to completely implement support for the new format. This is because the first group, the software, is still waiting for the second group, the consumer base, to care. Sony has committed to adding ".epub" support for books that the consumers bring to the Sony Reader on their own, but are consumers using the ".epub" format? Well, there can't be grass roots demand for the format when the average consumer is so unfamiliar with it, can't buy it, and has barely any software that supports it. So it falls to the third group, publishers, to start the ball rolling by ordering books to be made as ".epub" files for their archives.

The Benefits of the ".epub" Format

If the average person has never heard of the ".epub" format, let alone tried it out, you can see why more developers aren't yet rushing to make it a "value-added" feature for their software. But the format has some terrific virtues. Unlike a PDF, an ".epub" ebook is designed so that any reader can have better control over how they choose to read a text, with no matter what device they're using. They can easily change fonts, styles, or page sizes and the document will reflow appropriately. And, unlike new reflowable document formats like PDFX or MS Word's DocX, ".epub" is really uncomplicated and it makes for a good legacy format for digital text, because an ".epub" file could easily be converted into any file format you'd like because of its standardized XML structure.

There are two steps to making an ".epub" file. The first is to use OPS (Open Publication Structure), which is just a method of formatting text files with XML tags. This was developed so that there's a uniform way to prepare texts for any device and so that it's easy to reverse-engineer and edit. Next, additional materials, like a cover graphic, are then bundled with the text into a compressed folder with the extension ".epub," which is, really, just a .zip archive. This is the container file, known as OCF (Open Container Format).

For now, the ".epub" format will have to compete for reading audience against established favorites such as HTML formatted books, and RTF files, as well as PDFs, DOCs, and dozens of other conventional formats, so it's up to publishers and developers to make this happen.

The Future Starts Now

To break the old cycle, software and ebook technology companies are trying to spur the use of ".epub" files with some big guns. Adobe is one company that's trying to pave the way forward with its latest version of InDesign CS3, which can export ebooks to Digital Editions in the ".epub" format (more about that can be read here). Since it's official release in June, Digital Editions has been a free download; it's an effort by Adobe to create an iTunes Library equivalent for ebooks. So, with Adobe software you already have an end-to-end package for creating and reading standardized ebooks, and a showcase for the advantages of the next generation of ebooks. Now we have to impress upon everyone else sitting on their hands that this is what we want from them, too.

I corresponded with Nick Bogaty of the IDPF yesterday and he said, "All major and small publishers I have spoken to are very excited about (the 2.0 standard) and are contracting their conversion houses to start work on .epub conversions. Obviously, it helped to have a company like Adobe participate, but this was (equally helped by) the participation and leadership (of) the folks at eBook Technologies, Garth Conboy, John Rivlin and Brady Duga. It really was a joint effort which couldn't have been done without widespread industry support."

It's this collective effort that will, we all hope, provide the momentum publishers, including E-Reads, need to keep adding new titles. The bottom line is that we're all trying to create a useful and ever-growing body of legacy work that the public will want to access for a long time, and the ".epub" format is the best opportunity to get virtually everyone in the ebook world on the same virtual page.

- Michael Gaudet