ENTRIES TAGGED "Bill McCoy"
The future of the book is inherently linked to the browser
One common misnomer I have come across is that EPUB3 is ‘a technology’ – something in and of itself. I believe this category mistake is largely a result of the the IDPF’s (the organisation that maintains EPUB3) success in promoting EPUB as a ‘standalone’ technology to the publishing world.
Two experts help us navigate the ebook format jungle
One of the benefits of working on TOC is that I get to see some of the behind-the-scenes industry debates that take place via email. Since it’s “formats” month here in TOC-land I thought it would be fun to share a thread about HTML5 vs. EPUB 3 featuring O’Reilly’s Sanders Kleinfeld and the IDPF’s Bill McCoy. They’ve both agreed to share this thread with the TOC community since it helps clarify the state of both EPUB 3 and HTML5.
It all started with an HTML5 interview I did with Sanders earlier this month. Bill reached out to Sanders as follows:
Your mileage may vary, especially on the Nook
I also agree with you that Web-technologies-based apps are the future for experience delivery, both in browser and increasingly for native-class apps that are liberated from the browser (whether wrapped in PhoneGap or CEF, W8 Metro apps or the new Chrome Packaged App model Google rolled out this summer at I/O).
Sanders: Yes, I think what I find so frustrating is that we’ve got tablets on the market like the Nook, which use two different engines to render Web content–one for the Web browser and one for the ereader–and the ereader is lagging so far behind the browser in HTML5 support. The ereader is being treated like a second-class citizen, even though it’s ostensibly the primary feature of the tablet (or at least the primary feature by which the tablet is being marketed; I concede that there are many people buying the Nook who just want a low-cost Android tablet, and have no intention of reading ebooks on it).
One of the things I appreciate most about iBooks is that it uses the same Webkit engine as Mobile Safari, and if you test the same HTML5 content in Safari and in iBooks, you usually get the same results.
Distinguishing apps from ebooks
Bill: But… despite all this violent agreement… I’m having a hard time with your contention in the interview that “a lot less is going to fall in the eBook side than it does now for enhanced text and graphics… anything that’s more enhanced is going to drift over to the app side… we’ll have our standard EPUBs for fiction/nonfiction and then biology textbooks will be on the other side”. That’s what I want to probe on in this email.
Sanders: I’ve thought about this quite a bit after my initial conversation with Joe, and I think the debate of “ebook” vs. “app” can be pretty facile if you’re not careful about how you define those somewhat loaded terms. And I think I failed to do a good job of that in my interview. So let me step back and try to do better now.
I think Phase 1 of ebook creation for publishers was basically, “Let’s take all our print books and digitize them so they can be read on a Kindle or iPad”, without much in the way of innovation in terms of interactivity, customized rendering for a reflowable context, or even hyperlinking.
I think we’ve now graduated to Phase 2, where publishers are thinking, “How can we make customized digital content for tablet devices, instead of plain-old text-and-graphics ebooks? Do I make an ‘app’ or do I make an ‘enhanced ebook?'” I think publishers are generally taking two approaches to this:
Approach #1: Hire on software developers to make full-fledged native apps they can sell in the app stores for iPad/iPhone/iPad and Android (lots of these are children’s titles, e.g. “Finding Nemo: My Puzzle Book“)
Approach #2: Make an “enhanced ebook”, which takes the standard Phase 1 text-and-graphics context, and then grafts on some multimedia features, like audio and video clips (here I’m thinking of the Steven Tyler memoir “Does the Noise in My Head Bother You (Enhanced Edition)“, which was featured prominently in Ana Maria Allessi’s talk at Editech)
I’m rather against Approach #2, because I don’t think it’s especially innovative, and I don’t think it’s what customers really want out of next-generation e-content. I feel like the whole notion of “enhanced ebooks” is somewhat of a transitional concept, as publishers start making baby steps in rethinking how they produce content for a Digital First world. In the long term (next 5 years or so), I think a large part of the “enhanced-ebook” middle ground is going to go away, and ebook content is going to fall more neatly into one of two categories:
Category 1: The standard text-and-graphic content that you can read on even the lowest-end eInk ereader (because I don’t think all-text fiction/nonfiction is ever going to go out of favor)
Category 2: Everything else, which will be more and more app-like in the sense that it will be highly interactive, to-some-degree social (commenting, linked to Facebook/Twitter, etc.), and conceived from the start for a Web context (densely hyperlinked, with sophisticated mechanisms to search content and navigate it in a nonlinear fashion)
So, that’s what I was getting at above; I just wish I had articulated it better in my interview.
That’s just part one, folks. Stay tuned later this week for excerpts from the rest of the thread where Bill and Sanders talk further about the subtleties of EPUB 3, HTML5 and web apps.
EPUB3 is a big step forward but we haven't seen all the benefits it has to offer
This month’s TOC theme is “formats.” Even though our customers still tend to favor PDF it’s clear that mobi and EPUB are the formats with all the momentum. In order to get the scoop on EPUB I decided to go right to the source. The IDPF is the organization that develops and maintains the EPUB standard and Bill McCoy is the IDPF’s Executive Director. Bill was kind enough to sit down and talk with me about the current state of EPUB and where it’s heading.
Key points from the full audio interview (below) include:
- HTML5’s impact — EPUB3 is based on HTML5 and brings with it all the rich functionality that HTML5 has to offer. Global language support and accessibility are two very important improvements in EPUB3.
- Why do we need both EPUB3 and HTML5? — Bill points out that EPUB is a “reliable container” within which HTML5 content can be distributed. EPUB also allows you to step back from HTML5 coding and focus more on the structure of the document itself.
- Fixed layout — PDF is designed with fixed layout in mind whereas EPUB not only supports fixed layout but it also offers the reflowable option as well as a hybrid solution for those situations where both fixed and reflowable are needed in the same product.
- 12 years in the making — I’m puzzled over why it’s taking so long for EPUB3 support to show up on devices and in apps. Bill reminds me it was a pretty significant jump from EPUB2 to EPUB3 but that we’re already seeing signs of significant progress.
- Beyond today’s EPUB3 — Bill prefers to focus on EPUB3 but I did manage to pry a few details from him about what we can expect in the future: Advanced fixed layout (e.g., Manga), adaptive layout (page templates), dictionaries, indexes and annotations.
For more information be sure to download a copy of our free ebook, co-published with the IDPF, What Is EPUB3? If you’re attending the Frankfurt Book Fair you’ll also want to register for TOC Frankfurt to hear Bill and I debate the pros and cons of DRM. (Are there really any DRM pros?!)
You can listen the entire interview in the audio player below.