27
Bill Kasdorf VP and Principal Consultant, Apex Content Solutions Member of IDPF Board, EPUB 3 WG, W3C DPUB IG The Evolution of EPUB What’s New and What’s On the Horizon

The Evolution of EPUB

Embed Size (px)

Citation preview

Bill KasdorfVP and Principal Consultant, Apex Content Solutions Member of IDPF Board, EPUB 3 WG, W3C DPUB IG

The Evolution of EPUBWhat’s New and What’s On the Horizon

EPUB

1. The Continuing Evolution of EPUB.

EPUB 3 has become essential to the publishing ecosystem

E-Readers It’s the “master format” for virtually all systems

EPUB 3 has become essential to the publishing ecosystem

E-Readers It’s the “master format” for virtually all systems

Accessibility It’s the format for interchange of accessible content

EPUB 3 has become essential to the publishing ecosystem

E-Readers It’s the “master format” for virtually all systems

Accessibility It’s the format for interchange of accessible content

Education Platforms are built on the EPUB for Education profile

EPUB 3 has become essential to the publishing ecosystem

E-Readers It’s the “master format” for virtually all systems

Accessibility It’s the format for interchange of accessible content

Education Platforms are built on the EPUB for Education profile

Not Just Books It’s used for all kinds of publications

EPUB 3 has become essential to the publishing ecosystem

E-Readers It’s the “master format” for virtually all systems

Accessibility It’s the format for interchange of accessible content

Education Platforms are built on the EPUB for Education profile

Not Just Books It’s used for all kinds of publications

Global Widely adopted in US, EU, Far East, Israel

Time for a checkup:Developing EPUB 3.1

Interesting Spec Development Issue

Be aggressive and strict?

Or be peaceable, accommodating?

We gotta get rid of the NCX!

We can’t get rid of the NCX!

Minimize the metadata!

Hey, wait, not so

fast!

HTML & JSON rule!

Don’t take away my

XML!

We took the cautious route.

Tightens up EPUB 3 without breaking it.New spec format, better integrated

Deprecates unused features of EPUB 3.0Clarifies/extends support for remote resources

(e.g., metadata, fonts, datasets)Improves CSS behavior between author/RS/user

Improved and stricter accessibility supportFinal Notice Period (IP Review) thru Nov. 28;

Should be official by year end.

EPUB 3.1

Better alignment with OWPUndated references to HTML & SVG to stay in synch

No EPUB CSS profile; uses CSS WG “official definition”Some metadata improvements

Prioritizes linked bibliographic metadata recordsDeprecates refines attribute and adds

more explicit attributes for specific functionalityFinal notice on NCX

Slated for removal in next major revision of EPUB

EPUB 3.1

Separate spec devoted to accessibilityClear guidelines to enable certification of accessibility

and discovery of accessible features in an EPUBBased on WCAG 2.0: A is must, AA is recommended

Adds publication-specific requirementsRequires accessibility-specific metadata

Techniques document provides “how to do it” adviceApplicable and referenceable by

any version of EPUB and other specs too

EPUB Accessibility 1.0

Categories of compliance“Discovery-Enabled”: Just metadata

“Accessible”: MD + WCAG 2.0 + EPUB requirements“Optimized”: Metadata + specific features

Metadata aligned with schema.orgaccessMode (textual, visual, auditory, tactile)

accessibilityFeature (what features does it have)accessibilityHazard (e.g., flashing can cause seizures)accessibilitySummary (human-readable explanation)

accessModeSufficient (e.g. text + alt text = textual)

EPUB Accessibility 1.0

W3C

2. Meanwhile, work goes on to improve the Open Web Platform for publishing.

Digital Publishing Interest Group (DPIG)Active work with CSS Working Group

to improve typography and layout using CSSDigital Publishing Accessibility Note documents what

publishing needs from the W3C (May 2016)Digital Publishing WAI-ARIA Module 1.0 proposes

publishing-specific terms for ARIA (Wkg Draft 3/17/16)

schema.orgAdditions to schema.org for accessibility metadata

Improving the OWP for Publishing

Wouldn’t it be great if there was no difference between

an online publication and an EPUB?

Wouldn’t it be great if there was no difference between

an online publication and an EPUB?

We’re working on it.It’s called PWP:

Portable Web Publication.

PWP

Progress on the EPUB+Web convergence.

The Portable Web Publication Vision:ONE PUBLICATION FOR BOTH

ONLINE AND OFFLINE USE.The same content in two different “states”:

Offline, packaged or cached;Online, with all essential resources linked.

A canonical URL that leads to both.

(P)WP

Recent Realization:First we need to define a Web Publication!

Meaning an arbitrarily extensive and complex collection of resources on the web

(web pages, CSS, fonts, images, media, scripts, etc.)that has an identity, that can be referenced, etc.Whether/how it’s packaged is a separate issue.

EPUB 4 vs. PWPWe want to avoid two competing specs.

These need to be the same thing.Could be one master spec,

or a layered spec with “profiles”:e.g., PWP as a profile of a WP (a type of WP),

and “EPUB 4” in turn as a profile of PWP (like EPUB for Education is for EPUB),

a type of PWP requiring more predictability, accessibility, archivability.

The proposed IDPF+W3C is designed to facilitate and optimize this.

The proposed W3C Publishing Business Group, its Steering Committee, and an expected Working Group

will ensure publishing industry participation in this.EPUB 3 will continue to be maintained

as the work on EPUB 4 / PWP goes forward. IDPF Primary Reps are currently voting on this.

The IDPF Board strongly recommends that it be approved.

Thanks!

Bill [email protected]

+1 734 904 6252@BillKasdorf