23:48:27 RRSAgent has joined #epub 23:48:27 logging to https://www.w3.org/2020/10/15-epub-irc 23:48:37 rrsagent: start meeting 23:48:37 I'm logging. I don't understand 'start meeting', dauwhe. Try /msg RRSAgent help 23:48:57 rrsagent, help 23:50:01 Zakim has joined #epub 23:50:09 Meeting: EPUB 3 Working Group Telecon 23:50:24 Date: 2020-10-15 23:51:19 RRSAgent: make logs public 23:51:56 present+ 23:56:14 jyoshii has joined #epub 23:59:09 MasakazuKitahara has joined #epub 23:59:25 Yanni has joined #epub 23:59:34 LauraB__ has joined #epub 23:59:41 MattChan has joined #epub 00:00:09 toshiakikoike has joined #epub 00:00:15 present+ 00:00:17 present+ 00:00:19 present+ 00:00:26 present+ 00:01:06 present+ 00:01:14 Teenya has joined #epub 00:01:28 present+ 00:02:23 Chairs: Wendy Reid, Shinya Takami 00:02:25 marisa has joined #epub 00:02:30 duga has joined #epub 00:02:37 scribe+ dauwhe 00:02:38 present+ 00:03:00 present+ 00:03:36 present+ 00:04:03 wendyreid: if you are able to scribe, please let me know. 00:04:12 ... we need to equitably share the work 00:04:25 ... anyone new this week? 00:04:28 ShinyaTakami has joined #epub 00:04:46 ... we've talked a lot about media types 00:04:51 present+ 00:04:54 ... we'll talk about a few other media types today 00:05:05 BenSchroeter has joined #epub 00:05:09 ... it would be good to have for criteria for adding new media types 00:05:14 ... we've done this accidentally 00:05:23 present+ 00:05:28 ... we want broad support across all major browsers 00:05:33 present+ 00:05:36 ... we want a strong use case from the publishing industry 00:06:04 ... we mentioned this in one of Matt's pull requests 00:06:20 https://github.com/w3c/publ-epub-revision/pull/1345 00:06:48 q? 00:06:50 ... what should the criteria be for adding new media types? What are our requirements? 00:06:59 q+ 00:07:08 ack dauwhe 00:07:11 scribe+ 00:07:12 q+ 00:07:33 dauwhe: It's straightforward to say a media-type is supported by all major browsers and operating systems 00:07:41 ... and the promise of being supported by all major reading systems 00:07:59 ... query RS developers from around the world on their thoughts 00:08:01 q- 00:08:09 ... universality and support is important 00:08:43 zhengxu: I was going to ask... what is the benefit for a core media type? 00:08:50 ... I raised the question in epubcheck 00:09:02 ... making it easy to load something in OPF 00:09:07 q+ 00:09:18 ... what is purpose of core media type? 00:09:30 q+ 00:09:32 ... if a RS is using a browser engine, the media type is decided by browser. 00:09:34 q- 00:09:40 ... browsers don't define that 00:09:54 ... but some reading systems are not based on web browsers 00:10:04 ... I don't quite understand if this is necessary for us to define 00:10:08 ack shiestyle 00:10:30 shiestyle: (speaking in Japanese) 00:11:45 toshiakikoike: (speaking in Japanese) 00:12:10 shiestyle: I asked about RS in Japan 00:12:28 ... toshiakikoike said, their RS converts EPUB files in advance to deliver browser view 00:12:38 ... adding core media types is not a big issue 00:13:11 Yes 00:13:14 wendyreid: as long as we meet the criteria that it is supported (or almost supported) by all major browsers and operating systems 00:13:44 ... we'll talk about WebP, which is supported everywhere but versions of MacOS before the most recent 00:14:01 ... they have to be quite well supported at the time 00:14:05 ... we will have to test, of course 00:14:18 ... reading systems would need to commit to support, and we'd see that in testing 00:14:43 https://github.com/w3c/publ-epub-revision/issues/1344 00:14:45 wendyreid: the two issues... one is logged a couple days ago 00:14:50 https://github.com/w3c/publ-epub-revision/issues/1299 00:15:07 Topic: 1344, WebP as CMT 00:15:16 wendyreid: caniuse looks good 00:15:43 ... supported in Big Sur, which is out soon (?) 00:15:56 ... the argument is a more efficient image format 00:16:10 ... DeMarque feels it significantly reduces the overall size of their EPUBs 00:16:13 ... which is good 00:16:49 ... the other possible CMT is VTT, 00:17:04 ... used for video captions 00:17:08 q? 00:17:15 q+ 00:17:38 q+ 00:17:38 ack marisa 00:17:46 marisa: if we had web vtt as a core type 00:17:55 wendyreid: it's text vtt 00:17:56 q+ 00:18:04 marisa: does it accompany the video? 00:18:17 wendyreid: the mystery is how we refer to videos; we don't have a CMT for video 00:18:31 ... it would accompany whatever video format you were using 00:18:57 q+ to distinguish core media types from EPUB content documents 00:19:00 ack shiestyle 00:19:08 shiestyle: (speaks in Japanese) 00:20:28 ack duga 00:20:34 q+ 00:20:39 ... I discussed both of these with Mr. Koike... we don't know what impact they would have on RSs 00:20:48 q- 00:20:51 duga: Matt seems to think a fallback isn't needed in this case? 00:21:02 ... since VTT is itself a fallback for the track element? 00:21:20 ... do we really need to do anything other than clarifying the manifest section 00:21:25 wendyreid: that's a task on it's own 00:21:31 duga: that's why we have matt :) 00:21:42 ... you don't need a fallback for a foreign resource in this case 00:21:52 ... so it might make it confusing to have it as a CMT 00:21:58 ack dauwhe 00:21:58 dauwhe, you wanted to distinguish core media types from EPUB content documents 00:22:20 dauwhe: This is the perfect opportunity to mention that CMT doesn't mean that something can be a spine item 00:22:35 ... Content Docs can be spine items, but CMTs mean they don't need a fallback 00:22:51 ... a RS would be assured of finding something to display 00:23:04 q+ 00:23:11 ack duga 00:23:22 duga: that's a good point, but you could put vtt in an object tag :) 00:23:34 ... the real problem is, if we required a fallback for VTT, there isn't one. 00:23:51 ... so you couldn't use VTT. There's not a format that would work instead. You can't replace it with HTML. 00:24:02 ... I'm assuming it has time-based features. 00:24:21 ... if it does require a fallback, we should make it a CMT. If it doesn't require a fallback, there's no point. 00:24:25 q? 00:24:29 q+ 00:24:30 q+ 00:24:33 duga: thumbs up to WebP 00:24:37 ack shiestyle 00:24:56 shiestyle: how about adding 2nd-priority CMT 00:25:09 ... maybe JPEG/PNG is already popular 00:25:23 ... webp and opus are new technologies, maybe there should be fallbacks 00:25:24 q+ 00:25:29 ack zhengxu 00:25:53 zhengxu: If a CMT can be a spine item... 00:26:10 ... what is the core media type we wanted to define to have benefit for end user 00:26:24 ... we can use it as content doc without fallback 00:26:56 ... if CMT does not have this purpose, even some mimetype can be used as CMT but can't be put in spine item 00:27:07 ... how do we use this scope? 00:27:18 ... like web browser we have caniuse 00:27:27 ... if we have something like caniuse for reading systems 00:28:02 ... but if some reading system can't support webp, it's a reading system problem 00:28:27 ... we need to draw a line for CMT to ask creator to add fallback 00:28:35 ... it's still a question for me 00:28:39 wendyreid: it's a fair question 00:28:45 ... having tests will help 00:29:19 ... as we discussed earlier, do we throw away the idea of CMT, and the consensus was we didn't want to do that. 00:29:37 ... this puts a lot of pressure on content creators, and leads to interop problems. 00:29:41 ack duga 00:29:52 duga: re: fallbacks for webp and opus 00:30:02 ... defeats the whole purpose, which is to make your EPUB smaller 00:30:19 ... so that's why you want to extend CMTs 00:30:24 ... a size benefit 00:30:45 ... we can add to our list of reasons: Is there a benefit you cannot achieve with existing core media types 00:30:58 ... the answer for both WebP and Opus is that they are smaller. 00:31:07 ... we have opened things up, it was called FXL 00:31:35 ... we have insane hacks that downloads Times New Roman so that it can match fruit company's rendering 00:31:52 ... free-form content makes it hard to support lots of things 00:32:06 ... we also don't have enough people to make caniuse for epub work 00:32:07 q? 00:32:09 q+ 00:32:09 q+ 00:32:14 ack zhengxu 00:32:31 zhengxu: caniuse for RS... I know it would take a while 00:32:36 q+ 00:32:38 ... they have more content creators 00:32:45 ... we have smaller scope of user 00:33:01 ... say user wanted to use some type of... do whatever you want 00:33:12 ... use any font, but it might break FXL... sure 00:33:29 ... if we can define certain type... with web browsers people only test in 3 browsers 00:33:35 ... for reading systems it's the same 00:33:47 ... we have too many types of reading systems 00:34:04 ... as RS creator, if we cannot support it, we can put our support status in caniuse 00:34:15 ... it 00:34:26 ... it's kindof more use-case driven 00:34:31 ... if we draw a line here, 00:34:39 ... how can create a fallback for it? 00:34:49 ... this fallback blocks creator from using this feature 00:35:09 ... it's not possible to create fallback 00:35:16 ... I think purpose of creator and spec and RS 00:35:26 ... expand it, let it be more easy to use 00:35:42 ack dauwhe 00:36:01 dauwhe: I would just remind everyone we tried to do caniuse for EPUB and it failed epically 00:36:17 ... there's a handful of major browsers, and hundreds of reading systems 00:36:32 ... which all behave differently on different platforms 00:36:39 ... the vounteers could never keep up 00:36:59 ... we failed at trying to keep up with it and maintain 00:37:11 q+ 00:37:16 ... we need more marisas 00:37:19 ack marisa 00:37:22 marisa: you took the words out of my mouth 00:37:27 ... I developed the site 00:37:33 ... keeping it up to date was not possible 00:37:43 ... we relied on volunteer testers; the tests were not automated 00:37:52 ... even though we had some provisions to make it easier 00:38:05 ... the rate at which reading systems were changing required too much retesting 00:38:16 https://daisy.github.io/old-epub3-support-grid/features/ 00:38:20 ... a couple of months ago, BISG asked me to put the static site back 00:38:24 ... i've put it back 00:38:31 ... link ^^^ 00:38:39 ... this only scratches the surface 00:38:59 ... but this is what we tried to do for caniuse for epub 00:39:03 ack zhengxu 00:39:11 zhengxu: I understand; I respect the amount of work required 00:39:30 ... two things 00:39:37 ... one, in terms of caniuse or test 00:39:46 ... if it needed to be maintained by each RS 00:40:06 ... publishers would know how to create content for a RS 00:40:23 ... we might have more than a hundred reading systems. No 3rd party can do that. 00:40:42 ... webp... based on the current track, it's hard to add more to CMT 00:40:49 ... what is benefit of having this CMT? 00:41:04 ... we have spec, we have 3.3 that defines that webp must be CMT 00:41:13 ... but we have a RS that does not support this 00:41:16 ... that is a problem 00:41:33 wendyreid: we have to get back to the core of the core of the talk about core media types 00:41:43 ... it sounds like we have consensus on criteria 00:41:59 ... they need overwhelming support by browsers and operating systems, with a path to completion 00:42:11 ... and they need a direct benefit to content creators and/or reading systems 00:42:42 ... based on those criteria, let's start with WebP 00:42:46 ... I'll put in a proposal 00:42:53 Proposal: Add WebP as a core media type in EPUB 3.3 00:43:03 +2 (1 for me, 1 for Garth) 00:43:06 0 00:43:17 0 00:43:28 +1 00:43:31 +1 00:43:33 +1 00:43:34 +1 00:43:35 +1 00:43:48 0 00:44:02 +1 00:44:15 Resolved: Add WebP as a core media type in EPUB 3.3 00:44:38 wendyreid: I can't make a strong case for VTT 00:44:40 q+ 00:45:04 ack dauwhe 00:45:15 dauwhe: I don't think we should vote on this right now 00:45:22 ... it might not need to be a CMT 00:45:29 ... it should be available in EPUB 00:45:36 ... let's figure out how to do that 00:46:04 wendyreid: that's all I have for today 00:46:08 ... 's issue 00:46:19 ... thanks to everyohe who attended the joint meeting with APA/Silver 00:46:35 ... next week's meeting will be our not-face to not-face 00:46:40 ... we'll do two meetings 00:46:50 ... both meetings will be 3.5 hours with breaks 00:46:55 ... we're finalizing agendas now 00:47:16 ... we'll talk about testing, fxl a11y, some contentious github issues, etc. 00:47:24 ... be prepared to see the agenda early next week 00:47:40 ... please volunteer to scribe, we will need multiple scribes per session 00:47:49 ... anything else? 00:48:12 zhengxu: the CG will have the first meeting next week 00:48:29 ... do we want to try caniuse for ereader again, run by the community group? 00:48:40 wendyreid: that's wednesday 00:48:47 marisa: 21st? 00:48:53 ... Publishing CG? 00:48:58 ... I'll try to be there. 00:49:27 wendyreid: if that's everything, I'll let everyone get to their workday, worknight, or whatever. 00:49:38 ... see y'all next week at eTPAC. 00:49:49 ... stay positive and test negative :) 00:49:56 zakim, end meeting 00:49:56 As of this point the attendees have been wendyreid, toshiakikoike, MasakazuKitahara, MattChan, LauraB__, zhengxu, Teenya, duga, marisa, Yanni, shiestyle, BenSchroeter, jyoshii 00:49:59 RRSAgent, please draft minutes 00:49:59 I have made the request to generate https://www.w3.org/2020/10/15-epub-minutes.html Zakim 00:50:01 I am happy to have been of service, dauwhe; please remember to excuse RRSAgent. Goodbye 00:50:06 Zakim has left #epub 00:50:35 RRSAgent: make logs public 00:50:46 LauraB__ has left #epub 00:52:53 Funny Japanese :) 00:53:52 Yes! 00:54:45 See you next week! 00:55:48 zhengxu has joined #epub 00:59:34 zhengxu_ has joined #epub 03:42:51 zhengxu_ has joined #epub 06:02:31 Karen_ has joined #epub 10:16:51 zhengxu has joined #epub 10:24:02 zhengxu_ has joined #epub 11:04:58 zhengxu has joined #epub 12:01:38 tzviya has joined #epub 12:21:00 zhengxu has joined #epub