Screen Shot 2012 05 30 at 9 55 01 AM

Markus Gylling, CTO, IDPF:  it is the members of IDPF who will ultimately decide what happens in the future.  No plans for EPUB4 at this time.  Will be future maintenance releases which will start in the autumn.  IDPF is working in a modular manner to enhance and update existing features.  No changes to the core kernel.  Ongoing project in how to define glossaries and dictionaries in EPUB.  This has been missing too long. Use the dictionary as a book and as a service.  Publishing drafts in the late Summer.  Indexes: current situation of indexes in ebooks is poor.  The working group is trying to bring this into the modern world.  Linking and annotations is “lurking” including interoperable annotations.  Ties into the problem of inter-publication linking.  R but readium, reference implementation of an EPUB reader, is rapidly reaching feature complete.  Available are  EPUB3 samples have increased.  EpubCheck is not going away but are working on a new version and hoping to get something out this year.  Latest version, B5, works with both EPUB 2 and 3.  An EPUB Standard Widget Tooklit is in the planning stages.  All current projects are listed at

Garth Conboy, Google:  Completed the EPUB fixed layout module in March.  Not all that exciting from a specification standpoint and is basically a spec for metadata describing a fixed layout.  One page per stine item, spread support & control.  Can have fixed layout spine items in a reflowable layout.  Advanced Adaptive Layout is being brought out quickly.  Lightweight Content Protection: interoperability is a key motivator.  Does not prevent DRM-free from being the ultimate goal.  Request for comments is out.  May or may not start an effort.  If anything were to happen in this area, lightweight is defined as in implementation, user experience and intrusion.  Very early stage and in six months will now if there is any direction. 

Roger Webster, Barnes & Noble:  Working on Advanced “Hybrid” Layouts: includes multiple renditions with multiple root files, rendition selection, rendition mapping and panel-by-panel navigation and hotspots. Books are now software: EPUB3 books are now software using the same open technologies as the web.  But books are not web pages.  They have different processing models.  In a web page everything is visible, but in a book only stuff on the current page is visible.  EPUB3s are collections of web pages (spine items).  Need to look at EPUB specific Javascript APIs.  There a book-specific events that could be called out.  Today we access window and document objects,, but what do they mean in the context of a book?  Context is lost in following the pages of a book and so need a more context-sensitive book DOM: sharing context between pages, chapters and book.  


The TeleRead community values your civil and thoughtful comments. We use a cache, so expect a delay. Problems? E-mail