00:03:44 Karen has joined #dpub 14:25:30 RRSAgent has joined #dpub 14:25:30 logging to http://www.w3.org/2016/04/04-dpub-irc 14:25:32 RRSAgent, make logs public 14:25:32 Zakim has joined #dpub 14:25:34 Zakim, this will be dpub 14:25:34 ok, trackbot 14:25:35 Meeting: Digital Publishing Interest Group Teleconference 14:25:35 Date: 04 April 2016 14:26:09 Agenda: https://lists.w3.org/Archives/Public/public-digipub-ig/2016Apr/0003.html 14:26:54 Chair: Tzviya 14:27:04 Florian_ has joined #dpub 14:27:28 Regrets: Luc, Romain, Brady, Daniel 14:56:08 NickRuffilo has joined #dpub 14:58:32 present+ Tzviya 14:59:00 HeatherF has joined #dpub 14:59:04 bjdmeest has joined #dpub 14:59:43 agenda: https://lists.w3.org/Archives/Public/public-digipub-ig/2016Apr/0003.html 14:59:44 present+ Chris_Maden 15:00:00 Yay! I got the time zones correct! 15:00:01 present+ ivan 15:00:06 present+ Heather_Flanagan 15:00:31 Present+ Ben_De_Meester 15:00:34 mgylling has joined #dpub 15:01:00 Vlad has joined #dpub 15:01:23 Present+ Benjamin_Young 15:01:33 Avneesh_Singh has joined #DPUB 15:01:34 clapierre has joined #DPUB 15:01:42 ayla_stein has joined #dpub 15:01:48 present+ Charles_LaPierre 15:02:08 pkra has joined #dpub 15:03:39 present+ astearns 15:03:47 zakim, pick a victim 15:03:47 Not knowing who is chairing or who scribed recently, I propose Tzviya 15:03:48 present+ peter krautzberger 15:03:50 present+ ayla_stein 15:03:53 HAHAHA 15:04:06 I can scribe. 15:04:13 thank you peter! 15:04:14 TimCole has joined #dpub 15:04:15 pleasure. 15:04:17 scribenick: pkra 15:04:18 Yay Peter! 15:04:19 *swoon* 15:04:32 chair: Tzviya 15:04:50 Present+ Tim_Cole 15:04:50 https://www.w3.org/2016/03/21-DPUB-minutes.html 15:04:56 tzviya: review of last week's minutes. Any comments? 15:05:03 ... minutes are approved. 15:05:19 tzviya: ivan and others have attended the AC meeting in Boston recently. 15:05:44 ivan: link to minutes 15:05:46 https://www.w3.org/2016/03/21-ac-minutes.html 15:05:50 ... are members only. 15:05:50 https://www.w3.org/2016/03/22-ac-minutes.html 15:06:05 zakim, who is here? 15:06:05 Present: Tzviya, Chris_Maden, ivan, Heather_Flanagan, Ben_De_Meester, Benjamin_Young, Charles_LaPierre, astearns, peter, krautzberger, ayla_stein, Tim_Cole 15:06:08 On IRC I see TimCole, pkra, ayla_stein, clapierre, Avneesh_Singh, Vlad, mgylling, bjdmeest, HeatherF, NickRuffilo, Zakim, RRSAgent, cmaden2, darobin, tzviya, ivan, Karen, liam, 15:06:08 ... shepazu, leaverou, nikos, iank_, bigbluehat, astearns, plinss, trackbot 15:06:17 ... relevant for us: Bill made a publication on DPUB IG, pwp etc. 15:06:24 ... was a great talk! 15:06:49 Bill_Kasdorf has joined #dpub 15:06:58 ... lots of hallway conversations with people, incl. skeptics. 15:06:59 present+ Bill_Kasdorf 15:07:17 ... many other conversations about vertical areas. 15:07:28 ... web payment, entertainment, digital marketing etc. 15:07:30 Bert has joined #dpub 15:08:04 ... The second important part was Web Platform Group (html + APIs groups) 15:08:14 ... gave an overview of current work and plans 15:08:42 ... for us interesting: HTML 5.1 is coming up. CR in June, Rec in September. 15:09:05 ... not sure about details element; needs checking. 15:09:35 ... also a social/editorial aspect came up. 15:10:02 ... huge beast. Used to be only one person really understood it. 15:10:25 ... Also, a list / plans for other APIs came up. 15:10:43 ... lots of go ahead but no fixed timelines. 15:10:54 ... for us: web components and serviceworkers are on track. 15:11:24 ... mozilla and edge have started looking into serviceworkers. (Apple: unkown). 15:11:31 ... another item: manifest. 15:11:36 ... also going ahead. 15:11:52 ... Some things need trimming before shipping: web storage is worth keeping an eye on. 15:11:56 SW in mozilla: https://wiki.mozilla.org/Service_Workers 15:12:16 ... Some are essentially on hold / might move to other groups. In particular (for us): packaging. 15:12:23 ... packaging has not moved since we first considered it. 15:12:42 ... not clear who/where it will be moving. 15:13:04 ... Some things are really put on ice. E.g., finetext API [?] 15:13:14 s/finetext/FindText 15:13:17 oh... 15:13:20 :) 15:13:21 s/[?]/http://w3c.github.io/findtext/ 15:13:23 q? 15:13:26 thx. 15:13:45 ... The last day was dominated by security. A LOT about EME. 15:14:12 ... (you may have heard about protests.) 15:14:27 ... not directly relevant for us. 15:15:03 ... Also other things on security. Bruce Schneier gave great talk. Obviously, things need to be beefed up. But doesn't directly affect our work. 15:15:47 ... One issue/advise that came up indirectly: might be worth talking about PWP ideas/structure to TAG since it touches on issues relevant to TAG. Early is probably better than later. 15:15:54 q? 15:16:03 q+ 15:16:06 ack mg 15:16:17 mgylling: was there any update on WebRTC? 15:16:34 ivan: no. light conversation (people liking it) but not a topic. 15:16:39 ... why? 15:16:56 mgylling: b/c codec opus. this is relevant for audio books. 15:17:27 tzviya: regarding security. While it might not be directly relevant, it keeps coming up. Maybe we can recruit somebody to help us catch up? 15:17:47 ivan: ??? might be a good person to talk to. 15:17:55 sorry, missed it. 15:17:58 newbie has joined #dpub 15:18:07 :) 15:18:14 rdeltour has joined #dpub 15:18:19 s/???/Virginie Galindo/ 15:18:20 q? 15:19:00 tzviya: before we continue, we have one new member: Nicholas, Stanford University. Library team, archiving, presentation etc. 15:19:25 tzviya: let's have an update from the archival TF. 15:19:34 Topic: Archival TF 15:20:10 https://www.w3.org/2016/03/24-dpub-arch-minutes.html 15:20:26 TimCole: lots of data gathering. Last call with a lot about LOCKS (?). See the minutes. 15:20:38 ... also CLOCKS, Portico. 15:20:50 ... spidering, normalizing into standard format. 15:20:59 s/LOCKS/LOCKSS 15:21:03 LOCKSS: http://www.lockss.org/ 15:21:10 ... just getting started with ebooks. Good success with journals article (using JATS). 15:21:13 CLOCKSS: https://www.clockss.org/clockss/Home 15:21:13 Regrets+ Deborah 15:21:34 ... as much as possible straight from publishers. 15:22:00 blog post on signposting the scholarly web: http://blog.dshr.org/2015/12/signposting-scholarly-web.html 15:22:04 ... we see implications from our discussions for a profile / manifest adequate for archiving services. 15:22:34 ... e.g., finding enough of a version of a package that can be used for all browsers downstream (not just one). 15:22:53 ... e.g., migrating forward parts of a package (due to changes in standards). 15:23:10 ... e.g., multiple pieces from multiple servers 15:23:13 ... so a number of use cases. 15:23:29 q? 15:23:30 ... learnging from PDF/A from Leonard 15:23:31 mgylling_ has joined #dpub 15:23:50 s/learnging/learning/ 15:23:57 thx ivan. 15:24:12 nope 15:24:35 Yay for use cases! 15:24:56 ... we're also trying to provide links and documentation for people to understand archiving. There's a section in PWP where these can go. 15:24:59 q? 15:25:09 ... still planning to talk to more groups. 15:25:29 tzviya: next up: locators. 15:25:33 http://w3c.github.io/dpub-pwp-loc/ 15:25:41 Ben: we're finishing up our documents. 15:25:50 ... we have general consensus in the task force. 15:26:04 ... we talked about next steps for the TF and document. 15:26:21 ... thinking about integrating this with the PWP document. 15:26:48 http://w3c.github.io/dpub-pwp-loc/#manifest_algorithm 15:27:08 ... the doc explains terminology, explains manifest, locator, retrieval etc 15:27:30 ... maybe go through it in detail tomorrow? 15:27:37 tzviya: are there questions? 15:27:38 q+ 15:27:42 ack iv 15:28:21 ivan: one of the main outcome of the discussion, on the one hand, the really locator specific issues are relatively simple. Almost just a bunch of definitions (what do we mean "canonical locator" etc). 15:28:26 ... most of these discussed on group level. 15:28:42 ... nothing major / new really. 15:28:46 ... two things are more general. 15:29:05 ... on the terminology level: concepts, states etc. cf. PWP. 15:29:24 ... but became clear that we need an active entity which we call "PWP processor" for now. Mostly client-side thing. 15:29:43 ... not bound to any technology but trying to identify what functionality it will have to provide. 15:30:01 ... the other new item: the really core issue is the manifest. That's what the processor needs. 15:30:13 ... the algo itself is just saying "how do you get to the manifest in various settings". 15:30:31 ... (what if only canonical locator, what you receive on http etc.) 15:31:14 ... we're converging to the point where the most complicated thing will become: what kind of information do we have in the manifest (and then possibly format as well). 15:31:20 ... here we have to synchronize with epub WG. 15:31:43 ... this is the high-level view of the TF results. 15:31:59 ... Basically, the localtor TF has done what it was supposed to do. 15:32:15 tzviya: do we want to publish this on its own or integrate into PWP or leave alone? 15:32:39 Ben: recently we discussed that it makes sense to integrate it; lots of overlap with PWP discussion. 15:32:53 ... not sure if we have to wait for PWP to be further along. 15:32:57 mgylling_ has joined #dpub 15:33:31 ivan: I think this document would be better if it's part of PWP document. But not in its current form (or else it gets huge). 15:34:00 ... the first section of PWP is basically use cases. Now that we have a use case doc, we should move/incorporate there. 15:34:10 ... then the draft becomes a more formal document. 15:34:28 ... more on technology. describe the "PWP processor" more abstractly. 15:34:34 q+ 15:34:42 ... merge so that the technical content is more elaborate. 15:34:55 ... I'd expect a section on manifest there eventually 15:35:10 ... address the problems coming from archiving etc. 15:35:14 ack mg 15:35:40 mgylling: so the part that isn't use cases would go into the PWP whitepaper? 15:35:46 need to leave for another meeting 15:35:49 ivan: yes. and the use cases should move to use case doc. 15:36:06 mgylling: depends on what we see the PWP whitepaper to become. 15:36:19 ... originally a "shallow" document, overview. 15:36:39 ... if we do this, then we're saying: we'll be growing this into something with a lot more technical detail. 15:36:39 q+ 15:36:48 ivan: the current version already has a lot of detail. 15:36:54 ... SW, state etc. 15:37:00 ... so we're moving in that direction already. 15:37:38 ... but perhaps we should keep the a short vision document. 15:38:20 q- 15:38:24 mgylling: more a minor issue. More important to research and publish this. Not important to me, just want to clarify that the whitepaper was a vision paper and is slowly becoming something different. 15:38:51 ivan: just to recap: I think the locators doesn't work as a standalone doc. 15:39:04 q? 15:39:05 tzviya: we should probably discuss the direction for the whitepaper separatelu. 15:39:15 tzviya: next up: Use Cases. 15:39:25 topic: Use Cases 15:39:41 HeatherF: romain and I discussed next steps. 15:39:49 ... a bit of a gap coming up. 15:39:56 ... we have a wide collection of use cases. 15:40:05 https://github.com/w3c/dpub-pwp-ucr/wiki/Use-Cases-Overview 15:40:16 ... but I want to go ahead and create the PWP use cases in the spirit of CEIC [?] doc. 15:40:29 http://w3c.github.io/dpub-pwp-ucr/ 15:40:49 s/CEIC/CSV on the Web 15:40:50 ... I also looked at last minutes. Looks like a lot of discussion whether packaging is or is not in scope. 15:41:21 tzviya: I think I meant that we wanted to discuss this further. 15:42:09 mgylling: we realized it's in scope but a huge chunk so we should look at this in the groups. 15:42:22 ... maybe good for virtual F2F in May. 15:42:50 q+ to talk about how people should add info 15:43:06 HeatherF: we also talked about DRM, archiving use cases. 15:43:13 ... looking for those come in. Is DRM relevant? 15:43:33 ivan: early on decided DRM is not in scope. But maybe we should revisit. 15:43:46 ... we also "lost" people who were interested in DRM. 15:44:00 mgylling: but security and privacy are not out of scope. 15:44:09 ivan: agreed. 15:44:41 ack tz 15:44:41 tzviya, you wanted to talk about how people should add info 15:44:41 tzviya: from epub, we got the idea to look at hooks for encryption/DRM instead. 15:45:02 ... other TFs might be collecting use cases in their own repos / docs. 15:45:12 ... might just be waiting for sign to move them over. 15:45:30 ... should they do issues or just add to docs? 15:45:35 HeatherF: either works. 15:46:30 q+ 15:46:35 HeatherF: I think we've covered everything in the overview. 15:46:42 ack tim 15:46:49 tzviya: I think several people promised additions but haven't. 15:47:00 TimCole: we put ours up on our wiki page. 15:47:33 ... could you walk us through what should be in the use case? So that we're sure we get the right information in. 15:48:05 HeatherF: my take: tell a story of what an actor is trying to accomplish. 15:48:33 ... not saying "using X technology to do the following" but "read a recipe and need to read it offline". 15:49:42 TimCole: let me try. "I've archived a PWP that contains several components, one of which is shared among components but that component is now newer than previously archived, do I update the component so that it's identical to PWP and archive or do I consider the original archive for that PWP?"/ 15:49:53 tzivya: best practice is making it as simple as possible. 15:50:09 https://www.w3.org/annotation/wiki/Use_Cases 15:50:12 ... that way you end up finding out whether you have one or many. 15:50:16 ... cf. annotation use cases. 15:50:28 ... those are very good. 15:50:38 ... "Tim wants to do xyz". 15:50:51 HeatherF: from that try: at least 2-3 use cases. 15:51:01 TimCole: ok, we'll try to be very granular. 15:51:24 zakim, who is here? 15:51:24 Present: Tzviya, Chris_Maden, ivan, Heather_Flanagan, Ben_De_Meester, Benjamin_Young, Charles_LaPierre, astearns, peter, krautzberger, ayla_stein, Tim_Cole, Bill_Kasdorf 15:51:28 On IRC I see mgylling, rdeltour, nullhandle, Bert, TimCole, pkra, clapierre, Vlad, bjdmeest, HeatherF, NickRuffilo, Zakim, RRSAgent, cmaden2, darobin, tzviya, ivan, Karen, liam, 15:51:28 ... shepazu, leaverou, nikos, iank_, bigbluehat, astearns, plinss, trackbot 15:51:28 tzviya: to all: don't worry about the form too much. Just write them. If they're not perfect, we don't care -- we need the info out there and can clean it up. 15:51:31 q? 15:52:00 q+ 15:52:18 ... to those how volunteered: check the wiki where your name will show! 15:52:32 ack ni 15:53:06 NickRuffilo: I sent my use case to the group, got feedback, revised it. What's my next step? Put on wiki? 15:53:12 post use cases to https://github.com/w3c/dpub-pwp-ucr/issues 15:53:14 HeatherF: eithe on the wiki or put it in an issue. 15:53:19 ... whatever you find easier. 15:53:20 q+ 15:53:23 ack iv 15:54:22 ivan: re use cases. Permissions&Obligations is starting to collect use cases. We could use more publishing use cases. 15:54:40 ... we had a mention of this work in the metadata report last year. 15:54:55 ... This is the time! Submit something to the group. Send them to me or whatever works for you. 15:55:15 ... do it now. 15:55:53 ... one more thing: the AnnotationWG has published three drafts. Pretty final. Please read through and comment! 15:56:52 wait, there are points? 15:56:59 Yes, there are points 15:57:12 tzviya: we'll be discussing the annotations documents. 15:57:46 :-D 15:58:34 clapierre has left #dpub 15:58:43 TimCole: we have a bit of traveling shortages but hopefully get an update soon. 15:58:48 ivan: the week after next sounds good. 15:59:00 q? 15:59:11 :) 15:59:16 present+ 15:59:20 thanks! 15:59:51 rrsagent, draft minutes 15:59:51 I have made the request to generate http://www.w3.org/2016/04/04-dpub-minutes.html ivan 16:00:25 cmaden2 has left #dpub 16:00:37 trackbot, end telcon 16:00:37 Zakim, list attendees 16:00:37 As of this point the attendees have been Tzviya, Chris_Maden, ivan, Heather_Flanagan, Ben_De_Meester, Benjamin_Young, Charles_LaPierre, astearns, peter, krautzberger, ayla_stein, 16:00:40 ... Tim_Cole, Bill_Kasdorf, Vlad 16:00:45 RRSAgent, please draft minutes 16:00:45 I have made the request to generate http://www.w3.org/2016/04/04-dpub-minutes.html trackbot 16:00:46 RRSAgent, bye 16:00:46 I see no action items