Re: Proposed charter change for the 'Why EPUB 4' issue

Just to be absolutely sure, and avoid further misunderstandings, is this a text we can agreed upon? I adopted Graham's changes on the original text and,  actually, I allowed myself to add one more adjective, in line with the earlier comments (in another issue) of Richard Ishida, our Internationalization guy on the team, namely accessibility (this is something he asked to add on other places as well). I have put in bold the two important parts of the text in this discussion:

[[[
<a href="https://www.w3.org/Submission/2017/SUBM-epub31-20170125/ <https://www.w3.org/Submission/2017/SUBM-epub31-20170125/>">EPUB</a> has become the fundamental technology for the global publishing ecosystem (see the <a href="https://w3c.github.io/dpubwg-charter/EPUB4_business_case.html <https://w3c.github.io/dpubwg-charter/EPUB4_business_case.html>">separate document</a>, published by the <a href="https://www.w3.org/community/publishingbg/ <https://www.w3.org/community/publishingbg/>">W3C Publishing Business Group</a>, for more details and backgrounds). It is the preferred format for a broad range of types of publications, not only for distribution but also for authoring and production workflows.  As part of the work on Web Publications, described in this charter, it is also critical that a next generation of EPUB, currently referred to as EPUB&nbsp;4, retain the specificity, portability, predictability, internationalization, and accessibility required by the publishing ecosystem while benefitting from the improved features and functionalities offered by Packaged Web Publications. EPUB&nbsp;4 must not be in conflict with Web Publications; it must be a type of Web Publication that provides the predictability and interoperability that this ecosystem has come to rely on.
]]

Ivan


> On 20 Mar 2017, at 07:41, AUDRAIN LUC <LAUDRAIN@hachette-livre.fr <mailto:LAUDRAIN@hachette-livre.fr>> wrote:
> 
> Hi,
> 
> I prefer original language and support Graham proposition about « particular mention of accessibility ».
> 
> Luc
> 
> De : Graham Bell <graham@editeur.org <mailto:graham@editeur.org>>
> Date : dimanche 19 mars 2017 22:59
> À : Leonard Rosenthol <lrosenth@adobe.com <mailto:lrosenth@adobe.com>>
> Cc : Ivan Herman <ivan@w3.org <mailto:ivan@w3.org>>, W3C Publishing Business Group <public-publishingbg@w3.org <mailto:public-publishingbg@w3.org>>, Bill Kasdorf <bkasdorf@apexcovantage.com <mailto:bkasdorf@apexcovantage.com>>, Liisa McCloy-Kelley <lmccloy-kelley@penguinrandomhouse.com <mailto:lmccloy-kelley@penguinrandomhouse.com>>, W3C Digital Publishing IG <public-digipub-ig@w3.org <mailto:public-digipub-ig@w3.org>>, W3C Publishing Steering Committee <public-publishing-sc@w3.org <mailto:public-publishing-sc@w3.org>>
> Objet : Re: Proposed charter change for the 'Why EPUB 4' issue
> Renvoyer - De : <public-digipub-ig@w3.org <mailto:public-digipub-ig@w3.org>>
> Renvoyer - Date : dimanche 19 mars 2017 23:00
> 
> All
> 
> I'm don't agree with these proposed changes. They have the effect of making it sound a little like accessibility is the only reason to choose EPUB.
> 
> It is THE preferred format for a broad range of types of doc (while not necessarily being preferred for some other types of doc). And this is true irrespective of their level of accessibility -- accessibility is one of several reasons to prefer EPUB, and some are even listed in the next sentence.
> 
> Now I do agree there should be particular mention of accessibility. So instead of moving accessible earlier in the sentence, I would suggest it's added to "specificity, portability, predictability and accessibility" instead.
> 
>>  It is the preferred format for a broad range of types of accessible publications, not only for distribution but also for authoring and production workflows, and for accessibility. As part of the work on Web Publications, described in this charter, it is also critical that a next generation of EPUB, currently referred to as EPUB&nbsp;4, retain the specificity, portability, and predictability required by the publishing ecosystem while benefitting from the improved features and functionalities offered by Packaged Web Publications. EPUB&nbsp;4 must not be in conflict with Web Publications; it must be a type of Web Publication that provides the predictability and interoperability that this ecosystem has come to rely on.
> 
> Graham Bell
> EDItEUR
> 
> Sent from my iPhone
> 
> On 19 Mar 2017, at 08:45, Leonard Rosenthol <lrosenth@adobe.com <mailto:lrosenth@adobe.com>> wrote:
> 
>> Proposed changes to the EPUB 4 text in the charter:  (changes inline in red, and called out individually following)
>> 
>> <a href="https://www.w3.org/Submission/2017/SUBM-epub31-20170125 <https://www.w3.org/Submission/2017/SUBM-epub31-20170125>/">EPUB</a> has become a fundamental technology for the global publishing ecosystem (see the <a href="https://w3c.github.io/dpubwg-charter/EPUB4_business_case.html <https://w3c.github.io/dpubwg-charter/EPUB4_business_case.html>">separate document</a>, published by the <a href="https://www.w3.org/community/publishingbg <https://www.w3.org/community/publishingbg>/">W3C Publishing Business Group</a>, for more details and backgrounds). It is a preferred format for a broad range of types of accessible publications, not only for distribution but also for authoring and production workflows, and for accessibility. As part of the work on Web Publications, described in this charter, it is also critical that a next generation of EPUB, currently referred to as EPUB&nbsp;4, retain the specificity, portability, and predictability required by the publishing ecosystem while benefitting from the improved features and functionalities offered by Packaged Web Publications. EPUB&nbsp;4 must not be in conflict with Web Publications; it must be a type of Web Publication that provides the predictability and interoperability that this ecosystem has come to rely on.
>> 
>> 1 – the -> a (since there are many preferred formats used in publishing depending on the context)
>> 2 – moved accessibility to be more primary in the description of publications (and make the sentence clearer)
>> 
>> 
>> Leonard
>> 
>> From: Ivan Herman <ivan@w3.org <mailto:ivan@w3.org>>
>> Date: Saturday, March 18, 2017 at 3:50 PM
>> To: W3C Publishing Business Group <public-publishingbg@w3.org <mailto:public-publishingbg@w3.org>>
>> Cc: Bill Kasdorf <bkasdorf@apexcovantage.com <mailto:bkasdorf@apexcovantage.com>>, Liisa McCloy-Kelley <lmccloy-kelley@penguinrandomhouse.com <mailto:lmccloy-kelley@penguinrandomhouse.com>>, W3C Digital Publishing IG <public-digipub-ig@w3.org <mailto:public-digipub-ig@w3.org>>, W3C Publishing Steering Committee <public-publishing-sc@w3.org <mailto:public-publishing-sc@w3.org>>
>> Subject: Proposed charter change for the 'Why EPUB 4' issue
>> Resent-From: <public-publishingbg@w3.org <mailto:public-publishingbg@w3.org>>
>> Resent-Date: Sat, 18 Mar 2017 15:50:33 +0000
>> 
>> Dear all,
>> 
>> as agreed on the F2F meeting in London, there is now a proposal to settle Issue #27[1]. BillK (with minor help from Liisa and I) has created a document on the business case of EPUB & EPUB 4[2], and a there is also a proposal for the charter text that contains a single paragraph and a reference to that document[3] (see the paragraph right before section 2.1).
>> 
>> These changes have not yet been incorporated into the 'main' charter (hence the funny URL-s [2] and [3]). Please either add your  comment to [1] or the "Pull request" issue[4]. If you want to propose specific editorial changes, that can also be done by using [5] or [6], respectively.
>> 
>> Thanks
>> 
>> Ivan
>> 
>> P.S. The link to the 'business case' in the proposed new charter paragraph does not work at this moment; it points to the place where the final document will be if and when this proposed change, a.k.a. 'pull request' is merged to the main branch.
>> 
>> 
>> [1] https://github.com/w3c/dpubwg-charter/issues/27 <https://github.com/w3c/dpubwg-charter/issues/27>
>> [2] https://rawgit.com/w3c/dpubwg-charter/bcase-draft/EPUB4_business_case.html <https://rawgit.com/w3c/dpubwg-charter/bcase-draft/EPUB4_business_case.html>
>> [3] https://rawgit.com/w3c/dpubwg-charter/bcase-draft/index.html <https://rawgit.com/w3c/dpubwg-charter/bcase-draft/index.html>
>> [4] https://github.com/w3c/dpubwg-charter/pull/41 <https://github.com/w3c/dpubwg-charter/pull/41>
>> [5] https://github.com/w3c/dpubwg-charter/blob/bcase-draft/EPUB4_business_case.html <https://github.com/w3c/dpubwg-charter/blob/bcase-draft/EPUB4_business_case.html>
>> [6] https://github.com/w3c/dpubwg-charter/blob/bcase-draft/index.html <https://github.com/w3c/dpubwg-charter/blob/bcase-draft/index.html>
>> 
>> ----
>> Ivan Herman, W3C
>> Publishing@W3C Technical Lead
>> Home: http://www.w3.org/People/Ivan/ <http://www.w3.org/People/Ivan/>
>> mobile: +31-641044153
>> ORCID ID: http://orcid.org/0000-0003-0782-2704 <http://orcid.org/0000-0003-0782-2704>

----
Ivan Herman, W3C
Publishing@W3C Technical Lead
Home: http://www.w3.org/People/Ivan/ <http://www.w3.org/People/Ivan/>
mobile: +31-641044153
ORCID ID: http://orcid.org/0000-0003-0782-2704 <http://orcid.org/0000-0003-0782-2704>

Received on Monday, 20 March 2017 07:16:27 UTC