14:26:37 RRSAgent has joined #epub 14:26:37 logging to https://www.w3.org/2021/01/15-epub-irc 14:26:39 RRSAgent, make logs Public 14:26:40 please title this meeting ("meeting: ..."), ivan 14:27:15 ivan has changed the topic to: Meeting Agenda 2021-01-15: https://lists.w3.org/Archives/Public/public-epub-wg/2021Jan/0030.html 14:27:16 Chair: dauwhe 14:27:16 Date: 2021-01-15 14:27:16 Agenda: https://lists.w3.org/Archives/Public/public-epub-wg/2021Jan/0030.html 14:27:16 Meeting: EPUB 3 Working Group Telco 14:44:07 mgarrish has joined #epub 14:52:36 MattChan has joined #epub 14:54:46 Bert has joined #epub 14:58:12 present+ 14:58:19 MasakazuKitahara has joined #epub 14:58:19 juliette_mcshane has joined #epub 14:58:24 present+ 14:58:32 present+ 14:58:59 avneeshsingh has joined #epub 14:59:15 present+ 14:59:24 present+ 14:59:27 guest+ bert 14:59:36 present+ 14:59:36 guest+ Neil_Soiffer 14:59:44 present+ 14:59:48 guest+ Bruce_Miller 14:59:55 toshiakikoike has joined #epub 15:00:00 present+ Bert_Bos 15:00:01 guest+David_Farmer 15:00:07 present+ 15:00:15 guest+ David_Farmer 15:00:21 present+ 15:00:34 guest+ Steve_Noble 15:00:44 guest+ Sam_Dooley 15:00:49 gpellegrino has joined #epub 15:01:13 circularken_ has joined #epub 15:01:19 laurent_ has joined #epub 15:01:24 SteveNoble has joined #epub 15:01:33 present+ 15:01:41 present+ 15:01:42 George has joined #epub 15:01:44 BenSchroeter has joined #epub 15:01:48 Guest+ Deyan_Ginev 15:02:05 scribe + 15:02:07 scribe+ 15:02:12 CharlesL has joined #epub 15:02:19 NeilS has joined #epub 15:02:25 present+ 15:02:29 present+ 15:02:31 present+ 15:02:34 topic: MathML CG 15:02:36 Bill_Kasdorf has joined #epub 15:02:37 present+ hadrien 15:02:43 present+ 15:02:47 Teenya has joined #epub 15:02:47 dauwhe: We have a last minute change to the agenda 15:02:59 ... members of the soon to be MathML WG visiting today 15:03:02 present+ 15:03:07 ... their charter is being written and reviewed 15:03:11 present+ 15:03:20 duga has joined #epub 15:03:26 present+ 15:03:27 ... we thought this would be a good time to meet with the EPUBWG and share information on the scope and nature of the work 15:03:33 ... there's many publishers that use MathML 15:03:40 ... and math conventions 15:03:48 present+ Louis_Maher 15:03:52 ... it makes sense to share information on our use cases 15:03:56 present+ Sydnee 15:04:03 ... I am very excited by this new energy around math 15:04:06 present+ Brian_Kardell 15:04:23 NeilS: Two main prongs to the charter 15:04:25 https://mathml-refresh.github.io/charter-drafts/math-2020.html 15:04:30 guest+ Brian_Kardell 15:04:35 ... MathML Core: Igalia is leading this work 15:04:41 ... getting MathML into browsers 15:04:48 ... integrate with the existing tech stack 15:04:59 present+ Garth 15:05:02 ... we are running into the constraints of the browsers 15:05:07 present+ brady 15:05:12 present+ charles 15:05:14 ... other prong is to improve accessibility, search, and computability 15:05:19 ... allowing author intent 15:05:26 ... disabiguate what something means 15:05:42 ... if you had vertical bars around content, it could be an absolute value, or something else 15:05:50 ... screenreaders can guess, but its a guess 15:06:00 ... we want to allow authors to clarify that meaning 15:06:16 ... that's the high level overview 15:06:21 ... open to questions 15:06:23 q+ 15:06:27 present+ gpellegrino 15:07:02 Brian: Just wanted to correct one thing, the current and near-future of browsers are the target of MathML Core level 1 15:07:11 q+ 15:07:12 ... as things grow and change, we can grow with them 15:07:29 ack Bill 15:07:42 q+ to ask about LaTeX 15:07:44 Bill_Kasdorf: Thanks for joining, do you want to make any comments on backwards compatiblity 15:07:53 NeilS: There are things that aren't in Core 15:07:57 ... there is a level 2 planned 15:08:07 ... we want to get something out now instead of waiting 15:08:15 ... there are polyfills for the differences 15:08:25 ... there's a few things in MathML that are obscure and never implemented 15:08:31 q+ 15:08:32 ... many of the polyfills are deprecated 15:08:41 ... many things still work, but some javascript may be required 15:08:51 ... the idea of core is that the stuff people use will be supported 15:09:00 ... fractions, square roots, etc 15:09:05 q+ 15:09:06 ... line breaking is in level 2 15:09:17 ... mfenced is going away to be replaced by a polyfill 15:09:20 Hadrien has joined #epub 15:09:30 ... if you're willing to use those, it will be the same 15:09:34 q- 15:09:41 ... for Core, it covers about 95-98% of what you want 15:09:55 Brian: We based a lot of this on what MathML is in use in the market 15:09:58 q- 15:10:33 NeilS: Bevelled fractions, for example, I thought it was common, but in the research we found it's rarely used 15:10:40 ack tz 15:10:40 tzviya, you wanted to ask about LaTeX 15:10:45 tzviya: I have a few questions 15:10:48 ... first about authoring 15:11:05 ... are the workflows maintainable? 15:11:16 NeilS: David Farmer is on the call, he works on PreText 15:11:54 DavidF: The Math in PreText, designed to convert to any output, PDF, HTML, EPUB, braille 15:12:12 ... the way we do HTML is to use pretext?? and then add mathjax 15:12:22 ... we are working on an easier way for authors to write content 15:12:26 ... many textbooks in math 15:12:46 ... learning latex is a hurdle, we want to make it simpler 15:13:01 Garth has joined #epub 15:13:01 ... for accessibility we want to simplify 15:13:08 tzviya: I don't want a new tool 15:13:25 ... if an author wants to write in Latec, they will 15:13:36 s/Latec/LaTeX/ 15:13:48 ... what would be helpful for me (Wiley Scholarly), is to talk to us directly 15:13:55 ... how to incorporate into the tool chain 15:14:08 Brian: The goal is not to lose author information 15:14:28 ... flow from author, to latex, to the screenreader 15:14:36 ... if the author has some intent, let them express it 15:15:07 DavidF: It's still Latex, but we're considering the steps between 15:15:21 NeilS: Please get in touch 15:15:31 q? 15:15:34 ack ivan 15:15:34 Brian: In terms of existing tool chains, things should work as before if not better 15:15:39 ivan: Two questions 15:15:58 ... one: in terms of the standard and implementation, are you keeping the content markup and presentation markup? 15:16:09 NeilS: We have no intention of doing anything to content 15:16:17 ... presentation and content MathML will continue to exist 15:16:29 ... dealing with author intent, incorporates all of content MathML 15:16:35 ... threads the content tree 15:16:38 q? 15:16:51 ... that may at some point replace content MathML, for now we are keeping it 15:16:51 q+ 15:16:57 ivan: Other question is practical 15:17:03 ... can you speak to the timeline? 15:17:19 ... when do you plan to publish the new recommendations, and implementation? 15:17:32 ... this WG relies on what you do, as do the reading systems 15:17:40 ... they would love to incorporate core 15:17:54 NeilS: Going from memory, roughly Core will be out first 15:18:11 ... mostly already written, another year or so to release 15:18:18 ... CR in 6 moths 15:18:25 s/moths/months 15:18:43 ... we've been exploring other ideas, and the publication schedule is closer to the end of the charter 15:18:56 ... math player accessibility, working on the replacement for that now 15:19:04 ... developing as we finalize intent 15:19:11 ... NVDA will pick up all of that 15:19:35 ... as will ORCA, possibly JAWS, I have asked 15:19:43 ... Apple is a mystery 15:20:27 NeilS: Also spoke to the mathjax folks, the core work doesn't replace their work, but it might result in a new backend renderer, faster 15:20:41 q? 15:20:44 ... likely won't switch until browsers are implemented 15:20:51 ivan: What can this group do to help? 15:21:18 ... help with testing, review, support? 15:21:30 NeilS: I don't think there's anything before going to charter, aside from sign off 15:21:41 ... but as we get into development, comments on publisher needs 15:21:50 ... trying things out once implementations are out there 15:22:06 ivan: Is EPUB WG listed as a liaison? 15:22:11 NeilS: You're listed 15:22:22 dauwhe: We're doing it already! 15:22:29 present+ 15:22:40 ... A lot of people who use EPUB are educational publishers at all levels 15:22:54 ... is there a lot of support for pedagogical notation? 15:22:59 ... I mostly work on novels 15:23:29 ... just wondering about the teaching additions 15:23:39 Brian: There's a lot of different textbooks 15:23:40 q+ 15:23:46 ... there's not elementary math 15:23:53 ack dauwhe 15:24:11 dauwhe: Long division with things crossed out to show places and things 15:24:15 Karen has joined #epub 15:24:28 q+ 15:24:34 NeilS: That was in MathML 3, but there's no browser supports, it might change if there's need 15:24:57 Brian: The thing with that is finding someone to express the priority and achieve them 15:24:59 NeilS: Fund them 15:25:18 dauwhe: If you want stuff in MathML, Brian can make them happen, with some help 15:25:31 guest+ Murray_Sargent 15:25:33 Brian: It can be difficult to know what is important without people asking for them 15:25:49 q? 15:25:50 ... standards is a small group of people doing the work and owning it forever, 15:25:51 present+ laurent 15:26:04 ... from a practical standpoint, we need to know what is important 15:26:18 ... given the parameters we have now 15:26:22 ack George 15:26:32 George: At EPUBTest we have a math sample book 15:26:36 ... we are reporting results 15:26:45 ... support by reading systems and screenreaders 15:26:52 ... visual presentation and AT support 15:26:58 http://epubtest.org/test-books 15:27:06 q? 15:27:07 ... I can't wait to see the changes as it's better supported by Chrome 15:27:18 ... we still have chem on the web in publishing group happening 15:27:27 ... great to see the semantics of chemistry included 15:27:29 ... great work! 15:27:30 ack tz 15:27:36 tzviya: In terms of elementary math vs other math 15:27:54 ... this group doesn't have elementary (primary) mathematics 15:27:57 q? 15:28:20 ... I could help get samples from Cengage, McGraw-Hill 15:28:33 ... I have samples ranging from college to nobel prize winners 15:28:50 ... we can give you the samples, I know you have done research, but we can provide even more 15:28:53 q? 15:29:00 ... we have a large community 15:29:08 q+ 15:29:23 NeilS: Please support the charter! 15:30:04 dauwhe: If you're an AC rep, or ask your nicely 15:30:09 ... bake them cookies 15:30:30 q? 15:30:43 ack Bill 15:31:01 q? 15:31:02 Bill_Kasdorf: Quick, if you want elementary math, I can get the people from the conversion/pre-press houses 15:31:10 ... some are now members 15:31:20 NeilS: There's a polyfill for it, so I'd love testers 15:31:39 dauwhe: We're here and we're happy to help 15:32:32 topic, Testing 15:33:07 s/topic,/topic:/ 15:33:17 dauwhe: Do we have any new members? 15:33:31 Bert has left #epub 15:33:34 ... moving on to the regular agenda 15:33:39 ... I wanted to talk about testing again 15:33:47 ... we had hoped for a testing champion 15:33:51 ... in the short term it is me 15:34:01 ... I have a strange fascination with writing tests for EPUB 15:34:03 ... I have start 15:34:10 s/start/started 15:34:20 ... I am not sure if these will be used as CR exit criteria 15:34:27 ... but we can use them to learn about the spec 15:34:30 ... and make it better 15:34:47 ... I have been going through the RS spec and writing tests 15:34:54 ... working on a script felt premature 15:34:56 https://github.com/dauwhe/epub-tests 15:35:02 ... EPUB is weird and there's a lot of interaction 15:35:08 ... this is in a fork of the testing repo 15:35:12 https://github.com/dauwhe/epub-tests/blob/main/epub-test-notes.md 15:35:31 ... extracting normative statements from the spec 15:35:35 ... write a test for it 15:35:39 ... and add it to the list 15:35:49 ... I've been running into some interesting issues that I wanted to discuss 15:36:12 ... one thing that this has done has reminded me how much of the spec has not been implemeneted 15:36:19 ... biggest example is manifest fallbacks 15:36:31 ... at least among the commerical/trade oriented RSs 15:36:36 ... very little support 15:36:47 ... not supported in Thorium, Apple Books, etc 15:37:03 ... I have tests that show RSs aren't processing manifest fallbacks at all 15:37:17 ... one interesting consequence is looking at the way RSs handle foreign resources 15:37:29 ... test where I had a JSON content doc with an xhtml fallback 15:37:37 ... I have a few RSs where they display the JSON 15:37:47 ... throw it in a webview and see what happens 15:37:54 ... this seems incongruent with the spec 15:38:08 ... RSs are just trying to display the content no matter what 15:38:18 ... I made a bunch of manifest fallbacks with XML 15:38:26 ... they'll show the content, a tree view 15:38:36 ... that seems odd 15:38:56 ... I suspect I'll run into the same thing with linked metadata records 15:39:03 ... order of priorities of those 15:39:08 ... haven't seen support for this 15:39:24 ... I wanted to mention to the WG that we have these areas of little implementation 15:39:38 ... another issue is that we have a number of normative statements that feel hard to test 15:39:55 q? 15:39:59 ... we had to set it up this was, a EPUB 3 RS must process the container etc 15:40:03 q+ 15:40:03 ... meta safe statement 15:40:03 q+ 15:40:12 q+ 15:40:14 ack Gar 15:40:16 q+ 15:40:44 Garth: Assuming you're right and few commerical reading systems use fallbacks 15:40:51 ... what do you think that means for us? 15:40:57 ... we remove it from the spec 15:41:01 ... or the opposite? 15:41:07 dauwhe: I honestly don't know 15:41:15 ... it touches on the concept of the core media type 15:41:20 ... which is foundational to the idea of EPUB 15:41:25 ... a CMT doesn't require a fallback 15:41:32 ... but you also expect it to work 15:41:38 ... this finding blurs that a little 15:41:51 ... it's not a CMT, but the RS tries and fails in an odd way 15:41:53 ack tz 15:42:00 tzviya: I have a similar question to Garth 15:42:15 ... I think we need to be careful that testability isn't the only thing to look for 15:42:26 ... we're going to discover untestable things 15:42:28 ... but EPUB works 15:42:41 ... and we don't want to destroy something that works because it's hard to test 15:42:46 ... I'm not sure what the best solution is 15:43:03 ... maybe wordsmithing can help but won't help with the testing 15:43:25 ack ivan 15:43:25 dauwhe: It's a good illustration of remembering our larger goals 15:43:43 q+ 15:43:50 q? 15:43:51 ivan: Answer first, absolutely true that testability should not be the only criteria 15:44:06 ... even in the audiobooks spec or others, where vocabularies were defined and testing unclear 15:44:34 ... if there's features EPUB has, and are used, they must be part of the spec, it's on us to prove that for a feature there's a use 15:44:45 ... that's a criteria we need to fold into our testing 15:44:48 q+ 15:45:06 q+ 15:45:11 ... in the happy days of HTML5, and with versions of SVG, we did find features in both that were never implemented 15:45:35 ... there's some nice features people planned, but they were removed from later versions because they were never implemented 15:45:47 ... we would have to have a policy for features that haven't been used 15:46:04 ... and aren't implemented practically in any reading system 15:46:07 ... what do we do with them 15:46:23 ... and what do we do with the backwards compatibility 15:46:37 q- 15:46:54 ... we declare them as deprecated or dropped 15:47:04 ... we cannot hope for every feature implemented by every RS 15:47:14 ... but at least have reasonable coverage 15:47:25 ack Charl 15:47:32 q? 15:47:33 CharlesL: When I was wearing my developer app 15:47:40 ... for Java we had JUnit 15:47:46 ... testing framework 15:47:57 ... I am wondering if we need a unit test reading system 15:48:09 ... testing for hard-to-test features 15:48:17 ... we need to build a test reading system maybe 15:48:33 ack mg 15:48:45 Karen has joined #epub 15:48:51 mgarrish: I think we probably need to look at or consider what features are foundational 15:48:55 ... look for implementation 15:49:10 ... removing manifest fallbacks opens up the spine, which could be a problem 15:49:17 q+ 15:49:20 +1 to mg 15:49:25 ... I'm all for removing things we don't need, but we have to be careful 15:49:30 dauwhe: That's my concern as well 15:49:30 +1 to mgarrish 15:49:37 ... this feels foundational 15:49:43 ... but also neglected 15:49:46 +1 to mgarrish 15:49:49 ... I don't want to remove this 15:50:05 q? 15:50:10 ... I want to find a way forward that acknowledges the reality but promotes interop 15:50:11 ack Had 15:50:30 Hadrien: I'm wondering if fallbacks are not used as extensibility for some environments 15:50:53 ... I wouldn't be surprised where specific reading systems craft specific epubs with this in mind 15:51:06 ... I do wonder what is the intent 15:51:12 ... I don't remember where fallbacks came from 15:51:32 ... if there's a new version of something like images or video, the fallback could be used to maintain compatibility 15:51:42 ... but also could have extensibility 15:52:01 ... reading systems might have these use cases, but they don't allow sideloading 15:52:12 dauwhe: I hope we get to a point where we can pass these tests 15:52:13 q+ 15:52:20 ... ADE supports the fallbacks 15:52:26 ... and there's probably others 15:52:35 ... gives us the opportunity not to mangle the spec 15:52:37 ack gar 15:52:41 ... and allows for the extensiblity 15:52:45 Garth: I agree with Matt 15:52:55 ... we need to be careful not to rip out foundational things 15:53:06 ... CMTs and the fallback chain may not be foundational 15:53:23 ... you may not have to lose CMTs with losing the fallback chain 15:53:38 ack mg 15:53:38 ... I think it's worth questioning 15:53:48 mgarrish: Certainly there's ways of making things work 15:53:52 ... it becomes complicated 15:54:01 ... potentially invalidates content in the market 15:54:10 ... I think we have to balance priorities 15:54:17 ... further to Hadrien's point 15:54:24 ... there's other systems that aren't on our radar 15:54:32 ... libraries may be using linked metadata records 15:54:37 q+ 15:54:38 ... it's a means of having the record travel 15:54:54 ... there's lots of requirements on merging and consolidating that may not come into play 15:55:00 ... there's use cases that may not be on our radar 15:55:22 dauwhe: I think we'll be having lots of discussions like this 15:55:25 ack ivan 15:55:29 ... we don't have access to all useragents 15:55:36 ivan: This reminds me of a question I was asked 15:55:50 ... with web and HTML, a big search engine (i.e. google) 15:56:05 ... could come back with data that says "25% of websites use x feature" 15:56:24 ... there was an established way to have data like that 15:56:37 ... but is there an equivalent for EPUB 15:56:46 q+ 15:56:48 q? 15:56:49 q+ 15:56:56 dauwhe: We've done a little bit of this 15:57:13 ... thanks to the goodwill of group members who have access to this data 15:57:24 ... we can only do this in certain ways 15:57:30 ... it's a lot easier to do on the web 15:57:31 ack wen 15:58:31 duga: The web and EPUB are just really different 15:58:34 q+ 15:58:38 ack duga 15:58:44 ... there's no "open EPUB" equivalent for the open web 15:58:48 ack iv 15:58:54 wendyreid: It just takes a lot of processing 15:59:00 ivan: I expected that 15:59:10 ... we may have to think about ways to achieve something like this 15:59:28 ... we need to make some decisions feature by feature about what should or shouldn't be normative 15:59:33 ... is it implemented or not 15:59:42 ... implementability is not the only criteria 15:59:50 ... we need ways to determine this 16:00:15 q? 16:00:43 dauwhe: Thanks for the good discussion, I'll be filing issues on the things I find to discuss them 16:00:47 q+ 16:00:49 ... this will come up again! 16:00:51 ack geor 16:01:33 dauwhe: Thanks everyone, see you in a week! 16:01:49 zakim, end meeting 16:01:49 As of this point the attendees have been dauwhe, juliette_mcshane, MattChan, avneeshsingh, ivan, MasakazuKitahara, wendyreid, Bert_Bos, toshiakikoike, tzviya, SteveNoble, 16:01:52 ... gpellegrino, CharlesL, mgarrish, BenSchroeter, hadrien, Bill_Kasdorf, laurent_, Teenya, duga, Louis_Maher, Sydnee, Brian_Kardell, Garth, brady 16:01:52 RRSAgent, please draft minutes 16:01:52 I have made the request to generate https://www.w3.org/2021/01/15-epub-minutes.html Zakim 16:01:55 I am happy to have been of service, ivan; please remember to excuse RRSAgent. Goodbye 16:02:00 Zakim has left #epub