EPUB Extension Deprecation Survey
The EPUB Working Group is currently considering ways to better align with the Open Web Platform (OWP), including introducing support for the non-XML serialization of HTML5.

Among the constructs defined in EPUB, however, are four extensions that extend the rendering capabilities of the OWP: switches, triggers, bindings and manifest fallbacks. A fifth, canonical fragment idenfitiers (epubcfi), enables linking within the EPUB zip container.

In addition to not working natively on the OWP, many existing EPUB 3 reading systems still do not support these extensions (see www.epubtest.org).

Therefore, to help determine their continued support, we would appreciate your time to complete the following short survey on your use of them.

The deadline for submitting responses to this survey is December 15, 2015.

For more information about the EPUB 3.1 revision, please see the workplan (http://www.idpf.org/workplans/2015/epub/) and the minutes from the recent New York face-to-face meetings (https://goo.gl/45V6DS).

NOTE: Please complete this survey only if you are a content producer.

Sign in to Google to save your progress. Learn more
1. Do you currently use the switch element? *
The switch element (http://goo.gl/0r3utK) is intended to allow content to be conditionally displayed in content documents, with a fallback option that will always render (often used for mathml).
1.1. If you answered "Yes" to Question 1, what do you use switch for:
1.2. If you answered "No" to Question 1, please indicate the reason(s) why:
2. Do you currently use the trigger element? *
The trigger element (http://goo.gl/jybf5Q) is intended to allow control of audio/video playback without the need for scripting.
2.1. If you answered "Yes" to Question 2, which do you use triggers to control:
2.2. If you answered "No" to Question 2, please indicate the reason(s) why:
3. Do you currently use the bindings element? *
Bindings (http://goo.gl/Sme7Pc) are intended to provide a manifest-level fallback to a scripted content document for unsupported media types.
3.1. If you answered "Yes" to Question 3, what media types are you using bindings with:
3.2. If you answered "No" to Question 3, please indicate the reason(s) why:
4. Do you currently use manifest fallbacks? *
Manifest fallbacks (http://goo.gl/LQnLoK) are intended to provide fallbacks for foreign resources used in the spine (e.g., jpegs).
4.1. If you answered "Yes" to Question 4, which of the following do you use manifest fallbacks for:
4.2. If you answered "No" to Question 4, please indicate the reason(s) why:
5. Do you currently use epubcfi for hyperlinking in content documents? *
Note that the working group is only looking at deprecating eubcfi (http://goo.gl/bKRR5Q) within content documents. All other uses for linking into an EPUB, such as for attaching annotations in the Open Annotation in EPUB specification, will remain valid.
6. Are you planning to start using any of the following?
7. Are any of the following critical to your operations?
7.1. If you indicated any of the options in Question 6 are critical, please briefly explain why.
Additional Comments
Please provide any additional comments you have about these features here.
Name *
Affiliation *
Role *
Email *
Your email address will not be published or shared.
Submit
Clear form
Never submit passwords through Google Forms.
This content is neither created nor endorsed by Google. Report Abuse - Terms of Service - Privacy Policy
Google Forms