14:55:27 RRSAgent has joined #pbgsc 14:55:27 logging to https://www.w3.org/2018/09/21-pbgsc-irc 14:55:47 Zakim has joined #pbgsc 14:55:57 Meeting: Publishing Business Group Steering Committee 14:56:03 Chair: Liisa 14:56:09 Date: 2018-09-21 14:57:48 RickJ has joined #pbgsc 14:58:15 present+ RIckJ 14:58:32 present+ 14:58:40 Zakim, who is here? 14:58:40 Present: RIckJ, dauwhe 14:58:42 On IRC I see RickJ, Zakim, RRSAgent, jyoshii, Karen, tzviya, Rachel, dauwhe 14:59:08 present+ 14:59:14 regrets+ Rachel 14:59:18 present+ 15:00:52 present+ Karen 15:01:21 liisamk_ has joined #pbgsc 15:02:09 Bill_Kasdorf has joined #pbgsc 15:02:12 present+ liisamk 15:02:18 present+ 15:02:54 jeff has joined #pbgsc 15:02:59 present+ jeff 15:03:08 scribe: Karen 15:03:36 Liisa: I hear echo 15:03:53 q+ 15:03:55 q+ 15:03:56 ...Do we want to start with EPUBCheck funding? Have we seen any commitments 15:03:58 ack Tzviya 15:04:11 Tzviya: I have to check with Richard and George who are keeping track of the funding 15:04:24 ...I have heard of people who have committed anecdotally 15:04:31 ...Rachel spoke with orgs who said they would commit 15:04:39 ...There are amounts coming in; not sure how much 15:04:54 ...Julien @ contacted me about writing a post for a Brazilian blog 15:04:57 garth has joined #pbgsc 15:04:59 ...word is going out, getting some press 15:05:02 present+ Garth 15:05:04 ...keep pushing this. 15:05:16 ...I will ask George to give us an update; would be good to get regular updates 15:05:20 ack Bill_Kasdorf 15:05:31 Bill_Kasdorf: As soon as site went live we kicked into gear 15:05:43 ...Task force members would make personal contacts within orgs they signed up for 15:05:47 ...we also said that the chairs 15:05:54 ...a more formal appeal to go out from the chairs 15:06:02 ...I drafted and sent it out but have not heard yet 15:06:05 Liisa: we will do that 15:06:09 ...had a tough week 15:06:13 ...will need to look at that 15:06:30 Bill_Kasdorf: Just want to make sure if we do it; who will do the sending 15:06:40 ...thinking is should go out from one of the chairs, who would sign it 15:06:48 ...I need to send you the names and emails of contact emails 15:06:58 Liisa: I am happy to send to you contacts if you send me the list 15:07:06 ...in the same vein, I have not sent note to BG 15:07:11 ...we sent to WG and CG this week 15:07:26 ...will do that later today or top of Monday to make top of people's in-boxes 15:07:32 ...and help them understand 15:07:38 ...I went to my boss this week 15:07:45 ...explained why it was important 15:07:55 ...PRH will make a commitment, but need to finalize the amount 15:08:09 ...anything else we want to talk about relative to EPUBCheck funding? 15:08:17 Topic: EPUBCheck Funding 15:08:43 Liisa: I'll put purpose and future of SC later on call 15:08:50 Topic: Promoting TPI and membership levels 15:09:15 Liisa: In order to help Karen, Ralph, Alan we need to maybe work on a document that outlines what participation in each of these three groups entails 15:09:25 ...who are the right kind of people to be involved at each level 15:09:27 q+ 15:09:31 ack Tzviya 15:09:40 Tzviya: One thought I have is to start inviting 15:09:42 q+ 15:09:48 ...some of the evangelists like Bobby Tung 15:09:55 q+ 15:09:56 ...although timing is not great in Taiwan 15:10:06 q+ 15:10:09 q- 15:10:14 q- later 15:10:15 ...Good to communicate what the participation, and talk about exactly what the groups are doing and the distinction between the groups 15:10:23 ack Bill_Kasdorf 15:10:38 Bill_Kasdorf: Want to point out this is an opportune time to talk about the three groups 15:10:47 ...the BG we have talked about in more amorphous terms 15:11:06 ...When I tell people we're fixing EPUBCheck, that's a concrete thing people can get their heads around, and it's important for the echosystem 15:11:13 ...and draft for Web Publications 15:11:23 ...We have concrete things to talk about, not just generalities 15:11:27 Liisa: great point, Bill 15:11:41 Bill_Kasdorf: I bring it up because people wonder if these groups do things 15:11:43 ack Jeff 15:11:48 Jeff: some plus 1s 15:11:51 q+ 15:11:57 ...document you suggested would be helpful 15:12:01 ...Bill's point 15:12:07 ...documents are helpful, but in my mind 15:12:20 ...the core people who are involved every day and every week understand the momentum 15:12:23 q+ 15:12:37 ...the fringes of the old IDPF membership are not as plugged in as they used to be for whatever reason 15:12:46 ...having lots of conversations is important 15:12:52 ...perhaps even more than the document 15:13:00 q+ 15:13:07 ...Working Group is very specific, charter, specs, in what is trying to do 15:13:11 ...BG is less specific 15:13:13 ...and is more open 15:13:31 ...we should be able to tell people this is the watering hole where we discuss very specific things like EPUBCheck 15:13:46 ...but we also talk all together about how to get adoption; how to relate to Amazon 15:14:10 ...I would not call it a formal relaunch but make sure TPIs understand they can come here for conversations and get traction 15:14:15 ack RickJ 15:14:35 RickJ: I would like to make the case for an international audience for this document 15:14:43 ...Southeast Asia, South Africa 15:14:53 ...I want to do the next thing; help me get started and get involved 15:15:01 ...this document could help to address some of that as well 15:15:02 q+ 15:15:06 ack dauwhe 15:15:26 Dauwhe: I think we don't need a doc as much as communications coming out all the time 15:15:34 ...web site should have introduction to all the groups 15:15:46 ...but weekly blog posts, articles describing what is happening would be good 15:15:54 ...BG as focal point for problem-solving in the industry 15:15:59 ...we have not really taken on that role yet 15:16:07 ...as Jeff said having that watering hole 15:16:14 ...we have heard some pain points around the standards 15:16:20 ...we need a place where we can triage issues 15:16:31 ...I am having an issue, but is it a spec, workflow, vendor problem 15:16:35 ...best handled by whom? 15:16:39 ...one of our groups, BISG? 15:16:44 ...that is a useful role we could play 15:16:52 ...and would allow us to be more visible in the publishing world 15:17:02 ack Liisamk 15:17:14 Liisamk: I think we needed to be better about communications 15:17:27 ...suggested the document to help us be clearer about the messaging when we're out there talking 15:17:31 ...that personal 1:1 is important 15:17:43 ...we have all come to this in different ways and have made this commitment for different reasons 15:17:50 ...Personally, talking to my management about the work 15:17:55 ...and importance of putting money 15:18:07 ...reaction of 'you do this work for Liisa' not PRH 15:18:14 ...and I said 'no, I do it for PRH' 15:18:25 q+ 15:18:25 ...help people to make that case in their own organizations is a bit of what I would like to get to 15:18:33 ...a good argument for why your org should support 15:18:42 scribenick: dauwhe 15:18:47 Karen: we need both, in my experience 15:19:08 ... to rick and liisa's point, we do need some document with talking points that talks about the digital transformation 15:19:25 ... and how you get engaged in an org like w3c, and how to take advantage of all these things 15:19:33 ... there's a high-level opportunity here 15:19:46 ... and we need to talk about what each of the groups do 15:19:59 ... we should go through the exercise of getting these talking points down 15:20:04 ... and then how to communicate them 15:20:13 ... there's a huge need for education and understanding 15:20:23 ack Bill_Kasdorf 15:20:27 ack Karen 15:20:30 scribenick: Karen 15:20:39 Bill_Kasdorf: as you explain to your management 15:20:44 ...first target is former IDPF members 15:20:53 ...we want all publishers 15:21:06 ...but let's not let Jeff's comment that Amazon joined W3C get lost 15:21:09 ...that is significant 15:21:10 q+ 15:21:16 ...I'm sure we have to be careful about what we need to say 15:21:23 ...I am not advocating public things as much 15:21:31 ...we don't want to alienate Amazon 15:21:39 ...but personal conversations like you had with your management 15:21:44 ...that is an attention getter 15:21:49 ...Amazon is at the table 15:21:56 Liisa: But Amazon is not at the table yet 15:22:02 ...I told their book people they have joined 15:22:07 ...they are not ready to sit at the table 15:22:09 ...they are interested 15:22:14 q- 15:22:23 ...Jeff has good point, to carefully pull their book people in and back to the center 15:22:28 ...that is a tough nut to crack 15:22:36 Bill_Kasdorf: that is a good reality check 15:22:47 ...and the accessibility work is relevant to someone 15:22:55 ...at least a movement to get them more engaged 15:23:02 Liisa: Absolutely 15:23:11 ...anyone else want to jump in on this topic? 15:23:14 ...as a next step 15:23:18 ...I am going to commit to 15:23:26 ...after I have gotten Bill his doc and sent to BG 15:23:39 ...I am going to start a document that we can collectively edit; I'll send a Google doc link 15:23:40 +1 15:23:51 ...I think to Jeff's point of getting Amazon more engaged 15:23:57 ...we can talk about whether there is any chance 15:24:04 q+ 15:24:11 q+ 15:24:11 q+ 15:24:11 ...where we can do the one thing they want - warn people when their images are not big enough 15:24:14 q+ 15:24:19 ack RickJ 15:24:31 RickJ: is editing for the we the BG as a whole or this committee? 15:24:44 Liisa: I think we start here and then take it to the bigger group 15:24:47 ack Tzviya 15:24:58 Tzviya: you mentioned that Amazon has an issue 15:25:06 ...can you ask them to log it? 15:25:15 Liisa: Can I do it on their behalf? Is that ok with you? 15:25:19 Tzviya: yes 15:25:29 Liisa: let me talk to them and see if they will let me do that 15:25:36 ack Dauwhe 15:25:47 Dave: ....has not been best practices 15:26:07 ...pre-flight; normative statements in the specs; concern that EPUB is used to enforce vendor guidelines for ebooks 15:26:13 Liisa: I hear you and share that concern 15:26:23 ...maybe think about what the marketplace needs from EPUBCheck 15:26:41 ...does it become a more normative useful tool if it incorporates those processes that we all do on the fly 15:26:43 ack Jeff 15:26:51 q? 15:27:19 Jeff: I want to tiptoe into comments about Amazon and EPUBCheck 15:27:26 ...if there is something specific Amazon wants 15:27:34 ...and we have an EPUBCheck funding campaign 15:27:34 q+ 15:27:41 ...is there a way to size the cost of what they want 15:27:46 q+ 15:27:51 ...and get them started as participants by contributing 15:27:56 Liisa: I would think there is 15:27:59 ack Tzviya 15:28:09 Tzviya: If they are limiting image size 15:28:14 ...and others are not 15:28:23 ...then we are validating the spec 15:28:38 ...error warning would be triggered for Rick unless we have a less specific error warning 15:28:48 Liisa: They want biggest image files possible 15:28:54 ...they have a minimum; at least this big 15:28:54 q+ 15:29:02 Tzviya: That seems a bit more likely 15:29:06 ...we have opposite 15:29:16 ...people could have bad images and they still want to get them through 15:29:19 ...have legacy titles 15:29:24 ...still have a problem; it's not a spec 15:29:25 q+ 15:29:30 ...validation that other vendors don't have 15:29:46 ...need to create a Kindle-specific warning and require other vendors to ignore it if they choose to 15:29:56 Liisa: Or we engage more of the vendors and come to a standard about it 15:29:59 ack dauwhe 15:30:08 Dave: I am not seeing our role for the quality of content 15:30:21 I have to leave for another meeting. Sorry. 15:30:25 ...sounds further from mission of W3C to enforce private companies' quality control concerns 15:30:33 ...I see need for a tool, but don't see that as EPUBCheck 15:30:40 ...make sure content follows the EPUB spec 15:30:50 ...foresee large technical difficulties 15:30:58 ...see if Amazon can swap out PDF or image files 15:31:12 ...we are drifting into vendor-specific workflow territory 15:31:16 ack Garth 15:31:29 Garth: I think an info message from EPUBCheck would be overall good fo industry 15:31:37 ...I would be happy to throw them a bone to get them more involved 15:31:45 ...that would not be specific to Amazon 15:31:55 ...agree we need to be wary on vendor-specific stuff 15:31:58 ...this may be vague 15:32:02 q+ 15:32:07 q+ 15:32:09 ...but it may be done in EPUBCHeck and I woudl not oppose it 15:32:14 ack Bill_Kasdorf 15:32:29 Bill_Kasdorf: I agree with Garth; we do have best practices under development 15:32:33 ...other thing to point out 15:32:52 ...Accessibiltiy checking tools report errors and warnings and it is very useful 15:33:01 ...they say this thing does not align with best practices 15:33:11 ...doesn't say it's illegal or a violation 15:33:25 ...not uncommon for that kinds of checking tool to enforce conformance and good practices 15:33:32 ...admit that would be a next generation EPUBCheck 15:33:36 Liisa: I totally agreet 15:33:44 Bill_Kasdorf: We could add the image thing 15:33:47 ack Tzviya 15:33:57 Tzviya: EPUBCheck already does errors and warnings 15:34:05 ...in terms of low res images 15:34:10 ...think about medical publishing 15:34:15 ...a lot of those are not high res 15:34:22 ...I get flack from Amazon about the quality of images 15:34:26 ...they are not improvable 15:34:31 q+ 15:34:37 ...they are not clear images because the magnification is 1000 percent 15:34:48 ...we would need more detail about what Amazon wants before we say yes or no 15:35:02 Garth: I don't think we want to do machine learning on high res or fuzzy images 15:35:05 ack dauwhe 15:35:23 Dave: If book has warning in EPUBCheck it cannot get into the supply chain in US publishing industry 15:35:29 ...if not an error or warning 15:35:39 ...gate-keeping for content feels like a bad place for W3C to be 15:35:48 Liisa: complete agree it should be informational not a warning 15:36:06 Liisa: responding to your comment, Tzviya, why I have been arguing why we need to tag an image 15:36:19 ...tell everybody it's as good as it gets; accept it 15:36:27 ...don't put it on the page that it's low res 15:36:35 ...Amazon would be happy to accept if we tag it in some way 15:36:55 Tzviya: Do we have summary discussion about details tagging? I would like to invite them as a guest 15:37:09 Dave: that sounds like in-line metadata about image quality 15:37:15 ...stuff you don't want to expose to the end user 15:37:24 s/summary discussion about details/discussion about summary and details 15:37:24 Liisa; yes, that was the problem about summary and detail 15:37:30 ..I cannot let user see this 15:37:34 ...space, I cannot do things 15:37:44 ...It's Donald Trump from scan of paper from 1970s 15:37:56 ...they asked me to have images re-taken for that book 15:38:11 ...I explained I could not get him back with his exwife or make him younger again 15:38:27 Bill_Kasdorf: Maybe WashPost would like to get involved 15:38:34 Liisa: I like the EPUB fuzzy 15:38:40 Tzviya: There are ways to obfuscate 15:38:46 Dave: and schema, but that may take a while 15:38:53 Liisa: all right 15:38:58 ...Let's get back to the agenda 15:39:11 ...are there any specific things we want to take to the BG next week? 15:39:11 i will miss the meeting on tuesday 15:39:18 Topic: Agenda items for BG call next week 15:39:22 BillK: Fundraising 15:39:40 Liisa: Do we want to talk about image quality topic 15:39:50 ...to be considered for a future version? 15:40:02 Tzviya: It's fundamentally a change in the direction of EPUBCheck 15:40:08 ...we have not really come to agreement in this group 15:40:20 q+ 15:40:36 Liisa: what I am asking is if we should ask BG if they are grappling on how to deal with images across reading systems 15:40:40 q+ 15:40:42 ...or would you be interested in tools 15:40:49 ...or if others say they have it solved 15:40:53 ...But I think it's an issue 15:41:00 ...There is getting the backlist up to speed 15:41:14 ...and making sure the front list will work in that interim space for all the retailers you send to 15:41:21 ack liisamk_ 15:41:24 ...it is tough; not an easily definable space 15:41:30 ...I think there are things we can share 15:41:31 ack Garth 15:41:49 Garth: I don't have an issue with fuzziness 15:42:16 ...interesting discussion today, but wondering if it belongs in SC or be in BG because it's interesting stuff 15:42:28 ...and makes people realize it's TPI topic of value 15:42:32 ack dauwhe 15:42:39 Dave: a great topic for the BG agenda 15:42:39 q+ 15:42:46 Liisa: what else do we have on the agenda for next week 15:42:48 ack JEff 15:42:56 Jeff: one thing we may want to share somewhere 15:43:09 ...Dominique Hazael-Massieux is as W3C staff member for NDN 15:43:16 Fundraising update, I’d presume (for agenda for BG). 15:43:18 ...basically used to be the Mozilla Developer Network 15:43:20 s/NDN/MDN 15:43:21 s/NDN/MDN/ 15:43:29 ...he has been working to get their agreement to put things on MDN 15:43:47 ...related to developers not necessarily browser technologies like what Mozilla usually implements 15:43:52 https://developer.mozilla.org/en-US/docs/Related 15:43:55 q+ 15:43:55 ...but other web technologies that are used by others 15:44:10 ...would be good for Dom to share with BG on what his conversations have been and how to take that forward 15:44:19 Liisa: Could someone who can explain it join the call? 15:44:29 Jeff: Dom would do it; don't know if he is available 15:44:36 ack Tzviya: I have spoken with Dom about this 15:44:41 ...forgot to put on the agenda 15:44:50 ...I spoke extensively about what would be needed to add EPUB 15:44:53 ...dropped a link in 15:44:59 ...we still need to get to TPI discussion 15:45:16 ...we could put on the agenda for next time, or I could talk about what would be involved in documenting MDN 15:45:25 Liisa: Do you want to talk about it here before taking to the BG? 15:45:40 Tzviya: there is significant resource requirement; think we should discuss here first 15:45:44 Liisa: ok 15:45:56 ...any further comments for next week [agenda] for the BG 15:46:02 ...I want to raise a conversation about pagination 15:46:16 ...an interesting business level conversation to have; will likely push into best practices 15:46:24 ...from content and reading system standpoints 15:46:29 ...when you move things out of order 15:46:39 ...paginate not in print but inserted in middle of book 15:46:44 ...if people are addressing those issues 15:46:53 ...we have been looking at issues coming up from reading systems 15:47:01 ...think we are not alone in some of the questions that have been raised 15:47:23 Dave: by pagination, you mean expressing numbers in EPUB when they are not exact analogs? 15:47:27 Liisa: exactly 15:47:34 ...point made about different kinds of publishers 15:47:49 ...this may be different for different people; where is it needed and where is the preciseness of it needed 15:47:53 ...In time we have left 15:48:00 ...shall we talk about role of this group? 15:48:11 Topic: Role of Publishing Steering Committee 15:48:16 ...do we need to formalize it 15:48:22 ...put our thoughts on paper 15:48:24 q+ 15:48:27 ...now is time to jump in 15:48:29 ack Tzviya 15:48:48 ack dauwhe 15:48:56 Dave: I have 15:48:59 ...not entirely clear to me 15:49:03 ...what the role of the SC is 15:49:11 ...this is in some ways a holdover from the IDPF board 15:49:22 ...it was a literal board of directors that had many things it has to do 15:49:33 ...so the environment around that board has changed dramatically since the merger 15:49:35 q+ 15:49:40 ...the way these calls have been going is some combination 15:49:45 ...of working on agendas for BG meetings 15:50:03 ...and having substantive conversations about issues important to the industry that don't have to be restricted 15:50:10 ...I have impulse to try things without a SC 15:50:19 ...seems mission of BG is to provide coordination and leadership 15:50:28 q+ 15:50:30 ...and work on intneraction between other groups 15:50:38 ...feels like we may some duplication of effort 15:50:40 ack Barth 15:50:44 s/Barth 15:50:46 ack Garth 15:50:51 Garth: I agree with Dave 15:50:58 ...but cannot refer to merger as complete 15:51:06 ...it is still embroiled in litigation 15:51:22 ...we made a substantial change to be heads of working groups and task forces 15:51:43 ...I don't think we want SC to go away right now because merger is not complete 15:51:56 ...but SC should do as little as possible and put the bulk of the stuff into the BG proper 15:52:00 q+ 15:52:01 ack Bill_Kasdorf 15:52:10 BillK: mainly Garth's point 15:52:19 ...and observation that SC does a lot of the work and BG is more passive 15:52:24 q+ 15:52:36 ...that ambiguity of who approves decision on who gets the EPUBCheck development work 15:52:39 ...the SC did all that 15:52:49 ...nothing is really being done by the BG; it's all being done by the SC 15:53:05 ...does not seem like that was the original idea for the BG; that's the formal group in the W3C 15:53:12 ack Liisamk 15:53:30 Liisamk: as Garth said, the SC is the coordination among the groups 15:53:42 ...ask if we should bring certain items forward to other groups 15:53:47 ...we have strong opinions 15:54:01 ...kind of nice to talk through our opinions here so we don't overwhelm others 15:54:08 q+ 15:54:08 ...would we drown out other voices 15:54:16 ...how can we pull other voices into the conversations 15:54:20 ...put our feelings aside 15:54:24 ...seed conversations along 15:54:38 ...get the BG actually active and not overwhelm them with being a second meeting of all of us 15:54:43 ack dauwhe 15:54:51 Dave: I am worried about the flip side of that 15:55:08 ...how do we get people engaged if the interesting conversations are happening in the SC 15:55:20 ...other things happen in a group that you are not a member of 15:55:30 Liisa: I don't think we stop people from discussing 15:56:01 Dave: EPUBCHeck conversation would be a good one; don't think we're helping by insulating them from those discussion 15:56:10 ack Tzviya: maybe we are overprotective 15:56:22 ...this conversation about what EPUBCheck is and should we expand it, and resources is interesting 15:56:30 ...maybe we have these conversations with the larger group 15:56:36 ...WG has these kinds of conversations 15:56:48 ...having them twice is not as interesting the second time 15:56:52 +1 to tzviya 15:56:53 Liisa: anybody else? 15:57:00 q+ 15:57:06 ack Tzviya 15:57:10 ack dauwhe 15:57:17 Dave: Just briefly mention that the SC 15:57:28 ...is something that does not fit neatly in the W3C process right now 15:57:33 ...the BG makes all the decisions 15:57:40 ...we would be fine with the BG 15:57:44 Liisa: I honestly don't 15:57:50 ...I explained this to Jeff and Karen 15:58:02 ...I have tried over last year to see what it's like to just be a member not of BG 15:58:11 ...and not pay attention to other two groups 15:58:18 ...where I find out about the other groups is here 15:58:24 ...You don't bring them to the BG 15:58:27 q+ 15:58:41 ...and it makes me realize we need to figure out a better coordination 15:58:43 ...if not SC 15:58:48 ...we'll need to figure out where it is 15:59:01 ...We came here understanding that this is a bit of an experiment 15:59:10 ...not exactly the same model W3C has had 15:59:15 q+ 15:59:28 ...I am concerned we are effective and no one wastes their time 15:59:31 ack dauwhe 15:59:48 Dave: brings up communications and more topics in the BG and keep all participants informed 15:59:49 ack Jeff 15:59:56 Jeff: I don't have a strong opinion about this 16:00:02 ...the way the non-working groups 16:00:12 ...work is more for team to stay out of 16:00:24 ...but I'm hearing both sides and hearing that BG is where nexus of conversation should happen 16:00:33 ...and others say they are not happening is they are in SC instead 16:00:44 ...one possible way forward is to keep SC for a period of time 16:00:57 ...those who think conversations should be in BG, then be encouraged to do so 16:01:08 ...and they will have proved their point and SC is no longer needed 16:01:18 ...if not, we keep SC as a central point of coordination 16:01:24 +1 to Jeff 16:01:26 @: I like that 16:01:31 +1 16:01:41 Liisa: We are at over our time 16:01:57 ...if anybody thinks of anything else for BG agenda next week, let me know. I will send out agenda this afternoon 16:02:02 Garth: thanks Liisa and Karen 16:02:08 rrsagent, draft minutes 16:02:08 I have made the request to generate https://www.w3.org/2018/09/21-pbgsc-minutes.html Karen 16:43:48 Karen has joined #pbgsc 17:00:43 jeff has joined #pbgsc 17:31:16 RRSAgent: make logs public 17:33:10 rrsagent, byw 17:33:10 I'm logging. I don't understand 'byw', tzviya. Try /msg RRSAgent help 17:33:16 rrsagent, bye 17:33:16 I see no action items