EPUB 3.2 as a W3C Recommendation: Plusss and concerns

At the beginning of today's PBG Teleconference, Luc provided an 
articulate description of a case to take EPUB 3.2 to W3C Recommendation 
status [1].

It sounded good to me, but it also sounded like various people had 
various concerns.  I assembled what I heard as 7 concerns into a list, 
and Luc asked me to compile that list into an email.

Here is what I came up with:

1. Feature interoperability.  There have been many emails about this. 
Many of the emails have been to clarify that W3C generally seeks two 
interoperable implementations of every feature (not two totally 
interoperable solutions).  There are many emails about this, but a good 
place to start is [2].

2. Roadmap.  Making sure we understand the business vision behind the 
entire EPUB roadmap [3].

3. Which group has responsibility for what [4]?

4. Ensuring we have good interaction and review with the TAG. That arose 
in discussion on today's call, but is also referenced in [3,4].

5. Where will we get sufficient resources for all the work that needs to 
be done?  That arose on the call, I believe from Tzviya.

6. What is the business case for each individual activity? Mentioned in 
the call; also in [4].

7. How are EPUB 3.2, audiopub, and EPUB 4 positioned against each 
other?  What is the technology evolution plan?  What is the market 
adoption plan?  What time frames make sense?

On the call, I offered that a good approach might be to go beyond the 
"general concept" of an EPUB 3.2 REC, and instead develop a "specific 
plan" for an EPUB 3.2 REC which also addressed these questions.  It 
sounded like several people on the call, led by Liisa, were signing up 
for that.

HTH.  Glad to discuss more if people like.

Jeff

[1] https://www.w3.org/2018/11/06-pbg-minutes.html

[2] 
https://lists.w3.org/Archives/Public/public-publishingbg/2018Oct/0030.html

[3] 
https://lists.w3.org/Archives/Public/public-publishingbg/2018Nov/0022.html

[4] 
https://lists.w3.org/Archives/Public/public-publishingbg/2018Nov/0021.html

Received on Tuesday, 6 November 2018 18:59:38 UTC