Informative markup examples are in monospace font. Terms defined in the Terminology are in capital case. Normative and informative references are enclosed in square brackets. Only the first instance in each section is linked.
#EPUB PACKAGER CODE#
Links to markup and code definitions are underlined and in red-orange monospace font. The following typographic conventions are used in this specification:Īll markup (elements, attributes, properties), code (JavaScript, pseudo-code), machine processable values (string, characters, media types) and file names are in red-orange monospace font. A Scriptable Component conforms to all content requirements in this specification and in. Ī scripted Distributable Object that is distributed for use in other EPUB Publications. A Packaged Component is a Packaged Object that meets the additional requirement defined in 3.2 Packaged Components. The Packaged Component is the distributable package for the Scriptable Component. An Embedded Component is an Embedded Object that meets the additional requirements defined in 3.3 Embedding Components. The collection element definition of the Scriptable Component created when a Packaged Component is integrated into a Destination EPUB. The EPUB Publication into which an Scriptable Component is integrated for use.
The Base Document is the Scripted Content Document integrators reference to invoke a Scriptable Component, and that conforms to the content requirements defined in. Refer to for definitions of Distributable Object-specific terminology used in this document. Refer to the EPUB Specifications for definitions of EPUB-specific terminology used in this document. This specification subsets the framework for identifying, packaging and integrating objects defined in the EPUB Distributable Objects 1.0 specification. This section is informative 1.2.1 Relationship to Distributable Objects
Standalone debugging of Scriptable Components is possible, as the Scriptable Components can be ingested into any Reading System with scripting support (a component is simply a “page” with spine-level scripting).Ĭommon EPUB packaging also makes it easier to integrate and use Scriptable Components in EPUB Publications, as the process is typically no more involved than copying the resources and metadata into the Destination EPUB.Fixed-layout metadata can be used to communicate the desired aspect ratio.The Package Document can be used to store Scriptable Component metadata.The epubcheck validation tool can be used to ensure validity of the Scriptable Components, and that all necessary resources are present.īy packaging Scriptable Components as EPUB Publications for distribution, all of the following benefits are realized: This specification, EPUB Scriptable Components Packaging and Integration, defines a method for the creation and inclusion of dynamic and interactive components in EPUB® Publications. Example Packaging and IntegrationĪppendix B. This document may be updated, replaced, or rendered obsolete by other documents at any time.ġ.2.1 Relationship to Distributable Objectsģ.2.4.3.4 The epubsc:storage-required propertyģ.2.4.3.5 The epubsc:network-access-required propertyģ.2.4.3.6 The epubsc:required-params propertyĪppendix A. This document is an Draft Specification, produced by the IDPF EPUB 3 Working Group. ĮPUB is a registered trademark of the International Digital Publishing Forum. Reproduction and dissemination of this work with changes is prohibited except with the written permission of the International Digital Publishing Forum (IDPF). This work is protected under Title 17 of the United States Code. EPUB Scriptable Components Packaging and Integration 1.0Ĭopyright © 2013-2015 International Digital Publishing Forum™Īll rights reserved.
0 kommentar(er)
