EPUB® 3 defines a distribution and interchange format for digital publications and documents. The EPUB
format provides a means of representing, packaging, and encoding structured and semantically enhanced
Web content — including HTML, CSS, SVG, and other resources — for distribution in a single-file
container.
This specification defines the authoring requirements for EPUB Publications and represents the third
major revision of the standard.
Status of This Document
This section describes the status of this
document at the time of its publication. A list of current W3C
publications and the latest revision of this technical report can be found
in the W3C technical reports index at
https://www.w3.org/TR/.
Publication as a Working Draft does not
imply endorsement by W3C and its Members.
This is a draft document and may be updated, replaced or obsoleted by other
documents at any time. It is inappropriate to cite this document as other
than work in progress.
This document was produced by a group
operating under the
W3C Patent
Policy.
W3C maintains a
public list of any patent disclosures
made in connection with the deliverables of
the group; that page also includes
instructions for disclosing a patent. An individual who has actual
knowledge of a patent which the individual believes contains
Essential Claim(s)
must disclose the information in accordance with
section 6 of the W3C Patent Policy.
EPUB 3 has been widely adopted as the format for digital books (ebooks), and this revision continues
to increase the format's capabilities to better support a wider range of publication requirements,
including complex layouts, rich media and interactivity, and global typography features. The
expectation is that publishers will utilize the EPUB 3 format for a broad range of content,
including books, magazines, and educational, professional, and scientific publications.
This specification represents the core of EPUB 3 and includes the conformance requirements for
EPUB Publications — the product of the standard. The other specifications that comprise
EPUB 3 are as follows:
These specifications represent the formal list recognized as belonging to EPUB 3 and that contain
functionality normatively referenced as part of the standard. The development of extension
specifications periodically adds new functionality to EPUB Publications. Features and functionality
defined outside of core revisions to the standard, while not formally recognized in this
specification, are nonetheless available for EPUB Creators and Reading System developers to
use.
The informative EPUB 3 Overview [EPUB-OVERVIEW-33] provides a
general introduction to EPUB 3. A list of technical changes from the previous version is also
available in the change log.
1.2 Organization
This section is non-normative.
This section reviews the organization of the EPUB specifications through the central product they
define: the EPUB Publication.
An EPUB Publication is typically represented by a single Package Document. This document
includes metadata used by Reading Systems to present the content to the user, such as the
title and author for display in a bookshelf as well as rendering metadata (e.g., whether the content
is reflowable or has a fixed layout). It also provides a manifest of resources and includes a
spine that lists the default sequence in which to render documents as a user progresses
through the content. Refer to 2.3 Package Document for the requirements for the Package
Document.
An EPUB Publication also includes another key file called the EPUB Navigation Document. This
document provides critical navigation capabilities, such as the table of contents, that allow users
to navigate the content quickly and easily. Refer to 4. EPUB Navigation Document for more information
about this document.
The actual content of an EPUB Publication — what users are presented with when they begin
reading — is built on the Open Web Platform and comes in two flavors: XHTML and SVG. Called
EPUB Content Documents, these documents typically reference many additional resources
required for their proper rendering, such as images, audio and video clips, scripts, and style
sheets.
Refer to 3. EPUB Content Documents for detailed information about the rules and requirements to
produce EPUB Content Documents, and [EPUB-A11Y-11] for accessibility requirements.
Media Overlay Documents complement EPUB Content Documents. They provide declarative markup for
synchronizing the text in EPUB Content Documents with prerecorded audio. The result is the ability
to create a read-aloud experience where Reading Systems highlight the text as it is narrated.
Refer to 7. Media Overlays for the definition of Media Overlay Documents.
A ZIP-based archive with the file extension .epub bundles the EPUB Publication's
resources for distribution. As conformant ZIP archives, EPUB Publications can be unzipped by many
software programs, simplifying both their production and consumption.
The container format not only provides a means of determining that the zipped content represents an
EPUB Publication (the mimetype file), but also provides a universally-named directory
of informative resources (/META-INF). Key among these resources is the
container.xml file, which directs Reading Systems to the available Package
Documents. Refer to 6. Open Container Format for more information about the Container format.
While conceptually simple, an EPUB Publication is more than just a collection of HTML pages and
dependent assets in a ZIP package as presented here. Additional information about the primary
features and functionality that EPUB Publications provide to enhance the reading experience is
available from the referenced specifications, and a more general introduction to the features of
EPUB 3 is provided in the informative [EPUB-OVERVIEW-33].
Refer to [EPUB-RS-33] for the processing requirements for Reading Systems. Although it is not
necessary that EPUB Creators read that document to create EPUB Publications, an understanding
of how Reading Systems present the content can help craft publications for optimal presentation to
users.
1.3 Relationship to Other Specifications
This section is non-normative.
1.3.1 Relationship to HTML
The [HTML] standard is continuously evolving — there are no longer versioned releases of
it. That standard, in turn, references various technologies that continue to evolve, such as
MathML, SVG, CSS, and JavaScript.
The benefit of this approach for EPUB is that EPUB Publications always keep pace with
changes to the Web without the need for new revisions. EPUB Creators, however, must keep
track of the various changes to HTML and the technologies it references to ensure they keep
their processes up to date.
Caution
As HTML evolves, it is possible that previously-valid features may become obsolete or be
removed. In general, however, the removal of features typically only occurs when serious
issues arise with them (e.g., lack of support in browsers, security issues).
This specification does not reference a specific version of [SVG], but instead uses an undated
reference. Whenever there is any ambiguity in this reference, the latest recommended
specification is the authoritative reference.
This approach ensures that EPUB will always keep pace with changes to the SVG standard. EPUB
Creators, however, must keep track of changes to the SVG standard to ensure they keep
their processes up to date.
Caution
As SVG evolves, features previously-valid features may become obsolete or be removed. The
Working Group anticipates the W3C will make any such changes carefully to ensure minimal
disruption, but in the case of a backwards-incompatible revision the Working Group could
revisit the use of an undated reference.
1.3.3 Relationship to CSS
EPUB 3 supports CSS as defined by the CSS Working Group Snapshot [CSSSnapshot]. EPUB 3 also
maintains some prefixed CSS properties, to ensure consistent support for global languages.
This specification refers to the [URL] standard for terminology and processing related to URLs
expressed in EPUB Publications. It is anticipated that new and revised Web formats will adopt
this standard, but until then this may put this specification in conflict with the internal
requirements for some formats (e.g., valid relative paths), specifically with respect to the use
of internationalized URLs. If a format does not allow internationalized URLs (i.e., URLs must
conform to [RFC3986] or earlier), that requirement takes precedence within those
resources.
1.4 Terminology
This specification defines the following terms specific to EPUB 3. They appear capitalized wherever
used.
Only the first instance of a term in a section links to its definition.
Codec
Codec refers to content that has intrinsic binary format qualities, such as video and audio
media types designed for optimum compression or that provide optimized streaming
capabilities.
EPUB Container and OCF ZIP Container are synonymous.
EPUB Content Document
A Publication Resource with an XHTML or SVG media type that contains all or part of
the content of an EPUB Publication (i.e., the textual, visual and/or audio content). These
resources must conform to their respective XHTML or
SVG definitions to be used in the spine or be
referenced from another EPUB Content Document.
The person(s) or organization responsible for the creation of an EPUB Publication.
Depending on the process used to produce EPUB Publications, EPUB Creator may sometimes refer
to responsibilities of the organization (e.g., the publisher) or the individuals preparing
the publication (e.g., technical editors).
Note
Previous versions of this specification referred to the EPUB Creator as the Author.
EPUB Navigation
Document
A specialization of the XHTML Content Document that contains human- and
machine-readable global navigation information. The EPUB Navigation Document conforms to the
constraints expressed in 4. EPUB Navigation Document.
EPUB Publication
A logical document entity consisting of a set of interrelated resources packaged in an EPUB Container.
An EPUB Publication typically represents a single intellectual or artistic work, but this
specification does not restrict the nature of the content.
EPUB Reading System (or Reading System)
A system that processes EPUB Publications for presentation to a user in a manner
conformant with this specification.
File Name
The name of any type of file within an OCF Abstract Container, whether a directory or
a file within a directory.
File Path
The File Path of a file or directory is its full path relative to the root directory, as
defined by the algorithm specified in 6.1.4 Deriving File Paths.
An XML document that associates the XHTML Content Document with pre-recorded audio
narration to provide a synchronized playback experience, as defined in 7. Media Overlays.
Non-Codec
Non-Codec refers to content types that benefit from compression due to the nature of their
internal data structure, such as file formats based on character strings (for example, HTML,
CSS, etc.).
A Publication Resource that describes the rendering of an EPUB Publication, as
defined in 2.3 Package Document. The Package Document carries meta information
about the EPUB Publication, provides a manifest of resources and defines a default reading
order.
Publication Resource
A resource that contains content or instructions that contribute to the logic and rendering
of an EPUB Publication. In the absence of this resource, Reading Systems may
not render the EPUB Publication as the EPUB Creator intends. Examples of Publication
Resources include the Package Document, EPUB Content Document, CSS Style
Sheets, audio, video, images, embedded fonts, and scripts.
EPUB Creators typically list Publication Resources in the Package Document manifest and bundle them in the EPUB Container,
with the following exceptions:
they do not have to list resources encoded as data URLs
in the manifest; and
Examples of resources that are not Publication Resources include those identified in Package
Document link elements and those identified in
outbound hyperlinks that resolve to Remote Resources (e.g., referenced from the
href attribute of an [HTML] a element).
Remote Resource
A resource that is located outside of the EPUB Container, typically, but not
necessarily, online.
As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative.
The key words MAY, MUST, MUST NOT, OPTIONAL, RECOMMENDED, REQUIRED, SHOULD, and SHOULD NOT in this document
are to be interpreted as described in
BCP 14
[RFC2119] [RFC8174]
when, and only when, they appear in all capitals, as shown here.
For convenience, the following namespace prefixes [XML-NAMES] are used in this specification
without explicitly being declared. EPUB Creators MUST declare these prefixes to use them in an
EPUB Content Document.
prefix
URI
epub
http://www.idpf.org/2007/ops
2. EPUB Publications
2.1 Conformance Criteria
An EPUB Publication:
MUST define at least one rendering of its content as follows:
The Working Group typically only includes formats as Core Media Type Resources when they have
broad support in web browser cores — the rendering engines that EPUB 3 Reading Systems
build upon. They are an agreement between Reading System developers and EPUB Creators to
ensure the predictability of rendering of EPUB Publications.
Inclusion as a Core Media Type Resource does not mean that all Reading Systems will support
the rendering of a resource, however. Reading Systems support also depends on the
capabilities of the application (e.g., a Reading System with a Viewport must support
image Core Media Type Resources, but a Reading System without a Viewport does not). Refer to
Core Media Types [EPUB-RS-33] for
more information about which Reading Systems rendering capabilities require support for
which Core Media Type Resources.
Foreign Resources come with no guarantee of rendering support, which is why they require a
fallback to a Core Media Type Resource. EPUB Publications should be fully consumable on any
conforming Reading System, so providing a fallback is necessary to ensure that the use of
Foreign Resources does not impact on the ability of the user to consume the content.
EPUB also exempts some [HTML] elements from support requirements (see 3.1.4.4 Foreign Resource Restrictions). Resources referenced from these elements are
neither Core Media Type Resources nor Foreign Resources — they do not require
fallbacks, but they also have no support requirements.
The columns in the following table represent the following information:
Media Type—The MIME media type [RFC2046] used to represent the
given Publication Resource in the manifest.
If the table lists more than one media type, the first one is the preferred media
type. EPUB Creators should use the preferred media type for all new EPUB
Publications.
Content Type Definition—The specification to which the given Core Media
Type Resource must conform.
Applies to—The Publication Resource type(s) that the Media Type and
Content Type Definition applies to.
EPUB 3 allows EPUB Creators to include any video
codecs without fallbacks, although none are technically Core Media Type
Resources. Although the Working Group recommends that Reading Systems support at
least one of the H.264 [H264] and VP8 [RFC6386] video codecs, support is
not a conformance requirement — a Reading System might support other video
codecs, or none at all. EPUB Creators must consider factors such as breadth of
adoption, video playback quality, and technology usage royalty requirements when
making a choice to include video in either format, or both.
Tracks
EPUB Creators can include any kind of audio or
video track (for example, [WebVTT] captions, subtitles and descriptions)
without a fallback. Refer to 3.1.4.4 Foreign Resource Restrictions for more
information.
This exception allows EPUB Creators to include resources in the EPUB
Container that are not for use by EPUB Reading Systems. The primary case for this
exception is to allow data files to travel with an EPUB Publication, whether for scripts to
use in their constituent EPUB Content Documents or for external applications to use (e.g., a
scientific journal might include a data set with instructions on how to extract it from the
EPUB Container).
This specification also exempts some elements from Core Media Type requirements. In these
cases, Foreign Resources MAY be referenced without a fallback. For more information, refer
to 3.1.4.4 Foreign Resource Restrictions.
EPUB Creators MUST provide fallbacks for Foreign Resources in all other
cases. Fallbacks take one of the following forms:
intrinsic fallback mechanisms provided by the host format (e.g., [HTML] elements
often provide the ability to reference more than one media type or to display an
alternate embedded message when a media type cannot be rendered); or
EPUB Creators MUST store all other resources within the EPUB Container.
Storing all resources inside the EPUB Container allows users access to the entire presentation
regardless of connectivity status so is strongly encouraged whenever possible.
The data: URL scheme [RFC2397] is used to encode
resources directly into a URL string. The advantage of this scheme is that it allows EPUB
Creators to embed a resource within another, avoiding the need for an external file.
in the href attribute on [HTML] area elements (except when
inside an iframe element);
in calls to [ECMASCRIPT] window.open or document.open.
Note
The list of prohibited uses for data URLs is subject to change as the respective standards
that allow their use evolve.
This restriction on their use is to prevent security issues and also to ensure that Reading
Systems can determine where to take a user next (i.e., because these resources are not
be listed in the spine).
Resources represented as data URLs are not Publication Resources so are exempt from the
requirement for EPUB Creators to list them in the manifest.
EPUB Creators MUST encode Data URLs as Core Media Types or use them where they can provide a
fallback (i.e., Data URLs are subject to the foreign
resource restrictions).
[HTML] and [SVG] are removing support for the XML base attribute [XMLBase]. EPUB
Creators should avoid using this feature.
2.3 Package Document
2.3.1 Introduction
This section is non-normative.
The Package Document is an XML document that consists of a set of elements that each
encapsulate information about a particular aspect of an EPUB Publication. These elements
serve to centralize metadata, detail the individual resources, and provide the reading order and
other information necessary for its rendering.
The following list summarizes the information found in the Package Document:
Metadata — mechanisms to include and/or reference
metadata.
A spine — an ordered sequence of ID references to top-level
resources in the manifest from which Reading Systems can reach or utilize all other
resources in the set. The spine defines the default reading order.
Collections — a method of encapsulating and
identifying subcomponents within the Package.
Manifest fallback chains — a mechanism
that defines an ordered list of top-level resources as content equivalents. A Reading
System can then choose between the resources based on which it is capable of
rendering.
Note
An EPUB Publication can reference more than one Package Document, allowing for alternative
representations of the content. For more information, refer to 6.1.6.3.1 Container File (container.xml)
All [XML] elements defined in this section are in the http://www.idpf.org/2007/opf
namespace [XML-NAMES] unless otherwise specified.
2.3.2.1 Parsing URLs in the Package Document
To parse a URL string url used in the Package Document, the URL Parser [URL] MUST be applied to
url, with the content URL of the Package Document as base.
2.3.2.2 Shared Attributes
This section provides definitions for shared attributes (i.e., attributes allowed on two or
more elements).
dir
Specifies the base direction [BIDI] of the textual
content and attribute values of the carrying element and its descendants
Allowed values are:
ltr — left-to-right base direction;
rtl — right-to-left base direction; and
auto — base direction is determined using the Unicode Bidi
Algorithm [BIDI].
Reading Systems will
assume the value auto when EPUB Creators omit the attribute or use an
invalid value.
Note
The base direction specified in the dir attribute does not affect
the ordering of characters within directional runs, only the relative ordering
of those runs and the placement of weak directional characters such as
punctuation.
Establishes an association between the current expression and the element or resource
identified by its value. EPUB Creators MUST use as the value a path-relative-scheme-less-URL string, optionally followed by
U+0023 (#) and a URL-fragment string that references the resource or element they are
describing.
The refines attribute is OPTIONAL depending on the type of metadata
expressed. When omitted, the element defines a primary
expression.
When creating expressions about a Publication Resource, the
refines attribute SHOULD specify a fragment identifier that
references the ID of the resource's manifest entry.
Specifies the language of the textual content and attribute values of the carrying
element and its descendants, as defined in section 2.12 Language Identification of [XML]. The value of each
xml:lang attribute MUST be a well-formed language tag [BCP47].
The version attribute specifies the EPUB
specification version to which the given EPUB Publication conforms. The attribute MUST have
the value "3.0" to indicate conformance with EPUB 3.
Note
Updates to this specification do not represent new versions of EPUB 3 (i.e., each new 3.X
specification is a continuation of the EPUB 3 format). The Working Group is committed to
minimizing any changes that would invalidate existing content, allowing the
version attribute value to remain unchanged.
The unique-identifier attribute takes an
IDREF [XML] that identifies the dc:identifier element that provides the preferred, or primary,
identifier.
The Package Document metadata element has two primary functions:
to provide a minimal set of meta information for Reading Systems to use to
internally catalogue an EPUB Publication and make it available to a user
(e.g., to present in a bookshelf).
to provide access to all rendering metadata needed to control the layout and
display of the content (e.g., fixed-layout
properties).
The Package Document does not provide complex metadata encoding capabilities. If EPUB
Creators need to provide more detailed information, they can associate metadata records
(e.g., that conform to an international standard such as [ONIX] or are created for
custom purposes) using the link element. This
approach allows Reading Systems to process the metadata in its native form, avoiding the
potential problems and information loss caused by translating to use the minimal Package
Document structure.
In keeping with this philosophy, the Package Document only has
the following minimal metadata requirements: it MUST contain the [DCTERMS] title, identifier, and language elements together with the
[DCTERMS] modified property. All other
metadata is OPTIONAL.
The meta element provides a generic mechanism
for including metadata properties from any vocabulary.
Although EPUB Creators MAY use this mechanism for any metadata purposes, they will
typically use it to include rendering metadata defined in EPUB specifications.
Note
See [EPUB-A11Y-11] for accessibility metadata recommendations.
2.3.2.4.2 Metadata Values
The Dublin Core elements [DCTERMS] and meta
element have mandatory child text
content [DOM]. This specification refers to this content as the
value of the element in their descriptions.
These elements MUST have non-empty values after leading and trailing
ASCII whitespace [Infra] is stripped (i.e., they must consist of at least one
non-whitespace character).
Whitespace within these element values are not significant. Sequences of one or more
whitespace characters are collapsed to a single space [Infra] during processing .
2.3.2.4.3 DCMES Required Elements
2.3.2.4.3.1 The identifier Element
The [DCTERMS] identifier element contains an identifier such as a
UUID, DOI or ISBN.
Although not static, EPUB Creators should make changes to the Unique Identifier for
an EPUB Publication as infrequently as possible. Unique Identifiers should have
maximal persistence both for referencing and distribution purposes. EPUB Creators
should not issue new identifiers when making minor revisions such as updating
metadata, fixing errata, or making similar minor changes.
EPUB Creators MAY specify additional identifiers. The identifiers should be fully
qualified URIs.
EPUB Creators MAY use the identifier-type
property to indicate that an identifier conforms to an
established system or an issuing authority granted it.
The metadata section MUST contain at least one title
element containing the title for the EPUB Publication.
The first title element in document order is the main
title of the EPUB Publication (i.e., the primary one Reading Systems present to
users).
EPUB Creators should use only a single title element to ensure
consistent rendering of the title in Reading Systems.
Note
Although it is possible to include more than one title element for
multipart titles, Reading System support for additional title
elements is inconsistent. Reading Systems may ignore the additional segments or
combine them in unexpected ways.
For example, the following example shows a basic multipart title:
<metadata …><dc:title>
THE LORD OF THE RINGS
</dc:title><dc:title>
Part One: The Fellowship of the Ring
</dc:title>
…
</metadata>
The same title could instead be expressed using a single dc:title
element as follows:
<metadata …><dc:title>
THE LORD OF THE RINGS, Part One:
The Fellowship of the Ring
</dc:title>
…
</metadata>
Previous versions of this specification recommended using the title-type and display-seq properties to identify
and format the segments of multipart titles (see the Great Cookbooks example). It is still possible to add these semantics
but they are also not well supported.
2.3.2.4.3.3 The language Element
The [DCTERMS] language element specifies the language of the content
of the EPUB Publication.
The metadata section MUST contain at least one language
element. The value of each language element MUST be a well-formed language tag [BCP47].
Although EPUB Creators MAY specify additional language elements for
multilingual Publications, Reading Systems will treat the first
language element in document order as the primary language of the
EPUB Publication.
Note
Publication Resources do not inherit their language from the
dc:language element(s). EPUB Creators must set the language of
a resource using the intrinsic methods of the format.
2.3.2.4.4 DCMES Optional Elements
2.3.2.4.4.1 General Definition
All [DCTERMS] elements except for identifier, language, and title are designated as OPTIONAL. These elements conform
to the following generalized definition:
Element Name
contributor | coverage | creator |
date | description | format |
publisher | relation | rights |
source | subject | type
xml:lang[optional] – only allowed on contributor,
coverage, creator,
description, publisher,
relation, rights, and
subject.
Content Model
Text
This specification does not modify the [DCTERMS] element definitions except as
noted in the following sections.
2.3.2.4.4.2 The contributor Element
The [DCTERMS] contributor element is used to represent the name of a
person, organization, etc. that played a secondary role in the creation of the
content.
The requirements for the contributor element are identical to those for
the creator element in all other
respects.
2.3.2.4.4.3 The creator Element
The [DCTERMS] creator element represents the name of a person,
organization, etc. responsible for the creation of the content. EPUB Creators can associate a role
property with the element to indicate the function the creator played.
The creator element SHOULD contain the name of the creator as EPUB
Creators intend Reading Systems to display it to users.
If an EPUB Publication has more than one creator, EPUB Creators SHOULD specify each
in a separate creator element.
The document order of creator elements in the metadata
section determines the display priority, where the first creator
element encountered is the primary creator.
EPUB Creators SHOULD represent secondary contributors using the contributor element.
2.3.2.4.4.4 The date Element
The [DCTERMS] date element MUST only be used to define the publication
date of the EPUB Publication. The publication date is not the same as the last modified date (the last time the EPUB
Creator changed the EPUB Publication).
It is RECOMMENDED that the date string conform to [ISO8601], particularly the
subset expressed in W3C Date and Time Formats [DateTime], as such strings are both
human and machine readable.
EPUB Creators SHOULD express additional dates using the specialized date properties
available in the [DCTERMS] vocabulary, or similar.
EPUB Publications MUST NOT contain more than one date element.
2.3.2.4.4.5 The subject Element
The [DCTERMS] subject element identifies the subject of the EPUB
Publication. EPUB Creators SHOULD set the value of the element to the
human-readable heading or label, but MAY use a code value if the subject taxonomy
does not provide a separate descriptive label.
EPUB Creators MAY identify the system or scheme they drew the element's value
from using the authority property.
When a scheme is identified, EPUB Creators MUSTassociate a subject code using the term
property.
The values of the subject element and term property
are case sensitive only when the designated scheme requires.
2.3.2.4.4.6 The type Element
The [DCTERMS] type element is used to indicate that the EPUB
Publication is of a specialized type (e.g., annotations or a dictionary packaged in
EPUB format).
The former IDPF EPUB
3 Working Group maintained an informative registry of
specialized EPUB Publication types for use with this element. This
Working Group no longer maintains this registry and does not anticipate
developing new specialized publication types.
2.3.2.4.5 The meta Element
The meta element provides a generic means of including package metadata.
Each meta element defines a metadata expression.
The property attribute takes a property data type value that defines the statement made in the
expression, and the text content of the element represents the assertion. (Refer to D.1 Vocabulary Association Mechanisms for more information.)
This specification defines two types of metadata expressions that EPUB Creators can
define using the meta element:
A primary expression is one in which the expression
defined in the meta element establishes some aspect of the EPUB
Publication. A meta element that omits a refines attribute
defines a primary expression.
A subexpression is one in which the expression defined
in the meta element is associated with another expression or resource
using the refines attribute to enhance its meaning. A subexpression
might refine a media clip, for example, by expressing its duration, or refine a
creator or contributor expression by defining the role of the person.
EPUB Creators MAY use subexpressions to refine the meaning of other subexpressions,
thereby creating chains of information.
Note
All the DCMES [DCTERMS] elements represent primary expressions, and permit
refinement by meta element subexpressions.
The scheme attribute identifies the system or scheme the
EPUB Creator obtained the element's value from. The value of the attribute MUST
be a property data type value that
resolves to the resource that defines the scheme.
2.3.2.4.6 Last Modified Date
The metadata section MUST contain exactly one
[DCTERMS] modified property containing the last modification date. The
value of this property MUST be an [XMLSCHEMA-2] dateTime conformant date of
the form: CCYY-MM-DDThh:mm:ssZ
EPUB Creators MUST express the last modification date in Coordinated Universal Time (UTC)
and MUST terminate it with the "Z" (Zulu) time zone indicator.
EPUB Creators should update the last modified date whenever they make changes to the EPUB
Publication.
EPUB Creators MAY specify additional modified properties in the Package Document
metadata, but they MUST have a different subject (i.e., they require a
refines attribute that references an element or resource).
Note
The requirements for the last modification date are to ensure compatibility with
earlier versions of EPUB 3 that defined a release identifier [EPUBPackages-32] for EPUB Publications.
2.3.2.4.7 The link Element
The link element associates resources with an EPUB Publication, such
as metadata records.
included or embedded in an EPUB Content Document (e.g., a metadata record
serialized as RDFa [RDFA-CORE] or JSON-LD [JSON-LD11] embedded in an
[HTML] script
element).
In all other cases (e.g., when linking to standalone [ONIX] or [XMP] records), the
linked resources are not Publication Resources (i.e., are not subject to Core Media Type requirements) and EPUB Creators
MUST NOT list them in the manifest.
EPUB Creators MAY locate linked resources locally or remotely,
but should consider that Reading Systems are not required to retrieve to Remote
Resources (i.e., Reading Systems might not make Remote Resources available).
The media-type
attribute is OPTIONAL when a linked resource is located outside the EPUB
Container, as more than one media type could be served from the same URL [URL]. EPUB
Creators MUST specify the attribute for all Local Resources.
The OPTIONALhreflang attribute identifies the
language of the linked resource. The value MUST be a well-formed language tag [BCP47].
The REQUIREDrel attribute takes a space-separated
list of property values that establish the
relationship the resource has with the EPUB Publication.
The value of the media-type attribute is not always sufficient to identify
the type of linked resource (e.g., many XML-based record formats use the media type
"application/xml"). To aid Reading Systems in the identification of
such generic resources, the properties attribute can specify a semantic
identifier.
EPUB Creators MAY provide one or
more linked metadata records to enhance the information available
to Reading Systems, but Reading Systems may ignore these records.
When a Reading System processes linked
records [EPUB-RS-33], the document order of link elements is used
to determine which has the highest priority in the case of conflicts (i.e., first in
document order has the highest priority).
Note
Due to the variety of metadata record formats and serializations that an EPUB Creator
can link to an EPUB Publication, and the complexity of comparing metadata properties
between them, this specification does not require Reading Systems to process linked
records.
In addition to full records, EPUB Creators MAY also use the link element to
identify individual metadata properties available in an alternative format.
2.3.2.5 Manifest Section
2.3.2.5.1 The manifest Element
The manifest element provides an exhaustive list of Publication
Resources used in the rendering of the content.
Note that the manifest is not self-referencing: EPUB Creators MUST NOT
specify an item element that refers to the Package Document itself.
Note
Failure to provide a complete manifest of resources may lead to rendering issues.
Reading Systems might not unzip such resources or could prevent access to them for
security reasons.
The fallback attribute takes an IDREF [XML]
that identifies a fallback for the Publication Resource referenced from the
item element, as defined in 2.3.2.5.2.1 Manifest Fallbacks.
EPUB Creators MUST declare all applicable descriptive metadata properties for each
Publication Resource in this attribute (e.g., if the resource is the cover image, contains scripting, or references remote
resources).
EPUB Creators MUST declare exactly one item as the EPUB Navigation
Document using the nav property.
The order of item elements in the manifest is not
significant. The spine
element provides the presentation sequence of content documents.
2.3.2.5.2.1 Manifest Fallbacks
Manifest fallbacks are a feature of the Package Document that create fallback
chains to Core Media Type Resources. They are used to create fallbacks for Foreign
Resources in the spine and when intrinsic fallback
capabilities are not available (e.g., for the [HTML] img element) in order to
satisfy the requirements in 2.2.1.3 Foreign Resources.
The fallback attribute on the
manifestitem element specifies the fallback
for the referenced Publication Resource. The fallback attribute's IDREF
[XML] value MUST resolve to another item in the
manifest. This fallback itemMAY itself specify another
fallback item, and so on.
The ordered list of all the ID references that a Reading System can reach, starting
from a given item's fallback attribute, represents the fallback
chain for that item. The order of the resources in the fallback chain
represents the EPUB Creator's preferred fallback order.
Fallback chains MUST conform to one of the following requirements, as
appropriate:
As it is not possible to use manifest fallbacks for resources represented in data URLs, EPUB Creators can only represent
Foreign Resources as data URLs where an intrinsic fallback mechanism is
available.
2.3.2.5.2.2 Examples
2.3.2.5.3 The bindings Element (Deprecated)
The bindings element defines a set of custom handlers for media types not
supported by this specification. Its use is deprecated.
EPUB Creators MUST list in the spine all
Publication Resources that are hyperlinked to from Publication Resources in the
spine, where hyperlinking encompasses any linking mechanism that
requires the user to navigate away from the current resource. Common hyperlinking
mechanisms include the href attribute of the [HTML] a and area elements and scripted links
(e.g., using DOM Events and/or form elements). The requirement to list hyperlinked
resources applies recursively (i.e., EPUB Creators must list all Publication Resources
hyperlinked from hyperlinked Publication Resources, and so on.).
EPUB Creators also MUST list in the spine all Publication Resources
hyperlinked to from the EPUB Navigation Document, regardless of whether EPUB
Creators include the Navigation Document in the spine.
Note
As Remote Resources referenced from hyperlinks are not Publication Resources,
they are not subject to the requirement to include in the spine (e.g., Web pages and
resources).
Embedded Publication Resources (e.g., via the [HTML] iframe element) must not be
listed in the spine.
The page-progression-direction
attribute sets the global direction in which the content flows. Allowed values are
ltr (left-to-right), rtl (right-to-left) and
default. When EPUB Creators specify the default value,
they are expressing no preference and the Reading System can choose the rendering
direction.
Although the page-progression-direction attribute sets the global flow
direction, individual Content Documents and parts of Content Documents MAY override this
setting (e.g., via the writing-mode CSS property). Reading Systems can also
provide mechanisms to override the default direction (e.g., buttons or settings that
allow the application of alternate style sheets).
The legacytoc attribute takes an IDREF [XML] that identifies the manifest item that
represents the NCX.
2.3.2.6.2 The itemref Element
The itemref element identifies a Publication Resource in the default
reading order.
Each itemref element MUST reference the ID of an item in the manifest via the
IDREF [XML] in its idref attribute, and item IDs MUST NOT be referenced
more than once.
The linear attribute indicates whether the
referenced item contains content that contributes to the primary reading
order and that Reading Systems must read sequentially ("yes"), or auxiliary
content that enhances or augments the primary content that Reading Systems can access
out of sequence ("no"). Examples of auxiliary content include notes,
descriptions, and answer keys.
The linear attribute allows Reading Systems to distinguish content that a
user should access as part of the default reading order from supplementary content which
a Reading System might, for example, present in a popup window or omit from an aural
rendering.
Specifying that content is non-linear does not require Reading Systems to present it in a
specific way, however; it is only a hint to the purpose. Reading Systems may present
non-linear content where it occurs in the spine, for example, or may skip it until users
reach the end of the spine.
Note
EPUB Creators should list non-linear content at the end of the spine except when it
makes sense for users to encounter it between linear spine items.
The spineMUST contain at least one linear
itemref element — whose linear attribute value is
either explicitly or implicitly set to "yes". Reading Systems will assume
the value "yes" for itemref elements without a
linear attribute.
EPUB Creators MUST provide
a means of accessing all non-linear content (e.g., hyperlinks in the content or from the
EPUB Navigation Document).
The collection element allows EPUB Creators to assemble resources into
logical groups for a variety of potential uses: enabling reassembly into a meaningful
unit of content split across multiple EPUB Content Documents (e.g., an index
split across multiple documents), identifying resources for specialized purposes (e.g.,
preview content), or collecting together resources that present additional information
about the EPUB Publication.
The collection element, as defined in this section, represents a generic
framework from which specializations are intended to be derived (e.g., through EPUB
sub-specifications). Such specializations MUST define the purpose of the
collection element, as well as all requirements for its valid
production and use (specifically any requirements that differ from the general framework
presented below).
Each specialization MUST define a role value that uniquely
identifies all conformant collection elements. EPUB Creators MUST identify
the role of each collection element in its role attribute,
whose value MUST be one or more NMTOKENs [XMLSCHEMA-2] and/or absolute-URL-with-fragment
strings [URL].
This specification reserves the use of NMTOKEN values for roles defined in EPUB
specifications. NMTOKEN values not defined by a recognized specification are not valid.
This section does not define any roles.
Third parties MAY define custom roles for the collection element, but they
MUST identify such roles using absolute-URL-with-fragment strings [URL]. Custom roles MUST NOT incorporate
the string "idpf.org" in the host
component [URL] of their identifying URL.
Note
The former IDPF EPUB 3
Working Group maintained both a registry of role extensions and a list of custom extension roles.
This Working Group no longer maintains these registries and does not anticipate
defining new types of collections.
The OPTIONALmetadata element child of
collection is an adaptation of the package metadata element, with the following
differences in syntax and semantics:
EPUB specifications that implement collections MAY override package-level restrictions on
the use of metadata elements.
A collectionMAY define sub-collections through the inclusion of one or more
child collection elements.
The link element child of
collection is an adaptation of the metadata link element, with the following differences in syntax and
semantics:
The rel attribute is OPTIONAL.
The properties attribute also accepts manifest item properties
without a prefix (e.g., so that a collection can declare its own Navigation
Document or cover image).
EPUB Creators MUST NOT specify the refines attribute.
Each link element MUST reference a resource that is a member of the group.
The order of link elements is not significant.
Specializations of the collection element MAY tailor the requirements
defined above to better reflect their needs (e.g., requiring metadata, imposing further
restrictions on the use of elements and attributes, or making the order of
link elements significant). However, the resulting content model MUST
represent a valid subset of the one defined in this section (e.g., specializations
cannot introduce new elements or attributes, or re-introduce those expressly forbidden
above). Specializations MUST NOT define collections in a way that overrides the
requirements of the manifest and spine.
The rendering of an EPUB Publication MUST NOT be dependent on the recognition of
collection elements. The content MUST remain consumable by a user
without any information loss or other significant deterioration.
2.3.2.8 Legacy Content
2.3.2.8.1 The meta Element
The meta element [OPF-201] is a legacy
feature that previously provided a means of including generic metadata. The EPUB 3 meta element, which uses different attributes
and requires text content, replaces this attribute.
For more information about the meta element, refer to its definition in
[OPF-201].
Note
The [OPF-201] meta element is retained in EPUB 3 primarily so that
EPUB Creators can identify the cover image for compatibility with EPUB 2 Reading
Systems. In EPUB 3, the cover image must be identified using the cover-image property on the manifest item for the image.
For more information about the NCX, refer to its definition in [OPF-201].
3. EPUB Content Documents
3.1 XHTML Content Documents
3.1.1 Introduction
This section is non-normative.
This section defines a profile of [HTML] for creating XHTML Content Documents. An instance of
an XML document that conforms to this profile is a Core Media Type Resource and is
referred to in this specification as an XHTML Content Document.
3.1.2 XHTML Requirements
An XHTML Content Document:
MUST be an [HTML] document that conforms to the XHTML syntax.
MAY include extensions to the [HTML] grammar as
defined in 3.1.3 HTML Extensions, and MUST conform to all content
conformance constraints defined therein.
Unless specified otherwise, XHTML Content Documents inherit all definitions of semantics,
structure, and processing behaviors from the [HTML] specification.
Note
The recommendation that EPUB Publications follow the accessibility requirements in
[EPUB-A11Y-11] applies to XHTML Content Documents. See Accessibility.
Although [HTML] allows user agents to support vendor-neutral extensions, unless such extensions are listed in this section, they
are not supported features of EPUB 3.
As the [HTML] head element contains
metadata for the document, structural semantics expressed on this element or any descendant
of it have no meaning.
3.1.3.2 RDFa
The [HTML-RDFA] specification defines a set of attributes that EPUB Creators MAY use in
XHTML Content Documents to semantically enrich the content. The use of these
attributes MUST conform to the requirements defined in [HTML-RDFA].
The [HTML-RDFA] specification defines changes to the [HTML] content model when authors
use RDFa attributes. This modified content model is valid in XHTML Content Documents.
Note
The listing of RDFa does not express a preference on the part of the Working Group, only
that these attributes represent an extension of the HTML grammar. EPUB Creators can also
specify microdata attributes [HTML] and linked data [JSON-LD11] in XHTML Content Documents as
both are natively supported.
3.1.3.3 Content Switching (Deprecated)
The switch element provides a simple mechanism through which EPUB
Creators can tailor the content displayed to users, one that is not dependent on the
scripting capabilities of the EPUB Reading System.
The trigger element enables the creation of markup-defined user interfaces for
controlling multimedia objects, such as audio and video playback, in both scripted and
non-scripted contexts.
Custom attributes MAY be specified on any element in an XHTML Content Document.
When using custom attributes, the content MUST remain consumable by a user without any
information loss or other significant deterioration, regardless of the Reading System it is
rendered on.
3.1.4 HTML Deviations and Constraints
This section defines deviations from, and constraints on, the underlying [HTML] document model
applicable to EPUB 3 XHTML Content Documents.
3.1.4.1 Embedded MathML
XHTML Content Documents support embedded [MATHML3]. Occurrences of MathML markup MUST
conform to the constraints expressed in the MathML specification [MATHML3], with the
following additional restrictions:
Presentation MathML
The math element MUST contain only Presentation MathML, except within the
annotation-xml element.
Content MathML
EPUB Creators MAY include Content MathML within MathML markup in
XHTML Content Documents, and, when present, MUST include it within an
annotation-xml child element of a semantics
element.
When EPUB Creators include Content MathML per
the previous condition, they MUST set the given annotation-xml
element's encoding attribute to either of the functionally-equivalent
values MathML-Content or application/mathml-content+xml,
and the name attribute to contentequiv.
Deprecated MathML
EPUB Creators MUST NOT include elements and attributes
marked as deprecated in [MATHML3] within MathML markup in XHTML Content
Documents.
This subset eases the implementation burden on Reading Systems and promotes accessibility,
while retaining compatibility with [HTML] user agents.
Note
The mathml property of the manifestitem element indicates that an XHTML Content Document contains embedded
MathML.
3.1.4.2 Embedded SVG
XHTML Content Documents support the embedding of SVG document
fragments [SVG] by reference (embedding via reference, for example, from
an img or object element) and by inclusion (embedding via
direct inclusion of the svg element in the XHTML Content Document).
The [HTML] base element can be used to specify the document base URL for the purposes of parsing
URLs. When using it in an EPUB Publication, the interpretation of the
base elements may inadvertently result in references to Remote
Resources, i.e., resources that are outside the EPUB Container. Using the
base element in an EPUB Publication may cause Reading Systems to
misinterpret the location of resources (e.g., relative links to other documents in the
publication might appear as links to a Web site if the base element
specifies an absolute URL). To avoid significant interoperability issues, EPUB Creators
should not use the base element.
3.1.4.3.2 The rp Element
The [HTML] rp element is intended to provide a fallback for older
Reading Systems that do not recognize ruby markup (i.e., a parenthesis
display around ruby markup). As EPUB 3 Reading Systems are ruby-aware, and
can provide fallbacks, EPUB Creators should not use rp elements.
3.1.4.3.3 The embed Element
Since the [HTML] embed element does not include intrinsic facilities to provide
fallback content for Reading Systems that do not support scripting, EPUB Creators
are discouraged from using the element when the referenced resource includes scripting.
The [HTML] object element is a
better alternative, as it includes intrinsic fallback capabilities.
3.1.4.4 Foreign Resource Restrictions
EPUB Creators MAY reference Foreign Resources from
elements that have intrinsic fallback mechanisms, where an intrinsic fallback method is the
capability to offer an alternative presentation if Reading Systems do not support the
foreign resource. For example, most [HTML] embedded
content elements provide options for alternative rendering, such as allowing
multiple sources to be specified or allowing embedded HTML content for when user agents
cannot render a resource. When referencing a Foreign Resource, EPUB Creators MUST provide a
Core Media Type Resource or embedded HTML content via the given element's
intrinsic fallback mechanism.
EPUB Creators MAY embed [HTML] flow content within the audio and video elements for rendering in
older Reading Systems that do not recognize these elements (e.g., EPUB 2 Reading Systems),
but it does not represent a fallback Core Media Type Resource.
Due to the variety of sources that EPUB Creators can
specify in the [HTML] img element,
the following fallback conditions apply to its use:
it MUST reference Core Media Type Resources from its src and
srcset attributes, when EPUB Creators specify those attributes;
and
each sibling source
elementMUST reference a Core Media Type Resource from its
src and srcset attributes unless it specifies a
media type in its type attribute that is not a Core Media
Type.
Otherwise, it MAY reference Foreign Resources in its src and
srcset attributes provided EPUB Creators define a manifest fallback.
EPUB Creators MAY reference Foreign Resources from the
following [HTML] elements without providing a fallback Core Media Type Resource:
Refer to manifest fallbacks for the
provision of fallbacks for elements without intrinsic mechanisms, such as the [HTML]
iframe.
3.2 SVG Content Documents
Caution
Reading Systems may not support all the features of [SVG] or supported them across all
platforms that Reading Systems run on. When utilizing such features, EPUB Creators should
consider the inherent risks on interoperability and document longevity.
3.2.1 Introduction
This section is non-normative.
The Scalable Vector Graphics (SVG) specification [SVG] defines a format for representing
final-form vector graphics and text.
Although EPUB Creators typically use XHTML Content Documents as
the top-level document type, the use of SVG
Content Documents is also permitted. EPUB Creators will typically only need SVGs for
certain special cases, such as when final-form page images are the only suitable representation
of the content (e.g., for cover art or in the context of manga or comic books).
This section defines a profile for [SVG] documents. An instance of an XML document that
conforms to this profile is a Core Media Type Resource and is referred to in this
specification as an SVG Content Document.
Note
This section defines conformance requirements for SVG Content Documents. Refer to 3.1.4.2 Embedded SVG for the conformance requirements for SVG embedded in XHTML
Content Documents.
This section defines requirements for technologies usable in both XHTML and SVG Content
Documents.
3.3.1 Cascading Style Sheets (CSS)
3.3.1.1 Introduction
This section is non-normative.
CSS is an integral part of the Open Web Platform. Readers, publishers, and document authors
expect CSS to "just work," as they expect HTML to just work.
In the past, EPUB defined a profile of CSS that mandated support for certain properties and
provided prefixed versions of numerous other properties. Although the CSS Working Group no
longer recommends the use of prefixed properties, this specification maintains some prefixed
properties to avoid breaking existing content. But with the minor exceptions defined in this
section, EPUB defers to the W3C to define CSS.
Note
Keep in mind that some Reading Systems will not support all desired features of
CSS. The following are known to be particularly problematic:
Reading System-induced pagination can interact poorly with style sheets as
Reading Systems sometimes paginate using columns. This may result in incorrect
values for viewport sizes. Fixed and absolute positioning are particularly
problematic.
Some types of screens will render animations and transitions poorly (e.g., those
with high latency).
3.3.1.2 CSS Requirements
A CSS style sheet:
MAY include any CSS properties, with the following
exceptions:
MUST be encoded in UTF-8 or UTF-16 [Unicode], with UTF-8
as the RECOMMENDED encoding.
Note
This specification restricts the use of the direction and
unicode-bidi properties because Reading Systems may not implement, or
may switch off, CSS processing. EPUB Creators must use the following format-specific
methods when they need control over these aspects of the rendering:
Earlier version of EPUB included prefixed CSS properties, as many CSS features related to
world languages were not yet mature. To ensure backwards compatibility for content authored
using these prefixes, they have been retained in this specification. Unless otherwise noted,
prefixed properties and values behave exactly as their unprefixed equivalents as described
in the appropriate CSS specification. The prefixed properties are documented in an Appendix.
Caution
EPUB Creators should use unprefixed properties and Reading Systems should
support current CSS specifications. This specification retains the widely-used prefixed
properties from [EPUBContentDocs-301], but removes support for the less-used ones.
EPUB Creators should use CSS-native solutions for the removed properties whenever
available.
The Working Group recommends that EPUB Creators currently using these prefixed properties
move to unprefixed versions as soon as support allows, as the Working Group does not
anticipate supporting them in the next major version of EPUB.
Note
In some cases, the unprefixed versions of these properties now support
additional values. Reading Systems may support these values even with the prefixed
property.
3.3.2 Scripting
3.3.2.1 Script Inclusion
EPUB Content DocumentsMAY contain scripting using the facilities defined for this in
the respective underlying specifications ([HTML] and [SVG]). When an EPUB Content
Document contains scripting, this specification refers to it as a Scripted Content
Document. This label also applies to XHTML Content Documents when they
contain instances of [HTML] forms.
When an [HTML] script element contains a data
block [HTML], it does not represent scripted content.
Note
[SVG] does not define data blocks as of publication, but the same exclusion would apply
if a future update adds the concept.
EPUB Creators should note that Reading Systems are required to behave as though a unique origin [URL] has been assigned to each EPUB Publication. In
practice, this means that it is not possible for scripts to share data between EPUB
Publications.
Which context a script is used in also determines the
rights and restrictions that a Reading System places on it (refer to Scripting Conformance [EPUB-RS-33]
for more information).
Note
Reading Systems may render Scripted Content Documents in a manner that disables other
EPUB capabilities and/or provides a different rendering and user experience (e.g., by
disabling pagination).
Whether EPUB Creators embed the code directly in the script element or reference
it via the element's src attribute makes no difference to its executing
context.
Which context EPUB Creators use for their scripts affects both what actions the scripts can
perform and the likelihood of support in Reading Systems, as described in the following
subsections.
Note
Refer to G.1 Scripting Contexts for an example of the difference
between the two contexts.
3.3.2.2.1 Container-Constrained Scripts
A container-constrained script is either of the following:
An instance of the [SVG] script element contained in an SVG Content
Document that is embedded in a parent XHTML Content Document using the
[HTML] iframe
element.
A container-constrained script MUST NOT contain
instructions for modifying the DOM of the EPUB Content Document that embeds it (i.e.,
the one that contains the iframe element). It also MUST NOT contain
instructions for manipulating the size of its containing rectangle.
EPUB Creators should ensure container-constrained scripts degrade gracefully in Reading
Systems without scripting support (see 3.3.2.5 Scripting Fallbacks).
Note
EPUB Creators choosing to restrict the usage of scripting to the
container-constrained model will ensure a more consistent user experience between
scripted and non-scripted content (e.g., consistent pagination behavior).
Top-level Content Documents that include
spine-level scripting SHOULD remain consumable by the user without any information loss
or other significant deterioration when scripting is disabled or not available (e.g., by
employing progressive enhancement techniques or fallbacks). Failing to account for non-scripted environments in Top-level
Content Documents can result in EPUB Publications being unreadable.
3.3.2.3 Event Model
This section is non-normative.
EPUB Creators should consider the wide variety of possible Reading System
implementations when adding scripting functionality to their EPUB Publications (e.g., not
all devices have physical keyboards, and in many cases a soft keyboard is activated only for
text input elements). Consequently, EPUB Creators should not rely on keyboard events alone;
they should always provide alternative ways to trigger a desired action.
3.3.2.4 Scripting Accessibility
EPUB Content Documents that contain scripting SHOULD employ
relevant [WAI-ARIA] accessibility techniques to ensure that the content remains consumable
by all users.
3.3.2.5 Scripting Fallbacks
EPUB Content Documents that contain scripting MAY provide
fallbacks for such content, either by using intrinsic fallback mechanisms (such as those
available for the [HTML] object
and canvas elements) or, when an
intrinsic fallback is not applicable, by using a manifest-level fallback.
EPUB Creators MUST ensure that scripts only
generate Core Media Type Resources or fragments
thereof.
4. EPUB Navigation Document
4.1 Introduction
This section is non-normative.
The EPUB Navigation Document is a mandatory component of an EPUB
Publication. It allows EPUB Creators to include a human- and machine-readable global
navigation layer, thereby ensuring increased usability and accessibility for the user.
The EPUB Navigation Document is not exclusively for machine processing, however. There are no
restrictions on the structure or content of the EPUB Navigation Document outside of the specialized
navigation elements (i.e., EPUB Creators can mark the rest of the document up like any other XHTML
Content Document). As a result, it can also be part of the linear reading order, avoiding the need
for duplicate tables of contents. EPUB Creators can hide navigation elements that are only for
machine processing (e.g., the page list) with the hidden
attribute.
Note that Reading Systems may strip scripting, styling, and HTML formatting as they generate
navigational interfaces from information found in the EPUB Navigation Document, and this may make
the result difficult to read. If EPUB Creators require such formatting and functionality, then they
should also include the EPUB Navigation Document in the spine. The use of progressive
enhancement techniques for scripting and styling of the navigation document will help ensure the
content will retain its integrity when rendered in a non-browser context.
4.2 EPUB Navigation Document Definition
4.2.1 The nav Element: Restrictions
When a nav element carries the epub:type attribute in an EPUB Navigation Document, this
specification restricts the content model of the element and its descendants as follows:
Note that there are no restrictions on the attributes allowed on these elements.
Refer the definition below for additional requirements.
The following elaboration of the content model of the nav element explains the
purpose and restrictions of the various elements:
The ol child of the nav element represents
the primary level of content navigation.
Each list item of the ordered list represents a heading, structure, or
other item of interest. A child a element describes the target that the
link points to, while a span element serves as a heading for breaking down
lists into distinct groups (for example, an EPUB Creator could segment a large list of
illustrations into several lists, one for each chapter).
The child a or span element MUST provide
a non-zero-length text label after concatenation of all child content and application of
white space normalization rules. When determining compliance with this requirement, the
concatenated label MUST include text content contained in title or
alt attributes for non-textual descendant elements.
If an a or span element contains
instances of HTML embedded content that do not
provide intrinsic text alternatives, the element MUST also contain a title
attribute with an alternate text rendering of the link label.
The URL [URL] reference provided in the href
attribute of the a element:
An ol (ordered list) element representing a
subsidiary content level (e.g., all the subsection headings of a section) MAY follow an
a element.
An ol (ordered list) element MUST follow a
span element (span elements cannot occur in "leaf"
li elements).
Regardless of whether an a or span
element precedes it, every sublist MUST adhere to the content requirements defined in
this section for constructing the primary navigation list.
As a conforming XHTML Content Document, EPUB Creators MAY
include the EPUB Navigation Document in the spine.
In the context of this specification, the default display style of list
items within nav elements is equivalent to the list-style:none property [CSSSnapshot]. EPUB CreatorsMAY specify alternative
list styling using CSS for rendering of the document in the spine.
4.2.2 The nav Element: Types
4.2.2.1 Introduction
This section is non-normative.
The nav elements defined in an EPUB Navigation Document are distinguished
semantically by the value of their epub:type
attribute.
This specification defines three types of navigation aid:
Identifies the nav element that contains the table of contents. The
tocnav is the only navigation aid that EPUB Creators must include in the
EPUB Navigation Document.
Identifies the nav element that contains a list of points of
interest.
An EPUB Navigation Document may contain at most one navigation aid for each of these
types.
The EPUB Navigation Document may include additional navigation types. See 4.2.2.5 Other nav Elements for more information.
4.2.2.2 The toc nav Element
The tocnav element defines the primary navigational hierarchy. It conceptually
corresponds to a table of contents in a printed work (i.e., it provides navigation to the
major structural sections of the publication).
EPUB Creators SHOULD order the references in the tocnav element such that they reflect both:
the order of the targeted elements within their respective EPUB Content
Documents.
The tocnav element MUST occur exactly once in an EPUB Navigation Document.
4.2.2.3 The page-list nav Element
The page-listnav element provides navigation to positions in the content that correspond to
the locations of page boundaries present in a print source.
The page-listnav element is OPTIONAL in EPUB Navigation Documents and MUST NOT occur more
than once.
The page-listnav element SHOULD contain only a single ol descendant (i.e., no
nested sublists).
EPUB Creators MAY identify the destinations of the page-list references in their
respective EPUB Content Documents using the pagebreak term [EPUB-SSV-11].
4.2.2.4 The landmarks nav Element
The landmarksnav element identifies fundamental structural components in the content to
enable Reading Systems to provide the user efficient access to them (e.g., through a
dedicated button in the user interface).
The landmarksnav element SHOULD contain only a single ol descendant (i.e., no
nested sublists).
The epub:type attribute is REQUIRED on
a element descendants of the landmarksnav element. The structural semantics of each link target within the
landmarksnav element is determined by the value of this attribute.
The landmarksnavMUST NOT include multiple entries with the same epub:type
value that reference the same resource, or fragment thereof.
EPUB Creators should limit the number of items they define in the landmarksnav to only items that a Reading System is likely to use in its user interface.
The element is not meant to repeat the table of contents.
The following landmarks are recommended to include when available:
bodymatter [EPUB-SSV-11]
— Reading Systems often use this landmark to automatically jump users past the
front matter when they begin reading.
toc [EPUB-SSV-11] — If the
table of contents is available in the spine, Reading Systems may use this landmark to
take users to the document containing it.
Other possibilities for inclusion in the landmarksnav are key reference sections such as indexes and glossaries.
Although the landmarksnav is intended for Reading System use, EPUB Creators should still ensure that
the labels for the landmarksnav are human readable. Reading Systems may expose the links directly to
users.
The landmarksnav element is OPTIONAL in EPUB Navigation Documents and MUST NOT occur more
than once.
4.2.2.5 Other nav Elements
EPUB Navigation Documents MAY contain one or more nav elements in addition to
the toc, page-list, and landmarksnav elements defined in the preceding sections. If these nav
elements are intended for Reading System processing, they MUST have an epub:type attribute and are subject to
the content model restrictions defined in 4.2.1 The nav Element: Restrictions.
This specification imposes no restrictions on the semantics of any additional
nav elements: they MAY represent navigational semantics for any information
domain, and they MAY contain link targets with homogeneous or heterogeneous semantics.
4.2.3 The hidden attribute
In some cases, EPUB Creators might wish to hide parts of the navigation data within the
content flow (i.e., the Reading System's principal rendering of the spine contents). A
typical example is the list of page breaks, which EPUB Creators
do not want Reading Systems to render as part of the content flow.
While the display
property [CSSSnapshot] controls the visual rendering of EPUB Navigation Documents in
Reading Systems with Viewports, not all Reading Systems provide such an interface. To
control rendering across all Reading Systems, EPUB Creators MUST use the [HTML] hidden attribute to indicate which
(if any) portions of the navigation data are excluded from rendering in the content flow. The
hidden attribute has no effect on how Reading Systems render the navigation
data outside of the content flow (such as in dedicated navigation user interfaces provided by
Reading Systems).
5. Fixed Layouts
5.1 Introduction
This section is non-normative.
EPUB documents, unlike print books or PDF files, are designed to change. The content flows, or
reflows, to fit the screen and to fit the needs of the user. As noted in Rendering and CSS "content presentation adapts to
the user, rather than the user having to adapt to a particular presentation of content."
[EPUB-OVERVIEW-33]
But this principle does not work for all types of documents. Sometimes content and design are so
intertwined it is not possible to separate them. Any change in appearance risks changing the meaning
or losing all meaning. Fixed-Layout Documents give EPUB Creators greater control over
presentation when a reflowable EPUB is not suitable for the content.
EPUB 3 affords multiple mechanisms for representing fixed-layout content. When fixed-layout
content is necessary, the EPUB Creator's choice of mechanism will depend on many factors
including desired degree of precision, file size, accessibility, etc. This section does not
attempt to dictate the EPUB Creator's choice of mechanism.
5.2 Fixed-Layout Package Settings
5.2.1 Layout
The rendition:layout property specifies whether the content is reflowable or
pre-paginated.
When the rendition:layout property
is specified on a meta element, it indicates that the paginated or reflowable
layout style applies globally (i.e., for all spine items).
EPUB Creators MAY use the following values with the rendition:layout property:
reflowable
The content is not pre-paginated (i.e., Reading Systems apply dynamic pagination when
rendering). Default value.
pre-paginated
The content is pre-paginated (i.e., Reading Systems produce exactly one page per spine itemref when rendering).
Note
Reading Systems typically restrict or deny the application of user or user agent style sheets
to pre-paginated documents because dynamic style changes are likely to have unintended
consequence on the intrinsic properties of such documents. EPUB Creators should consider the
negative impact on usability and accessibility that these restrictions have when choosing to
use pre-paginated instead of reflowable content. Refer to Guideline 1.4 - Provide text configuration
[UAAG20] for related information.
When the property is set to
pre-paginated for a spine item, its content dimensions MUST be set as defined
in 5. Fixed Layouts.
The rendition:layout property MUST NOT be declared more than once.
5.2.1.1 Layout Overrides
EPUB Creators MAY specify the following properties locally on
spine itemref elements to override the global value for the given spine item:
layout-pre-paginated
Specifies that the given spine item is pre-paginated.
layout-reflowable
Specifies that the given spine item is reflowable.
EPUB Creators MAY use only one of these overrides on any given spine item.
5.2.2 Orientation
The rendition:orientation property specifies which orientation the EPUB Creator
intends the content to be rendered in.
When the rendition:orientation property is specified on a meta
element, it indicates that the intended orientation applies globally (i.e., for all spine
items).
EPUB Creators MAY use the following values with the rendition:orientation
property:
landscape
Reading Systems should render the content in landscape orientation.
portrait
Reading Systems should render the content in portrait orientation.
auto
The content is not orientation constrained. Default value.
EPUB Creators MUST NOT
declare the rendition:orientation property more than once.
5.2.2.1 Orientation Overrides
EPUB Creators MAY specify the following properties locally on
spine itemref elements to override the global value for the given spine item:
orientation-auto
Specifies that the Reading System determines the orientation to render the spine item
in.
orientation-landscape
Specifies that Reading Systems should render the given spine item in landscape
orientation.
orientation-portrait
Specifies that Reading Systems should render the given spine item in portrait
orientation.
EPUB Creators MAY use only one of these overrides on any given spine item.
5.2.3 Synthetic Spreads
The rendition:spread property specifies the intended Reading System synthetic spread
behavior.
When the rendition:spread property is specified on a
meta element, it indicates that the intended Synthetic Spread behavior
applies globally (i.e., for all spine items).
EPUB Creators MAY use the following values with the rendition:spread property:
none
Do not incorporate spine items in a Synthetic Spread. Reading Systems should display the
items in a single viewport positioned at the center of the screen.
landscape
Render a Synthetic Spread for spine items only when the device is in landscape
orientation.
portrait (deprecated)
The use of spreads only in portrait orientation is deprecated.
EPUB Creators should use the value "both" instead, as spreads that are
readable in portrait orientation are also readable in landscape.
both
Render a Synthetic Spread regardless of device orientation.
auto
The EPUB Creator is not defining an explicit Synthetic Spread behavior. Default
value.
The rendition:spread property MUST NOT be declared more than once.
Note
When Synthetic Spreads are used in the context of HTML and SVG Content Documents, the
dimensions given via the viewportmeta element and viewBox
attribute represents the size of one page in the spread, respectively.
Note
Refer to spine for information about declaration of global flow
directionality using the page-progression-direction attribute and that of local
page-progression-direction within content documents.
5.2.3.1 Synthetic Spread Overrides
EPUB Creators MAY specify the following properties locally on
spine itemref elements to override the global value for the given spine item:
spread-auto
Specifies the Reading System determines when to render a synthetic spread for the spine
item.
spread-both
Specifies the Reading System should render a synthetic spread for the spine item in both
portrait and landscape orientations.
spread-landscape
Specifies the Reading System should render a synthetic spread for the spine item only
when in landscape orientation.
spread-none
Specifies the Reading System should not render a synthetic spread for the spine
item.
EPUB Creators MAY use only one of these overrides on any given spine item.
5.2.4 Spread Placement
When a Reading System renders a Synthetic Spread, the default behavior is to populate the
spread by rendering the next EPUB Content Document in the next available unpopulated
viewport, where the next available viewport is determined by the given page progression direction or by local declarations within Content Documents. An EPUB
Creator MAY override this automatic population behavior and force Reading Systems to place a
document in a particular viewport by specifying one of the following properties on its spine
itemref element:
rendition:page-spread-center
The rendition:page-spread-center property is an alias of the spread-none property for centering a spine
item.
rendition:page-spread-left
The rendition:page-spread-left property is an alias of the page-spread-left property for placing a spine
item in the left-hand slot of a two-page spread.
rendition:page-spread-right
The rendition:page-spread-right property is an alias of the page-spread-right property for placing a spine
item in the right-hand slot of a two-page spread.
The rendition:page-spread-center, rendition:page-spread-left, and
rendition:page-spread-right properties apply to both pre-paginated and
reflowable content. They only apply when the Reading System is creating Synthetic Spreads.
Although EPUB Creators often indicate to use a spread in certain device orientations, the content
itself does not represent true spreads (i.e., two consecutive pages that Reading Systems must
render side-by-side for readability, such as a two-page map). To indicate that two consecutive
pages represent a true spread, EPUB Creators SHOULD use the
rendition:page-spread-left and rendition:page-spread-right
properties on the spine items for the two adjacent EPUB Content Documents, and omit the
properties on spine items where one-up or two-up presentation is equally acceptable.
EPUB Creators MAY only declare one page-spread-* property on any given spine
item.
Note
The rendition:page-spread-left and rendition:page-spread-right
properties were created to allow the use of a single vocabulary for all fixed-layout
properties. EPUB Creators can use either property set, but older Reading Systems might only
recognize the unprefixed versions.
The rendition:page-spread-center was created to make it easier for EPUB Creators
to understand the process of switching between two-page spreads and single centered pages.
EPUB Creators can use either rendition:page-spread-center or
spread-none to disable spread behavior in Reading Systems.
5.2.5 Viewport Dimensions (Deprecated)
The rendition:viewport property allows EPUB Creators to express the CSS
initial containing block (ICB) [CSS2] for XHTML and SVG Content Documents whose
rendition:layout property has been set to pre-paginated.
The OCF Abstract Container file system model uses a single common Root Directory
for all the contents. All Local Resources for the EPUB Publication are located
within the directory tree headed by the Root Directory, but no specific file system structure
for them is mandated by this specification.
The file system model also includes a mandatory directory named META-INF that is a
direct child of the Root Directory and stores the following special files:
The OCF Abstract Container MUST include a directory for configuration files named
META-INF that is a direct child of the container's Root Directory. Refer to 6.1.6 META-INF Directory for the requirements for the contents of this
directory.
EPUB Creators MAY locate all other files within the OCF Abstract Container in any location
descendant from the Root Directory, provided they are not within the META-INF
directory. EPUB Creators MUST NOT reference files in the META-INF directory from an
EPUB Publication.
Note
Some Reading Systems do not provide access to resources outside the directory where the
Package Document is stored. EPUB Creators should therefore place all resources at or below
the directory containing the Package Document to avoid interoperability issues.
If EPUB Creators dynamically integrate resources (i.e., where the naming is beyond their
control), they should be aware that automatic truncation of File Names to keep them within
the 255 bytes limit can lead to corruption. This is due to the difference between bytes and
characters in multibyte encodings such as UTF-8; it is, therefore, important to avoid
mid-character truncation. See the section on "Truncating or limiting the length of
strings" in [international-specs] for more information.
Note
EPUB Creators should use an abundance of caution in their file naming when interoperability
of content is key. The list of restricted characters is intended
to help avoid some known problem areas, but it does not ensure that all other Unicode
characters are supported. Although Unicode support is much better now than in earlier
iterations of EPUB, older tools and toolchains may still be encountered (e.g., ZIP tools
that only support [US-ASCII]).
If EPUB Creators need to ensure compatibility with EPUB 2 Reading Systems that only accept
URIs [RFC3986], they should further consider restricting resource names to the ASCII
character set [US-ASCII].
6.1.4 Deriving File Paths
To derive the File Path, given a file or directory file
in the OCF Abstract Container, apply the following steps
(expressed using the terminology of [INFRA]):
Return the concatenation of path
using the U+002F (/) character.
6.1.5 URLs in the OCF Abstract Container
The container root
URL is the URL [URL] of the Root Directory.
It is implementation-specific, but EPUB Creators MUST assume it has the following
properties:
Parsing may replace some characters in the File
Path by their percent encoded alternative. For
example, A/B/C/file name.xhtml becomes
A/B/C/file%20name.xhtml.
The goal of the algorithm is to detect whether url could be
seen as "leaking" outside the container. To do that, the standard URL parsing algorithm is used with an
artificial root URL; the detection of the "leak" is done by comparing the result of
the parsing with the presence of the first test path segment (A). (Note
that the artificial container root URL wilfully violates, for the purpose of this
algorithm, the required properties by using that
first test path segment.)
The reasons to repeat the same steps twice with different, and
artificial, settings of the container root URL is to avoid collision which may occur
if the url string also includes /A/. Consider, for example,
the case where url is ../../A/doc.xhtml.
Set testURLRecord to be the result of applying the URL parser to url, with
base.
Let testURLStringB be the result of applying the URL Serializer to testURLRecord.
If testURLStringA does not start with https://a.example.org/ or
testURLStringB does not start with https://b.example.org/,
return true. Explanation
Note
If any of the result does not share the test URL host, it means that
url, or its base URL (for example, in HTML, if it is explicitly set
with the base element), was absolute and points outside the
container. This is acceptable.
If testURLStringA starts with https://a.example.org/A/ and
testURLStringB starts with https://b.example.org/B/, return
true. Explanation
Note
The presence of the first test path segments (A,
respectively B) indicate that the URL doesn't leak outside the
container.
The properties of the container root URL are such that whatever the amount of double-dot path segments in a URL string
(for example, ../../../secret), it is parsed to a content URL (and not
"leak" outside the container). This avoids potential run-time security issues. The
additional constraint on valid-relative-container-URL-with-fragment strings ensures
that such potentially problematic URLs can also be detected when checking the EPUB
Publication.
For better interoperability with non-conforming or legacy Reading Systems and toolchains,
EPUB Creators should not use more double-dot path
segments than needed to reach the target container file.
All [XML] elements defined in this section are in the
urn:oasis:names:tc:opendocument:xmlns:container namespace [XML-NAMES]
unless specified otherwise.
The contents of this file MUST be valid to the definition in this section after removing
all elements and attributes from other namespaces (including all attributes and contents
of such elements).
Note
An XML Schema also informally defines
the content of this file.
6.1.6.3.1.1 The container Element
The container element is the root element of the
container.xml file.
Identifies the media type of the Package Document.
The value of the attribute MUST be
"application/oebps-package+xml".
Content Model
Empty
If an EPUB Creator defines more than one rootfile element, each MUST
reference a Package Document that conforms to the same version of EPUB. Each Package
Document represents one rendering of the EPUB Publication.
Note
Although the EPUB Container provides the ability to reference more than one
Package Document, this specification does not define how to interpret, or select
from, the available options. Refer to [EPUB-MULTI-REND-11] for more
information on how to bundle more than one rendering of the content.
6.1.6.3.1.4 The links Element
The links element identifies resources
necessary for the processing of the OCF ZIP Container.
Identifies the type and format of the referenced resource.
The value of the attribute MUST be a media type [RFC2046].
rel[required]
Identifies the relationship of the resource.
The value of the attribute MUST be a space-separated list of
tokens.
Content Model
Empty
6.1.6.3.1.6 Examples
This section is non-normative.
6.1.6.3.2 Encryption File (encryption.xml)
The OPTIONALencryption.xml file in the META-INF directory
holds all encryption information on the contents of the container. If an EPUB Creator
encrypts any resources within the container, they MUST include an
encryption.xml file to provide information about the encryption
used.
6.1.6.3.2.1 The encryption element
Element Name
encryption
Namespace
urn:oasis:names:tc:opendocument:xmlns:container
Usage
Root element of the encryption.xml file.
Attributes
None
Content Model
In any order:
EncryptedKey [1 or more]
EncryptedData [1 or more]
The encryption element contains child elements of type
EncryptedKey and EncryptedData as defined by
[XMLENC-CORE1].
An EncryptedKey element describes
each encryption key used in the container, while an EncryptedData element describes
each encrypted file. Each EncryptedData element refers to an
EncryptedKey element, as described in XML Encryption.
Note
An XML Schema also informally
defines the content of the encryption.xml file.
OCF encrypts individual files independently, trading off some security for improved
performance, allowing the container contents to be incrementally decrypted.
Encryption in this way exposes the directory structure and file naming of the whole
package.
OCF uses XML Encryption [XMLENC-CORE1] to provide a framework for encryption,
allowing a variety of algorithms to be used. XML Encryption specifies a process for
encrypting arbitrary data and representing the result in XML. Even though an OCF
Abstract Container may contain non-XML data, EPUB Creators can use XML
Encryption to encrypt all data in an OCF Abstract Container. OCF encryption supports
only the encryption of entire files within the container, not parts of files. EPUB
Creators MUST NOT encrypt the encryption.xml file when present.
Encrypted data replaces unencrypted data in an OCF Abstract Container. For example,
if an EPUB Creator encrypts an image named photo.jpeg, they should
replace the contents of the photo.jpeg resource with its encrypted
contents. Within the ZIP directory, EPUB Creators SHOULD store encrypted files
rather than Deflate-compress them.
Note that some situations require obfuscating the storage
of embedded fonts referenced by an EPUB Publication to make them more
difficult to extract for unrestricted use. Although obfuscation is not encryption,
Reading Systems use the encryption.xml file in conjunction with the font obfuscation algorithm to identify fonts to
deobfuscated.
EPUB Creators MUST NOT encrypt the following files:
EPUB Creators MAY subsequently encrypt signed resources using the Decryption
Transform for XML Signature [XMLENC-DECRYPT]. This feature enables a Reading
System to distinguish data encrypted before signing from data encrypted after
signing.
6.1.6.3.2.2 Order of Compression and Encryption
When stored in a ZIP container, EPUB Creators SHOULD compress streams of data with
Non-Codec content types before encrypting them. EPUB Creators MUST use
Deflate compression. This practice ensures that file entries stored in the ZIP
container have a smaller size.
EPUB Creators SHOULD NOT compress streams of data with Codec content types
before encrypting them. In such cases, additional compression introduces unnecessary
processing overhead at production time (especially with large resource files) and
impacts audio/video playback performance at consumption time. In some cases, the
combination of compression with some encryption schemes might even compromise the
ability of Reading Systems to handle partial content requests (e.g. HTTP byte
ranges), due to the technical impossibility to determine the length of the full
resource ahead of media playback (e.g. HTTP Content-Length header).
When EPUB Creators compress streams of data before encrypting, they SHOULD provide
additional EncryptionProperties metadata to specify the size of the
initial resource (i.e., before compression and encryption), as per the
Compression XML element defined below. When EPUB Creators do not
compress streams of data before encrypting, they MAY provide the additional
EncryptionProperties metadata to specify the size of the initial
resource (i.e., before encryption).
Element Name
Compression
Namespace
http://www.idpf.org/2016/encryption#compression
Usage
OPTIONAL child of EncryptionProperty.
Attributes
Method [required]
Identifies the compression method used.
Value is either "0" (no compression) or "8"
(Deflate algorithm).
OriginalLength [required]
Represents the size of the initial resource (number of bytes).
Value is a positive integer.
Content Model
Empty
6.1.6.3.3 Manifest File (manifest.xml)
The OPTIONALmanifest.xml file in the META-INF directory
provides a manifest of files in the Container.
The OCF specification does not mandate a format for the manifest.
This feature exists only for compatibility with [ODF].
6.1.6.3.4 Metadata File (metadata.xml)
EPUB Creators MUST use the OPTIONALmetadata.xml file in the
META-INF directory only for container-level metadata.
If EPUB Creators include a metadata.xml file, they SHOULD use only
namespace-qualified elements [XML-NAMES] in it. The file SHOULD contain the root
element metadata in the namespace
http://www.idpf.org/2013/metadata, but this specification allows other
root elements for backwards compatibility.
This version of the specification does not define metadata for use in the
metadata.xml file. Future versions of this specification MAY define
container-level metadata.
6.1.6.3.5 Rights Management File (rights.xml)
This specification resrves the OPTIONALrights.xml file in the
META-INF directory for digital rights management (DRM) information for
trusted exchange of EPUB Publications among rights holders, intermediaries, and
users.
When EPUB Creators do not include a rights.xml file, no part of the
container is rights governed at the container level. Rights expressions might exist
within the EPUB Publications.
If EPUB Creators do not include a rights.xml file, no part of the OCF
Abstract Container is rights governed.
6.1.6.3.6 Digital Signatures File (signatures.xml)
Note
Adding a digital signature is not a guarantee that a malicious actor cannot tamper
with an EPUB Publication as Reading Systems do not have to check signatures.
The OPTIONALsignatures.xml file in the META-INF directory
holds digital signatures for the container and its contents.
6.1.6.3.6.1 The signatures element
Element Name
signatures
Namespace
urn:oasis:names:tc:opendocument:xmlns:container
Usage
Root element of the signature.xml file.
Attributes
None
Content Model
Signature [1 or more]
The signature element contains child elements of type
Signature, as defined by [XMLDSIG-CORE1]. EPUB Creators can apply
signatures to an EPUB Publication as a whole or to its parts, and can specify the
signing of any kind of data (i.e., not just XML).
Note
An XML Schema also informally
defines the content of the signatures.xml file.
When an EPUB Creator does not include a signatures.xml file, they are
not signing any part of the container at the container level. Digital signing might
exist within the EPUB Publication.
When an EPUB Creator creates a data signature for the container,
they SHOULD add the signature as the last child Signature element of
the signatures element.
Note
Each Signature in the signatures.xml file identifies by
URL [URL] the data to which the signature applies, using the [XMLDSIG-CORE1]
Manifest element and its Reference sub-elements.
EPUB Creator may sign individual container files separately or together.
Separately signing each file creates a digest value for the resource that
Reading Systems can validate independently. This approach might make a Signature
element larger. If EPUB Creators sign files together, they can list the set of
signed files in a single XML Signature Manifest element and
reference them by one or more Signature elements.
EPUB Creators can sign any or all files in the container in
their entirety, except for the signatures.xml file since that file will
contain the computed signature information. Whether and how EPUB Creators sign the
signatures.xml file depends on their objective.
If the EPUB Creator wants to allow signatures to be added or removed from the
container without invalidating their signature, they SHOULD NOT sign the
signatures.xml file.
If the EPUB Creator wants any addition or removal of a signature to invalidate their
signature, they can use the Enveloped Signature transform defined in Section 6.6.4 of
[XMLDSIG-CORE1] to sign the entire preexisting signature file excluding the
Signature being created. This transform would sign all previous
signatures, and it would become invalid if a subsequent signature were added to the
package.
Note
If the EPUB Creator wants the removal of an existing signature to invalidate the
their signature, but also wants to allow the addition of signatures, they could
use an XPath transform to sign just the existing signatures. The details of such
a transform are outside the scope of this specification, however.
The [XMLDSIG-CORE1] specification does not associate any semantics with a
signature; an agent might include semantic information, for example, by adding
information to the Signature element that describes the signature. The
[XMLDSIG-CORE1] specification describes how additional information can be added to
a signature, such as by use the SignatureProperties element.
OCF ZIP Containers MUST NOT use the features in the ZIP application
note [ZIP] that allow ZIP files to be spanned across multiple storage media or be
split into multiple files.
OCF ZIP Containers MUST include only stored (uncompressed) and
Deflate-compressed ZIP entries within the ZIP archive.
OCF ZIP Containers MAY use the ZIP64 extensions defined as "Version
1" in section V, subsection G of the application note [ZIP] and SHOULD use only those
extensions when the content requires them.
OCF ZIP Containers MUST NOT use the encryption features defined by
the ZIP format; instead, encryption MUST be done using the features described in 6.1.6.3.2 Encryption File (encryption.xml).
OCF ZIP Containers MUST encode File System Names using UTF-8
[Unicode].
The following constraints apply to specific fields in the OCF ZIP Container archive:
In the local file header table, EPUB Creators MUST set the
version needed to extract fields to the values 10,
20 or 45 to match the maximum version level needed by the
given file (e.g., 20 for Deflate, 45 for ZIP64).
In the local file header table, EPUB Creators MUST set the
compression method field to the values 0 or
8.
6.2.3 OCF ZIP Container Media Type Identification
EPUB Creators MUST include the mimetype file as the first file in the OCF ZIP
Container. In addition:
The contents of the mimetype file MUST be the MIME media type [RFC2046]
string application/epub+zip encoded in US-ASCII [US-ASCII].
The mimetype file MUST NOT contain any leading or trailing padding or white
space.
The mimetype file MUST NOT begin with the Unicode byte order mark U+FEFF.
EPUB Creators MUST NOT compress or encrypt the mimetype file, and MUST NOT
include an extra field in its ZIP header.
Better methods of protecting fonts exist. Both [WOFF] and [WOFF2] fonts, for example, allow
the embedding of licensing information and also provide some protection through font table
compression. The use of remotely hosted fonts also allows for font subsetting. EPUB Creators are
advised to use font obfuscation as defined in this section only when no other options are
available to them. See also the limitations of
obfuscation.
6.3.1 Introduction
This section is non-normative.
Since an OCF ZIP Container is fundamentally a ZIP file, commonly available ZIP tools can
be used to extract any unencrypted content stream from the package. Moreover, the nature of ZIP
files means that their contents might appear like any other native container on some systems
(e.g., a folder).
While this simplicity of ZIP files is quite useful, it also poses a problem when ease of
extraction of fonts is not a desired side-effect of not encrypting them. An EPUB Creator
who wishes to include a third-party font, for example, typically does not want that font
extracted and re-used by others. More critically, many commercial fonts allow embedding, but
embedding a font implies making it an integral part of the EPUB Publication, not just providing
the original font file along with the content.
Since integrated ZIP support is so ubiquitous in modern operating systems, simply placing a font
in the ZIP archive is insufficient to signify that the font cannot be reused in other contexts.
This uncertainty can undermine the otherwise useful font embedding capability of EPUB
Publications.
To discourage reuse of their fonts, some font vendors might only allow their use in EPUB
Publications if the fonts are bound in some way to the EPUB Publication. That is, if the font
file cannot be installed directly for use on an operating system with the built-in tools of that
computing device, and it cannot be directly used by other EPUB Publications.
It is beyond the scope of this specification to provide a digital rights management or
enforcement system for fonts. This section instead defines a method of obfuscation that will
require additional work on the part of the final OCF recipient to gain general access to any
obfuscated fonts.
6.3.2 Limitations
This section is non-normative.
This specification does not claim that obfuscation constitutes encryption, nor does it guarantee
that the resource will be secure from copyright infringement. The hope is only that this
algorithm will meet the requirements of vendors who require some assurance that their fonts
cannot be extracted simply by unzipping the OCF Container and copying the resource.
Obfuscation, like any protection scheme, cannot fully protect fonts from being accessed in their
deobfuscated state. The mechanism only provides a stumbling block for those who are unaware of
the license details. It will not prevent a determined user from gaining full access to the font
through such alternative means as:
applying the deobfuscation algorithm to extract the raw font file;
accessing the deobfuscated font through a Reading System that must dedobfuscate it to render
the content (e.g., by accessing the resources through a browser-based Reading System);
or
accessing the deobfuscated font through authoring tools that provide the visual rendering of
the content.
As a result, whether this method of obfuscation satisfies the requirements of individual font
licenses remains a question for the licensor and licensee. EPUB Creators are responsible for
ensuring their use of obfuscation meets font licensing requirements.
EPUB Creators should also be aware that obfuscation may lead to interoperability issues in
Reading Systems as Reading Systems are not required to deobfuscate fonts. As a result, the
visual presentation of their publications may differ from Reading System to Reading System.
Also note that the algorithm is restricted to obfuscating fonts. It is not intended as a
general-purpose mechanism for obfuscating any resource in the EPUB Container.
6.3.3 Obfuscation Key
EPUB Creators MUST derive the key used in the obfuscation algorithm from the Unique
Identifier.
All white space characters, as defined in section 2.3 of the
XML 1.0 specification [XML], MUST be removed from this identifier — specifically, the
Unicode code points U+0020, U+0009, U+000D and
U+000A.
EPUB Creators MUST generate a SHA-1 digest of the UTF-8 representation of the resulting string as
specified by the Secure Hash Standard [FIPS-180-4]. They can then use this digest as the key
for the algorithm.
6.3.4 Obfuscation Algorithm
The algorithm employed to obfuscate fonts consists of modifying the first 1040 bytes (~1KB) of
the font file. (In the unlikely event that the font file is less than 1040 bytes, this process
will modify the entire file.)
To obfuscate the original data, store, as the first byte of the embedded font, the result of
performing a logical exclusive or (XOR) on the first byte of the raw font file and the first
byte of the obfuscation key.
Repeat this process with the next byte of source and key and continue for all bytes in the key.
At this point, the process continues starting with the first byte of the key and 21st byte of
the source. Once 1040 bytes are encoded in this way (or the end of the source is reached),
directly copy any remaining data in the source to the destination.
EPUB Creators MUST obfuscate fonts before compressing and adding them to the OCF Container. Note
that as obfuscation is not encryption, this requirement is not a violation of the one in 6.1.6.3.2 Encryption File (encryption.xml) to compress fonts before encrypting
them.
The following pseudo-code exemplifies the obfuscation algorithm.
set ocf to OCF container file
set source to font file
set destination to obfuscated font file
set keyData to key for file
set outer to 0
while outer < 52 and not (source at EOF)
set inner to 0
while inner < 20 and not (source at EOF)
read 1 byte from source (Assumes read advances file
position)
set sourceByte to result of read
set keyByte to byte inner of keyData
set obfuscatedByte to (sourceByte XOR
keyByte)
write obfuscatedByte to destination
increment inner
end while
increment outer
end while
if not (source at EOF) then
read source to EOF
write result of read to destination
end if
Deflate destination
store destination as source in ocf
6.3.5 Specifying Obfuscated Fonts
Although not technically encrypted data, all obfuscated fonts MUST have an entry in the encryption.xml file accompanying the EPUB Publication (see 6.1.6.3.2 Encryption File (encryption.xml)).
EPUB Creators MUST specify an EncryptedData element for each obfuscated font. Each
EncryptedData element MUST contain a child EncryptionMethod
element whose Algorithm attribute has the value
http://www.idpf.org/2008/embedding. The presence of this attribute signals the
use of the algorithm described in this specification.
EPUB Creators MUST list the path to the obfuscated font in the CipherReference child
of the CipherData element. As the obfuscation algorithm is restricted to fonts, the
URI attribute of the CipherReference element MUST reference a Font Core Media Type.
To prevent trivial copying of the embedded font to other EPUB Publications, EPUB Creators MUST NOT provide the obfuscation key in the encryption.xml
file.
7. Media Overlays
7.1 Introduction
This section is non-normative.
Mainstream ebooks, educational tools and ebooks formatted for persons with print disabilities are
some examples of works that contain synchronized audio narration. In EPUB 3, EPUB Creators can
create these types of books using Media Overlay Documents to describe the timing for the
pre-recorded audio narration and how it relates to the EPUB Content Document markup. The
specification defines the file format for Media Overlays as a subset of [SMIL3], a W3C
recommendation for representing synchronized multimedia information in XML.
The text and audio synchronization enabled by Media Overlays provides enhanced accessibility for any
user who has difficulty following the text of a traditional book. Media Overlays also provide a
continuous listening experience for readers who are unable to read the text for any reason,
something that traditional audio embedding techniques cannot offer. They are even useful for
purposes not traditionally considered accessibility concerns (e.g., for language learning).
The Media Overlays feature is transparent to EPUB Reading Systems that do not support the
feature. The inclusion of Media Overlays in an EPUB Publication has no impact on the ability of
Media Overlay-unaware Reading Systems to render the EPUB Publication as though the Media Overlays
are not present.
Media Overlays in EPUB are not an equivalent to audiobooks, as audiobooks are primarily audio-based
with text occasionally provided as an alternate format. The W3C [Audiobooks] recommendation is for
building audio publications.
Although future versions of this specification might incorporate support for video media (e.g.,
synchronized text/sign-language books), this version supports only synchronizing audio media with
the EPUB Content Document.
As this specification does not define any metadata properties that must occur in the Media
Overlay Document, the head element is OPTIONAL.
7.2.2.3 The metadata Element
The metadata element represents metadata for the Media Overlay Document. The
metadata element is an extension point that allows the inclusion of
metadata from any metainformation structuring language.
This specification does not require any metadata properties in the Media Overlay Document;
the metadata element is provided for custom metadata requirements.
7.2.2.4 The body Element
The body element is the starting point for the presentation contained in the
Media Overlay Document. It contains the main sequence of par and
seq elements.
Element Name
body
Usage
The body element is a REQUIRED child of the smil element. It follows the head element, when that element is present.
Attributes
epub:type[optional]
An expression of the structural semantics of the corresponding element in the
EPUB Content Document.
The text element references an element in an EPUB Content Document. A
text element typically refers to a textual element but can also refer to
other EPUB Content Document media elements (see 7.3.2.4 Embedded Media). In the
absence of a sibling audio element textual content referred to by this element
may be rendered via text-to-speech.
The ID [XML] of the element, which MUST be unique within the document
scope.
Content Model
Empty
Note
This specification places no restriction on the src attribute of a
text element. Authors should, however, refer to a content that can be
styled with CSS to make the association with style
information effective, i.e., palpable
content for XHTML or paths, basic shapes, or text elements in SVG.
7.2.2.8 The audio Element
The audio element represents a clip of audio media.
The chronological offset of the terminating position MUST be after the
starting offset specified in the clipBegin attribute.
Content Model
Empty
7.3 Creating Media Overlays
7.3.1 Introduction
This section is non-normative.
EPUB Creators can represent a pre-recorded narration of a publication as a series of audio clips,
each corresponding to part of an EPUB Content Document. A single audio clip, for example,
typically represents a single phrase or paragraph, but infers no order relative to the other
clips or to the text of a document. Media Overlays solve this problem of synchronization by
tying the structured audio narration to its corresponding text (or other media) in the EPUB
Content Document using [SMIL3] markup. Media Overlays are, in fact, a simplified subset of
SMIL 3.0 that define the playback sequence of these clips.
The SMIL elements primarily used for structuring Media Overlays are body (used for the main sequence), seq (sequence) and par
(parallel). (Refer to 7.2.2 Media Overlay Document Definition for more information on these and other
SMIL elements.)
The par element is the basic building block of an Overlay and corresponds to a
phrase in the EPUB Content Document. The element provides two key pieces of information for
synchronizing content: 1) the audio clip containing the narration for the phrase; and 2) a
pointer to the associated EPUB Content Document fragment. The par element uses two
media element children to represent this information: an audio element and a text
element. Since par elements render their children in parallel, Reading Systems play
the audio clip and EPUB Content Document fragment at the same time, resulting in a synchronized
presentation.
The text element src attribute references the associated phrase,
sentence, or other segment of the EPUB Content Document by its URL [URL] reference. The
audio element src attribute similarly references the location of
the corresponding audio clip and adds the OPTIONALclipBegin and clipEnd
attributes to indicate a specific offset within the clip.
EPUB Creators place par elements together sequentially to form a series of phrases
or sentences. Not every element of the EPUB Content Document will have a corresponding
par element in the Media Overlay, only those relevant to the audio
narration.
EPUB Creators can also add par elements to seq elements to define more
complex structures such as parts and chapters (see 7.3.2.1 Overlay Structure).
The body of a Media Overlay Document consists
of two elements: the par element and the seq element. The ordering of these elements
represents how Reading Systems render the content in the corresponding EPUB Content
Documents during playback.
The par element represents a segment of content to render, such as a word,
phrase, sentence, table cell, list item, image, or other identifiable piece of content in
the markup. Each element identifies both the content to display (in the text element) and audio to synchronize (in
the audio element) during playback.
The seq element represents sequences — sets of seq and/or
par elements that together represent a logical component of the content.
EPUB Creators can use it to represent nested containers such as sections, asides, headers,
tables, lists, and footnotes. It allows EPUB Creators to retain the structure inherent in
these containers in the Media Overlay Document.
The seq element MUST contain an epub:textref attribute. As seq elements do not
provide synchronization instructions, this attribute allows a Reading System to match the
fragment to a location in the text.
Note
The reason for grouping structures like sections, figures, tables, and footnotes in a
seq element is so that Reading Systems can identify their start and end
positions during playback. Reading Systems can then offer playback options tailored to
the layout of the content, such as jumping past a long figure, turning off rendering of
page break announcements (see 7.4 Skippability and Escapability), or customizing
the reading mode to suit structures such as tables.
7.3.2.2 Referencing Document Fragments
The epub:textref attribute and the text element'ssrc attribute both require a fragment identifier that references a specific
fragment (e.g., an element or text string) of the associated EPUB Content
Document.
EPUB Creators MAY use other fragment identifier schemes, but Reading Systems may not support
such identifiers.
7.3.2.3 Overlay Granularity
This section is non-normative.
The granularity level of the Media Overlay depends on how EPUB Creators mark up the EPUB
Content Document and the type of fragment identifier they use in the text elements'src attributes. For example, when referencing target elements [HTML], if the finest level of
markup is at the paragraph level, then that is the finest possible level for Media Overlay
synchronization. Likewise, if sub-paragraph markup is available, such as [HTML] span elements representing phrases or
sentences, then finer granularity is possible in the Media Overlay. Finer granularity gives
users more precise results for synchronized playback when navigating by word or phrase and
when searching the text but increases the file size of the Media Overlay Documents. Fragment
identifier schemes that do not rely on the presence of elements could provide even finer
granularity, where supported.
7.3.2.4 Embedded Media
Any EPUB Content Document associated with a Media Overlay MAY contain embedded media
such as video, audio, and images. EPUB Creators MAY use the Media Overlay text element in such instances to reference
the embedded media by its element's id attribute value.
7.3.2.4.1 Embedded Audio and Video
When a text element references embedded
audio or video, Reading Systems will intiate playback of the media in the absence of an
audio element sibling.
EPUB CreatorsSHOULD avoid using scripts to control playback of referenced
embedded EPUB Content Document media, as this might conflict with Media Overlays
playback behavior.
EPUB Creators should carefully examine any overlapping audio situations and deal with
them at the production stage, as Reading Systems handling of simultaneous volume levels
is optional.
7.3.2.4.2 Embedded Images
When a text element references an embedded image, the audio sibling element is OPTIONAL. In
the absence of an audio element, Reading Systems will voice the image using
Text-to-Speech rendering.
EPUB Creators MUST ensure they provide fallback text for an image when an omitting an
audio element (e.g., using the [HTML] alt
attribute).
7.3.2.5 Text-to-Speech Rendering
This specification allows the use of text-to-speech (TTS) — the rendering of the
textual content of an EPUB Publication as artificial human speech using a synthesized
voice — in addition to pre-recorded audio clips.
When a Media Overlay par element omits its audio element, its text element may be rendered in Reading
Systems via TTS. If the text fragment is not appropriate for TTS rendering (e.g., is not a
text element and/or has no text fallback), this may produce unexpected results.
EPUB Creators MAY express visual rendering information for the currently playing EPUB Content
Document element in a CSS Style Sheet using author-defined classes.
When used, EPUB Creators MUST declare the class names in the Package Document using the active-class and playback-active-class properties.
EPUB Creators MUST define exactly one CSS class name in each property they define. Each property
MUST define a valid CSS class
name not including any selectors
[CSS2]. This specification does not reserve names for use with these
properties.
EPUB Creators MAY define any CSS properties for the specified CSS classes, but must ensure that
each EPUB Content Document with an associated Media Overlay Document includes a CSS stylesheet
(either embedded or linked) containing the class definitions. In the absence of such definitions
Reading Systems might provide their own styling, or no styling at all.
EPUB Creators MUST NOT use the active-class and playback-active-class
properties in conjunction with a refines attribute
as they always apply to the entire EPUB Publication.
7.3.5 Media Overlays Packaging
7.3.5.1 Including Media Overlays
If an EPUB Content Document is wholly or partially referenced by a Media Overlay, then
its manifestitem elementMUST specify a
media-overlay attribute. The attribute MUST reference the ID [XML] of the
manifest item for the corresponding Media Overlay Document.
EPUB Creators MUST only specify the media-overlay attribute on manifest
item elements that reference EPUB Content Documents.
Manifest items for Media Overlay Documents MUST have the media type
application/smil+xml.
In addition, EPUB Creators MUST provide the duration of each Media Overlay Document. EPUB
Creators may use the refines attribute to
associate each duration declaration to the corresponding manifestitem.
The sum of the durations for each Media Overlay Document SHOULD equal the total duration.
The media: prefix is reserved
for inclusion of these properties in package metadata.
7.4 Skippability and Escapability
7.4.1 Skippability
While reading, users may want to turn on or off certain features of the content, such as
footnotes, page numbers, or other types of secondary content. This feature is called
skippability. Reading Systems use the semantic information provided by Media Overlay elements'
epub:type attribute to determine
when to offer users the option of skippable features.
The following non-exhaustive list represents terms from the Structural Semantics
Vocabulary [EPUB-SSV-11] for which Reading Systems may offer the option of skippability:
footnote
endnote
pagebreak
Note
Reading System are not required to support for skippability based on epub:type
values.
7.4.2 Escapability
Escapable items are nested structures, such as tables and lists, that users might wish to skip
over, continuing to read from the point immediately after the nested structure. The escapability
feature differs from the skippability feature in that it does not enable or disable entire types
of items, but provides an exit from them (e.g., a user can listen to some of the content before
choosing to escape).
The following non-exhaustive list represents terms from the Structural Semantics
Vocabulary [EPUB-SSV-11] for which Reading Systems may offer the option of escapability:
When included in the spine, playback of the EPUB Navigation Document's Media Overlay obeys
the same conformance requirements as with any other XHTML Content Document.
When exposed in a presentation context that allows users to access and activate the links,
Reading Systems MAY implement additional presentation behaviors to expose audio feedback
when user access navigation links.
Note
Specific implementation details are beyond the scope of this specification. The DAISY
Media Overlays Playback Requirements document describes best practices for EPUB Creators
and provides recommendations for Reading System developers.
8. Accessibility
This section is non-normative.
EPUB 3 builds upon the Open Web Platform expressly so that it can leverage the structure, semantics and,
by extension, accessibility built into its underlying technologies.
The requirements and practices for creating accessible web content have already been documented in the
W3C's Web Content Accessibility Guidelines (WCAG) [WCAG2].
These guidelines also form the basis for defining accessibility in EPUB Publications.
As the current WCAG guidelines (version 2) are heavily focused on web pages, a separate specification, EPUB Accessibility [EPUB-A11Y-11], defines how to apply the standard
to EPUB Publications. It also adds EPUB-specific requirements and recommendations for metadata,
pagination, and media overlays.
This specification recommends that EPUB Publications conform to the EPUB
Accessibility standard. A benefit of following this recommendation is that it helps ensure that
EPUB Publications meet the accessibility requirements legislated in jurisdictions around the world,
ensuring EPUB Creators are not locked out of potential markets.
EPUB Creators, however, should look beyond legal imperatives and treat accessibility as a
requirement for all their content. The more accessible that EPUB Publications are, the greater the
potential audience for them.
Note
This specification does not integrate the accessibility requirements to allow them to adapt and
evolve independent of the EPUB specification — accessibility practices often need more
frequent updating. The accessibility specification is also intended for use with past, present, and
future versions of EPUB. The approach of a separate specification ensures that the evolution of EPUB
does not lock accessibility in time (i.e., it allows producers of older versions of EPUB to
reference the latest accessibility requirements).
9. Security and Privacy
This section is non-normative.
9.1 Overview
The particularity of an EPUB Publication is its structure. The EPUB format provides a means of
representing, packaging, and encoding structured and semantically enhanced web content — including
HTML, CSS, SVG, JavaScript, and other resources — for distribution in a single-file container.
This means that EPUB 3's security and privacy issues are primarily linked to the features of those
formats, and closely mirror the threats presented by web content generally.
Although content risks are often equated with deliberately malicious authoring intent, EPUB Creators
need to be aware that many practices followed with the best of intentions may expose users to
privacy and security issues. The rest of this section explores the risk model of EPUB 3 with the aim
of helping EPUB Creators recognize and mitigate these risks.
EPUB Publications pose a variety of privacy and security threats to unsuspecting users. Many of these
threats intersect with web content generally, but EPUB also introduces its own unique methods of
attack that can be used to trick users into accessing malicious content or into providing sensitive
information. Some of the more important attack vectors that EPUB Creators and users need to be aware
of include:
Embedding of remote resources
EPUB 3 allows some resources to be remotely hosted,
specifically resources whose sizes can negatively affect the downloading and opening of the
EPUB Publication (e.g., audio, video, and fonts). Although helpful for users when used as
intended, these exemptions can also be used to inject malicious content into a
publication.
This threat is not limited to accessing content created by a bad actor. If EPUB Creators
embed content from untrustworthy sources (e.g., third party audio and video), there is
always the possibility that users may receive compromised resources.
Checking for malware and exploits at distribution time is not always reliable, either, as the
malicious content can be swapped in any time after publication, unlike resources that come
embedded in the EPUB Container.
The origin of an EPUB is both unknown to the EPUB Creator
and specific to each Reading System implementation. Consequently, if the EPUB Creator hosts
remote resources on a web server they control, the server effectively cannot use security
features that require specifying allowable origins, such as headers for CORS, Content-Security-Policy, or X-Frame-Options.
Linking to external resources
Whether intentional or not, links to external web sites and resources expose users to
potential exploits that can compromise their Reading System or operating system. Although
external links will typically open in a web browser, and be subject to the browser security
model, this does not protect users from all exploits.
Even if the intentions of the EPUB Creator are not malicious, adding tracking information to
external links is problematic for user privacy as it can allow a user's activity to be
tracked without their consent.
Broken-link hijacking — when a domain expires and is bought by another party to exploit
the links to it — can also lead to users being taken to resources the EPUB Creator did
not intend.
Including malicious content
Resources embedded in the EPUB Container are not immune to malicious actors, especially when
EPUB Publications are obtained from untrusted sources. Resources may contain exploits or
forms may submit sensitive information to unintended parties.
The use of third-party content, such as games and quizzes, may also lead to security and
privacy issues if the EPUB Creator is not able to fully vet the content.
Allowing scripts network access
When scripts can access a device's network, it provides a variety channels to exploit the
user:
collecting information about the user and their activities, whether malicious or
not;
attempting to access the file system and local storage to harvest information;
phishing attempts (e.g., making an EPUB Content Document appear like a trusted web site
to get the user to submit login information); and
injecting malicious content from external sites into the EPUB Publication.
Network access may allow third-party content an EPUB Creator uses to exploit the user even if
it was never the EPUB Creators intent.
Securing content with digital rights management
The encryption and decryption of EPUB Publications using digital rights management schemes
may allow personally identifiable information about the user, what vendors they use, and
their reading choices to be relayed to third parties.
The effectiveness of these attacks also often depends on tricking users into believing that the
publication they are interacting with is from a trustworthy source. These deceptions can take the
following forms:
Falsified publication information
The EPUB Publication may include false information about itself to trick users into believing
that it comes from a legitimate source. A malicious EPUB Creator might, for example, fake
the title, authors, identifiers, and publisher for the work.
Although this misinformation itself does not present an immediate harm, it could lead users
to trust malicious forms, links, and other content within the EPUB Publication believing it
comes from a reliable source.
Spoofed platforms
Malicious EPUB Creators may also design their content to imitate or replicate a platform's
experience to trick users into trusting their content.
9.2.1 EPUB-Specific Features
EPUB 3 tries to avoid extending the underlying technologies it builds on, but it has introduced
some new features. The restricted scope of these features generally limits the threats they
might pose, however:
Content switching and multimedia control elements only allow hiding of
content and script-less control of playback in HTML. Moreover these features, introduced
in the first release of EPUB 3.0, are deprecated and no longer
recommended for use.
The one potential exception is the epubReadingSystem object [EPUB-RS-33] that allows EPUB Creators to
query information about the current Reading System. EPUB Creators need to be mindful that they
only use the information exposed by this object to improve the rendering of their content (i.e.,
avoid using the information to profile the user and their environment).
9.3 Recommendations
Although EPUB Creators cannot prevent every method of exploiting users, they are ultimately
responsible for the secure construction of their content. That means that they should take
precautions to limit the exposure of their EPUB Publications to the types of malicious exploits described in the previous section.
Avoiding third-party resources, especially those hosted on servers outside the control of the
EPUB Creator.
Avoiding links to untrustworthy web sites (e.g., that browsers do not recognize as safe).
Using secure connections to external sites and resources (i.e., using the HTTPS protocol).
Not using scripts to send or receive data over the network without the consent of the user.
Avoiding embedding content not provided by reputable organizations or individuals.
Avoiding deprecated features of EPUB due to the potential for undiscovered bugs in
implementations.
EPUB Creators also need to consider the privacy rights of users and avoid situations where they are
intentionally collecting data. Ideally, EPUB Creators should not track their users, but this is not
realistic for all types of publishing.
When tracking must occur, EPUB Creators should obtain the approval of the user to collect information
prior to opening the EPUB Publication (e.g., in educational course work). If this is not possible,
they should obtain permission when the EPUB Publication is accessed for the first time. EPUB
Creators should also allow users to opt out of tracking, when feasible, and provide users the
ability to manage and delete any data that is collected about them.
Content authors also need to consider the inadvertent collection of information about users. Linking
to content on a publisher's web site, or remotely hosting resources on their servers, can lead to
profiling users, especially if unique tracking identifiers are added to the URLs.
When publishers and vendors must use digital rights management schemes, they should prefer schemes
that do not utilize or transmit information about the user or their content to external parties to
perform encryption or decryption.
EPUB Creators who want to maximally limit the privacy and security issues in their EPUB Publications
should work to make the content as self-contained as possible. An EPUB Publication that comes with
all its needed resources and has no dependencies on network access or links to external content not
only benefits users but reduces future maintenance and improves archivability.
A. Unsupported Features
This specification contains certain features that are not yet fully supported in Reading Systems, that
the Working Group no longer recommends for use, or that are only retained for interoperability with EPUB
2 Reading Systems. This section defines the meanings of the designations attached to these features and
their support expectations.
A.1 Under-implemented Features
A under-implemented feature is a feature introduced prior to EPUB 3.3 for which the
Working Group has not been able to establish enough implementation
experience.
These features are considered important to retain despite this limitation because they are known to
be implemented by EPUB Creators (i.e., their deprecation would invalidate existing content) and/or
they are integral to the content model on which EPUB is built.
If this specification designates a feature as under-implemented, the following hold true:
Validation tools SHOULD alert EPUB Creators to the presence of under-implemented features when
encountered in EPUB Publications but MUST NOT treat their inclusion as a violation of the standard
(i.e., not emit errors or warnings).
Caution
Whether under-implemented labels are removed or replaced by deprecation in a future version of
the standard cannot be determined at this time. EPUB Creators should strongly consider the
interoperability problems that may arise both now and in the future when using these
features.
Note
The marking of features as under-implemented is a one-time event to account for the different
process under which EPUB was developed prior to being brought into W3C. This label will not be
used for new features developed under W3C processes.
A.2 Deprecated Features
A deprecated feature is one the Working Group no longer recommends for use in this
version of the specification. Deprecated features typically have limited or no support in Reading
Systems and/or usage in EPUB Publications. If this specification designates a feature as deprecated,
the following hold true:
Developers should consider the unlikelihood of encountering content with
deprecated features before adding new support for them.
Validation tools SHOULD alert EPUB Creators to the presence of deprecated features when encountered
in EPUB Publications.
A.3 Legacy Features
A legacy feature is one that the Working Group has retained only for authoring
content that is compatible with versions of EPUB prior to 3.0. If this specification designates a
feature as legacy, the following hold true:
EPUB CreatorsMAY include the legacy feature for compatibility purposes.
Reading SystemsMUST NOT support the legacy feature in content that conforms to this
version of EPUB.
Validation tools SHOULD NOT alert EPUB Creators about the presence of legacy features in an EPUB
Publication, as their inclusion is valid for backwards compatibility. Validation tools MUST
alert EPUB Creators if a legacy feature does not conform to its definition or otherwise breaks a
usage requirement.
EPUB Creators MAY use these external identifiers only in Publication Resources with the listed
media types specified in their manifest declarations. (Refer to 2.2.4 XML Conformance for more information.)
Media Type(s)
Public Identifier
System Identifier
application/mathml+xml
application/mathml-presentation+xml
application/mathml-content+xml
-//W3C//DTD MathML 3.0//EN
http://www.w3.org/Math/DTD/mathml3/mathml3.dtd
application/svg+xml
-//W3C//DTD SVG 1.1//EN
http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd
C. Expressing Structural Semantics
C.1 Introduction
Structural semantics add additional meaning about the specific structural purpose an element plays.
The epub:type attribute is used to express
domain-specific semantics in EPUB Content Documents and Media Overlay Documents, with
the structural information it carries complementing the underlying vocabulary.
The applied semantics refine the meaning of their containing elements without changing their nature
for assistive technologies, as happens when using the similar role attribute [HTML]. The attribute does not enhance the accessibility
of the content, in other words, only provides hints about the purpose.
Semantic metadata enriches content for use in publishing workflows and for author-defined purposes.
It also allows Reading Systems to learn more about the structure and content of a document (e.g., to
enable skippability and escapability in Media
Overlays).
This specification defines a method for adding structural semantics using the attribute
axis: instead of adding new elements, EPUB Creators can append the epub:type
attribute to existing elements to add the desired semantics.
White space is the set of characters as defined in [XML].
Note
Although the epub:type attribute is similar in nature to the role attribute [HTML], the attributes
serve different purposes. The values of the epub:type attribute do not enhance the
accessibility of EPUB Publications, for example, they do not map to accessibility APIs used by assistive technologies. The
epub:type attribute is only intended for publishing semantics and Reading
System enhancements. Refer to Digital Publishing WAI-ARIA Module
1.0 [DPUB-ARIA-1.0] for more information about accessible publishing roles.
The epub:type attribute inflects semantics on the element on which it appears. Its value
is one or more white space-separated terms stemming from external vocabularies associated with the
document instance.
The inflected semantic MUST express a subclass of the semantic of the carrying element. In the case
of semantically neutral elements, such as the [HTML] div and span
elements, the inflected semantic MUST NOT attach a meaning that is already conveyed by an existing
element (e.g., that a div represents a paragraph or section).
The default vocabulary for the epub:type attribute is
the EPUB 3 Structural Semantics Vocabulary [EPUB-SSV-11]. EPUB Creators MAY include unprefixed
terms that are not part of this vocabulary, but the preferred method for adding custom semantics is
to use prefixes for them. Refer to D.1 Vocabulary Association Mechanisms
for more information.
D. Vocabularies
This appendix defines a general set of mechanisms by which attributes in this specification can reference
terms from vocabularies. It also defines EPUB-specific vocabularies for use with the attributes.
D.1 Vocabulary Association Mechanisms
D.1.1 Introduction
This section is non-normative.
EPUB defines a formal method of referencing terms and properties defined in metadata and semantic
vocabularies using the property data type. The
epub:type attribute uses this data type in EPUB Content Documents and
Media Overlay Documents to add structural
semantics, for example, while the property and rel attributes
use the data type to define properties and relationships in the Package Document.
A property value is like a CURIE [RDFA-CORE] — it represents a URL [URL] in
compact form. The expression consists of a prefix and a reference, where the prefix — whether
literal or implied — is a shorthand mapping of a URL that typically resolves to a term
vocabulary. When a Reading System converts the prefix to its URL representation and combines
with the reference, the resulting URL normally resolves to a fragment within that vocabulary
that contains human- and/or machine-readable information about the term.
To reduce the complexity for authoring, each attribute that takes a property data type
also defines a default vocabulary. Terms and properties
referenced from the default vocabularies do not include a prefix as the mapping Reading
Systems use to map to a URL is predefined.
The power of the property data type lies in its easy extensibility. To incorporate new
terms and properties, EPUB Creators only need to declare a prefix. In another authoring convenience, this specification also reserves prefixes for many commonly used
publishing vocabularies (i.e., their declaration is optional).
The following sections provide additional details on the property data type and
vocabulary association mechanism.
D.1.2 The property Data Type
The property data type is a compact means of expressing a URL [URL] and consists of
an OPTIONAL prefix separated from a reference by a colon.
(EBNF productions ISO/IEC 14977) All terminal symbols are in the Unicode Block 'Basic Latin'
(U+0000 to U+007F).
This specification derives the property data type from the CURIE data type defined in
[RDFA-CORE]. A property represents a subset of CURIEs.
When an EPUB Creator omits a prefix from a property value, the expressed reference
represents a term from the default vocabulary for that
attribute.
An empty string does not represent a valid property value, even though it is valid to
the definition above.
D.1.3 Default Vocabularies
A default vocabulary is one that EPUB Creators do not have to declare a prefix for in order to use its terms and properties where a property value is expected. EPUB Creators MUST NOT add a prefix to terms and properties from a default vocabulary.
EPUB Creators MUST NOT assign a prefix to the URLs associated with these vocabularies using the
prefix attribute.
Note
Refer to the definition of each attribute that takes a property data type for more information about its default
vocabulary.
D.1.4 The prefix Attribute
The prefix attribute defines prefix mappings for use in property values.
The value of the prefix attribute is a white space-separated list of one or more
prefix-to-URL mappings of the form:
(EBNF productions ISO/IEC 14977) All terminal symbols are in the Unicode Block 'Basic Latin'
(U+0000 to U+007F).
Although the prefix attribute is modeled on the identically named
prefix attribute in [RDFA-CORE], EPUB Creators cannot use the attributes
interchangeably. The prefix attribute without a namespace in EPUB Content
Documents is the RDFa attribute.
It is common for both attributes to appear in EPUB Content Documents that also specify RDFa
expressions.
To avoid conflicts, EPUB Creators MUST NOT use the prefix attribute to declare a
prefix that maps to the default vocabulary.
EPUB Creators MUST NOT declare the prefix '_' as this specification reserves this prefix for
future compatibility with RDFa [RDFA-CORE] processing.
For future compatibility with alternative serializations of the Package Document, EPUB Creators
MUST NOT declare a prefix for the Dublin Core /elements/1.1/ namespace [DCTERMS].
EPUB CreatorsMUST use only the [DCTERMS] elements allowed in the Package Document metadata.
D.1.5 Reserved Prefixes
Caution
Although reserved prefixes are an authoring convenience, EPUB Creators should avoid relying
on them as they may cause interoperability issues. Validation tools will often reject new
prefixes until their developers update the tools to the latest version of the specification,
for example. EPUB Creators should declare all prefixes they use to avoid such issues.
The properties in this vocabulary are usable in the meta
element'sproperty attribute.
Unless indicated otherwise in its "Extends" field, the properties defined in this section are used to
define subexpressions: in other words, a meta element carrying a property defined in this section MUST have a refines attribute referencing a resource or expression being
augmented.
In each property definition, the Allowed values field indicates the expected type of
value (using [XMLSCHEMA-2] datatypes), the Cardinality field indicates the number of
times the property MAY be attached to another property, and the Extends field
identifies the properties it MAY be attached to.
The alternate-script property provides an alternate expression of the
associated property value in a language and script identified by the
xml:lang attribute.
This property is typically attached to creator and title
properties for internationalization purposes.
Allowed value(s):
xsd:string
Cardinality:
zero or more
Extends:
All properties.
D.2.2 authority
Name:
authority
Description:
The authority property identifies the system or scheme the referenced
element's value is drawn from.
Allowed value(s):
one of the following case-insensitive reserved authority values:
The belongs-to-collection property identifies the name of a collection
to which the EPUB Publication belongs. An EPUB Publication MAY belong to one or more
collections.
It is also possible chain these properties using the refines attribute to indicate that one collection is
itself a member of another collection.
To allow Reading System to organize collections and avoid naming collisions (e.g.,
unrelated collections might share a similar name, or different editions of a
collection could be released), an identifier SHOULD be provided that uniquely
identifies the instance of the collection. The dcterms:identifier
property must carry this identifier.
The collection MAY more precisely define its nature by attaching a collection-type property.
The position of the EPUB Publication within the collection MAY be provided by
attaching a group-position property.
Allowed value(s):
xsd:string
Cardinality:
zero or more
Extends:
Applies to the EPUB Publication and can refine other instances of itself.
D.2.4 collection-type
Name:
collection-type
Description:
The collection-type property indicates the form or nature of a
collection.
When the collection-type value is drawn from a code list or other formal
enumeration, the scheme attributeSHOULD
be attached to identify its source.
When a scheme is not specified, Reading Systems SHOULD recognize the following
collection type values:
series
A sequence of related works that are formally identified as a group,
typically open-ended with works issued individually over time.
set
A finite collection of works that together constitute a single intellectual
unit, typically issued together and able to be sold as a unit.
The display-seq property indicates the numeric position in which to
display the current property relative to identical metadata properties.
This property only applies where precedence rules have not already been defined
(e.g., precedence is given to creators based on
their appearance in document order).
Allowed value(s):
xsd:unsignedInt
Cardinality:
zero or one
Extends:
All properties.
D.2.6 file-as
Name:
file-as
Description:
The file-as property provides the normalized form of the associated
property for sorting.
Allowed value(s):
xsd:string
Cardinality:
zero or one
Extends:
All properties.
D.2.7 group-position
Name:
group-position
Description:
The group-position property indicates the numeric position in which the
EPUB Publication is ordered relative to other works belonging to the same group
(whether all EPUB Publications or not).
The group-position property can be attached to any metadata property
that establishes the group but is typically associated with the belongs-to-collection
property.
An EPUB Publication can belong to more than one group.
Allowed value(s):
A single xsd:unsignedInt or series of decimal-separated numbers (e.g.,
1 or 2.2.1).
Cardinality:
zero or one
Extends:
All properties.
D.2.8 identifier-type
Name:
identifier-type
Description:
The identifier-type property indicates the form or nature of an
identifier.
When the identifier-type value is drawn from a code list or other formal
enumeration, the scheme attributeSHOULD
be attached to identify its source.
For more information about this property, refer its definition in [EPUBPublications-30].
D.2.10 role
Name:
role
Description:
The role property describes the role of a creator,
contributor or publisher in the creation of an EPUB
Publication.
When the role value is drawn from a code list or other formal
enumeration, the scheme attributeSHOULD
be attached to identify its source.
When attaching multiple roles to an individual or organization, the importance of the
roles should match the document order of their containing meta elements
(i.e., the first meta element encountered should contain the most
important role).
The source-of property indicates a unique aspect of an adapted source
resource that has been retained in the EPUB Publication.
This specification defines the pagination value to indicate that the
referenced dc:source element is the source of the pagebreak properties defined in the content.
The title-type property indicates the form or nature of a
title.
When the title-type value is drawn from a code list or other formal
enumeration, the scheme attributeSHOULD
be attached to identify its source. When a scheme is not specified, Reading Systems
should recognize the following title type values:
main, subtitle, short,
collection, edition and
expanded.
The alternate keyword is a subset of the HTML
alternate keyword for links. It differs as follows:
It cannot be paired with other keywords.
If an alternate link is included in the Package Document metadata, it
identifies an alternate representation of the Package Document in the format
specified in the media-type attribute.
If an alternate link is included in a collection element's metadata, it identifies an
alternate representation of the collection in the format
specified in the media-type attribute.
Reading Systems do not have to generate hyperlinks for alternate links.
Cardinality:
Zero or more
Extends:
Only applies to the EPUB Publication or collection. MUST NOT be used when the refines attribute is present.
Indicates that the referenced audio file provides an aural representation of the
expression or resource (typically, the title or creator) specified by the
refines attribute.
The media type of the audio file is identified in the media-type attribute when
this keyword is specified.
Cardinality:
Zero or more
Extends:
All properties. The refines attributeMUST be present when this value is used.
Use of the xml-signature keyword is deprecated.
It is not replaced by another linking method. Identification of XML signatures will be addressed in a
future version of EPUB.
For more information about this property, refer its definition in [EPUBPublications-30].
For more information about this property, refer its definition in [EPUBPublications-30].
D.3.2 Link Properties
The following values can be used in the link element'sproperties attribute to establish the type of record a referenced resource represents.
These values are provided for record formats that cannot be uniquely identified by their media
type.
D.3.2.1 onix
Name:
onix
Description:
The onix property indicates the referenced resource is an ONIX record
[ONIX].
Not all rendering information can be expressed through the underlying technologies that EPUB is
built upon. For example, although HTML with CSS provides powerful layout capabilities, those
capabilities are limited to the scope of the document being rendered.
This section defines general-purpose properties that allow EPUB Creators to express package-level
rendering intentions (i.e., functionality that can only be implemented by the EPUB Reading
System). If a Reading System supports the desired rendering, these properties enable the
user to be presented the content as the EPUB Creator optimally designed it.
The "rendition:" prefix is reserved for
use with the package rendering properties and does not have to be declared in the
Package Document.
D.4.1 General Properties
D.4.1.1 The rendition:flow Property
The rendition:flow property specifies the EPUB Creator preference for how Reading
Systems should handle content overflow.
When the rendition:flow
property is specified on a meta element, it indicates the EPUB Creator's
global preference for overflow content handling (i.e., for all spine items). EPUB Creators MAY
indicate a preference for dynamic pagination or scrolling. For scrolled content, it is
also possible to specify whether consecutive EPUB Content Documents are to be
rendered as a continuous scrolling view or whether each is to be rendered separately
(i.e., with a dynamic page break between each).
The following values are defined for use with the rendition:flow
property:
paginated
Dynamically paginate all overflow content.
scrolled-continuous
Render all Content Documents such that overflow content is scrollable, and the
EPUB Publication is presented as one continuous scroll from spine item to spine
item (except where locally overridden).
Note that EPUB Creators SHOULD NOT create publications in which different resources
have different block flow directions, as continuous scrolled rendition in EPUB
Reading Systems would be problematic.
scrolled-doc
Render all Content Documents such that overflow content is scrollable, and each
spine item is presented as a separate scrollable document.
auto
Render overflow content using the Reading System default method or a user
preference, whichever is applicable. Default value.
Note that when two reflowable EPUB Content Documents
occur sequentially in the spine, the default rendering for their [HTML] body elements is consistent with the page-break-before property [CSSSnapshot] having been set to
always. In addition to using the rendition:flow property,
EPUB Creators MAY override this behavior through an appropriate style sheet declaration, if
the Reading System supports such overrides.
The rendition:flow property MUST NOT be declared more than once.
Figure 1 Rendering of an EPUB publication with a single spine item, and with the
rendition:flow set to paginated.Image description
Three column-like rectangles linked left-to-middle and middle-to-right with respective arrows,
with a text flowing from one rectangle to the next one. The text is sectioned with headers
figuring 'Chapter 1', '2', and '3'. The leftmost rectangle is enclosed in a schematic view of
a tablet.
Figure 2 Rendering of an EPUB publication with multiple spine items, and with the
rendition:flow set to paginated.Image description
Three column-like rectangles linked left-to-middle and middle-to-right with respective arrows,
with a text flowing from one rectangle to the next one. The text is sectioned with headers
figuring 'Chapter 1', '2'. The section with 'Chapter 2' starts at the top of the rightmost
rectangle, leaving an empty space at the bottom of the middle rectangle. The leftmost rectangle
is enclosed in a schematic view of a tablet.
Figure 3 Rendering of an EPUB publication with a single spine item, and with the
rendition:flow set to scrolled-continuous.Image description
A single, column-like strip (i.e., a rectangle without a bottom edge) with a text flowing down the strip.
The text is sectioned with headers figuring 'Chapter 1', '2'. The top part of the strip
is enclosed in a schematic view of a tablet.
Figure 4 Rendering of an EPUB publication with multiple spine items, and with the
rendition:flow set to scrolled-doc.Image description
Three column-like strips (i.e., a rectangles without bottom edges) linked left-to-middle
and middle-to-right with respective arrows, each containing a text flowing down the strip.
The text is sectioned with headers figuring 'Chapter 1', '2' and '3'. Each strip starts with
a chapter header and flows down the strip. The top part of the leftmost strip is enclosed
in a schematic view of a tablet.
D.4.1.1.1 Spine Overrides
EPUB Creators MAY specify the following properties locally on
spine itemref elements to override the
global value for the given spine item:
flow-auto
Indicates no preference for overflow content handling by the EPUB Creator.
flow-paginated
Indicates the EPUB Creator preference is to dynamically paginate content overflow.
flow-scrolled-continuous
Indicates the EPUB Creator preference is to provide a scrolled view for overflow content,
and that consecutive spine items with this property are to be rendered as a
continuous scroll.
flow-scrolled-doc
Indicates the EPUB Creator preference is to provide a scrolled view for overflow content,
and each spine item with this property is to be rendered as a separate scrollable
document.
Only one of these overrides is allowed on any given spine item.
D.4.1.2 The rendition:align-x-center Property
The rendition:align-x-center property specifies that the given spine item should
be centered horizontally in the viewport or spread.
The property cannot be set globally for all EPUB Content Documents. It is only available as a spine
override for individual EPUB Content Documents via the itemref element's properties
attribute.
Note
This property was developed primarily to handle "Naka-Tobira (中扉)" (sectional title
pages), in the absence of reliable centering control within the content rendering. As
support for paged media evolves in CSS, however, this property is expected to be
deprecated. EPUB Creators are encouraged to use CSS solutions when effective.
D.4.2 Fixed-Layout Properties
The following properties belong to the Package Rendering Vocabulary. Refer to their respective
definitions in 5. Fixed Layouts for the details of their use.
The Applies to field indicates which Publication Resource type(s) the given property MAY
be specified on, the Cardinality field indicates the number of times the property MUST
appear within the Package Document scope, and the Usage field indicates usage
conditions.
The remote-resources property indicates that the described Publication
Resource contains one or more internal references to other Publication Resources
that are located outside of the EPUB Container.
MUST be set if and only if the criterion specified in the description is met.
D.5.5 scripted
Name:
scripted
Description:
The scripted property indicates that the described Publication Resource is
a Scripted Content Document (i.e., contains scripted content and/or HTML form
elements).
MUST be set if and only if the criterion specified in the description is met.
D.5.6 svg
Name:
svg
Description:
The svg property indicates that the described Publication Resource
embeds one or more instances of SVG markup.
This property MUST be set when SVG markup is included directly in the resource and
MAY be set when the SVG is referenced from the resource (e.g., from an [HTML]
img, object or iframe element).
MUST be set if and only if the criterion specified in the description is met.
D.5.8 Usage
The mathml, remote-resources, scripted and switch
properties MUST be specified whenever the resource referenced by an item matches their
respective definitions. These properties do not apply recursively to content included into a
resource (e.g., via the HTML iframe element). For example, if a non-scripted XHTML
Content Document embeds a scripted Content Document, only the embedded document's manifest
itemproperties attribute will have the scripted value.
The page-spread-left property indicates that the first page of the
associated item element's EPUB Content Document represents the
left-hand side of a two-page spread.
D.6.2 page-spread-right
Name:
page-spread-right
Description:
The page-spread-right property indicates that the first page of the
associated item element's EPUB Content Document
represents the right-hand side of a two-page spread.
D.6.3 Examples
D.7 Media Overlays Vocabulary
The properties in this vocabulary are usable in the meta
element'sproperty attribute.
The duration of the entire presentation or of a specific Media Overlay. The specified
durations account for the audio clips known at authoring time, and so exclude live
streaming from external resources and speech synthesis.
This appendix describes the prefixed CSS properties supported by EPUB.
E.1 CSS Writing Modes
This section describes the -epub- prefixed properties for [CSS-Writing-Modes-3].
E.1.1 The -epub-text-orientation Property
This is a prefixed version of the CSS text-orientation property.
Name:
-epub-text-orientation
Value:
mixed | upright | sideways | sideways-right
Previous versions of EPUB 3 used additional values of -epub-text-orientation. User
agents MUST interpret these values according to the following table:
Deprecated value
Value to be used
vertical-right
mixed
rotate-right
sideways
rotate-normal
sideways
E.1.2 The -epub-writing-mode Property
This is a prefixed version of the CSS writing-mode property, with the same syntax
and behavior.
Name:
-epub-writing-mode
Value:
horizontal-tb | vertical-rl | vertical-lr
E.1.3 The -epub-text-combine-horizontal and -epub-text-combine
Properties
These are prefixed versions of text-combine-upright, although
-epub-text-combine is deprecated. See the table below for how values of both
properties translate to unprefixed CSS.
Name:
-epub-text-combine-horizontal
Value:
none | all
Name:
-epub-text-combine (deprecated)
Value:
none | horizontal | horizontal <number>
The following table shows how to map from the prefixed versions to the current CSS versions.
Prefixed version
CSS equivalent
-epub-text-combine-horizontal: none
text-combine-upright: none
-epub-text-combine-horizontal: all
text-combine-upright: all
-epub-text-combine: none
text-combine-upright: none
-epub-text-combine: horizontal
text-combine-upright: all
-epub-text-combine: horizontal <number>
Error
E.2 CSS Text Level 3
This section describes the -epub- prefixed properties (and one prefixed value) for
[CSS-Text-3].
E.2.1 The -epub-hyphens Property
This is a prefixed version of the hyphens property.
Name:
-epub-hyphens
Value:
none | manual | auto | all
Note
The all value is no longer supported in CSS.
E.2.2 The -epub-line-break Property
This is a prefixed version of the line-break property.
Name:
-epub-line-break
Value:
auto | loose | normal | strict
E.2.3 The -epub-text-align-last Property
This is a prefixed version of the text-align-last property.
Name:
-epub-text-align-last
Value:
auto | start | end | left | right | center | justify
E.2.4 The -epub-word-break Property
This is a prefixed version of the word-break property.
Name:
-epub-word-break
Value:
normal | keep-all | break-all
E.2.5 The text-transform Property
This is a prefixed value for the text-transform property.
Name:
text-transform
Value:
-epub-fullwidth
The following table describes the equivalent value in CSS.
EPUB version
CSS equivalent
text-transform: -epub-fullwidth
text-transform: full-width
E.3 CSS Text Decoration Level 3
This section describes the -epub- prefixed properties for [CSS-Text-Decor-3].
E.3.1 The -epub-text-emphasis-color Property
This is a prefixed version of the text-emphasis-color property.
Name:
-epub-text-emphasis-color
Value:
<color>
E.3.2 The -epub-text-emphasis-position Property
This is a prefixed version of the text-emphasis-position property.
Name:
-epub-text-emphasis-position
Value:
[ over | under ] && [ right | left ]
E.3.3 The -epub-text-emphasis-style Property
This is a prefixed version of the text-emphasis-style property.
the code in the script element in the head in
scripted01.xhtml is a spine-level script
because the document is referenced from the spine; and
the code in the script element in scripted02.xhtml is a container-constrained script because the
HTML file it occurs in is included in scripted01.xhtml via the
iframe element.
G.2 Packaged EPUB
This example demonstrates the use of the OCF format to contain a signed and encrypted EPUB
Publication within an OCF ZIP Container.
<signaturesxmlns="urn:oasis:names:tc:opendocument:xmlns:container"><SignatureId="AsYouLikeItSignature"xmlns="http://www.w3.org/2000/09/xmldsig#"><!--
SignedInfo is the information that is actually signed.
In this case, the SHA-1 algorithm is used to sign the
canonical form of the XML documents enumerated in the
Object element below.
--><SignedInfo><CanonicalizationMethodAlgorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315"/><SignatureMethodAlgorithm="http://www.w3.org/2000/09/xmldsig#dsa-sha1"/><ReferenceURI="#AsYouLikeIt"><DigestMethodAlgorithm="http://www.w3.org/2000/09/xmldsig#sha1"/><DigestValue>
…
</DigestValue></Reference></SignedInfo><!--
The signed value of the digest above, using the DSA
algorithm
--><SignatureValue>
…
</SignatureValue><!--
The key used to validate the signature
--><KeyInfo><KeyValue><DSAKeyValue><P>…</P><Q>…</Q><G>…</G><Y>…</Y></DSAKeyValue></KeyValue></KeyInfo><!--
The list of resources to sign (note that the canonical
form of XML documents is signed, while the binary form
of all other resources is used)
--><Object><ManifestId="AsYouLikeIt"><ReferenceURI="EPUB/As_You_Like_It.opf"><Transforms><TransformAlgorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315"/></Transforms><DigestMethodAlgorithm="http://www.w3.org/2000/09/xmldsig#sha1"/><DigestValue></DigestValue></Reference><ReferenceURI="EPUB/book.html"><Transforms><TransformAlgorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315"/></Transforms><DigestMethodAlgorithm="http://www.w3.org/2000/09/xmldsig#sha1"/><DigestValue></DigestValue></Reference><ReferenceURI="EPUB/images/cover.png"><DigestMethodAlgorithm="http://www.w3.org/2000/09/xmldsig#sha1"/><DigestValue></DigestValue></Reference></Manifest></Object></Signature></signatures>
The contents of the META-INF/encryption.xml file
<?xml version="1.0"?><encryptionxmlns="urn:oasis:names:tc:opendocument:xmlns:container"xmlns:enc="http://www.w3.org/2001/04/xmlenc#"xmlns:ds="http://www.w3.org/2000/09/xmldsig#"><!--
The RSA-encrypted AES-128 symmetric key used to encrypt
data enumerated in EncryptedData blocks below
--><enc:EncryptedKeyId="EK"><enc:EncryptionMethodAlgorithm="http://www.w3.org/2001/04/xmlenc#rsa-1_5"/><ds:KeyInfo><ds:KeyName>
John Smith
</ds:KeyName></ds:KeyInfo><enc:CipherData><enc:CipherValue>
xyzabc…
</enc:CipherValue></enc:CipherData></enc:EncryptedKey><!--
Each EncryptedData block identifies a single resource
that has been encrypted using the AES-128 algorithm.
The data remains stored, in its encrypted form, in the
original file within the container.
--><enc:EncryptedDataId="ED1"><enc:EncryptionMethodAlgorithm="http://www.w3.org/2001/04/xmlenc#kw-aes128"/><ds:KeyInfo><ds:RetrievalMethodURI="#EK"Type="http://www.w3.org/2001/04/xmlenc#EncryptedKey"/></ds:KeyInfo><enc:CipherData><enc:CipherReferenceURI="EPUB/book.html"/></enc:CipherData></enc:EncryptedData><enc:EncryptedDataId="ED2"><enc:EncryptionMethodAlgorithm="http://www.w3.org/2001/04/xmlenc#kw-aes128"/><ds:KeyInfo><ds:RetrievalMethodURI="#EK"Type="http://www.w3.org/2001/04/xmlenc#EncryptedKey"/></ds:KeyInfo><enc:CipherData><enc:CipherReferenceURI="EPUB/images/cover.png"/></enc:CipherData></enc:EncryptedData></encryption>
The contents of the EPUB/As_You_Like_It.opf file
<?xml version="1.0"?><packageversion="3.0"xml:lang="en"xmlns="http://www.idpf.org/2007/opf"unique-identifier="pub-id"><metadataxmlns:dc="http://purl.org/dc/elements/1.1/"><dc:identifierid="pub-id">
urn:uuid:B9B412F2-CAAD-4A44-B91F-A375068478A0
</dc:identifier><dc:language>
en
</dc:language><dc:title>
As You Like It
</dc:title><dc:creatorid="creator">
William Shakespeare
</dc:creator><metaproperty="dcterms:modified">
2000-03-24T00:00:00Z
</meta><dc:publisher>
Project Gutenberg
</dc:publisher><dc:date>
2000-03-24
</dc:date><metaproperty="dcterms:dateCopyrighted">
9999-01-01
</meta><dc:identifierid="isbn13">
urn:isbn:9780741014559
</dc:identifier><dc:identifierid="isbn10">
0-7410-1455-6
</dc:identifier><linkrel="xml-signature"href="../META-INF/signatures.xml#AsYouLikeItSignature"/></metadata><manifest><itemid="r4915"href="book.html"media-type="application/xhtml+xml"/><itemid="r7184"href="images/cover.png"media-type="image/png"/><itemid="nav"href="nav.html"media-type="application/xhtml+xml"properties="nav"/></manifest><spine><itemrefidref="r4915"/></spine></package>
G.3 Clock Values
The following are examples of allowed clock values:
0:05:01.2 = 5 minutes, 1 second, and 200 milliseconds
0:00:04 = 4 seconds
09:58 = 9 minutes and 58 seconds
00:56.78 = 56 seconds and 780 milliseconds
76.2s = 76.2 seconds = 76 seconds and 200 milliseconds
7.75h = 7.75 hours = 7 hours and 45 minutes
13min = 13 minutes
2345ms = 2345 milliseconds
12.345 = 12 seconds and 345 milliseconds
H. Media Type Registrations
This section is non-normative.
H.1 The application/oebps-package+xml Media Type
This appendix registers the media type application/oebps-package+xml for the EPUB
Package Document. This registration supersedes [RFC4839].
The Package Document is an XML file that describes an EPUB Publication. It identifies the resources
in the EPUB Publication and provides metadata information. The Package Document and its related
specifications are maintained and defined by the World Wide Web
Consortium (W3C).
MIME media type name:
application
MIME subtype name:
oebps-package+xml
Required parameters:
None.
Optional parameters:
None.
Encoding considerations:
Package Documents are UTF-8 or UTF-16 encoded XML.
Security considerations:
Package Documents contain well-formed XML conforming to the XML 1.0 specification.
Clearly, it is possible to author malicious files which, for example, contain malformed data.
Most XML parsers protect themselves from such attacks by rigorously enforcing
conformance.
All processors that read Package Documents should rigorously check the size and validity of
data retrieved.
There is no current provision in the EPUB 3 specification for encryption, signing, or
authentication within the Package Document format.
Interoperability considerations:
None.
Published specification:
This media type registration is for the EPUB Package Document, as described by the EPUB 3
specification located at https://www.w3.org/TR/epub-33/.
The EPUB 3 specification supersedes the Open Packaging Format 2.0.1 specification, which is
located at http://www.idpf.org/epub/20/spec/OPF_2.0.1_draft.htm and which also uses the application/oepbs-package+xml media type.
Applications which use this media type:
This media type is in wide use for the distribution of ebooks in the EPUB format.
Additional information:
Magic number(s):
none
File extension(s):
.opf
Macintosh File Type Code(s):
TEXT
Fragment Identifiers:
EPUB Canonical Fragment Identifiers are custom fragment identifiers that can resolve
to application/oebps-package+xml documents.
Person & email address to contact for further information:
public-epub3@w3.org
Intended usage:
COMMON
Author/Change controller:
World Wide Web Consortium (W3C)
H.2 The application/epub+zip Media Type
This section is non-normative.
This appendix registers the media type application/epub+zip for the EPUB Open Container
Format (OCF).
An OCF ZIP Container, or EPUB Container, file is a container technology based on the
[ZIP] archive format. It is used to encapsulate the EPUB Publication. OCF and its related
standards are maintained and defined by the World Wide Web
Consortium (W3C).
MIME media type name:
application
MIME subtype name:
epub+zip
Required parameters:
None.
Optional parameters:
None.
Encoding considerations:
OCF ZIP Container files are binary files encoded in the application/zip media type.
Security considerations:
All processors that read OCF ZIP Container files should rigorously check the size and
validity of data retrieved.
In addition, because of the various content types that can be embedded in OCF ZIP Container
files, application/epub+zip may describe content that poses security
implications beyond those noted here. However, only in cases where the processor recognizes
and processes the additional content, or where further processing of that content is
dispatched to other processors, would security issues potentially arise. In such cases,
matters of security would fall outside the domain of this registration document.
Security considerations that apply to application/zip also apply to OCF ZIP
Container files.
Interoperability considerations:
None.
Published specification:
This media type registration is for the EPUB Open Container Format (OCF), as described by the
EPUB 3 specification located at https://www.w3.org/TR/epub-33/.
OCF ZIP Container files are most often identified with the extension
.epub.
Macintosh file type code(s):
ZIP
Fragment identifiers:
EPUB Canonical Fragment Identifiers are custom fragment identifiers that can resolve
to application/epub+zip and application/oebps-package+xml
documents.
Person & email address to contact for further information:
public-epub3@w3.org
Intended usage:
COMMON
Author/change controller:
World Wide Web Consortium (W3C)
I. Change Log
This section is non-normative.
Note that this change log only identifies substantive changes since EPUB 3.2 — those that affect the
conformance of EPUB Publications or are similarly noteworthy.
19-Feb-2022: Clarified the audio element's
definition by making it optional, and adapt the specification's text elsewhere to address the
situation when the element is indeed not present. See issue 1986.
04-Feb-2022: Expanded the section on security and privacy to include new sections on the threat
model for EPUB Publications and additional recommendations for ensuring security and privacy. See issue 1871, issue 1872, issue 1875 and issue 1876.
21-January-2022: term "risky", used for the class of unsupported features, has been renamed to
"under-implemented". See the WG resolution.
08-Dec-2021: The page-spread-center property is now an alias for
spread-none. See issue
1929.
03-Dec-2021: Added a new risky class for unsupported features. See issue 1944.
03-Dec-2021: Remove the element-based restrictions on remote resources. See issue 1913.
01-Dec-2021: Deprecated the use of page-spread-center. It is now an alias for
spread-none. See issue
1929.
26-Nov-2021: A requirement and an algorithm to detect out-of-container URLs has been added to the
specification. See issue 1912.
18-Nov-2021: Change to only disallow deprecated characters in the Tags and Variation Selectors
Supplement. See issue 1885.
12-Nov-2021: Change the recommendation to use SHA-1 to encrypt the obfuscation key to a requirement.
See issue 1873.
12-Nov-2021: Restrict the obfuscation algorithm to fonts and add caution to use better protection
methods whenever possible. See issue
1873.
12-Nov-2021: Removed the statement about rights.xml being reserved for future standardization of DRM
information. See issue 1874.
10-Nov-2021: Proper definition of the content URL and handling of relative URLs. See issue 1374 and issue 1888
29-Oct-2021: Recommended that EPUB Creators not use path-absolute-URL strings for referencing
resources due to the lack of a consistent root. See issue 1681.
18-Oct-2021: Clarified the contexts from which remote resources may be referenced. See issue 1857.
12-Oct-2021: The Structure Semantics Vocabulary has been moved into a separate Working Group Note.
See issue 1763.
27-Aug-2021: Add clarifications for including landmarks, such as limiting the number, recommending
known semantics, and ensuring the labels are human readable. Also added recommendation to not
include nested lists to match the page list. See issue 1761.
22-July-2021: Clarified TTS handling of images in media overlays. See issue 1745.
09-July-2021: Restored the custom attributes section due to known usage but without reference to the
attribute registry. See issue 1602.
09-July-2021: Added the "Relationship to URL" section to explain the use of URL standard terminology
in this document relative to resource formats that do not reference it. See issue 1726.
05-July-2021: Removed the section on private use area characters from the XHTML restrictions. The
issues are more complex than what is covered and not in scope of EPUB to define. See issue 1732.
28-June-2021: Added a note discouraging EPUB Creators from referencing resources outside the
directory containing the Package Document to avoid interoperability issues. See issue 1687
23-June-2021: Added the base element to the list of discouraged XHTML constructs. See
issue 1699.
18-June-2021: Moved requirements for authoring SSML, PLS lexicons and CSS 3 Speech to the EPUB 3 Text-to-Speech Enhancements note. The
ability to use these technologies in EPUB 3 Publications remains unchanged. See issue 1690.
16-June-2021: Absolute URLs with file scheme should not be used on manifest items. See
issue 1688.
31-May-2021: Require Unicode normalization and full case folding (in this order) for file name
uniqueness comparisons. See issue 1631
and pull request 1648.
31-May-2021: Confirmed that SVG Content Documents do not have to be valid to the SVG specification,
only meet the well-formedness and ID requirements currently referenced and the restrictions imposed
by this specification. See issue
1323.
12-May-2021: Clarified that manifest items must not contain fragment identifiers. See issue 1303.
12-May-2021: Changed all references to URIs/IRIs to URLs and references to RFCs 3986 and 3987 to the
URL standard. See issue 808.
08-May-2021: Added clarifying text that link element can be used to link individual
metadata properties in an alternative format. See issue 1666.
06-May-2021: Noted that the working group will no longer maintain the publication type and
collection role registries and removed dependence on the latter for validating collection types (use
of NMToken values remains restricted to extension specifications). The registry of authority codes
is now integrated into the property definition. See pull request 1664.
06-May-2021: Added application/ecmascript as a core media type for scripts. See issue 1353.
06-May-2021: Added new section on fragment identifiers to Media Overlays and now recommend HTML
target element references and SVG fragment identifiers instead of requiring conformance to the
incompatible XPointer Shorthand syntax. See issue 1586.
28-Apr-2021: Drop requirement for resources referenced from HTML link elements to have
core media type fallbacks. See issue
1312.
22-Apr-2021: The usage of UTF-16 for CSS and XML has been changed, UTF-8 is the recommended
encoding. See issue 1628.
19-Apr-2021: The use of custom attributes in EPUB Content Documents is no longer supported. See issue 1602.
13-Apr-2021: Require path names in OCF to also be UTF-8 encoded. See issue 1630.
09-Apr-2021: Added a new section dedicated to accessibility in EPUB Publications.
04-May-2021: Removed requirements around SVG requiredExtensions attribute. See issue 1087.
26-Mar-2021: Removed requirement for page list ordering to reflect the order of page breaks in the
content. See issue 1500.
26-Mar-2021: Allowed creator and contributor elements to have multiple
roles and allowed roles for publisher. See issue 1129 and issue 1583
23-Mar-2021: Clarified the requirements for the use of data URLs in EPUB Publications. See issue 1564.
17-Mar-2021: Include non characters at the end of the supplementary planes in list of characters not
allowed in file names. See issue
1538.
15-Mar-2021: Removed the normative dependencies on XML schemas and added element and attribute
definitions for the container.xml, encryption.xml and
signatures.xml files. All schemas are considered informative. See issue 1566.
10-Mar-2021: Require that resources referenced from an EPUB Publication not be located in the
META-INF directory. See issue 1205.
08-Mar-2021: The fix for issue 1322 on
20-Jan-2021 incorrectly mentioned EPUB Content Documents having durations. Corrected to Media
Overlay Documents.
08-Mar-2021: Added recommendation that refines attribute use fragment identifiers to
reference Publication Resources. See issue
1361.
08-Mar-2021: Change requirement that Media Overlay par and seq ordering
match the default reading order to guidance. See issue 1458
05-Mar-2021: Clarified that whitespace within metadata element values is collapsed per the [Infra]
specification definition. See issue
1528.
26-Feb-2021: Created a new section for describing general metadata value requirements, specifically
whitespace handling. See issue
1528.
17-Feb-2020: File extension recommendations have been removed (affects the Package Document, XHTML
Content Documents, Media Overlay Documents). See issue 1294.
15-Feb-2021: Clarified that nav elements without an epub:type attribute
are not subject to the EPUB Navigation Document's content model restrictions. See issue 976.
04-Feb-2021: Clarify that the value of dc:language elements must be well-formed
language tags. See issue 1325.
02-Feb-2021: Added auto value for dir attribute and clarified the
precedence of the attribute. See issue
1491 and issue 1494.
02-Feb-2021: Added the hreflang attribute to link elements to identify the
language of linked resources. See issue
1488.
20-Jan-2021: Clarified that user-defined media overlay style classes must be declared in the Package
Document metadata. See issue 1319.
20-Jan-2021: Add recommendation that the sum of the media overlay durations for each Content
Document match the total duration specified for the EPUB Publication. See issue 1322.
20-Jan-2021: Clarified that the epub:type attribute does not improve the accessibility
of publications. Added pointers to the role attribute and the DPUB-ARIA vocabulary for
accessibility.
13-Jan-2021: The requirement for progressive enhancement with spine-level scripting has been changed
to a recommendation that top-level content documents remain consumable when scripting is not
available. See issue 1444.
24-Dec-2020: The specification no longer makes reference to a release identifier, but the
requirement to include a last modification date remains for backwards compatibility. See issue 1440.
16-Dec-2020: Terminology and requirements related to "renditions" of an EPUB Publication have been
simplified to improve the readability of the specifications (i.e., to align with the generally
understood concept that an EPUB Publication has only a single rendering described by a single
Package Document). These changes do not affect the ability to include multiple renditions, which are
now more fully covered in [EPUB-MULTI-REND-11]. See issue 1436.
14-Nov-2020: The term "semantic inflection" is no longer used to describe the process of adding
structural semantics to elements. The term is not widely understood outside of EPUB, and is
unnecessarily complex. The specification now simply refers to "expressing" or "adding" structual
semantics.
09-Nov-2020: The requirement that the ordering of the toc nav match the ordering of
EPUB Content Documents in the spine, and the elements within each file, has been reduced to a
recommendation. See issue 1283.
12-Oct-2020: Added OPUS to the audio core media types with a warning
that it is still subject to review depending on support in Mac/iOS. See issue 645.
30-Sept-2020: The structure of the EPUB core specifications has been simplified to ease
understanding and access to information. This specification now consolidates the authoring
requirements from the EPUB 3.2 specification together with the Packages, Content Documents, OCF and
Media Overlays specifications. A separate document, EPUB Reading Systems 3.3, consolidates the
reading system requirements from those documents.
J. Acknowledgements
This section is non-normative.
Specifications, like art, are human creations. No human has done more for EPUB than Garth Conboy, who has
been there every step of the way, from the very first OEB 1.0 in 1999 to today's EPUB 3.3. None of this
would have happened without Garth's vision, knowledge, and preternatural good nature. We dedicate EPUB 3.3 to his memory.
We are forever in your debt, Garth.
The following members of the EPUB 3 Working Group contributed to the development of this specification:
Juliette Alexandria (Access2online Inc.)
Luc Audrain (W3C Invited Expert)
Will AWAD (Newgen Knowledgeworks)
Sofia Bautista (Legible Media Inc.)
Laura Brady (W3C Invited Expert)
Leah Brochu (National Network for Equitable Library Service)
Matthew C. Chan (House of Anansi Press)
Yu-Wei Chang (Taiwan Digital Publishing Forum)
Fred Chasen (Scribd)
Garth Conboy (Google LLC)
Juan Corona (Legible Media Inc.)
Dave Cramer (W3C Invited Expert, chair)
Romain Deltour (DAISY Consortium)
Marisa DeMeglio (DAISY Consortium)
Brady Duga (Google LLC)
Reinaldo Ferraz (NIC.br - Brazilian Network Information Center)
John Foliot (W3C Invited Expert)
Teenya Franklin (Pearson plc)
Hadrien Gardeur (EDRLab)
Matt Garrish (DAISY Consortium)
Jen Goulden (Crawford Technologies)
Ivan Herman (W3C, staff contact)
Tetsu Hoshino (Kodansha, Publishers, Ltd.)
Norikazu Ishizu (Kadokawa Corporation)
Norihito IYENAGA (Kodansha, Publishers, Ltd.)
Ken Jones (Circular Software)
Deborah Kaplan (W3C Invited Expert)
Bill Kasdorf (Book Industry Study Group)
George Kerscher (DAISY Consortium)
Kazuhito Kidachi (Mitsue-Links Co., Ltd.)
Masakazu Kitahara (Voyager Japan, Inc.)
Toshiaki Koike (Voyager Japan, Inc.)
Ryo Kuroda (ACCESS CO., LTD.)
Charles LaPierre (Benetech)
Dan Lazin (Google LLC)
Laurent Le Meur (EDRLab)
Farrah Little (National Network for Equitable Library Service)
Karan Malhotra (Newgen Knowledgeworks)
Makoto Murata (DAISY Consortium)
Cristina Mussinelli (Fondazione LIA)
Yoichiro Nagao (Kodansha, Publishers, Ltd.)
Yoshinori Ohmura (SHUEISHA Inc.)
Rachel Osolen (National Network for Equitable Library Service)
