Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
PD ISO IEC TS 30135 โ Digital Publishing EPUB3 Standard Series
Information Technology โ Digital Publishing โ EPUB3 (2014 Series, UK implementation of ISO/IEC TS 30135)
๐ PD ISO/IEC TS 30135 is the British Standards Institution (BSI) implementation of the ISO/IEC TS 30135 technical specification series on information technology โ digital publishing โ EPUB3. EPUB (Electronic Publication) is the most widely adopted open e-book format in international digital publishing, developed by the International Digital Publishing Forum (IDPF, now merged into W3C) and published as an ISO/IEC technical specification. EPUB3 is built on Web technologies such as HTML5, CSS3, SVG and JavaScript, supporting rich layout, multimedia, interactivity and accessibility. UK participation was entrusted to Technical Committee ICT/-/1 (Information systems co-ordination); the ICS classification is 35.240.30. The seven parts systematically define the EPUB3 publication structure, content documents, open container format and media overlays.
๐ก Notable background: the UK committee voted against the specification at the enquiry stage โ although it considered the EPUB3 specification technically sound, it had concerns about the editorial quality, specifically the grouping of terms and definitions, the use of cross-references between parts, and the typographic layout, fearing these could hinder interpretation by users who had not participated in EPUB development and were unfamiliar with assumptions made by other users. Readers should therefore combine W3C/IDPF official guidance and implementation experience when using this series.
1. Background and Design Goals ๐
Digital publishing needs an open format that is compatible with the Web ecosystem while suited to the “book” form: it must remain consistently readable across different readers (phones, tablets, e-ink readers, desktop apps), and support reflowable and fixed layouts, complex scripts, mathematical formulae, multimedia and accessibility. EPUB3 addresses these needs with a “Publication โ Content Documents โ OCF packaging” architecture, inheriting HTML5/CSS3 capabilities to achieve consistent cross-device presentation.
The parts each perform a dedicated role: Part 1 provides the overall overview; Part 2 defines the publication structure and metadata; Part 3 specifies content documents (XHTML, SVG, etc.); Part 4 specifies the Open Container Format (OCF, i.e., ZIP packaging and metadata); Part 5 defines Media Overlays for audio-synchronized reading; Parts 6/7 supplement fixed-layout and multi-modal presentation. Together they form the complete technical system of EPUB3.
โ ๏ธ Four of the seven parts in this series are scanned versions without a full searchable text, including Parts 4, 5, 6 and 7. Descriptions of these parts in this article are compiled from public domain knowledge; always refer to the official BSI published edition for authoritative clauses.
2. Series Composition ๐งฉ
| Part | Edition | Subject | Notes |
|---|---|---|---|
| PD ISO/IEC TS 30135-1 | 2014 | EPUB3 overview | Readable version |
| PD ISO/IEC TS 30135-2 | 2014 | Publications structure | Readable version |
| PD ISO/IEC TS 30135-3 | 2014 | Content documents | Readable version |
| PD ISO/IEC TS 30135-4 | 2014 | Open container format (OCF, ZIP packaging and metadata) | Scanned version |
| PD ISO/IEC TS 30135-5 | 2014 | Media overlays | Scanned version |
| PD ISO/IEC TS 30135-6 | 2014 | Fixed-layout related | Scanned version |
| PD ISO/IEC TS 30135-7 | 2014 | Multi-modal / additional presentation related | Scanned version |
3. Key Technical Requirements ๐ง
3.1 EPUB3 Overview โ Part 1
Part 1 (2014 edition) gives the overall overview of EPUB3, explaining its design goals, its relationship with Web technologies, the terminology system and reader conformance requirements, and how to read the following parts. It is the entry point of the series, helping developers understand EPUB3’s architecture, namespaces and conformance framework.
3.2 Publications and Content Documents โ Parts 2 and 3
Part 2 specifies the structure of an EPUB3 publication: OPF metadata (dc metadata, manifest, spine, guide, etc.), navigation documents and version identifiers. Part 3 specifies content documents: EPUB content documents (XHTML), SVG documents, and the embedding, referencing and namespace constraints of content documents, ensuring consistent presentation and accessibility in readers.
3.3 Open Container Format and Media Overlays โ Parts 4 and 5
Part 4 specifies the Open Container Format (OCF): packaging an EPUB as a ZIP container, defining the mimetype, META-INF container metadata, resource encryption (e.g., font obfuscation) and content-encryption mechanisms โ the storage and transport-level specification of an EPUB file. Part 5 defines Media Overlays, using SMIL to synchronise audio with text for “read-along” and text-to-speech synchronisation โ a key feature of EPUB3 for accessibility and enhanced reading.
โ
Implementation advice: when producing an EPUB, first fill in metadata and spine reading order correctly per Part 2, then organise content with compliant XHTML/SVG per Part 3; validate packaging (Part 4) and media overlays (Part 5) with reader conformance tools before release; handle complex scripts and mathematical formulae according to namespace and encoding rules.
4. Engineering Practice and Use Cases ๐ญ
- ๐ E-book publishing: publishers produce reflowable and fixed-layout e-books per EPUB3, balancing different screen sizes and reader consistency.
- ๐ค Accessible publishing: combine media overlays with accessibility semantics (ARIA) of content documents to provide read-aloud and navigation support for visually impaired readers.
- ๐ฑ Educational content: textbooks, question banks and interactive courseware use EPUB3’s multimedia and interactivity for rich media presentation.
- ๐ง Toolchain development: write validation scripts as a quality gate per the OCF and content-document specifications, preventing compatibility issues caused by packaging errors, illegal namespaces or missing metadata.
5. FAQ โ
โ Q: What is the essential difference between EPUB3 and PDF?
A: PDF is a “fixed print” layout suited to precise typesetting and printing; EPUB3 is a “reflowable” Web format in which text adapts to the screen, suiting readers, phones and accessibility scenarios, and supporting interactivity and media โ but complex layout control needs fixed-layout supplementation.
A: PDF is a “fixed print” layout suited to precise typesetting and printing; EPUB3 is a “reflowable” Web format in which text adapts to the screen, suiting readers, phones and accessibility scenarios, and supporting interactivity and media โ but complex layout control needs fixed-layout supplementation.
๐ Q: Why does EPUB3 need a dedicated “Open Container Format” (OCF) part?
A: An EPUB is essentially a ZIP package; without specifying the mimetype, META-INF and encryption rules, “EPUBs” produced by different tools may not be consistently recognised by readers. OCF standardises the container structure, resource encryption and storage details, ensuring file-level interoperability.
A: An EPUB is essentially a ZIP package; without specifying the mimetype, META-INF and encryption rules, “EPUBs” produced by different tools may not be consistently recognised by readers. OCF standardises the container structure, resource encryption and storage details, ensuring file-level interoperability.
โ Q: What are Media Overlays useful for?
A: They use SMIL to synchronise audio with text (or images) segment by segment, achieving “text highlighting + synchronised read-aloud” โ serving visually impaired readers’ accessibility needs, and also used in audiobooks, read-along and language learning scenarios. It is a key capability distinguishing EPUB3 from traditional e-books.
A: They use SMIL to synchronise audio with text (or images) segment by segment, achieving “text highlighting + synchronised read-aloud” โ serving visually impaired readers’ accessibility needs, and also used in audiobooks, read-along and language learning scenarios. It is a key capability distinguishing EPUB3 from traditional e-books.
๐ Q: Why was this series questioned editorially by the UK committee?
A: The UK committee accepted its technical soundness but had reservations about editorial issues such as term grouping, cross-references between parts and typographic layout, concerned it could hinder readers not involved in the standard’s development. Users should therefore combine W3C/IDPF official guidance and implementation experience rather than interpreting solely from the terminology tables.
A: The UK committee accepted its technical soundness but had reservations about editorial issues such as term grouping, cross-references between parts and typographic layout, concerned it could hinder readers not involved in the standard’s development. Users should therefore combine W3C/IDPF official guidance and implementation experience rather than interpreting solely from the terminology tables.