13:15:51 RRSAgent has joined #epub 13:15:51 logging to https://www.w3.org/2020/09/25-epub-irc 13:15:53 RRSAgent, make logs Public 13:15:54 please title this meeting ("meeting: ..."), ivan 13:16:03 ivan has changed the topic to: Meeting Agenda 2020-09-25: https://www.w3.org/mid/571B5ED9-2E38-478B-B468-DFA5D0C46C2E@rakuten.com 13:16:04 Chair: wendy, dauwhe 13:16:04 Date: 2020-09-25 13:16:04 Agenda: https://www.w3.org/mid/571B5ED9-2E38-478B-B468-DFA5D0C46C2E@rakuten.com 13:16:04 Meeting: EPUB 3 Working Group Telco 13:55:23 Daihei has joined #epub 13:55:37 present+ 13:57:27 toshiakikoike has joined #epub 13:57:42 present+ 13:58:08 MasakazuKitahara has joined #epub 13:58:16 present+ 13:58:21 ReinaldoFerraz has joined #epub 13:59:20 present+ 13:59:48 present+ MasakazuKitahara 14:00:51 Avneesh has joined #epub 14:00:52 zhengxu_ has joined #epub 14:01:03 present+ zhengxu_ 14:01:10 mgarrish has joined #epub 14:01:14 present+ 14:01:20 present+ 14:02:06 duga has joined #epub 14:02:15 present+ 14:02:19 present+ garth 14:02:26 present+ 14:02:29 present+ brady 14:02:32 present+ 14:02:38 present+ billk 14:02:48 garth has joined #epub 14:02:55 romain has joined #epub 14:02:58 present+ romain 14:03:03 present+ Garth 14:03:03 present+ 14:03:25 Bill_Kasdorf has joined #epub 14:03:34 present +juliette 14:03:38 present+ hadrien 14:03:45 present+ 14:04:02 present+ george 14:04:26 present+ charles 14:04:34 scribe+ garth 14:04:42 regrets+ dauwhe 14:04:44 CharlesL has joined #epub 14:05:04 wendy: Minutes coming soon; approve after meeting. 14:05:05 present+ 14:05:16 https://github.com/w3c/epub-wg/projects 14:05:17 Hadrien has joined #epub 14:05:26 … Over view of Projject Structure 14:05:34 topic: overview on projects 14:05:40 … Github Project Managment Tool 14:06:05 … E.g., Publication Schedule 14:06:24 … EPUB Testing & A11Y Revision 14:06:40 q+ 14:06:41 q? 14:06:42 … Questions? 14:06:44 George has joined #epub 14:06:46 ack romain 14:06:59 present+ 14:07:08 Romain: Is the Project View accessible? 14:07:32 … Issues may be better, allow screen readers to see project details. 14:08:24 q+ 14:08:29 Wendy: Needs explorations; can’t link issues from other projects. Use tags & lables. 14:08:34 ack Avneesh 14:08:58 Avneesh: There were issues with editing in the Project View. 14:09:39 … If it’s the high level view mainly for Chairs, mightbe fine. Issues are A11Y. 14:09:51 Wendy: Yes, it should be that way. 14:10:06 … That’s where status will be. 14:10:18 Topic: document structure 14:10:20 … Document Structure now. 14:10:40 … Lots of satelite docs historically. 14:10:48 … How do we do this for EPIB 3.3? 14:10:55 … What’s Matt thinking? 14:10:57 s/EPIB/EPUB/ 14:11:23 mgarrish: Bring the core specs into one specification. 14:11:59 … Much of what we did in 3.1 headed this direction, but we didn’t do the combination. Do it now. 14:12:19 -> https://www.w3.org/2020/08/epub-wg-charter.html#deliverables for info, the official deliverable list of the WG 14:12:32 … Simpler with less documents to maintain should be a feature. 14:12:42 https://mattgarrish.github.io/publ-epub-revision/epub33/spec/epub-spec.html 14:12:45 … Should help our publishing process. 14:13:13 … Combine front/back matters, then get to one main document. 14:13:29 … RS Requirements could be broken out. 14:13:46 • https://mattgarrish.github.io/publ-epub-revision/epub33x/spec/epub-rs.html 14:13:50 … Should they be merged (or not) with Content requirements? 14:14:24 q+ 14:14:30 … These are a couple of simplification options. 14:14:32 q+ 14:14:36 ack ivan 14:14:50 ivan: Reference to charter above. 14:15:06 present+ 14:15:08 … MO and A11Y are seperate. Why? 14:15:45 q+ 14:15:55 mgarrish: Consolidate the core, MO is not required — so keeping that secondary may make sense. 14:16:02 … Could also combine all. 14:16:16 q- 14:16:24 q+ 14:16:42 ack Bill_Kasdorf 14:16:42 wendyreid: Agree on MO. Maybe A11Y wants to be combined in to the main spec? 14:16:53 q+ 14:16:53 q+ 14:16:58 Bill_Kasdorf: Likes RS requirements being broken out. 14:17:18 … Likes A11Y being part of Core. 14:17:33 q+ 14:17:44 ack Avneesh 14:17:49 … If RS Reqs would be broken out, how much content needs duplication? 14:18:25 Avneesh: A11Y was broken out to support independent versioning and branding. 14:18:54 ack CharlesL 14:18:55 q+ 14:18:59 … Europpean A112Y Act — A11Y will be presented thee — being standalone helps. 14:18:59 I'm sold by Avneesh that A11y needs to be its own document 14:19:10 CharlesL: Agree with Avneesh. 14:19:34 … Though A11Y doesn’t want to be step-child. 14:19:42 … A11Y might want to move faster. 14:19:49 ack mgarrish 14:19:54 … Still “born accessible” but sperate might be better. 14:20:25 mgarrish: A11Y is vesion indeptendant. So broken out makes sense. 14:21:33 … This not overly complicaed. Ppossiblr to break RS Conformance. 14:21:37 ack zhengxu_ 14:22:33 q+ 14:22:36 zhengxu_: A11Y broken out from RS Conformance makes sense. 14:23:11 … Difficult to connect with MO, provided by publisher. 14:23:27 ack ivan 14:23:38 … Good to draw some line — A11Y for EPUB and A11Y for Content. 14:23:49 q+ 14:24:03 q+ 14:24:05 ivan: Understand what Avneesh was saying, but maybe there is some middle count. 14:24:24 … We clearly don’t want folks to ignore A11Y reqs. 14:24:46 … When we publish at the end, could we renumber the A11Y to match (at that point in time). 14:24:54 … So it feels like a complete set. 14:25:21 q+ 14:25:22 … Just like MO. 14:25:24 ack Avneesh 14:25:47 Avneesh: EPUB A11Y can be applied to all EPUBs (1.x … 3.x). 14:25:48 q+ 14:25:57 ack mgarrish 14:26:03 … Tying to EPUB 3.3 could create wrong impression. 14:26:25 mgarrish: Yep, get that. Started at 1.0 as it started later. 14:26:36 … like CFI too. 14:26:50 … It would be strange to jump to 3.3 14:27:13 … There is an A11Y spec a section dealing with RS A11Y. 14:27:37 q- 14:27:41 q+ 14:27:46 ack Bill_Kasdorf 14:28:13 Just for information EPUB reading system accesssibility protocol is in actin at www.epubtest.org 14:28:19 ack George 14:28:24 Bill_Kasdorf: Might not be good to tie A11Y to EPUB to support updates on their one timelines. 14:28:54 s/one/own/ 14:28:54 George: WCAG 1.2 was specifially about HTML, extracted and expanded in 2.0. 14:29:25 … We reference other specs in our specs (HTML, XML), could we do the same with the A11Y spec? 14:29:33 … Reference the latest version. 14:29:40 george, it is already referenced. 14:29:42 q+ 14:30:05 ack zhengxu_ 14:30:07 … Incorporaste A11Y metadata, So, don’t include the spec into the 3.3 integrate/refence the then current version. 14:30:19 zhengxu_: Not crazy. 14:30:32 q+ 14:31:16 … MO should be seperate. A11Y covers voice over — different from MO. 14:32:33 ack mat 14:32:36 ack mgarrish 14:32:40 … Should provide something to be more accessible for 3.3. Consider RS implementations. 14:33:26 mgarrish: EPUB A11Y Spec may wind down in lue of “silver requriements”? Thus, broken out may make sense for that reason. 14:33:27 ack wendyreid 14:33:34 q+ 14:33:48 wendyreid: Worth digging into further. 14:34:05 … We do have a TPAC meeting with APA/Silver folks. 14:34:14 … Should discuss schedules. 14:35:10 ack ivan 14:35:12 … Can we come to some decision re Document structure. Matt’s proposal seems a good start. 14:35:25 ivan: Ivan and Wendy are mind melding! 14:35:59 … Can we have consense on what I put in IRC? 14:36:34 … Need to map Charter Docs on to the above. 14:36:48 … Can we resolve with this? 14:36:55 Proposal: we will publish the following documents: EPUB 3.3 Content, EPUB 3.3 RS, Accessibility 1.1, Media Overlays 3.3 14:36:56 q+ 14:37:01 q+ 14:37:05 ack CharlesL 14:37:19 ack duga 14:37:37 +1 14:37:47 +1 14:37:52 +1 14:37:53 duga: Have faith in Matt — content/RS split needs to be understood. 14:37:53 +1 14:37:55 +1 14:38:01 +1 14:38:02 +1 14:38:04 +1 14:38:09 +1 14:38:15 +1 14:38:17 +1 14:38:21 +1 14:38:23 Avneesh: 1.1 for A11Y is fine for now. 14:38:30 Resolution: we will publish the following documents: EPUB 3.3 Content, EPUB 3.3 RS, Accessibility 1.1, Media Overlays 3.3 14:38:54 Topic: FPWD 14:39:01 wendyreid: FPWD next. 14:39:23 … Stake in the ground for the project. 14:39:34 q+ 14:39:35 … Advantage of starting with fully implemented dcoument. 14:39:49 https://github.com/w3c/publ-epub-revision/issues 14:39:54 … Just the result of restructuring could be FPWD. 14:40:04 q+ 14:40:12 … Or we could tackle somes issues in the FPWD. 14:40:17 … Typos would be easy! 14:40:23 … Any other pet issues? 14:40:29 ack ivan 14:41:09 ack Avneesh 14:41:09 ivan: FPWD is what starts the whole IPR proceedure. IPR seems like it’s not a huge issue with EPUB. 14:41:48 Avneesh: FPWD of EPUB A11Y — 1.5 year effort on ISO version. 14:42:12 … ISO version improved readability. 14:42:32 … We should bring those enhancements into the EPUB A11Y version for FPWD. 14:42:41 ivan: Sounds Good. For 1.1. 14:42:47 q+ 14:42:52 ack George 14:43:30 George: When we port the ISO version back, we re-W3C the should’s, must’s, et al. 14:43:44 … Maybe slihgtly worried about what ISO would think. 14:43:46 q+ 14:44:30 q+ 14:44:43 q- 14:44:58 ack Avneesh 14:45:29 q+ 14:45:36 q+ 14:46:03 ack mgarrish 14:46:37 mgarrish: ISO version work would be inspiration for W3C/IDPF version. 14:46:40 ack George 14:47:22 George: Always an expectation that spec would evolve within W3C. 14:47:39 … Geroge is feeling good! :-) 14:48:13 q+ 14:48:20 q- 14:48:44 q+ 14:48:47 wendyreid: Any other issues that should be included FPWD? Maybe new Core Media types? Image, audio, video? 14:49:31 ack Avneesh 14:49:44 Avneesh: OPUS was in queue since IDPF days. 14:50:07 … Not enough browser support in the old days — things likely changes (for the better) by now. 14:50:12 q+ 14:50:36 wendyreid: OPUS looks generally supported. 14:50:41 ack ivan 14:50:57 q+ 14:51:01 ivan: New media types could be a techncial low hanging fruit. 14:51:30 … Would such mean each RS would need to handle these new Media Types? 14:51:38 ack mgarrish 14:51:42 … Backward compatibility, oh my! 14:51:44 q+ 14:52:20 q+ 14:52:29 mgarrish: Core Media type may not directly drive Core support — but one does audio need to do ‘em all. So, yes, an issue. 14:52:57 q+ 14:52:58 … Do we have a policy on adding types? Need to all be royalty free? 14:53:06 ack zhengxu_ 14:54:24 zhengxu_: Support is not really a “force” to support. Up to implementor. Recomendation rather than force. 14:54:46 … unsure we really need such Core Media types specified. 14:54:55 … What about fallbacks? 14:55:03 q? 14:55:39 … Need to consider work with epubcheck too. 14:55:45 ack Bill_Kasdorf 14:55:53 zakim, close queue 14:55:53 ok, wendyreid, the speaker queue is closed 14:56:20 Bill_Kasdorf: OPUS might be fine as “generally implemented” and we’d be equally early in the spec process. 14:56:22 ack ivan 14:56:51 q+ 14:56:54 ivan: Now we list media types. Can we just refer back to HTML5? 14:57:08 … and be off the hook ourselves. 14:58:17 duga: Really complicated issue. Not one to be resolved today. OPUS needs special handing on iOS/macOS. Not a rathole for today! 14:58:57 wendyreid: Made one big decision. FPWD published by TPAC? One a month out! 15:00:00 regrets+ tzviya 15:00:23 CharlesL has left #epub 15:00:29 zakim, end meeting 15:00:29 As of this point the attendees have been Daihei, toshiakikoike, ivan, wendyreid, MasakazuKitahara, zhengxu_, Avneesh, garth, mgarrish, brady, duga, billk, romain, hadrien, 15:00:30 zhengxu_ has left #epub 15:00:32 ... Bill_Kasdorf, george, charles, CharlesL 15:00:32 RRSAgent, please draft minutes 15:00:32 I have made the request to generate https://www.w3.org/2020/09/25-epub-minutes.html Zakim 15:00:34 I am happy to have been of service, ivan; please remember to excuse RRSAgent. Goodbye 15:00:38 Zakim has left #epub 15:04:25 rrsagent, bye 15:04:25 I see no action items