EPUB 3: Building a standard on unstable ground

Matt Garrish on the work behind the EPUB 3 specification.

Now that the ink is dry on the final EPUB 3 specification from the International Digital Publishing Forum (IDPF), it seemed a good time to touch base with “What is EPUB 3?” author Matt Garrish, who also was the chief editor of the EPUB 3 suite of specifications.

Our interview follows.

What advantages/challenges will EPUB 3 bring to the publishing table?

Matt Garrish: The biggest bang I see EPUB 3 bringing to the digital publishing world is undoubtedly the ease with which it will allow the creation of rich multimedia and interactive experiences. The ebook market has moved beyond the static two dimensions of the print page, and I don’t think there’s any stopping the march forward into uncharted digital territory.

We need to let go of the digital book — the one that doesn’t have a print antecedent — and see where it will go, knowing full well that it won’t translate back to print. I think that’s still a scary idea to many people, but as the ebook market expands, growth in print-incompatible books is inevitable.

That’s the biggest benefit I see this new revision bringing to the table, that it offers a clear path away from the print-centric ebook. EPUB is back ahead of the curve and will be both waiting as the format of choice as publishers embrace its new powers and doing its regular duties facilitating dual print/electronic production streams until then.

EPUB 3 alone isn’t going to solve all the challenges that exist in digital content creation, but the new revision adds a lot of new weapons to your arsenal, making it that much easier to make high-quality ebooks. The specification is also so newly minted that trying to predict what challenges it will bring with it is a bit premature. Some we can all see coming, like audio and video size and location inside the container file or outside possibly affecting playback. But until the content gets developed, distributed and consumed, it’s hard to say which of the many models that could emerge will prove best. I’m confident, though, that the IDPF will be providing guidance and instruction to producers as these kinds of issues develop, if not working to fix them in future revisions.

How do web standards affect EPUB 3?

Matt Garrish: The challenge creating a format like EPUB is navigating the unstable landscape that results when you have to build on top of moving targets. On the one hand, you have an HTML5 specification that isn’t finished. On the other, you have browser makers already implementing the standard and the features becoming generally available. Do you wait years and years until the specification is “signed, sealed and delivered,” or do you jump in head first and take advantage of what exists now? The IDPF obviously opted to make the leap, so a good deal of the revision work went into circumscribing how to use the technologies in the state they’re in so producers don’t have to worry about future incompatibilities.

There’s little to worry about in terms of using the new HTML5 elements that are available, like audio and video. But there’s always concern when you have two agencies separately maintaining the same standard, as is the case right now with the W3C and WHATWG. If browser cores start supporting custom new additions, as the WHATWG encourages, then suddenly you have a situation where reading systems may render features that are not allowed by the EPUB 3 specification. With the door open, how do you manage the standard and ensure interoperability between devices if people jump on a feature because they discover one platform supports it even though others possibly don’t? The IDPF has plans for integrating experimental features using the epub:switch element, but it’s not an easy problem to solve.

CSS3 is another unfinished suite of specifications, and its support in EPUB 3 was a little trickier than HTML5’s. Many of the specifications are now reaching candidate recommendation status (i.e., they’re at the point where they are considered stable) and are unlikely to change. But there were also needed properties that were not yet stable, which is why you’ll find some prefixed with “-epub-” in the Content Documents specification (primarily from the CSS3 Speech and Text modules). We’ve taken a kind of snapshot in time of the standards they’re defined in so we can use them and not worry if their behaviors change later, if their names are changed, or if they’re dropped entirely. The IDPF was fortunate to have Elika Etemad (@fantasai) helping with the revision and coordinating our issues with the CSS groups, too.

Finally, standardized metadata expression languages (both publication-wide and inline) are still unstable within the W3C, with competing languages being proposed. The EPUB working group decided to postpone making a decision on inclusion of any of these until a future version when the landscape has stabilized. But even still, we’ve improved our metadata significantly with the ability now to add semantic tagging to XHTML5 documents — so you can indicate whether section elements represent parts or chapters or a prologue or epilogue, for example — and to refine metadata in the package document using ONIX code lists and other industry-standard controlled vocabularies.

TOC NY 2012 — O’Reilly’s TOC Conference, being held Feb. 13-15, 2012 in New York City, is where the publishing and tech industries converge. Practitioners and executives from both camps will share what they’ve learned and join together to navigate publishing’s ongoing transformation.

Register to attend TOC 2012

What is accessible publishing? How does it apply to EPUB 3?

Matt Garrish: Accessible publishing is the realm I’ve been working in for the last six or seven years now and probably is not what many people might think it is. There is, disturbingly, still a great chasm in terms of access to information in the new digital age. The oft-quoted estimate in accessibility circles is that only about 5% of the print books produced in any year are ever made available in formats usable by persons with print disabilities. And a big chunk of that 5% is being produced by agencies around the world dedicated to trying to level the playing field. The CNIB here in Canada, which I’ve worked for, is one such agency that maintains a library and a production arm to republish books in accessible formats.

These types of agencies are not publishers in the mainstream sense. They don’t sell the materials they produce and don’t typically create new content, but they work with publishers when they can — or chop and scan when they can’t — to reformat and publish print sources in braille, talking-book format, large print and many other formats. The DAISY Consortium is like a central voice for these organizations. It advocates accessible publishing practices and maintains its own talking-book specification. But I think everyone in the “business” would tell you it would be a better world if none of us had to be employed playing this catch-up game.

Where EPUB 3 comes in is that the IDPF, with great forethought and compassion in my opinion, has made a real effort to pick up the torch that DAISY has been carrying in the digital publishing world. The EPUB 3 revision saw many DAISY members taking an active role in porting accessibility features over, and of course, the revision was chaired by the incredibly dedicated Markus Gylling, the CTO of DAISY and now IDPF, and someone I’ve had the great fortune to have worked with on DAISY specifications in the past.

EPUB 3 is now in line to be the successor to DAISY’s current talking-book format. But just because a format can be authored accessibly doesn’t mean everyone will, or will know how, so we’re working to get guidelines and best practices out for people to be able to create great accessible EPUB 3 content. Whatever comes, this is a fantastic leap forward for cutting the middleman out of the process.

How close will Kindle Format 8 (KF8) bring Amazon to EPUB 3? And, do you expect Amazon to eventually adopt EPUB?

Matt Garrish:Well, that’s a bit of a loaded question — and I don’t presume to speak for the IDPF or its members, to be clear, but I read an article by Thad McIlroy the other day that I think very bluntly summed up the current situation. It was inevitable that Amazon would have to upgrade Mobi when it introduced the Kindle Fire, but I’ll temper my response to say I was disappointed Amazon opted to continue to pursue a second format that parallels EPUB. But I was not surprised.

We’re sort of back to the same place we were a year ago, though. EPUB, to me, remains the richer of the two formats — having accessibility and greater CSS support built in — but you’ll be able to transform your data back and forth from KF8 more easily than if Amazon had stayed with Mobi. The headache once again gets dropped on the consumer. Choose Amazon or everyone else, but don’t expect your books to move back and forth seamlessly either way.

The community-driven nature of EPUB, I expect, will always keep it one step ahead of the competition. You may get periodic pronouncements of new format improvements from Amazon, but the IDPF, in my experience, works hard with industry stakeholders to make sure the format reflects what they actually want and need. Work is already getting started on adding indexes and dictionaries to EPUB, for example, and meetings were just held in Taiwan to deal with fixed formats — involving the manga experts who work at the issues every day.

There are many great things coming down the pipe with EPUB, and with the IDPF committed to keeping the specifications open and accessible, I don’t expect I’ll stop championing the format any time soon.

This interview was edited and condensed.


tags: , , ,