14:46:01 RRSAgent has joined #pbg 14:46:01 logging to https://www.w3.org/2018/10/09-pbg-irc 14:46:06 Zakim has joined #pbg 14:46:18 Meeting: Publishing Business Group Telecon 14:46:24 Date: 2018-10-09 14:46:51 Chair: Liisa McCloy-Kelley 15:07:06 ivan has joined #pbg 15:22:09 wolfgang has joined #pbg 15:27:28 rrsagent, set log public 15:27:28 Meeting: Publishing Business Group Telco 15:27:28 Chair: liisamk 15:27:28 Date: 2018-10-09 15:27:28 Regrets+ Brian, Luc, Jens, junko_kamata 15:27:28 Agenda: https://lists.w3.org/Archives/Public/public-publishingbg/2018Oct/0004.html 15:27:29 ivan has changed the topic to: Meeting Agenda 2018-10-09: https://lists.w3.org/Archives/Public/public-publishingbg/2018Oct/0004.html 15:54:38 Ralph has joined #pbg 15:59:35 ivan_ has joined #pbg 16:00:10 Avneesh has joined #pbg 16:01:55 MURATA has joined #pbg 16:02:20 Me too. 16:02:35 i just started the meeting 16:02:42 present+ 16:02:51 present+ Karen 16:02:56 present+ 16:03:09 present+ RalphS 16:03:14 present+ wolfgang 16:03:17 rkwright has joined #pbg 16:03:50 present+ 16:03:50 present+ 16:03:57 jeff_ has joined #pbg 16:04:24 present+ jeff 16:04:36 liisamk has joined #pbg 16:04:57 present+ 16:05:05 Bill_Kasdorf has joined #pbg 16:05:14 present+ 16:05:37 scribenick: rkwright 16:05:53 Dan_Sanicola has joined #pbg 16:05:59 Topic: CG EPUB3.2 16:06:02 present+ 16:06:04 present+ 16:06:23 dauwhe: Community group has officially approved the spec and is requesting the business group to approve. 16:06:28 present+ 16:06:45 ... 3.2 is backwards compatible, has been reformatted to be clearer 16:07:10 ... updated the conformation to external specs, such as SVG, etc. 16:07:27 ... so users of 3.0.1 shouldn't have to change their workflows. 16:07:41 George has joined #pbg 16:07:53 ... How do we present this to the world? EPUBCheck needs to be updated, for example. 16:08:09 present+ Mateus_Teixeira 16:08:16 present+ George 16:08:22 ... So we would prefer to reserve the announcement until all our ducks are in a row? 16:08:49 +q 16:08:49 q+ 16:09:01 present+ makoto 16:09:13 liisa: Foes the BG need to use a particular process? 16:09:34 s/Foes/Does/ 16:09:41 ack mur 16:10:11 murata: We did add some features for Japanese support. Do we know that reading systems will support it? 16:10:20 q+ 16:10:31 ack Bill_Kasdorf 16:10:59 Bill_Kasdorf: What is being asked is approval but not necessarily action outside the group? 16:11:00 Julian_Calderazi has joined #pbg 16:11:00 What I said: We published 3.0.1, but was ignored by Apple. 16:11:05 present+ 16:11:09 I do not want to repeat the same experience. 16:11:13 Little late. Sorry 16:11:48 I might be overworried. But we had a bad experience. 16:11:52 dauwhe: We did have active participation from some of the RS (e.g. Microsoft and Google) so it is not obvious why RS WOULDN'T support it 16:11:53 q+ 16:11:57 ack dauwhe 16:12:01 ack dauwhe 16:12:42 Sounds great to me. 16:12:48 liisamk: If we, the BG, bless the proposed spec and then reach out to the RS to get their support. 16:12:52 q+ 16:13:36 ivan: This makes sense, but why, for example, did Apple did not support 3.0.1 16:13:42 https://github.com/w3c/publ-epub-revision/issues/974 16:14:09 murata: But apple refused to support the reserved prefixes (see issue above) 16:14:59 ack iv 16:15:04 +1 tzviya 16:15:49 George: I agree with the recommendation and if we were a real WG, what would be our next step? Validation that at least two RS support 3.2 16:15:53 q+ 16:16:17 ack ge 16:16:38 ack dauwhe 16:17:00 dauwhe: EPUB's status has been complicated by the merger. There is a lot of value in a rigorously qualified spec. 16:17:25 I'm not requesting a test suite. 16:17:28 ... But we are NOT a WG and in the W3C this is not the purview of the CG 16:17:32 q+ 16:17:42 present+ tzviya 16:18:12 tzviya: Testing is a good idea but there is some concern about one specific vendor, i.e. Apple Have we talked to them? 16:18:40 dauwhe: These are not great big problems in the grand scheme of things. 16:18:55 ack tz 16:18:57 ... It would be good to get Apple's view on these things but... 16:19:18 tzviya: Agreed. This is valuable but not essential. 16:19:40 murata: So when do we publish and get testimonials 16:20:06 dauwhe: We publish THEN get testimonials 16:20:29 liisamk: I believe we should wait until it is a bit more 16:20:31 q+ 16:21:28 rkwright: I am the only reading system vendor on this call is, what is exacctly what you are asking from us. Without a test suite it is difficult to prove that we are conforming to the spec 16:21:52 s/exacctly/exactly/ 16:22:15 dauwhe: We need to exercise the differences between 3.0.1 and 3.2 16:22:16 ack rkwright 16:22:36 q+ 16:22:38 q+ 16:23:14 rkwright: i have a quick quesiton, I agree with dave, but is there a formal document that goes and lists the differences? 16:23:20 ack rkwright 16:23:22 https://w3c.github.io/publ-epub-revision/epub32/spec/epub-changes.html 16:23:29 s/quesiton/question/ 16:23:33 ack ivan 16:23:39 q+ 16:23:49 rkwright: Is there a formal doc for the differences between 3.0.1 and 3.2? 16:23:51 charter says 5 days email vote 16:23:59 dauwhe: yes, I will supply link 16:24:02 q+ 16:24:07 ack dauwhe 16:24:45 dauwhe: So we need to set up a formal 5-day vote 16:24:58 Bill_Kasdorf: What is the process? SImple majority? 16:25:22 q+ 16:25:28 Ralph: It is a call consensus 16:25:38 ack bill_ 16:25:47 ack dauwhe 16:25:50 liisamk: So we should start an email process to drive this? 16:26:24 dauwhe: Is it correct that the BG is waiting for the RS to weigh in ? Or what? 16:26:36 q+ 16:26:45 ack ivan 16:27:34 ivan: I think it is fine if we do these actions in parallel, i.e. we ask the RS to give their opinion, but at the same time the BG can continue with their processes 16:27:52 q+ 16:27:59 ack Avn 16:28:22 avneesh: Would 5 days be enough for RS? 16:28:30 +1 to ivan and avneesh 16:28:35 +1 for 2 weeks 16:28:36 q+ 16:28:40 +1 16:28:41 +1 to two weeks 16:29:07 Ivan: How about 2 weeks for the RS to give feedback 16:29:09 ack tzviya 16:29:18 q+ 16:29:36 Just wondering. Can we expect this window of time to be enough for RS? 16:29:52 rkwright: When would the bell sound on this two weeks? 16:30:18 liisamk: How about we start at the end of this week, i.e Friday 12 October? 16:30:19 +1 16:30:23 deadline on 26th right? 16:30:26 +1 16:30:59 George: Do we also want to ask for testimonials ? 16:31:13 liisamk: Yes, that would be good. 16:31:40 dauwhe: Is the timeline the same for testimonials? 16:32:01 topic: epubcheck 16:32:02 liisamk: We will always accept testimonials. 16:32:59 Tzviya: EPUBCheck work has begun. DAISY is starting to look at the code base. Luc and Tzviya will set up a regular meeting with DAISY to track the work 16:33:28 ... Logistical work will begin soon (moving repos from IDPF to W3C, for example) 16:33:41 https://www.w3.org/blog/2018/10/epubcheck-fundraising/ 16:34:03 ... alpha of the EPUB 3.2 support should be ready in November, with final release circa March 2019 16:34:12 ... Still looking for funding! 16:34:39 topic: bg and wg together at TPAC 16:34:44 https://docs.google.com/document/d/1Mt9PTcOdmrCwIsgfxbGMGjwHlUsySU01I0D4oBkSbcA/edit?usp=sharing 16:34:52 q+ 16:34:54 q+ 16:35:49 ack ge 16:36:06 George: Question of nomenclature. We have been using "EPUB 3" but do we need to be more explicit in our discussions, etc? 16:37:13 ivan: As WG member, I would like to know is what we do at the WG of interest to the various participants in the BG? 16:37:27 +1 to ivan_ 16:37:35 ... It would be very good if this point could be addressed at our discussions at TPAC 16:37:36 ack ivan 16:37:36 ack ivan_ 16:39:01 jeff_: Dave mentioned that EPUB status has been complicated by the merger. If so, it would be a worthwhile discussion at TPAC to explore what it means to be "complicated". 16:39:24 q+ 16:39:34 ack jeff_ 16:39:38 liisamk: Agreed. This also relates to George's point about nomenclature. 16:39:42 q+ 16:40:12 ack dauwhe 16:40:33 dauwhe: Agreed, good topic for TPAC but it also raises the largerr issue of how does EPUB fit into the W3C and web-publishing. 16:40:46 q+ 16:40:51 ... Many meaty questions there that are worth discussing 16:40:59 ack tzviya 16:41:34 tzviya: In planning for TPAC, we have explicitly tried to cover this in the agenda 16:41:55 ... So hopefully we will be able to come up with a cohesive vision. 16:41:56 q+ 16:42:03 ack jeff_ 16:42:26 s/largerr/larger/ 16:42:32 jeff_: Agreed that these are the right questions and discussion to have. 16:43:06 dauwhe: I will volunteer to try and drive this as Tzviya is pretty busy at TPAC 16:43:26 ack lii 16:43:38 liisamk: How do we we ensure that we are building the right tools and processes? 16:43:38 q+ 16:43:40 +1 Liisa's comments 16:45:10 ack je 16:45:15 jeff_: We are looking for a new champion to drive this general area. We have interviewed two people but are still looking for our champion. 16:45:36 topic: conference collection 16:46:12 liisamk: We have started work on this set of information for people on the BG 16:46:40 https://docs.google.com/spreadsheets/d/1W_WWvwV93Cwx_hFTmeDQ2bBFW_Qn1j2duVJT1e3Wxfc/edit#gid=0 16:46:44 topic: math and ebooks 16:46:54 q+ 16:47:12 q+ 16:47:28 dauwhe: There has been a fair amount of work on this topic, notably by Benetech 16:47:55 q+ 16:48:02 ... It seems like the direction we are heading is that there are multiple specialized markups that need to be implemented 16:48:02 ack dauwhe 16:48:07 ack tzviya 16:48:10 sorry! 16:48:27 q+ 16:48:33 ... One approach is to use some form of polyfills using SVG, but there isn't a lot of interest in doing so. 16:49:11 ... It may be that there is NOT one single, all-encompassing solution 16:49:35 ... We need someone who is willing to track this. 16:50:33 q+ 16:50:35 +1 to "we need to solve this for the Web" 16:50:37 ack George 16:50:44 ack tzviya 16:50:44 ack tzviya 16:50:47 tzviya: This problem is not unique to EPUB. We need to recognize this and broaden our view 16:51:00 +1 16:51:34 George: Support what Tzviya said. We do have a test book for Math that allows one to pass the MathML to an assistive technology 16:51:52 The test book: http://epubtest.org/epubs/epub30-test-0330-20180905.epub 16:52:03 ... It is not a complete solution but is a start. 16:52:54 ... A solution based on SVG that transforms from MathML to SVG to allow accessibility would be great, but it doesn't currently exist. 16:53:29 Sorry I'm with a neumatic hammer very close to me. could you write? 16:53:34 (...) 16:54:04 kinda complicated to listen to you guys 16:54:16 is there anything you want to add to the conversation about methyl? 16:54:19 math ML 16:54:41 Ho. yes. we have to keep in mind we will need to take this as a serious issue as regards to 'EPUB for education' 16:54:41 s/methyl/MathML/ 16:54:47 q? 16:54:50 ack ivan 16:55:41 ivan: MathML is only one of dialects that we need to be aware. And it is unreasonable to expect the browsers to do this. 16:56:43 ... Alternatively, we end up relying on these "ML-polyfills" so it is incumbent on this group to work with those groups and help them improve their support 16:57:35 ... Where the W3C could help would be to help guide these polyfiller groups understand the problem space and how to solve it. 16:57:40 +1 to ivan 16:58:27 +1 to Ivan too 16:58:32 q+ 16:58:35 George: There is some SVG work that has been ongoing in this area. 16:58:38 ack avn 16:58:42 Is there a link to the SVG work? 16:59:36 https://www.w3.org/Graphics/SVG/WG/wiki/Main_Page 16:59:38 avneesh: IN the ISO task force call that happened yesterday, does someone want to share that information with this group 17:00:45 ... One of the concerns of the ISO group is that they are not clear on how it relates to W3C efforts? 17:01:46 ... Also some concern about how some of these conflicts and how they get resolved. Plus, what is the timeline for these efforts? 17:02:51 rrsagent, draft minutes 17:02:51 I have made the request to generate https://www.w3.org/2018/10/09-pbg-minutes.html ivan_ 17:02:51 zakim, bye 17:02:51 rrsagent, bye 17:02:51 I see no action items 17:02:51 leaving. As of this point the attendees have been tzviya, Karen, dauwhe, RalphS, wolfgang, rkwright, ivan_, jeff, liisamk, Bill_Kasdorf, Dan_Sanicola, Avneesh, Mateus_Teixeira, 17:02:51 Zakim has left #pbg 17:02:54 ... George, makoto, Julian_Calderazi