C LICK TO EDIT M ASTER TITLE STYLE Digital Replica Plus

C LICK TO EDIT M ASTER TITLE STYLE 2 History and Motivation Derived from PDF-based print workflows Minimal overhead for publishers Semi-automatic tool for creation No browser needed Predictable, fast render times › Direct GPU utilization, direct HW image decoding “Readability” through article view › … and a basis for Accessiblity

C LICK TO EDIT M ASTER TITLE STYLE 3 Two “Renditions” The page images and the articles Articles are pointed at by the OPF Images are “known” via file structure & presence of the Replica Map Not a great solution, but… All of the problems we solved are very real

C LICK TO EDIT M ASTER TITLE STYLE 4 ReplicaMap Motivations Mapping Between Two Renditions List of Hot-spots Metadata On Spine Items Alternate Linear Flows

C LICK TO EDIT M ASTER TITLE STYLE 5 Mapping Between Two Renditions - Magazines Rendition 1: an image per page Rendition 2: lightly styled XHTML content of articles ReplicaMap provides a list of areas in Rendition 1 that link to Rendition 2.

C LICK TO EDIT M ASTER TITLE STYLE 6 A List of Hot Spots- Magazines In addition to mapping between alternative renditions, hot-spots on a particular page can provide links to other information. In this case – links to individual video messages from the editors.

C LICK TO EDIT M ASTER TITLE STYLE 7 Metadata On Spine Items - Magazines A magazine generally contains a collection of articles, and the articles have their own set of metadata: - Article Title (dc:title) - Byline (dc:creator) - Date (dc:date) - Original Publication/Reprint Info (Note: also applies to collection of short stories)

C LICK TO EDIT M ASTER TITLE STYLE 8 Alternate Flows - Comics On small screen devices, fixed-size rendered pages may not be legible One solution is to provide a set of regions to zoom in on as a traversal of the content. Example: A list of cells in a comic page. Can be thought of as a mapping from one rendition, back to itself (with a different set of media constraints/selectors)

C LICK TO EDIT M ASTER TITLE STYLE 9 Observations The key notion in Fixed Layout is “fixed” › No dynamic layout › Re-layout can cause a host of incompatibilities › No font licensing issues The fixed rendition(s) is the basis Other renditions map onto the fixed version › But can be (and in our case, are) bi-directional Overlays are easy, because › The basis is fixed We strongly favor declarative markup that informs the user experience over embedding the UX in (e.g.) JavaScript

C LICK TO EDIT M ASTER TITLE STYLE 10 More Observations WoodWing, Adobe and others have created non- ePub-based fixed formats › Adobe’s.folio format appears closed and proprietary › WoodWing converging on.folio (abandoning the open “OFIP” format?) These are essentially images of pages, XML describing a “spine” and related notions, and overlays Evolved ePub can and should encompass such formats

C LICK TO EDIT M ASTER TITLE STYLE 11 Futures & Recommendations Formalize replica map and call it Rendition Map › Fix the “bug” in CFIs that prevent them from referencing non-default renditions Make multiple renditions useful Images should be legal spine items B&N is announcing, and will release to Open Source, an InDesign plug-in to create “DRP” directly, including “article mode” Please see the IDPF Wiki for details on RenditionMap and related thoughts and samples

C LICK TO EDIT M ASTER TITLE STYLE 12 Thank You!