16:32:12 RRSAgent has joined #dpub 16:32:12 logging to http://www.w3.org/2017/02/06-dpub-irc 16:32:14 RRSAgent, make logs public 16:32:14 Zakim has joined #dpub 16:32:16 Zakim, this will be dpub 16:32:16 ok, trackbot 16:32:17 Meeting: Digital Publishing Interest Group Teleconference 16:32:17 Date: 06 February 2017 16:33:21 Agenda: https://lists.w3.org/Archives/Public/public-digipub-ig/2017Feb/0009.html 16:33:35 Agenda call 2017-02-06: https://lists.w3.org/Archives/Public/public-digipub-ig/2017Feb/0009.html 16:33:41 Chair: Garth 16:34:17 Regrets: Luc, Romain, Laurent, Heather, Peter, Alan, Rick 16:49:03 garth has joined #dpub 16:49:21 q? 16:52:14 BillMcCoy has joined #DPUB 16:55:21 dkaplan3 has joined #dpub 16:56:10 Avneesh has joined #dpub 16:56:39 present+ Avneesh 16:57:35 present+ Deborah_Kaplan 16:57:42 present+ dauwhe 16:57:44 Nick regretted... so looking for a scribe! 16:59:18 present+ 16:59:57 hadrien has joined #dpub 17:00:02 regrets+ bert, nick 17:00:06 scribenick: dauwhe 17:00:14 Sel has joined #dpub 17:00:25 present+ hadrien 17:00:43 present+ Karen 17:01:19 garth: one more minute... 17:01:22 Bill M on the call? Muted? 17:01:36 Bill_Kasdorf has joined #dpub 17:01:45 present+ Bill_Kasdorf 17:02:16 +1 Dave Cramer 17:02:48 clapierre1 has joined #DPUB 17:02:56 present+ 17:03:05 present+ george 17:03:33 it is a snow day in Seattle too! 17:03:45 Vlad has joined #dpub 17:03:54 garth: let's get started 17:04:20 present+ 17:04:24 ... I sent out malformed minutes, but didn't send the better ones 17:04:31 DanielWeck has joined #dpub 17:04:37 ... let me know if I missed anything 17:04:50 ... are there any objections? 17:04:58 [silence] 17:05:04 garth: minutes approved 17:05:32 ... do we have Harriet Greene on the call? We have a new member from University of Illinois 17:05:50 ... welcome in absentia :) 17:05:58 ... update on merger: it's complete! 17:06:02 topic: idpf w3c merge 17:06:04 (general rejoicing) 17:06:10 Yeah! 17:06:25 Another yeah! :) 17:06:30 ... Bill McCoy is now digital publishing champion at W3C. Can you give an intro? 17:06:51 ... I do want to talk about chartering 17:07:04 BillMcCoy: hello from W3C staff side 17:07:14 ... I'm bmccoy@w3.org 17:07:27 ... I expect to be a more frequent participant in this meeting 17:07:42 ... I'm happy to be here. Looking forward to a working group. 17:07:51 garth: we have some tech discussions on PWP draft 17:08:09 ... I'd like to move the penultimate agenda item up front 17:08:25 ... can you go ahead on that? 17:08:37 q+ 17:08:43 ... between BillM and Ivan, we can talk about the business group 17:08:49 topic: pub business group 17:08:53 q? 17:08:59 ack Bill 17:09:12 BillMcCoy: the DPUB IG already has rough consensus on a possible direction for WG draft 17:09:21 q+ 17:09:31 ... the most urgent thing is the broader IDPF community gets in the loop soon 17:09:39 ... so we can get WG charter proposal as soon as possible 17:10:00 ... so everyone should join publishing BG this week 17:10:20 ... as soon as the BG is rolling, then they should have input into charter process 17:10:20 q- 17:10:44 ... the kickoff meeting for Publishing BG will be March 13 in London, details later this week 17:11:15 q+ 17:11:18 ... let's get a WG charter, with input from BG, as soon as possible 17:11:25 garth: that matches my 2 cents 17:11:42 ... the BG kickoff before London Book Fair 17:12:02 q+ 17:12:02 ... and then we discussed a first F2F of digital pub working group in NYC in... May 17:12:23 ... but there are some issues related to the U.S. going insane politically 17:12:48 ... so we're not sure if the U.S. is a feature or a bug for meetings 17:12:54 vagner_ has joined #dpub 17:13:12 ... if we're heading for late May/early June f2f, we need to figure that out soon 17:13:18 ... we have an offer from Adobe to host in NYC 17:13:31 ... and we could have our co-chair 17:13:38 ... and BEA brings pub folks to town 17:13:50 Q? 17:13:51 ... we don't need to decide today 17:14:03 ack Bill 17:14:15 Bill_Kasdorf: the relationship between this IG and the WG 17:14:24 ... will this IG wind up if the WG is chartered? 17:14:45 ... if so, is there anything the IG can do to help smooth the transition 17:14:53 garth: I assumed the IG would morph to the WG 17:15:10 BillMcCoy: I don't know who's decision that is 17:15:23 ... bandwidth is a problem 17:15:35 q? 17:15:35 ... and this group has acted like a WG 17:16:00 ... so the default assumption is the IG would wind down, and some tasks would move to the BG or the CG 17:16:10 ... but this group should discuss this 17:16:25 ivan: BillK, this is undecided 17:16:34 ... We haven't discussed too much 17:16:45 ... are there things that the interest group can do? 17:16:58 ... the last six-seven months, the IG was preparing for the WG 17:17:11 ... there are some pending issues around CSS, a11y, etc 17:17:26 ... which of these should go to the WG, or should they stay separate? 17:17:30 ... I don't have the answer 17:17:30 q? 17:17:41 ack ivan 17:17:58 ... if we think there's a need for an IG to stay, then we need to ask ourselves if it's realistic 17:18:12 ... the community of tech people in publishing is not overly big 17:18:33 brady_duga has joined #dpub 17:18:34 ... we'll have the BG, the WG, some of us may be involved in epub3 maintenance in the CG 17:18:41 ... we'll have to have chairs, staff people, etc. 17:18:44 present+ duga 17:19:02 ... one possibility is that the IG dissolves, and people join the WG 17:19:18 q? 17:19:26 Bill_Kasdorf: this has a big bearing on the scope of the WG charter 17:19:36 ... if the IG exists, the WG charter can be narrower 17:19:44 present+ Vagner 17:19:45 ... if the IG goes away, WG will need broader charter 17:20:06 ivan: what was put into the draft charter are those items that are clearly rec-track work 17:20:17 ... I did not consider other things 17:20:37 q? 17:20:40 ... one thing from today's agenda is something from the mailing list 17:20:58 ... to see exactly what our role be in the continuation of WCAG etc 17:21:11 ... there's also the CSS-related work 17:22:05 ... whether that needs to be in the IG, or that can just be in csswg 17:22:17 garth: wind-down can be independent of wind-up of WG 17:22:36 ivan: aria is a bit different... dpub-aria work is rec-track 17:22:47 ... so if it stays in IG, we must work with a working group 17:23:01 ... so that needs to be in WG, and is already in the charter 17:23:28 garth: CSS-related work could happen in liason between WG and CSSWG 17:23:39 ivan: or the BG 17:23:56 garth: so there's at least three groups here--BG, WG, CG 17:24:06 ... based on bandwidth, I think IG may want to wind down 17:24:26 ... and all of us may be delighted at Garth's able leadership 17:24:39 ... but I wouldn't see us doing both 17:24:43 q? 17:24:43 q+ 17:25:55 clapierre1: the a11y task force published a note on WCAG gaps 17:26:01 ... that should be considered for the WG 17:26:03 q+ 17:26:06 agreed with charles 100% 17:26:07 ack clapierre1 17:26:09 ... there are certainly some gaps 17:26:11 ack cl 17:26:17 many things were left as "future work" 17:26:18 ack ivan 17:26:28 ivan: this is separate agenda item 17:26:35 Topic: WCAG and the WG 17:26:44 ... maybe George knows 17:27:07 ... my understanding is that in the new WCAG charter, the publishing industry's a11y requirements are now in scope 17:27:17 q+ 17:27:20 ... if this is really the case, that WCAG will pick up those items 17:27:29 q+ 17:27:31 ... then I don't think it's helpful if 2 working groups do that work 17:27:37 .... that can only lead to problems 17:27:56 ... if WCAG is doing the work, then our job is to liase, offer oversight, bring new issues, review work... 17:28:04 ... but the work focused on WCAG 17:28:20 ... if not, then there would need to be a rec from Pubishing WG 17:28:22 q? 17:28:30 ... but I would be thrilled if admin fell on WCAG 17:29:00 Avneesh: the WCAG 2.1 journey started in 2016 17:29:03 q? 17:29:08 ack Avn 17:29:10 "Develop a recommendation-track update to the Web Content Accessibility Guidelines 2.0. This update will clarify and improve applicability to content on mobile devices, in digital publications, and on devices using a wider range of inputs such as touch screens and stylus digitizers, as well as adding improvements to better support users with disabilities including low vision and cognitive, language, and learning impairments." 17:29:15 ... that group wanted only dpub-aria, but we added publishing to their scope 17:29:26 ... this was a reluctand addition to WCAG scope 17:29:36 ... when we talk about practical things 17:29:46 ... there are a lot of issues, such as a11y metadata 17:29:57 ... WCAG doesn't think of this as a high priority 17:30:04 ... there is a lot of uncertainty there 17:30:19 ... this is a new thing for them; there is some resistance 17:30:22 q+ 17:30:26 ... we need a big push from the DPUB community 17:31:03 ... the ball is being passed back and forth. we need to know who is responsible 17:31:11 garth: does this need to be nailed down before the WG charter? 17:31:14 Avneesh: YES 17:31:15 1+ 17:31:29 ... the IDPF has given a high priority to a11y, and we have achieved a lot 17:31:34 ... we cannot drop that in W3C 17:31:42 garth: agreed 17:31:49 q+ 17:31:58 ack dp 17:31:58 dkaplan3: I agree with Ivan that having one group focusing is good 17:32:01 adk dk 17:32:03 ack dkaplan3 17:32:03 q? 17:32:11 ack dkap 17:32:12 ack dkaplan 17:32:18 ... one problem with a11y task force was all the different groups with non-ideal communication 17:32:39 ... but I want to emphasize that, although WCAG is theoretically open to DPUB concerns 17:32:51 ... but we are a tiny priority, and they don't understand 17:33:02 ... that publishing has a separate set of priorities 17:33:18 ... and people on WCAG don't understand why they are particularly important 17:33:37 ... So maybe we can get more publishing folks on WCAG 17:33:47 ... or else we need other groups to advise WCAG 17:33:59 ... but we can't just hope WCAG will understand today 17:34:18 ivan: we will have to have a joint meeting with WCAG 17:34:24 +1 to joint meeting w/ WCAG 17:34:28 ... we cannot decide unilaterally 17:34:46 ... there there is the a11y metadata story 17:34:57 ... I understand that that community never did 17:35:10 ... I think a11y metadata will be in scope for our WG no matter what 17:35:29 ... for the WCAG story, the problem I have is that I don't know how modular WCAG is 17:35:39 ... it was a monolithic document which addressed several things 17:35:51 ... if we do WCAG work in our WG then we create a different document 17:35:57 q? 17:36:01 ... a REC is usually under the "control" of one WG 17:36:05 ack ivan 17:36:24 ... there have been cases in the past where there was a joint publication of two WGs, but that's complicated 17:36:46 ... so if we do it here, it would not be a formal part of WCAG; it will be a separate document 17:36:49 ... which concerns me 17:37:04 q+ 17:37:18 ... talking to WCAG people as soon as possible, in next few weeks, will be very important 17:37:22 garth: exactly 17:37:35 ... who does the drafting? is a good question 17:37:41 ... we need this meeting. 17:38:16 BillMcCoy: Jeff and Tim and others want is that there are things in EPUB that could benefit the web as a whole 17:38:23 ... Media overlays is a great example 17:38:32 ... it's not specific to publications 17:38:44 ... but we should be thinking about making this an OWP feature 17:38:49 q? 17:38:53 ack Bill 17:39:08 ... packaging is another example, something that applies to more than publishing 17:39:10 [+1 to getting DBup folks into Accessibility group. Note also that there is support for a11y metadata from others who are not currently engaged but understand the requirement - https://github.com/w3c/wcag21/issues/82 … Note that WCAG 2.1 is essentially working on being able to add *specific, generally applicable* criteria - i.e. it won't make it if it helps some things but breaks others, and it needs to be directly about accessibility] 17:39:14 q+ Bill_Kas 17:39:27 ack BillMc 17:39:27 ... but let's do them in a general matter, not a publication-specific manner 17:39:28 q+ 17:40:02 George: I see that there are items in publishing that are specific to publishing 17:40:06 ... for example, reading order 17:40:24 ... there isn't that concept in WCAG, and it's specific to publishing, and very important for a11y 17:40:33 q+ 17:40:44 ... can we identify certain things that are part of publication content that we could develop and have WCAG people review 17:40:57 ... what is the breakpoint/handoff between the two groups? 17:41:06 ack Bill 17:41:27 Bill_Kasdorf: the fate of all the EPUB specs, including the satellite specs, specifically EPUB A11Y 1.0 17:41:46 ... that was deliberately not an EPUB 3.X spec, but to be referencable outside of EPUB 17:41:55 ... what happens to those specs in the future? 17:42:11 q+ 17:42:12 ... that's the result of George's push for a baseline a11y spec 17:42:29 ... I'm not sure it belongs in the EPUB3 CG becasuse that is so EPUB-specific 17:42:32 ack ivan 17:43:13 ivan: I think it would be helpful if the a11y experts in the group draft, very explicitly, things you think are very necessary work items 17:43:28 ... the generalization of the EPUB a11y doc might be one of them 17:43:32 ... there is the metadata issue 17:43:39 ... and maybe more to be added to WCAG 17:43:48 ... we should bring a good list of items to these meetings 17:43:55 ... I don't have the knowledge to make such a list 17:44:23 ... so then we can say, for example, metadata is in scope for Pub WG charter, the other things might go to other groups, etc 17:44:33 dkaplan3: I'm going to do magic 17:44:42 ... and answer what Ivan and George asked for 17:44:53 ... remember the note that the a11y task force published last year? 17:45:01 ... we know it doesn't cover everything 17:45:24 q+ 17:45:25 ... but this note precisely states our a11y priorities, many of which can be addressed by other groups at w3c 17:45:27 q? 17:45:35 ack dkaplan 17:45:35 ack dkap 17:45:52 ... but this is a note to other groups dealing with a11y that we think need to be addressed 17:45:57 ... so we should remind folks of this 17:46:04 ... I don't think we should edit it 17:46:14 ... we need people to act on it 17:46:39 ack Avn 17:46:58 Avneesh: epub ally is build on WCAG, but includes stuff missing in WCAG 17:47:09 ... the techniques are in line with what WCAG does 17:47:27 ... so this spec, in conjunction with the DPUB note, describe what we need 17:48:02 ... how do we move EPUB A11Y spec forward in W3C? We don't want to just maintain, we want to move forward 17:48:09 EPUB 3 Community Group charter include ongoing development not just "maintenance" 17:48:19 ... it would take 3-5 years to put everything in WCAG 17:48:20 we can tweak if the language in the starter charter is not clear 17:48:22 ... that's not fast enough 17:48:31 garth: that's an argument for doing that in this WG? 17:48:33 Avneesh: yes 17:48:38 q+ 17:48:47 ack ivan 17:48:47 ... CG looks too weak for more than maintenance 17:49:02 ivan: however, my down-to-earth job is to write a charter 17:49:09 ... and I can't put the a11y note in the charter 17:49:30 ... I would need the two paragraphs that defines in the charter level this is what this or that WG must deliver 17:49:40 [WCAG 2.1 is on a very fixed timeline, so you need to have stuff ready for them on that timeline, and the rest might get into 2.2 or whatever comes next, which doesn't *yet* seem to have a time pressure] 17:49:44 ... the input docs are these two things (DPUB a11y note and EPUB a11y spec) 17:50:05 ... then we can go back to WCAG and say, 'this is what we think shoudl be done' 17:50:16 ... and we can ask them if it's ok if we do it 17:50:32 ivan: there is a timeline with WCAG 17:50:35 q? 17:50:54 Avneesh: there is some push to put things in WCAG 3, which is a long way off 17:51:16 garth: Ivan, it looks like you want a volunteer to draft charter text. Can Deborah or Avneesh do that? 17:51:20 dkaplan3: I'll jump in 17:51:37 +1 17:51:43 ... the a11y task force put itself on hold 17:51:53 ... but we're seeing the bat-signal, and need to come out of retirement 17:52:09 garth: that sounds like an action item for the a11y task force 17:52:22 q+ 17:52:23 ... and to provide the elevator pitch for a11y in the DPUB charter 17:52:24 +1 17:52:29 ivan: can I add one thing? 17:52:44 ... if you look at the charter draft, one is the geeral description, which is where I need your help 17:52:51 ... there are reference docs, which is easy 17:52:55 ... and there's a liason section 17:53:14 ... so we have to have a diplomatically acceptable of how we would work together with WCAG 17:53:22 ... I'll need your help there, too 17:53:33 Ivan, we'll have to call on you for diplomatic expertise! 17:53:34 ack ivan 17:53:45 BillMcCoy: I agree with Ivan about liason with WCAG 17:53:47 ack BillM 17:53:49 q? 17:53:58 ... occam's razor is for things that will end up in W3C REC 17:54:09 ... the a11y thing is intended to be a moving target 17:54:37 q+ 17:54:42 ... but scope of epub3 CG should not be just errata, but also ongoing development of things that don't need w3c rec track 17:54:47 q? 17:54:53 ... I think the a11y stuff might be suitable for the CG 17:55:15 ... the CG is more than errata 17:55:15 q+ 17:55:34 ack ivan 17:55:35 ivan: one thing, BillM 17:55:36 q? 17:55:59 ... as far as I know, the a11y it's much more important for certain docs to be recommendations, due to legal results 17:56:05 EPUB 3 is an ISO Technical Specification and we plan to upgrade EPUB 3.1 to ISO Standard 17:56:27 EPUB Accessibility as an ISO Specification in 18 months may trump EPUB Accessibility as W3C Recommendation in 3 years 17:56:34 ... notes may work for some things, but with a11y we may need recs 17:57:09 sorry to use the word "trump" ;-) 17:57:09 garth: EPUB3 exists in ISO world 17:57:21 ... I think we should get this in the charter at least for discussion 17:57:30 ... but more discussions to come about where the work would happen 17:57:33 q? 17:57:38 ack clap 17:57:46 clapierre1: the a11y task force will meet this Thursday to draft something for the charter 17:58:08 q? 17:58:15 garth: there's nobody on the queue 17:58:31 ... I thought the wcag discussion would take moments 17:58:41 ... but it may be good in that Leonard is missing 17:58:53 ... and he kicked off the initial discussions of the PWP topics 17:59:56 ... the discussion last week about the definition of web publication, and the text about a11y--both of those were drafted by Ivan, so those are resolved 18:00:16 q? 18:00:20 ... so I'd consider that finished, then we can move to online/offline and manifests next week 18:00:30 q? 18:00:36 --- adjurned 18:00:37 ... and as the hour has past, we are done! 18:00:45 ... thanks to the a11y task force! 18:01:05 clapierre1 has left #dpub 18:01:40 rrsagent, draft minutes 18:01:40 I have made the request to generate http://www.w3.org/2017/02/06-dpub-minutes.html ivan 18:02:07 trackbot, end telcon 18:02:07 Zakim, list attendees 18:02:07 As of this point the attendees have been Avneesh, Deborah_Kaplan, dauwhe, ivan, hadrien, Karen, Bill_Kasdorf, clapierre, george, Vlad, duga, Vagner 18:02:15 RRSAgent, please draft minutes 18:02:15 I have made the request to generate http://www.w3.org/2017/02/06-dpub-minutes.html trackbot 18:02:16 RRSAgent, bye 18:02:16 I see no action items 18:02:16 And from the agenda for this week, we did items: 1,2,4,5, and 3.1