14:52:57 RRSAgent has joined #pbgsc 14:52:57 logging to https://www.w3.org/2020/10/30-pbgsc-irc 14:53:07 Zakim has joined #pbgsc 14:53:21 Meeting: Publishing Steering Committee 14:53:28 Date: 2020-10-30 14:53:35 Chair: Tzviya 14:58:23 jyoshii has joined #pbgsc 14:58:35 Ralph has joined #pbgsc 15:00:17 present+ George, Cristina, Ralph 15:00:42 George has joined #pbgsc 15:01:32 present+ Liisa, Tzviya, Bill, Daihei, Junichi, Avneesh 15:01:34 Bill_Kasdorf has joined #pbgsc 15:01:54 liisamk has joined #pbgsc 15:02:10 present+ 15:02:11 present+ 15:02:12 Avneesh has joined #pbgsc 15:02:20 agenda+ EPUBCheck fundraising 15:02:34 present+ 15:02:43 present+ 15:02:47 Daihei has joined #pbgsc 15:02:52 Cristina has joined #pbgsc 15:02:53 present+ 15:02:59 present+ 15:03:04 agenda+ TPAC debreif 15:04:06 scribe+ 15:04:23 PRESENT+ 15:04:39 agenda: https://lists.w3.org/Archives/Public/public-publishing-sc/2020Oct/0022.html 15:04:49 zakim, who's on the call? 15:04:49 Present: George, Cristina, Ralph, Liisa, Tzviya, Bill, Daihei, Junichi, Avneesh, liisamk, Bill_Kasdorf, jyoshii 15:04:54 present+ Ivan 15:05:34 zakim, next item 15:05:34 agendum 1. "EPUBCheck fundraising" taken up [from tzviya] 15:05:52 George: there's about $10k we still need to raise to meet the financial commitments for next year 15:05:56 Garth has joined #pbgsc 15:06:06 present+ Garth 15:06:07 present+ 15:06:24 ... some companies may have money left in their budget before the year end 15:06:31 ... can we take advantage of that? 15:06:38 Tzviya: what this can accomplish ... 15:06:42 zhengxu has joined #pbgsc 15:06:45 ... we mapped this out in the EPUBcheck roadmap 15:06:57 present+ 15:07:02 ... the part that will make it easier for others to contribute to EPUBcheck 15:07:23 ... EPUBcheck is in a good state but currently only the developers are able to contribute 15:07:40 ... the $10k will make it easier for others to contribute in the future 15:07:57 Garth: where can I find something written up? 15:08:25 Tzviya: I'll dig up the old documentation 15:08:25 q+ 15:08:31 https://www.w3.org/blog/2018/10/epubcheck-fundraising/ 15:08:34 ack George 15:08:50 George: maybe we could write something that could be sent to the list also 15:09:02 Tzviya: good idea; I'll add that to my list 15:09:13 s/list/to-do list 15:09:20 ... happy for someone else to help with that 15:09:31 zakim, next item 15:09:31 agendum 2. "TPAC debreif" taken up [from tzviya] 15:10:25 s/reif/rief 15:10:27 Cristina has joined #pbgsc 15:10:32 q+ 15:10:37 ack dauwhe 15:11:14 Dave: I feel a disconnect between what happes in teleconferences and what happens in GitHub 15:11:32 ... I feel we're not truly able to make technical decisions in conference calls because important voices are not on the calls 15:11:44 ... this particularly impacted the recent EPUB 3 WG calls 15:11:55 ... in GitHub it's the same voices who have been commenting for decades 15:12:07 ... I'm not sure what to do about this 15:12:22 ... how to get things to move forward 15:12:29 q+ 15:12:36 ack Garth 15:12:46 ... I'm not sure what to do, but it's an issue 15:12:56 Garth: one thing that falls into that category is external entities 15:13:10 ... the GitHub discussion does seem to be coalescibng around what was said in the calls 15:13:24 q+ 15:13:27 Dave: I see that as a symptom; a particularly clear example, but it's not the only one 15:13:43 ...in a broader sense, I'm wondering about the goals of the WG 15:14:03 ... it feels like some of what's happening is that we're focusing on the spec in a very technical way 15:14:10 q+ to talk about growing pains 15:14:14 ... which to me feels a little removed from the needs of end users and the community 15:14:27 ... this maybe boils down to a question of participation 15:14:38 ... and where we're getting input and feedback 15:15:06 ... if an outsider were observing the WG right now, they'd be wondering how it affects them as an author or publisher 15:15:13 ack George 15:15:15 ... deep details of XML processing models 15:15:27 George: that thread was painful 15:15:40 ... I doubt there's many people who could actually follow and digest it 15:16:05 ... for something like this if we could get a short summary and the decision we made, that would help people 15:16:08 q+ 15:16:15 ... it was a very detailed thread and hard to follow 15:16:29 Dave: there's a user-facing question here 15:16:34 ... Ivan identified it early 15:16:48 q+ 15:16:51 ... if a tool puts a DTD in an EPUB and EPUBcheck rejects it 15:16:57 ... that's not friendly 15:17:08 ... why should we care what the DTD says? 15:17:38 tzviya, you wanted to talk about growing pains 15:17:50 Tzviya: it's an important question how to sync the WG telecons with GitHub 15:18:08 ... summarizing the issue as George suggests is a tremendous amount of work and doesn't have enough benefit 15:18:33 ... at some point we'll have to say that the conversation needs to happen in a different way 15:18:47 ... maybe we can help manage the conversation a bit better 15:19:25 ... in terms of how that coordinates with meetings, maybe the chairs can help by using what the charter says the WG should be doing 15:19:29 ack ivan 15:19:31 ... set some milestones 15:19:56 Ivan: the problem is that it's sometimes difficult to avoid getting into these kinds of discussions 15:19:58 Cristina has joined #pbgsc 15:20:10 q+ 15:20:16 ... the issue I hit did get into a complicated technical issue 15:20:21 present+ 15:20:26 q+ 15:20:28 ... it is converging, so I hope we'll be able to close it 15:20:42 ... when these situations arise we don't know how to avoid it 15:21:13 ... if we were able to shut in a room the 5 people who want to discuss this, maybe they could solve it separately 15:21:27 ... perhaps ad-hoc teleconferences are something we should do systematically 15:21:28 q- 15:21:41 q? 15:21:44 +1 to Ivan--that's what I was on the queue to suggest 15:21:54 ... the WG charter is to clean up the document; make it more readable, create tests 15:22:11 q+ 15:22:14 ... last week I read through the whole spec and raised many issues; some trivial, some less trivial 15:22:49 ... I don't know how to solve the difference between GitHub discussions and WG calls 15:22:58 ... most of the detailed work happens in GitHub 15:23:19 ack Avneesh 15:23:48 Avneesh: I feel there's a deeper issue 15:24:21 ... W3C's organizational needs vs. the community's needs 15:24:55 ... we can encourage technical discussion in the CG 15:25:01 ack George 15:25:26 +1 Avneesh 15:25:43 George: it's great that we have Ivan and Matt to work on the document in such detail 15:26:13 ... there was an ask for a document that laid out the importance of reading; I had to roll my eyes and wonder how often we have to redo the same thing 15:26:26 ... I wonder if there's a connection with the affordances document that we've written 15:26:46 ... so the functionality and affordances that a RS brings can connect the CG with the WG 15:26:57 ack zhengxu 15:27:03 ... so the WG has to make sure all the plumbing is there to allow these systems to work together 15:27:14 q? 15:27:19 Zheng: the spec needs to be precise and not have conflicts 15:27:36 ... we need a deep discussion about expertise 15:27:50 ... the WG needs to be more specific about the spec 15:28:13 ... many people use Java but how many really read the Java spec? not many -- only those who implement the language 15:28:24 ... how to present the spec to end users? 15:28:43 ... some people who use the spec to define -- the EPUBcheck community 15:28:57 ... if the spec has conflicts, it's difficult for the community to resolve 15:29:11 ... it's important to have a good deep discussion on the spec itself 15:29:38 ... in the meetings it's important, even if we can't solve the specific problem, it's useful to use the time to figure out the approach to resolve it 15:30:09 ... as an example, last week during TPAC, the discussion about EPUB tests was good 15:30:19 ... we can build ideas about how we'll approach that 15:30:26 ack Ralph 15:30:26 Ralph, you wanted to ask about triage 15:30:30 Ralph: @@ 15:31:47 q? 15:32:15 s/@@/it's all about triage -- the WG can own the responsibility to triage the issues 15:32:34 Tzviya: action items from TPAC 15:32:41 q+ 15:32:48 ack liisamk 15:32:50 ... I wasn't able to attend either BG session but I heard they were good and interesting 15:33:18 Liisa: we learned that doing this kind of quick-paced talking about topics that are a bit on the fringe but business-based and wide was super-helpful to people 15:33:23 ... it got people engaged 15:33:35 ... we had bigger audiences that we'd had in previous meetings 15:33:38 ... 90 minutes worked well 15:34:02 ... we've been considering maybe once a quarter having focused single-topic sessions 15:34:18 ... and digging into those in the regular meetings 15:34:31 ... e.g. fonts in Asia 15:34:46 ... we've received some nice notes from people who attended and felt it was helpful 15:34:47 George_ has joined #pbgsc 15:34:56 ... we've gotten some good energy 15:35:01 Tzviya: any actions from WoT? 15:35:09 Liisa: we'll be helping with some use cases 15:35:17 ... this may pull more people in; e.g. on audio stuff 15:35:25 ... we'll definitely be doing some followup with WoT 15:35:53 Cristina has joined #pbgsc 15:36:01 Tzviya: we have a lot of a11y experts in this group but there's a lot of work happening in Web Accessibility 15:36:18 ... we could have other speakers from that work talk in BG meetings 15:36:31 ... Wendy and I did two History of EPUB sessions 15:36:49 ... from that we have an offer to help with a CSS crash course 15:37:00 ... in our survey we see a lot of desire for pixel-perfect layout 15:37:34 ... Jen Simmons was one of the people who created CSS Grid; she did a lot of training to explain that pixel-perfect isn't really what people want on different screen sizes 15:37:50 ... she has offered to do some training to help people understand what modern CSS does 15:38:10 ... since a lot of our users read on phones this should not require huge changes to RS 15:38:28 Zheng: the CG launch kickoff meeting was last week 15:38:41 ... we've started the A11Y TF; Avneesh has sent that email 15:38:56 ... we're looking forward to finding more TF leaders and starting more TFs 15:39:10 ... we'll send email next week 15:39:14 present+ 15:39:19 ... we're preparing updates to the web site 15:39:38 ... I'm contacting folks in Asia to see if we can schedule an Asia-friendly kickoff meeting too 15:39:51 ... I have in mind a Japan TF 15:40:03 ... the content guidelines really need to be updated 15:40:08 q+ 15:40:36 ack ivan 15:41:11 Ivan: we should be very proactive in setting up the EPUB TF; don't just wait for people to come 15:41:42 ... we have to be careful not to put more expectations on the WG; the WG has to do the detailed job of getting the spec right 15:42:15 ... the work on testing is also very detailed 15:42:49 ... we need to build the mechanism for a TF to develop things that the spec should do 15:43:05 ... find 2-3 persons who will drive that community 15:43:28 ... the WG cannot be the place [to develop new things]; it has a lot of detailed work to do 15:44:00 ... the MathML session this week gave me some optimism that maybe we'll have a decent level of MathML implementation in the web core and then eventually in RS 15:44:22 ... what's important for this group is that there is a charter in development for a MathML WG 15:44:38 https://mathml-refresh.github.io/charter-drafts/math-2020.html 15:44:46 ... this relies on a level of MathML that is close to having implementations in the three browser engines 15:45:01 ... it is important to Publishing for that WG to be chartered and be successful 15:45:16 +1000 to the importance of MathML 15:45:24 q? 15:45:32 Tzviya: yes; that was an excellent session; it gave me a lot of hope 15:45:36 q+ 15:45:45 ack wendyreid 15:45:51 Wendy: +1 to optimism 15:46:02 ... it was exciting to see so many people excited about math 15:46:14 ... we should give that charter our full support 15:46:29 ... the virtual breakout sessions were great; I felt I was able to attend more of them 15:46:43 ... there's a lot of energy out there for getting publications closer to the web 15:46:51 ... that made me feel good 15:47:01 ... format-wise, a 3-week long TPAC is exhausting 15:47:08 ... I hope we can be in-person next year 15:47:35 Tzviya: +1; if we have to do this virtually again, we have to find a less exhausting way 15:48:01 ... I have some ideas 15:48:16 ... what other sessions did people attend? 15:48:47 Wendy: Long-form reading, Living Standards 15:49:10 .. .talking about Process is dry but it was interesting to get a better idea of the process for Audiobooks in the next iteration 15:49:21 ... we declared that we will be a "routinely updated standards" 15:49:26 s/ds"/d" 15:49:40 q+ 15:49:41 .. it was nice to get an explanation of what that will really be 15:49:51 ... I think the Process change will be exciting for many WGs 15:49:58 Ivan: including EPUB 15:49:58 q+ 15:50:03 ack ivan 15:50:07 ... Process 2020 will affect the future of EPUB a lot 15:50:39 Tzviya: once you publish something as a REC there can be incremental updates 15:51:25 Ivan: there was a session about the industry around advertisement and how that related to journal publishing 15:51:42 ... there's a bit of a mess in terminology; the term "publishing" is used in many places 15:52:12 Robin Berjon's session, "Media Publishers of the Web, Unite" is a good example of what Ivan is talking about. 15:52:34 ... the European Publishing Council session had a discussion about who represents whom 15:52:36 In fact that's exactly the one he's talking about. 15:52:53 q+ to mention CAT 15:53:07 Avneesh: as Ivan said; the "Media Publishers" session 15:53:14 ... the terminology is confusing 15:53:24 ... how this connects to various distribution mechanisms 15:53:36 ... what ways can we collaborate? 15:53:43 George_ has joined #pbgsc 15:53:55 ... there are similarites in the distribution systems; the supply chains 15:54:12 ack av 15:54:31 ... I feel EPUB 3 is OK in W3C now but to justify Publishing@W3C we need representation from all parts of the publishing industry 15:54:45 Tzviya: Robin's session was about the business models of news publishing 15:54:52 ... it's really not that different from trade publishing 15:54:56 +1 to Tzviya 15:54:58 https://nytimes.github.io/std-cat/ 15:55:07 ... trade doesn't depend on advertising but we do rely on third parties for distribution 15:55:19 ... CAT can apply to EPUB 15:55:28 ... the privacy issues Robin was talking about are very relevant to EPUB 15:55:54 ... David Wood focused a lot on this in the Publishing WG; the trust relationship between the consumer and the publisher 15:56:12 ... this issue occurs in both news publishing and trade publishing 15:56:54 Dave: the NYT relationship with content aggregation is very different from Hachette's relationship with content aggregation 15:57:07 ... NYT has a lot of native traffic to their web site and they have subscribers 15:57:18 ... trade publishers are pretty much completely dependent on content aggregators 15:57:27 ... Hachette doesn't sell books on their web site 15:57:36 (that is not true of all publishers) 15:57:46 ... a lot of the issues Robin raised were about what the world would look like if we do have books online 15:57:56 Cristina has joined #pbgsc 15:57:57 ... how will we evaluate the health of any particular aggregation system? 15:58:17 ... what new web features would be required that something like AMP provides but aren't in a standards? 15:58:26 ... can these be created in a less-centralized way? 15:58:39 ... Robin is proposing some ways to evaluate these technologies 15:58:52 q? 15:58:54 ... but slow publishing is still very different from fast publishing, even if there is common ground 15:58:55 ack me 15:58:55 tzviya, you wanted to mention CAT 15:59:18 https://twitter.com/dauwhe/status/1316095166126710792 15:59:28 Wendy: let's invite Robin to visit! 15:59:44 ... it would be good to liaise with others in the slack #publishing channel 15:59:52 +1000 to inviting Robin, Aram to come to talk with us 16:00:10 ... it would be good to understand where we align and can support them 16:00:28 Please mention the Japanese situation,Trade publishing company also publish magazines, even news paper. 16:02:06 [adjourned] 16:02:18 sorry that I have to leave for another meeting 16:03:40 My time is almost up. Bye. 16:04:22 https://www.w3.org/2020/10/TPAC/HallwayDiscussion.html 16:05:21 zakim, end meeting 16:05:21 As of this point the attendees have been George, Cristina, Ralph, Liisa, Tzviya, Bill, Daihei, Junichi, Avneesh, liisamk, Bill_Kasdorf, jyoshii, Ivan, Garth, zhengxu, wendyreid 16:05:24 RRSAgent, please draft minutes v2 16:05:24 I have made the request to generate https://www.w3.org/2020/10/30-pbgsc-minutes.html Zakim 16:05:26 I am happy to have been of service, Ralph; please remember to excuse RRSAgent. Goodbye 16:05:30 Zakim has left #pbgsc 16:09:13 Liisa: as of Tuesday, Amazon only accepts EPUB for reflow; mobi is out 16:25:30 dauwhe has joined #pbgsc 16:36:19 rrsagent, bye 16:36:28 rrsagent, please make record public 16:36:33 rrsagent, bye 16:36:33 I see no action items