14:36:38 <RRSAgent> RRSAgent has joined #dpub
14:36:38 <RRSAgent> logging to http://www.w3.org/2016/06/20-dpub-irc
14:36:40 <trackbot> RRSAgent, make logs public
14:36:40 <Zakim> Zakim has joined #dpub
14:36:42 <trackbot> Zakim, this will be dpub
14:36:42 <Zakim> ok, trackbot
14:36:43 <trackbot> Meeting: Digital Publishing Interest Group Teleconference
14:36:43 <trackbot> Date: 20 June 2016
14:36:47 <ivan> Chair: Tzviya
14:37:02 <ivan> Agenda: http://www.w3.org/mid/b0c40dda2ca84095874350febfc23caa@AUS-WNMBP-005-n.wiley.com
14:37:14 <ivan> ivan has changed the topic to: Agenda 2016-06-20: http://www.w3.org/mid/b0c40dda2ca84095874350febfc23caa@AUS-WNMBP-005-n.wiley.com
14:37:27 <ivan> Regrets: Ayla, Brady
14:40:34 <HeatherF> HeatherF has joined #dpub
14:57:04 <Avneesh> Avneesh has joined #dpub
14:57:19 <dkaplan3> dkaplan3 has joined #dpub
14:57:57 <tzviya> present+ Tzviya
14:58:23 <nickbarreto> nickbarreto has joined #dpub
14:58:24 <ivan> present+
14:58:28 <tzviya> agenda: https://lists.w3.org/Archives/Public/public-digipub-ig/2016Jun/0071.html
14:58:33 <tzviya> chair: Tzviya
14:58:45 <ivan> Regrets+ markus
14:58:54 <laudrain> laudrain has joined #dpub
14:59:05 <clapierre> clapierre has joined #DPUB
14:59:05 <TimCole> TimCole has joined #dpub
14:59:35 <Avneesh> present+ Avneesh
14:59:40 <dauwhe> present+ dauwhe
14:59:56 <laudrain> present+ Luc
15:00:04 <ivan> Present+ nickbarreto
15:00:09 <ivan> present+ George
15:00:18 <cmaden2> present+ Chris_Maden
15:00:31 <clapierre> present+ Charles_LaPierre
15:00:33 <Vlad> Vlad has joined #dpub
15:00:34 <TimCole> present+ Tim_Cole
15:00:35 <lrosenth> lrosenth has joined #dpub
15:00:47 <Vlad> present+
15:01:06 <ivan> scribenick: nickbarreto
15:01:10 <bjdmeest> bjdmeest has joined #dpub
15:01:11 <NickRuffilo> NickRuffilo has joined #dpub
15:01:13 <George> George has joined #dpub
15:01:21 <tzviya> scribenick: nickbarreto
15:01:38 <ivan> present+ heather
15:01:53 <astearns> present+ astearns
15:01:53 <lrosenth> present+ Leonard
15:02:00 <George> George is present on dial in
15:02:03 <ivan> present+ vlad
15:02:04 <NickRuffilo> waoh - i don't have to scribe?
15:02:13 <NickRuffilo> what universe have i come to?
15:02:28 <pkra> present+ peter krautzberger
15:02:31 <bigbluehat> present+ Benjamin_Young
15:02:47 <bjdmeest> Present+ Ben_De_Meester
15:02:47 <ivan> present+ michael_miller
15:03:04 <tzviya> https://www.w3.org/2016/06/13-dpub-minutes.html
15:03:26 <nickbarreto> Tzviya: "Any comments on minutes last week?"
15:03:28 <dkaplan3> present+ Deborah_Kaplan
15:03:30 <ivan> Topic: Approaches to bridging with the CSS WG
15:03:40 <nickbarreto> Tzviya: "No comments, minutes approved"
15:03:56 <ivan> zakim, who is here?
15:03:56 <Zakim> Present: Tzviya, ivan, Avneesh, dauwhe, Luc, nickbarreto, George, Chris_Maden, Charles_LaPierre, Tim_Cole, Vlad, heather, astearns, Leonard, peter, krautzberger, Benjamin_Young,
15:04:00 <Zakim> ... Ben_De_Meester, michael_miller, Deborah_Kaplan
15:04:00 <Zakim> On IRC I see George, NickRuffilo, bjdmeest, lrosenth, Vlad, TimCole, clapierre, laudrain, nickbarreto, dkaplan3, Avneesh, HeatherF, Zakim, RRSAgent, pkra, cmaden2, darobin, tzviya,
15:04:00 <Zakim> ... dauwhe, Karen, Florian, ivan, rego, liam, nikos, bigbluehat, iank_, astearns, trackbot, plinss
15:04:34 <nickbarreto> Tzviya: "This week we wanted to talk about suggestions group may have to bridge our work and the work of CSS working group"
15:04:43 <NickRuffilo> +present
15:04:45 <Bill_Kasdorf> Bill_Kasdorf has joined #dpub
15:04:50 <tzviya> q?
15:04:50 <NickRuffilo> present+ Nick Ruffilo
15:04:54 <lrosenth> q+
15:04:56 <nickbarreto> Tzviya: "Does anyone have any ideas to start with, and after that we will discuss ones we already had noted down"
15:04:56 <Bill_Kasdorf> present+ Bill_Kasdorf
15:05:11 <pkra> q+
15:05:12 <tzviya> ack lr
15:05:16 <nickbarreto> Dave Cramer: "Our goals are something we should talk about, which are different from CSS working Group's goals"
15:05:35 <ivan> q+
15:05:41 <nickbarreto> Leonard: "What do people think is not working in this group? What is missing?"
15:06:15 <nickbarreto> Tzviya: "Let's talk about not just what we need, but some proposed implementations. They don't want to just hear 'we need page layout'. The publishing world should show some implementation guidelines
15:06:33 <ivan> q-
15:07:16 <nickbarreto> Alan: "Publishers won't make browsers fulfill the best setup for your needs, and then move into it. They need to decide to move into the fixer-upper, and then get what they need implemented"
15:07:47 <pkra> it's fine.
15:08:01 <nickbarreto> Leonard "One furstration is that sometimes we will ship code, but then it will be removed afterwards"
15:08:20 <bigbluehat> s/furstration/frustration
15:08:36 <nickbarreto> Alan "Well, one browser did implement pagination views, but then didn't get them used at all"
15:08:59 <tzviya> ack pk
15:09:11 <nickbarreto> Alan: "Use of a polyfill works, but browers only implement polyfills if significant number of developers are actualling using that polyfill"
15:09:18 <dauwhe> q+ about what stats browsers see when features are used inside Google play books, ibooks, etc.
15:09:28 <dauwhe> q?
15:09:33 <dauwhe> q+
15:10:07 <nickbarreto> Peter: "I was wondering, from a personal perspective, what bugs are there that cause a problem. Is there an easier way for implmentation elsewhere?"
15:10:58 <nickbarreto> Peter "The call for a moratorium was one thing last week. What features are a little bit problematic, or could have more implementation. I've been thinking of superscript and subscript, which is very simple, but what is actually still needed? How deep does the rabbit hole go on such a simple item?"
15:11:27 <pkra> s/last week/a few months ago
15:11:30 <ivan> q+
15:12:08 <nickbarreto> George: "If we wait for browser implementations, that is not controlling our own destiny. Why not look at Readium, for example, to develop CSS sheets that we like, and have it open source as an example and offer it to any browser and it shows and implementation. It could be something we let the browsers have and insert into W3C specs when they feel like they can handle it"
15:12:13 <laudrain> +1
15:12:14 <ivan> q-
15:12:15 <tzviya> ack dau
15:12:24 <nickbarreto> Tzviya: "Ivan and I had considered this and we can come back to it, thank you George"
15:12:39 <astearns> +1 to Readium, but also other projects. Shouldn't put all of your eggs in one basket
15:13:13 <nickbarreto> Dave Cramer "First of all, I would say Adobe's experience here are interesting. Browsers stats on usage, as far as I know, it wouldn't go into rendering engines that are inside other programs like iBooks or Google Play Books."
15:13:26 <astearns> q+ on iBooks
15:13:30 <nickbarreto> Dave Cramer "That is not a problem I know how to solve, but it is there."
15:14:08 <lrosenth> q+
15:14:38 <nickbarreto> Tzviya: "We were considering having a Reading System meeting. A regular DPUB meeting or a specialized meeting where we invite Reading Systems to come in and demonstrate working code and show off how they do various things. Readium, Nick Ruffilo at AER.IO do some of this. Ask if they would be willing to share some of their code.
15:15:01 <tzviya> ack as
15:15:01 <Zakim> astearns, you wanted to comment on iBooks
15:15:15 <nickbarreto> Tzviya: "Readium for one is open to open sourcing their setups. They may not be polyfills now, but Reading Systems do paginate nowadays and that is usage, it may be  starting point."
15:15:31 <laudrain> q+
15:16:14 <tzviya> ack lr
15:16:23 <nickbarreto> Alan: "Dave said browser statistics don't take into account reading systems in their stats, but stats are not the only thing they do take into account when implementing polyfills. Approaching browser engineers with reading systesm such as iBooks and Google Play books is a good idea and can work, depending on who you are talking to."
15:17:05 <nickbarreto> Leonard: "Alan covered some of this, but I think it is a great idea. Get Readium, iBooks and Google Play and maybe if we reach out hard enough, even Amazon Kindle, to get their input on this"
15:17:25 <astearns> including Edge engineers who are acutely aware of web-based Win reading systems
15:17:26 <tzviya> ack la
15:17:40 <nickbarreto> Leonard: "Seriously though, getting them in on a meeting is a good idea and it should be a special one, maybe a face to face."
15:17:58 <ivan> q+
15:18:06 <tzviya> ack iv
15:18:19 <nickbarreto> Luc: "Readium isn't as well funded as say iBooks or Google Play books, can they really contribute to this well?"
15:18:35 <nickbarreto> Tzviya: "They wouldn't necessarily do anything new, just contribute already existing code"
15:19:25 <david_stroup> david_stroup has joined #dpub
15:20:06 <nickbarreto> Ivan: "These systems are doing pagination already, so it may not be just CSS, there may be HTML and a category of features that publishers would like to have, and beceause it isn't available in CSS, they don't even try to do it. So I'm looking at Dave and Tzviya who do it every day, they restrict themselves because they know that CSS doesn't have this feature, so they don't even go there. Reading systems may not have these things, so they
15:20:06 <nickbarreto>  will not be a complete answer for this."
15:20:07 <lrosenth> q+
15:20:12 <Bill_Kasdorf> q+
15:21:02 <tzviya> ack lr
15:21:07 <nickbarreto> Ivan: "We need to talk to people, technical people to look into those things that are missing, to make a whole new polyfill and if there things catch on and publishers use them, they will prove to browsers that there is a community there that has certain needs. Unfotunately I don't have andy specific examples for this and I hope you can offer some."
15:21:13 <astearns> for those things that are necessary, but are currently too hard for a polyfill to implement, I'd encourage you to bring it up as a Houdini use case
15:21:14 <nickbarreto> Tzviya: "Yes. Chemistry is an example of this"
15:21:34 <ivan> +1 to astearns
15:21:59 <tzviya> ack Bill
15:22:07 <nickbarreto> Leonard "Technical Publications are something we need to consider, they have use cases that are beyond what we thing of as books, and we need to keep in mind what they have as requirements that are not a part of what we think of as books, that we need to bear in mind
15:22:58 <nickbarreto> Bill "The workarounds that are already existing would be useful to keep in mind, and know which ones are the most used, and this would also be a good pointer"
15:23:05 <lrosenth> ivan & astearns - Houdini will certainly be helpful but I wonder if it is a “stop gap” or a “solution"
15:23:10 <laudrain> q+
15:23:44 <astearns> lrosenth: both :)
15:23:45 <tzviya> ack la
15:23:55 <nickbarreto> Tzviya: "Yes. My question is wider. We can't just request reading systems to come to meeting. We need some specific questions to pose to them. "What are some hacks that you use?" for instance. Which isn't good enough either. Pagination of course, but we maybe keep it more informal and have a wiki"
15:24:29 <Bill_Kasdorf> s / workarounds / workarounds in Antenna House and Prince
15:24:48 <nickbarreto> Luc: "A wiki for Tech docs comparison of what is in CSS and what is accessible, this would be help to keep in mind what would be possible in a PWP"
15:24:55 <ivan> q+
15:24:58 <tzviya> ack iv
15:24:59 <nickbarreto> Tzviya: "So are you volunteering to create this wiki?"
15:25:07 <nickbarreto> Luc: "okay, if you insist"
15:25:39 <nickbarreto> Ivan "What is the attitude of the CSS working ground viz a viz accessible? Is it like the HTML people vs XML, do they never look at it at all? What is the situation there?"
15:26:03 <nickbarreto> Dave "I don't think people think about it at all. Some people would be horrified by some of the use cases, I think"
15:26:49 <nickbarreto> Alan "There is a certain bias in CSS WG, and in some WG, about rejecting a full solutions over investigating a use case. XSL-FO is a full solution we won't try to mimic. But we want to see what use cases they solve and which pieces we want to take"
15:26:58 <lrosenth> +1 to astearns
15:27:04 <tzviya> q?
15:28:29 <nickbarreto> Michael "Certainly Antenna House has a foot in each camp in CSS WG and XSL-FO. With FO we can solve structure documents today. In the wiki I provided some links to techinical documents you can download today, that auto manufacterers use."
15:29:23 <laudrain> q+
15:29:39 <tzviya> ack la
15:29:42 <nickbarreto> Michael "What we are seeing today is an increase in CSS and the number of orders that we realise in CSS and I proved links to a comparison that we make between FO functionality and CSS functionality. An offer I made is if anyone wants a copy of our formatter to actually try it towards CSS I would be happy to provide that for evaluation, not for produciton of course, but to compare features"
15:30:14 <nickbarreto> Luc "How can we make Antenna House or Prince aware of our discussion? I don't know them at all"
15:30:23 <nickbarreto> Tzviya: "Michael who just spoke is from Antenna House"
15:30:38 <nickbarreto> Dave Cramer "Prince I am in touch with while they are not in WGs"
15:30:48 <nickbarreto> Luc "So we can be put in touch with them?"
15:31:07 <nickbarreto> Tzviya: "Yes. So we can put together this wiki for them. Thank you Luc for volunteering"
15:31:10 <ivan> Topic: Use Cases Document Structure and Editing
15:31:12 <tzviya> http://w3c.github.io/dpub-pwp-ucr/
15:31:29 <nickbarreto> Tzviya: "Next point is use cases doc, because we want to get this into good shape now"
15:32:00 <HeatherF> Organization! Yay!
15:32:42 <tzviya> q?
15:32:44 <HeatherF> q+
15:32:47 <tzviya> ack h
15:32:58 <nickbarreto> Tzviya: "At this point we want to focus on structure and editorial changes so this document can be more organised, so someone who is totally new to this, can understand oh, the issues with a PWP are these. And then they can get to the next set of issues futher on. It needs to read as if it was not written by committee, even though it was. If anyone wants to make suggestions for organisation that would be great."
15:33:39 <nickbarreto> Heather "So Ivan sent me some suggestions on how to at least link things like requirements into their associated use cases, which is somehting I want done. One thing that I think would really help this docuemnt is a well written introduction.
15:34:00 <nickbarreto> Heather "If anyone can help with that, it would be fantastic"
15:34:12 <nickbarreto> Tzviya: "Do we have any good writers to write an introduction?"
15:34:19 <nickbarreto> No one volunteers
15:34:27 <nickbarreto> Ivan "We have a lot of publishers, not authors"
15:34:39 <nickbarreto> Tzviya: "Any other requirements?"
15:34:54 <nickbarreto> Heather "The introduction is the main one. And getting the use cases linked in."
15:34:56 <ivan> q+
15:35:00 <tzviya> ack iv
15:36:09 <TimCole> http://w3c.github.io/dpub-pwp-arch/Archival-UCR.html#LOCKSS
15:36:26 <nickbarreto> Ivan "Two very different things. The archival group did a use case, and I tried to find a URL for it, as they looked for uses cases, for a strict requirement for each uses case and the collate everything at the end. THis is something I think is good to have and I hacked some javascript to do that, because I think we have a lot of use cases and having as structure is important for navigation"
15:37:55 <ivan> 2.7 Manifests/Metadata
15:38:05 <ivan> http://w3c.github.io/dpub-pwp-ucr/#manifests-metadata
15:38:26 <nickbarreto> Ivan "Second thing is to repeat my call for volunteers as after the last call we had a long list of features which are important in a manifest, but each of those are just features but we need use cases. In that email I picked two, I made use cases for them. One is easy, the other we need to have some discussion with Vlad but I think we should pick though them and make use cases and featuers, as well as go through the whole document and fi
15:38:26 <nickbarreto> nd what may be a use case or just a one sentence feature. The one I picked out is this one section that I will share the URL as they are absolutely essential, the very core of the use case document
15:38:29 <lrosenth> q+
15:38:43 <nickbarreto> Ivan "If everyone could take one or two like I did, that would move things along very well"
15:38:55 <tzviya> ack lr
15:39:08 <nickbarreto> Ivan "Heather, if you need help with editorial or other structures, let me know."
15:39:10 <HeatherF> q+
15:40:21 <tzviya> ack he
15:40:35 <nickbarreto> Leonard "one of the things that may be for the next Virtual face to face, there are things here that are mutually exclusive. We need to choose. If we pick some of them, it precludes doing others. We need to make those choices, which ones are our top targets and which ones are not as those contraditions will be evident to those outside this organisation, so before we share things more widely it needs to be decided"
15:41:17 <nickbarreto> Heather "Agree with Leonard and it is important to make those choices. I also note that some advice is contraditory, so what do we want to see for cleanup more clearly?"
15:41:29 <TimCole> q+
15:41:50 <HeatherF> q+
15:42:29 <nickbarreto> Ivan "We can probably push aside specs etc. Why we are developing it, what this is for, this is ok, but it is interest things, not really for readers. The stakeholders is important. What I don't know is, do we have any kind of set of possible stakeholders becasue that might become unmanagable if we are not careful"
15:43:15 <tzviya> ack tim
15:43:24 <HeatherF> OK. I've seen that; I'll see about applying that to this one.
15:43:25 <TimCole> https://www.w3.org/dpub/IG/wiki/UseCase_Template
15:43:28 <nickbarreto> Tzviya: "We want an in-between probably. Use cases at the moment are just one sentence, and they probably need a little more fleshing out, contextualising them, for a reader from the outside to get to it so they understand what the use cases are about. So the use cases would be short, a few sentences and then examples of that use case"
15:43:35 <tzviya> Web Anno Use Cases: https://www.w3.org/annotation/wiki/Use_Cases
15:44:13 <HeatherF> q-
15:44:38 <nickbarreto> Tim "There is a lot in the document there now, but piece that I pasted the URL of right now, that is too short. We need to think what is a correct or better list of stakeholders."
15:45:22 <nickbarreto> Tzviya: "That list is from when this group was very very young. I don't think this is that accurate. Whenever writing stakeholders I tend to think 'everyone', because who am I to say who needs this?"
15:45:33 <lrosenth> q+
15:45:54 <tzviya> ack lr
15:46:07 <nickbarreto> Tzviya: "If we are going to use that template, we need to edit it carefully, because it isn't quite what we are after"
15:46:19 <pkra> Apologies -- I have to drop off early today.
15:46:32 <ivan> q+
15:46:37 <nickbarreto> Ivan "There are a lot of stakeholders, are we talking about reading system developers, browsers, etc, or are we saying other WGs are stakeholders too?
15:46:45 <tzviya> ack ivan
15:46:50 <nickbarreto> Tzviya: "This template had categories of publishers, which at this point is mostly moot
15:47:10 <nickbarreto> Ivan "When we are talking about stakeholders in this document, user communities is what we mean, not other WGs"
15:47:12 <lrosenth> nickbarreto - that was me (lrosenth) not Ivan, fwiw
15:48:17 <nickbarreto> Ivan "Other WGs are a very different thing. If we want at some point to target other groups, we could later, but now I don't think so. The other stakeholder difference is perhaps between end user and broswer implementors, which is not very granular, but anything more than that can become not useful|
15:48:30 <HeatherF> yes
15:48:51 <lrosenth> nick - no problem :)
15:49:07 <tzviya> https://www.w3.org/dpub/IG/wiki/May_2016_2nd_Virtual_F2F
15:49:11 <HeatherF> We need to do introductions, I need to highlight where the contradictions are for the F2F, and it would be helpful if I structured this to look a bit more like the annotations use case doc
15:50:09 <ivan> http://w3c.github.io/dpub-pwp-ucr/#manifests-metadata
15:50:10 <nickbarreto> Tzviya: "remember to attend that virtual face to face on July 7th. As people head for their holidays, remember to keep this available if possible. If you have editorial experience, please pitch in, but I like Ivan's idea that we can each take two things are write a use case. That is something I can do, can everyone else?
15:50:42 <nickbarreto> Tzviya: "Section Seven, the manifest metadata section, has 15 or 20 one sentence use cases. Can we each commit to take on of those and flesh it out?"
15:50:54 <nickbarreto> Tzviya: "Then next week can be in good shape"
15:50:59 <nickbarreto> Ivan "Ive already done my two!"
15:51:11 <nickbarreto> Tzviya: "Ivan is ahead of the game then. What if we say two weeks?"
15:51:15 <lrosenth> sorry - next few weeks are overloaded for me :(.   July is better...
15:51:39 <Vlad> Vlad has joined #dpub
15:51:39 <HeatherF> q+
15:51:42 <nickbarreto> Nick Barreto "I'll do one, or two as it is"
15:51:43 <tzviya> ack h
15:52:23 <nickbarreto> Heather "Since I want to work on the document more consistently, rather than waiting for godot errr, use cases, then I'll keep things update on github so everyone can keep track of where we are
15:52:54 <nickbarreto> Ivan "When there is more there, I am happy to pick it up and put more structure in as well"
15:53:05 <tzviya> http://w3c.github.io/dpub-pwp-ucr/#manifests-metadata
15:53:26 <ivan> q+
15:53:28 <nickbarreto> Tzviya: "In case you get inspired during the week, here is the link, you don't have to tell us you are doing it, just take two from this section"
15:53:29 <tzviya> ack iv
15:54:25 <tzviya> https://www.w3.org/2016/09/TPAC/
15:54:25 <nickbarreto> Ivan "One more thing that we need because we don't have enough work yet, is that when we have use cases, we need to distill those 15 or 20 to requirements. So if we have ideas on that this would be good, and it may be good to concentrate on that in the Virtual Face to Face
15:54:33 <ivan> Topic: TPAC
15:55:17 <ivan> q+
15:55:19 <tzviya> ack iv
15:55:21 <lrosenth> all registered and looking forward to it
15:55:24 <tzviya> https://www.w3.org/2016/09/TPAC/
15:55:38 <nickbarreto> Tzviya: "Last agenda item is that TPAC is coming, it is in Lisbon, one of the most beautiful cities according to Ivan. Schedule yourself in! Our meetinge are on mondays and tuesdays, which I think is the same as CSS, so we may have some joint meetings. TPAC is a party, we hope to see you there! Register yourself as soon as possible, I haven't done so yet but will do."
15:55:54 <lrosenth> q+
15:55:59 <tzviya> ack lr
15:56:00 <HeatherF> +1
15:56:04 <tzviya> +1
15:56:06 <clapierre> +1
15:56:06 <astearns> +1
15:56:07 <nickbarreto> Ivan "Because of the joint meetings, it may be more interesting and exiting than usual, eveyrone should try and come"
15:56:08 <ivan> +1
15:56:12 <Bill_Kasdorf> I hope to be there but it isn't confirmed yet
15:56:12 <Vlad> +1
15:56:13 <laudrain> perhaps
15:56:15 <lrosenth> +1
15:57:05 <nickbarreto> Leonard "What is the procedure for, or when do we think we will start putting in the agenda for our TPAC meetings?"
15:57:20 <nickbarreto> Tzviya: "Tighter planning probably to begin in august, but we will get back to you on that"
15:58:59 <clapierre> clapierre has left #dpub
15:59:04 <laudrain> laudrain has left #dpub
15:59:10 <ivan> Present+ David_Stroup
15:59:29 <ivan> rrsagent, draft minutes
15:59:29 <RRSAgent> I have made the request to generate http://www.w3.org/2016/06/20-dpub-minutes.html ivan
15:59:39 <ivan> trackbot, end telcon
15:59:39 <trackbot> Zakim, list attendees
15:59:39 <Zakim> As of this point the attendees have been Tzviya, ivan, Avneesh, dauwhe, Luc, nickbarreto, George, Chris_Maden, Charles_LaPierre, Tim_Cole, Vlad, heather, astearns, Leonard, peter,
15:59:42 <Zakim> ... krautzberger, Benjamin_Young, Ben_De_Meester, michael_miller, Deborah_Kaplan, present, Ruffilo, Bill_Kasdorf, David_Stroup
15:59:47 <trackbot> RRSAgent, please draft minutes
15:59:47 <RRSAgent> I have made the request to generate http://www.w3.org/2016/06/20-dpub-minutes.html trackbot
15:59:48 <trackbot> RRSAgent, bye
15:59:48 <RRSAgent> I see no action items