15:37:15 RRSAgent has joined #pwg 15:37:15 logging to https://www.w3.org/2018/03/12-pwg-irc 15:37:16 rrsagent, set log public 15:37:16 Meeting: Publishing Working Group Telco 15:37:16 Chair: Tzviya 15:37:16 Date: 2018-03-12 15:37:16 Regrets+ evan, rkwright, rdeltour, josh, nickruffilo 15:37:16 Agenda: https://lists.w3.org/Archives/Public/public-publ-wg/2018Mar/0026.html 15:37:17 ivan has changed the topic to: Meeting Agenda 2018-03-12: hhttps://lists.w3.org/Archives/Public/public-publ-wg/2018Mar/0026.html 15:55:00 dkaplan3 has joined #pwg 15:57:02 toshiakikoike has joined #pwg 15:57:22 present+ 15:57:33 present+ 15:58:09 evan has joined #pwg 15:58:18 laurab_ has joined #pwg 15:58:52 jbuehler has joined #pwg 15:58:54 present+ dauwhe 15:59:02 present+ 15:59:14 present+ 15:59:24 present + laurab_ 15:59:31 cmaden2 has joined #pwg 15:59:55 present+ wolfgang 16:00:12 mateus has joined #pwg 16:00:22 present+ 16:01:19 zakim, pick a victim 16:01:19 Not knowing who is chairing or who scribed recently, I propose dauwhe 16:01:31 lsullam has joined #pwg 16:01:36 pkra has joined #pwg 16:01:36 Teenya has joined #pwg 16:01:39 scribenick: dauwhe 16:01:44 jasminemulliken has joined #pwg 16:01:44 Presetn+ 16:01:45 present+ 16:02:00 clapierre has joined #pwg 16:02:00 present+ 16:02:01 garth has joined #pwg 16:02:01 present+ 16:02:07 present+ 16:02:07 present+ Garth 16:02:12 tzviya: shall we approve the minutes? 16:02:12 https://www.w3.org/publishing/groups/publ-wg/Meetings/Minu5-tes/2018/2018-03-05-minutes 16:02:15 Vlad has joined #pwg 16:02:15 Bill_Kasdorf has joined #pwg 16:02:17 laudrain has joined #pwg 16:02:20 present+ 16:02:24 present+ 16:02:25 present+ 16:02:35 ... minutes approved 16:02:48 ... anyone new joining the call this week? 16:03:25 present+ Chris_Maden 16:03:29 tzviya: let's review some F2F logistics/agenda stuff 16:03:43 marisa has joined #pwg 16:03:54 https://docs.google.com/document/d/1Qe8Q8wMC1LKy_-JO-UCy8bFw4D4VN0si1Q5EPW9c-rY/edit# 16:03:55 present+ pkra 16:03:56 present+ George 16:04:06 caller 04, could you mute yourself? 16:04:11 present+ 16:04:15 Topic: F2F meeting 16:04:17 tzviya: here's a link to F2F info 16:04:21 Hadrien has joined #pwg 16:04:25 ... please propose agenda items there 16:04:26 present+ 16:04:32 ... please add your name if you're attending 16:04:58 ... Wendy said she will send a link so we can book on our own, but that hasn't happened yet 16:05:04 ... but we need to talk about the agenda 16:05:05 George has joined #pwg 16:05:17 ... we need to think of deliverables for before the F2F 16:05:19 present+ 16:05:24 present+ George 16:05:34 ... one of the goals of the task forces was for them to accomplish something before the F2F 16:05:36 duga has joined #pwg 16:05:49 present+ 16:05:52 ... Jasmine/Matteus, can you give us an overview of what you hope to accomplish before the F2F? 16:06:09 s/Matteus/Mateus 16:06:11 mateus: one of our goals is to review open issues, and identify ones that can close 16:06:20 ... and then look at tech requirements for open issues 16:06:31 MustLazMS has joined #pwg 16:06:31 ... and then have a draft towards completion of the affordances section 16:06:35 BenSchroeter has joined #pwg 16:06:44 present+ 16:06:45 jasminemulliken: I don't have the issue link 16:06:49 present+ 16:07:04 mateus: I have the link, just a moment 16:07:06 https://github.com/w3c/wpub/labels/topic%3Aaffordances 16:07:07 https://github.com/w3c/wpub/issues?q=is%3Aissue+is%3Aopen+label%3Atopic%3Aaffordances 16:07:16 jasminemulliken: and we hope to do a call this week 16:07:23 mateus: we have a few times that might work 16:07:48 ... having a call this week would make sense, tuesday or wednesday 16:08:00 ivan: I am supposed to set up a webex? 16:08:07 mateus: yes, I'll confirm with you 16:08:18 zheng_xu has joined #pwg 16:08:21 tzviya: there were problems with doodle and DST 16:08:23 present+ 16:09:26 bigbluehat: the WAM task force will work on anything tagged with that label 16:09:36 https://github.com/w3c/wpub/labels/topic%3Amanifest 16:09:42 ... we're mostly focusing on direct requests 16:10:04 ... especially things that have applicability outside publishing 16:10:18 q? 16:10:23 ivan: did I miss a call for timing? 16:10:48 bigbluehat: there's a doodle poll; there will be an email about a call soon 16:11:00 ... we'll go through the list on the first call 16:11:17 JunGamo has joined #pwg 16:11:18 ... then work on github, then a follow-up call 16:11:31 tzviya: anything else as a deliverable? 16:11:42 (silence) 16:11:44 present+ gpellegrino 16:11:53 regrets+ gpellegrino 16:11:58 tzviya: last week, ivan put together a list of issues that were closable 16:12:08 Topic: closing issues 16:12:08 ... we can spend the rest of the meeting closing issues 16:12:11 https://gist.github.com/iherman/581247543c670faa30f1ab89ff1c11eb 16:12:47 ivan: the low-number issues were the ones that led to long discussions 16:12:56 ... my tendency would be to close those 16:13:47 tzviya: I don't think it's a good use of time to read through every comment of issue 1 :) 16:14:01 timCole has joined #pwg 16:14:30 I've been following on github so I assume I have. 16:14:43 tzviya: I don't think it's a good use of time to read through the list 16:14:57 garth: or do we want to close them and wait for complaints? 16:15:07 tzviya: I don't think it's productive for me to read issues 16:15:25 https://gist.github.com/iherman/581247543c670faa30f1ab89ff1c11eb 16:15:37 garth: read the issues not the topics? 16:15:45 +1 16:15:46 +1 16:15:48 +1 16:15:51 +1 16:15:54 +1 16:15:54 +1 16:15:56 +1 16:15:58 +1 16:15:59 +1 16:15:59 tzviya: Issue 1; do we agree to close it? 16:16:00 +1 16:16:02 +1 16:16:07 +1 16:16:12 BillM has joined #pwg 16:16:16 tzviya: the other issue is 129??? 16:16:22 https://github.com/w3c/wpub/pull/129 16:16:43 dkaplan3: ivan has made notes about why these are closable 16:17:15 Hadrien: Ivan and myself has introduced new language in the draft to deal with this 16:17:29 tzviya: I'm seeing agreement to close #1 16:17:37 Avneesh has joined #pwg 16:17:59 q+ 16:18:05 ack duga 16:18:17 present+ 16:18:19 duga: do all these issues have your summaries? 16:18:22 ivan: yes 16:18:31 Resolved: close issue 1 16:18:35 topic: issue 2 16:18:56 tzviya: navigating a web pub; this is obsoleted by the current infoset and the affordances discussion 16:19:01 ... it's covered in our doc 16:19:01 sorry for joining late 16:19:08 +1 16:19:08 +1 16:19:09 +1 16:19:12 +1 16:19:12 +1 16:19:12 +1 16:19:13 +1 16:19:13 +1 16:19:14 proposed closing 16:19:14 +1 16:19:15 +1 16:19:15 +1 16:19:16 +1 16:19:26 +1 16:19:32 subtopic: issue 9 16:19:38 resolved: close issue 2 16:19:42 topic: issue 9 16:19:44 +1 16:19:53 tzviya: machine readable navigation 16:20:02 +1 16:20:10 ... the comments lost focus, let's close and creaate more focused issues 16:20:19 s/aa/a/ 16:20:33 ... we should look more closely 16:20:45 ... Avneesh, could you look at this and see if it needs new issues 16:20:53 +1 to closing issue and opening specific tickets 16:20:56 Avneesh: it has grown in too many directions 16:21:17 bigbluehat: there's still tension about where things come from 16:21:29 ... the machine-readable-navigation things 16:21:43 ... some like nav stuff from HTML, others want it expressed in JSON 16:21:58 tzviya: that has been picked up in other issues around webidl 16:22:03 bigbluehat: I'll try to link back 16:22:15 +1 to closing 9 & reopening focused issues or moving discussions to other open issues 16:22:27 +1 to closing 16:22:29 +1 16:22:31 resolved: close 9 and open new issues if needed 16:22:32 +1 16:22:39 +1 16:22:43 topic: issue 13 16:22:43 +1 16:23:00 tzviya: associating manifest with pub resources 16:23:02 +1 16:23:06 +1 16:23:14 +1 16:23:16 +1 because WAM TF 16:23:17 +1 16:23:21 proposed: close the issue 16:23:27 +1 16:23:30 ... any comments? 16:23:30 +1 16:23:31 +1 16:23:35 +1 16:23:58 Good, I was afraid of running out of +1s 16:24:10 +1 to that 16:24:12 ivan: let's discuss, but no need for +1s in IRC 16:24:18 resolved: close the issue 16:24:26 topic: issue 22 16:24:44 tzviya: manifest requirements for offline 16:24:56 ... the issue has lost focus 16:25:08 ... we should go through and make sure everything necessary is covered 16:25:14 Topic: issue 22 16:25:20 ... jasminemulliken, can this be part of the affordances task force 16:25:24 jasminemulliken: I don't see why not 16:25:45 resolved: issue 22 will be closed by Jasmine, and if necessary new issues opened 16:26:02 topic: issue 23 16:26:16 tzviya: must manifest include secondary resources? 16:26:31 ivan: the secondary resources are part of the infoset 16:26:56 resolved: close issue 23 16:27:04 topic: issue 29 16:27:17 tzviya: do all docs in reading order have to be reachable from TOC 16:27:32 ... this is covered in our current draft 16:27:33 s/29/39/ 16:28:11 tzviya: any comments about closing this issue? 16:28:30 resolved: close issue 39 16:28:40 topic: issue 69 16:28:59 tzviya: this is now a separate CG for Media Overlays 16:29:29 ... marisa, can you drop a link to the CG? 16:29:36 resolved: close issue 69 16:29:37 https://www.w3.org/community/sync-media-pub/ 16:30:31 I’m in and not a DAISY member… 16:30:32 resolved: close issue 70 16:30:38 topic: issue 72 16:30:39 q+ 16:30:46 tzviya: mathml and web publications 16:31:05 ack timCole 16:31:07 ... the issues of math are not in scope for this WG 16:31:09 I would suggest MathML is a best practices issue 16:31:21 timCole: I agree with closing it, but am concerned with the language 16:31:29 ... mathML being a problem is the implication 16:31:43 ... it sounds like it's being closed with prejudice 16:31:44 q+ 16:31:51 ack George 16:31:53 tzviya: timCole, can you add a comment to the issue? 16:31:59 George: I agree it should be closed 16:32:16 ... we may find that the CG on best practices will bring us solutions 16:32:18 q+ 16:32:24 ack zheng_xu 16:32:42 DIAGRAM Center is working on this as well as a best practice and will share our solution with you all soon. 16:33:09 will type later 16:33:10 mattg has joined #pwg 16:33:33 resolved: close issue 72 but Tim Cole will add comments 16:33:37 topic: issue 74 16:33:51 tzviya: infoset should not include specialized metadata 16:33:58 ... which was a bit of a misunderstanding? 16:34:08 ... we can link to any metadata in our infoset 16:34:12 ... any comments? 16:34:23 ... the proposal is to close because it is included in our current infoset 16:34:29 q+ 16:34:33 ack Hadrien 16:34:57 Hadrien: the concept is that we'll be linking to other metadata, but we haven't discussed how 16:35:11 ... will it be handled by the manifest? there's work on how we handle that. 16:35:25 ivan: correct. but that was not how the issue was raised. 16:35:34 tzviya: we need a more specific issue. 16:35:40 ivan: do we have it yet? 16:36:11 tzviya: the issue we've been talking about with alternate rendering is similar, but not the same 16:36:24 ... if the issue you mentioned isn't open yet, open one 16:36:35 Hadrien: we could use the same element to solve both of them 16:36:44 tzviya: let's open separate issues 16:36:58 ivan: the one in 74 was in a much more general level, the infoset level 16:37:14 ... on that level we have consensus that we can refer to ONIX or whatever 16:37:21 ... the details are still to be worked out 16:37:26 ... but 74 is not about that 16:37:47 tzviya: let's open a new issue, and to see the problem stated. if there's a proposed solution it can be a comment 16:38:02 Hadrien: yes, but we do need the big picture 16:38:13 ivan: isn't that part of the serialization details 16:38:20 Hadrien: it's more related to the infoset 16:38:46 tzviya: I would prefer to see the solution separate from the question 16:38:53 q+ 16:39:30 Hadrien: we've said we won't have specialized metadata, but we havent said how to point to the metadata 16:39:32 ack dkaplan 16:39:57 dkaplan3: I like the separation; hadrien's concerns can be addressed by linking... "see main justification for this at link X" 16:40:40 tzviya: if you want to leave the issue open, leave comments 16:40:46 Hadrien: I can open a new one 16:41:04 resolved: close issue 74 16:41:16 tzviya: and Hadrien will open a new issue on how to do this 16:41:22 topic: issue 121 16:41:31 tzviya: this is in the current draft 16:41:45 ivan: we should have closed this when the PR for the lifecycle section was accepted 16:42:14 resolved: close 121 16:42:25 topic: issue 124 16:42:37 tzviya: expressing metadata in multiple language 16:42:58 Comment about https://github.com/w3c/wpub/issues/72 16:43:13 dauwhe: we're closing 124 for the same reason as 121? 16:43:15 ivan: yes 16:43:21 resolved: close issue 124 16:43:58 ok I just type 16:44:20 so I hope can know where will this problem go? 16:44:38 Because we have a lot of problem of supporting MathML 16:44:44 q+ 16:44:48 ack bigbluehat 16:44:55 ack Bill_Kasdorf 16:44:57 done 16:45:24 Bill_Kasdorf: my suggestion is that DAISY's work is relevant, and about to be public, and belongs in the best practices work of the CG 16:45:27 q+ 16:45:31 ack Avneesh 16:45:55 Avneesh: MathML is the current state, it is the best way for a11y, and belongs to EPUB3CG 16:46:10 ... for PWG we just need to keep an eye on math in general; this issue can be closed 16:46:27 Yes. Thanks tzviya 16:46:35 tzviya: I think zheng_xu is speaking as a reading system developer for supporting math ml rather than supplying mathml 16:46:37 q+ 16:46:41 ack ivan 16:46:53 ivan: the point is that, this WG cannot solve this problem 16:47:09 ... I agree it's a major problem, there are discussions outside this WG, I hope they lead somewhere 16:47:23 ... but it can't be this WG's job to solve the problem. that's why the issue should be closed. 16:47:30 tzviya: agreed. 16:48:23 topic: issue 4 16:48:37 tzviya: this is a precurser to the affordances task force 16:48:43 ... we've revisited over and over 16:48:49 ... I think it's a good idea to close 16:49:12 ... and the affordances TF will make us more comfortable with this; the TF can see if there's anything useful in here 16:49:16 jasminemulliken: we'll take a look 16:49:23 s/precurser/precursor/ 16:49:45 q? 16:49:48 tzviya: any objections to closing this, and opening new issues as affordances? 16:49:56 resolved: close issue 4 16:49:59 topic: issue 5 16:50:12 tzviya: how to identify a WPUB and its components 16:50:26 ... tim handled this with his doc, and there's stuff in the infoset 16:50:37 ... I think we're covered here? 16:50:44 q+ 16:50:47 ack timCole 16:50:48 q+ 16:51:08 timCole: I think there are open aspects of this issue, but I don't think it's settled 16:51:34 tzviya: can you go through this and open new issues? 16:51:40 ... over next 2-3 weeks? 16:52:07 ack bigbluehat 16:52:53 bigbluehat: I've been posted related thoughts to PWPUB repo... this identification of the parts as well as the whole matters 16:53:22 ... the google web package formats doesn't provide inter-pub links 16:53:34 tzviya: any other comments? 16:53:52 resolved: Tim Cole to review, and close after perhaps opening new issues 16:53:53 https://github.com/w3c/wpub/issues/35 16:54:07 topic: issue 35 16:54:31 tzviya: this does seem to be different than our current proposal 16:54:35 q+ 16:54:38 ivan: dauwhe and bigbluehat started this 16:54:39 avk bigbluehat 16:54:44 ack bigbluehat 16:55:09 bigbluehat: I've continued to experiment with this in Dave's html-first repo, on how to enable to have browsers discover this progressively 16:55:27 ... it's helped inform what I'm looking at with the WAM task force 16:55:32 sorry, have to run for another meeting 16:55:40 ... if we hoist a WP out of an HTML doc 16:55:55 ... but HTML is the foundational layer we build on 16:56:09 ... with hypermedia as a foundational affordance 16:56:36 ... to the issue at hand, that would be the operating understanding expressed in terms of a fallback 16:56:51 ... I'd love to explore this more as a group 16:57:17 ... we still have yet to touch on DOM affordances, and how a web publication might understand itself and how it might be influenced by JS 16:57:41 ... I would like to explore this, and have demos before the F2F 16:57:47 ivan: what do we do with this issue? 16:57:52 bigbluehat: I'm ok with closing it 16:58:00 ... it's still a proposal 16:58:01 regrets+ laurent 16:58:23 bigbluehat: if rebooting with a fresh start would be helpful, than I'm ok with it 16:58:32 tzviya: ivan proposes to close, is that OK/ 16:58:43 q? 16:58:45 resolved: close issue 35 16:59:05 https://docs.google.com/document/d/1Qe8Q8wMC1LKy_-JO-UCy8bFw4D4VN0si1Q5EPW9c-rY/edit# 16:59:07 garth: the closing homework for non-chair-folk is to comment in the document we looked at initially for agenda items 16:59:41 George: I'll be at Web Accesibility Initiative F2F next week on guidelines 3.0 development 17:00:02 ... and I'll be emailing Avneesh on points we want to get into their roadmap that are important to publishing 17:00:14 s/Accesibility/Accessibility/ 17:00:21 Jeff: another comment about #72 17:00:21 present+ mattg 17:00:32 ... I can understand that MathML isn't in the scope of the wg 17:00:32 present+ Tim_Cole 17:00:44 ... what group or task force should we work with? 17:00:50 ... we have lots of publishers using MathML 17:01:03 q+ 17:01:07 .. we are using JS liberary in Chrome, I would like to see better support in browsers 17:01:18 s/Jeff/Zheng/ 17:01:22 ack Hadrien 17:01:22 ... where should this issue go? Which group does this belong to? 17:01:46 Another Community Group https://w3c.github.io/mathonwebpages/ 17:01:58 Hadrien: readium take on MathML: we polyfilled with MathJaz, in Readium 2 we won't polyfill, we'lll be limited to what the browser can do 17:02:06 ... but this is an issue for web as a whole 17:02:06 https://mathml.igalia.com/ 17:02:08 q+ 17:02:14 ack av 17:02:16 tzviya: we are over time 17:02:16 s/MathJaz/MathJax/ 17:02:33 Avneesh: the screenreaders support MathML, so if browser exposes than JAWS can use 17:02:43 ... it's not only the reading system, it's the screenreader 17:03:00 zheng_xu: it's very slow 17:03:21 tzviya: I've posted some links. there's a math CG, etc. 17:03:28 ... w3c is aware of the problem 17:03:48 zheng_xu: maybe there can be a joint task force with other groups 17:03:57 tzviya: ivan will pay attention to this 17:04:07 ... thanks all. work on the F2F agenda. 17:04:07 dkaplan3 has left #pwg 17:04:18 cmaden2 has left #pwg 17:04:34 evan has left #pwg 17:04:49 rrsagent, draft minutes 17:04:49 I have made the request to generate https://www.w3.org/2018/03/12-pwg-minutes.html ivan 17:04:55 rrsagent, draft minutes 17:04:55 I have made the request to generate https://www.w3.org/2018/03/12-pwg-minutes.html ivan 17:04:55 zakim, bye 17:04:55 rrsagent, bye 17:04:55 I see no action items 17:04:55 leaving. As of this point the attendees have been toshiakikoike, dkaplan, dauwhe, tzviya, ivan, wolfgang, mateus, lsullam, jasminemulliken, evan, clapierre, Garth, Bill_Kasdorf, 17:04:55 Zakim has left #pwg