14:07:22 RRSAgent has joined #dpub 14:07:22 logging to http://www.w3.org/2015/06/01-dpub-irc 14:07:31 rrsagent, set log public 14:07:53 Meeting: Digital Publishing IG Telco 14:08:09 Chair: Tzviya 14:09:42 Agenda: https://lists.w3.org/Archives/Public/public-digipub-ig/2015May/0044.html 14:10:14 Date: 2015-05-01 14:48:36 Karen_ has joined #dpub 14:50:05 tmichel has joined #dpub 14:54:41 Julie has joined #dpub 14:56:55 clapierre1 has joined #DPUB 14:57:06 philm has joined #dpub 14:57:10 phil_m has joined #dpub 14:58:15 Really interesting discussion of packaging in the public-web-perf ML. One highlight: https://lists.w3.org/Archives/Public/public-web-perf/2015Jan/0041.html 14:58:55 pkra has joined #dpub 15:00:00 brady_duga has joined #dpub 15:00:32 kwkbtr has joined #dpub 15:00:38 The audio is really bad. can't understand anything ... 15:01:03 laudrain has joined #dpub 15:01:19 tzviya has joined #dpub 15:01:20 Bert has joined #dpub 15:01:22 Present: ivan_Herman 15:01:38 +Thierry Michel 15:01:40 Present+ Dave_Cramer 15:01:51 Present+ Jeff_Xu 15:01:52 Vlad has joined #dpub 15:02:08 Present+ Charles 15:02:09 Present Laura_Dawson 15:02:10 AH_Miller has joined #DPUB 15:02:19 Present+ Michael_Miller 15:02:26 bjdmeest has joined #dpub 15:02:29 Present_ Phil_Madans 15:02:37 Pressent+ Phil_Madans 15:02:40 present+ TzviyaSiegman 15:03:03 for call in information, see http://www.w3.org/dpub/IG/wiki/WebEx 15:03:13 present+ duga 15:03:19 Pressent+ Bert 15:03:24 Present+ Bert 15:03:28 HeatherF has joined #dpub 15:03:35 present+ astearns 15:03:50 Present+ bjdmeest 15:04:11 Present+ kwkbtr 15:04:19 YOu can see who is making noise on WebEx by looking at the "Speaking" bar in the top right 15:04:41 scribenick: dauwhe 15:04:45 chair: tzviya 15:04:52 TimCole has joined #dpub 15:04:57 Also, if the host mutes a person, that person cannot unmute themselves. They'll need to ask via chat. 15:05:03 all: gnashing of teeth around audio issues 15:05:30 tzviya: first we will approve minutes 15:05:33 http://www.w3.org/2015/05/17-dpub-minutes.html 15:05:36 ... minutes from last phone call 15:05:40 ... any comments? 15:05:48 [crickets] 15:05:57 ... minutes are approved 15:06:11 ... thanks to Ivan for summarizing F2F and doing tons of other work 15:06:21 http://www.w3.org/2015/05/26-dpub-minutes.html 15:06:28 ... any comments on F2F minutes? 15:06:32 [crickets] 15:06:49 Yay for scribes! 15:06:50 ... we will stipulate that all have read the minutes. 15:06:55 ... minutes are approved. 15:07:33 ... next item is recap of F2F, so let's take a look at Ivan's summary 15:07:55 https://gist.github.com/anonymous/6d1eb70a7eb2ba2a067e 15:07:56 sumary fo f2f: http://www.w3.org/blog/dpub/2015/05/30/dpub-ig-face-to-face-2015-05-26/?pk_campaign=feed&pk_kwd=dpub-ig-face-to-face-2015-05-26 15:08:14 ... we had an excellent F2F 15:08:28 ... we have lots of work ahead 15:08:33 ... [1] Packaging 15:08:47 ... we need to define core requirements, and decide if we need packaging 15:09:03 ... [2] identifiers, and laying out requirements 15:09:23 ... [3] pagination, and relationship to CSSWG and Houdini. Dave will be talking to CSSWG 15:09:37 ... [4] a11y. Defining goals of task force, working on docs 15:10:01 ... serving as liason with other publishing groups like BISG 15:10:11 ... [5] Education outreach 15:10:19 ... people don't know what we do now 15:10:31 ... we have blog, slides, etc 15:10:38 ... [6] rechartering 15:10:39 q? 15:10:44 Jeff_Xu has joined #dpub 15:10:45 ... and the future of this group over next two years 15:10:50 ... any comments? 15:10:54 [crickets] 15:11:02 q+ 15:11:06 ack K 15:11:07 q+ 15:11:09 ack Karen_ 15:11:28 Karen_: thanks to IDPF board members for attending, and Diane Kennedy from IDEAliance 15:11:39 tzviya: it was good to have a diverse group 15:11:50 ack la 15:12:03 laudrain: reading the summary, i was wondering about education 15:12:10 ... did you speak about edupub? 15:12:33 tzviya: we talked about educating the publishing community, not about edupub as a topic 15:12:54 ... Ivan, Markus, and Ralph discussed rechartering on Friday 15:13:01 https://github.com/w3c/dpub-charter/issues 15:13:04 ivan: I collected the various items on what we decided 15:13:13 ... and put up as series of issues on github 15:13:16 https://github.com/w3c/dpub-charter/labels/DPUB%20IG%20comments 15:13:38 ... 1 issue is to make it clear taht the new group is not completely new 15:13:46 ... we must follow up on work already started 15:13:51 s/taht/that/ 15:14:20 ... the other thing is possible misunderstanding on epubweb story 15:14:38 ... and there were conflicting misunderstandings 15:15:05 ... some voices seemed to understand this is a profile of epub like edupub is a profile of epub; this is not true 15:15:27 ... others were afraid that it's throwing epub 3.01 out of the window; this is not true 15:15:57 ... this is also not restricted to books, also includes journals and magazines; this is true :) 15:16:07 ... what is a possible alternative name for epubweb? 15:16:21 ... we did not find a consensus, as all possible names have downsides 15:16:34 ... and we could easily descend into css-style bikeshedding 15:16:52 ... we could call the whole thing EPUB+WEB 15:17:02 ... (emphasis on "+") 15:17:12 ... may be temporary, but I don't have anything better 15:17:19 ... there are stylistic issues 15:17:38 ... Heather pointed us to an IETF draft on packaging 15:18:08 ... it's not an alternative to w3c spec, but rather having a top-level name for package, then package/epub etc 15:18:24 http://datatracker.ietf.org/wg/arcmedia/charter/ 15:18:37 ... this shows that whole issue of packaging is interesting, and lots of people are thinking of it 15:18:53 ... that's what happened on the charter 15:19:13 ... I'm busy changing the charter, you can see it on new branch on github 15:19:36 ... the biggest problem is the deliverables and milestones 15:19:48 ... i hope a new draft will be available on Tuesday or Wednesday 15:19:54 q? 15:19:59 ... and I really really really really really really want comments 15:20:20 ... tzviya, did I forget anything? 15:20:47 tzviya: I'd cut down on number of issues, and focus on big ones, like packaging, identifiers, pagination 15:21:04 ... not everything we work on will be in charter, as they fall under bigger issues 15:21:20 ... we'll have milestones and even deadlines 15:21:38 https://rawgit.com/w3c/dpub-charter/post-f2f/index.html current draft 15:21:39 ivan: this is the current draft 15:21:59 ivan: Does HeatherL have any comment on IETF work? 15:22:13 take the red pill. 15:22:19 s/HeatherL/HeatherF 15:22:21 HeatherF: the arcmedia group is still mostly getting started, a good time to get engaged 15:22:36 ... the next ietf meeting is July in Prague; most work is done on mailing lists 15:22:42 ivan: will you be there? 15:22:45 HeatherF: Yes 15:22:53 q? 15:22:53 ivan: that will be interesting! 15:23:21 tzviya: I wanted to stress is that this the point where we decide what we're doing for the next two years 15:23:28 ... this is the soul-searching moment 15:23:40 ... speak now! 15:23:46 ... or else. 15:24:00 [mysterious beep] 15:24:02 I haven't had a chance to review the latest text, but I have it on my list for this week. 15:24:31 https://www.w3.org/dpub/IG/wiki/Functional_Requirements#Functional_Requirements_for_Packaging_Spec 15:24:43 tzviya: We need to start to put together functional requirements for various things 15:25:04 ... I wrote up some functional requirements for packaging, dauwhe added a few comments 15:26:01 ... [reading from requirements] 15:26:26 ivan: I don't understand "multiple methods of navigation" 15:26:39 tzviya: in addition to trad toc, we need a list of tables, etc 15:26:55 ... might not be part of packaging, or something you build out of ARIA 15:27:25 q+ 15:27:30 Karen has joined #dpub 15:27:57 q+ 15:28:20 Karen__ has joined #dpub 15:29:49 q? 15:29:53 ack he 15:30:08 q+ 15:30:18 HeatherF: with regards to no file size limitations, I thought we decided the operating systems may be the problem 15:30:30 ... so I'm not sure if we can do anything 15:30:50 ack brady_duga 15:30:53 brady_duga: at the end of the day it's nice to say there's no file size limits 15:31:07 ... i've seen 600k CSS files, but we handle it slowly 15:31:22 ... we can't handle arbitrarily large content, in practice there will be limits 15:31:37 ... in terms of zip, reading systems must support zip 64 15:31:52 ... if you give me a book larger than zip64 limit, I refuse to process 15:32:01 ... so I don't thing there's a serious limit in epub today 15:32:11 tzviya: how would you modify the file size comment 15:32:29 brady_duga: saying there's no limit is impossible because physics 15:32:41 ... a really huge limit is fine 15:32:56 q? 15:32:58 ... any limit we set today will be meaningless in five years 15:33:04 tzviya: does that work for you 15:33:18 HeatherF: I'm sad we can't just say, "Don't be stupid!" 15:33:30 q+ 15:33:38 ack iv 15:33:39 :-) 15:33:39 tzviya: anything else, brady? 15:33:46 ivan: there's a minor thing 15:33:57 ... maybe we want to add possibility of heirarchy 15:34:05 ... you already do this in edupub 15:34:16 tzviya: I'll add this 15:34:22 ivan: the other thing is more complicated 15:34:30 https://lists.w3.org/Archives/Public/public-digipub-ig/2015Jun/0001.html 15:34:37 ... I sent an email a few hours ago, early in the U.S. morning 15:34:54 ... we have a separate issue in fragmentation, but the problem is interrelated 15:35:12 ... [fragment IDs, unrelated to layout] 15:35:22 ... problem is with online vs offline 15:35:40 email discussion: https://lists.w3.org/Archives/Public/public-digipub-ig/2015Jun/0001.html 15:35:53 ... if there's no packaging, some of these issues disappear, says brady_duga 15:36:02 ... so first question is, do we need a package at all? 15:36:09 ... we had part of that question last week 15:36:21 ... we had some consensus about needing a package 15:36:32 q? 15:36:37 ... we need differentiation between publication as package and on web 15:36:41 ... there are deep issues here 15:36:56 tzviya: I've been in meetings all morning, but haven't read the email chain 15:37:04 ... I think it needs to be a long discussion 15:37:12 ... for purpose of requirements 15:37:15 q+ 15:37:24 ... a package is necessary; I tried to capture it in first item 15:37:34 ... I can break that into two items 15:38:00 [uncomfortable silence] 15:38:02 ack jeff 15:38:12 Jeff_Xu: First time for me at this meeting 15:38:20 ... I have question about file size limitation 15:38:31 ... even if OS can allow large package 15:38:50 ... how to download package efficiently, is that in the scope of our requirements 15:39:18 tzviya: I don't think we want to talk about specific component size limits 15:39:22 ... things like change over time 15:39:30 s/like/like that/ 15:39:43 ... if we say a video can only be 1g today 15:39:50 ... in a few years the limit may be higher 15:40:04 ... we're all in agreement that file size should not be specified 15:40:18 Jeff_Xu: even with size limitations now, can be changed in future 15:40:37 ack br 15:40:37 ... do we want to provide protocol to download large packaage separately 15:40:47 brady_duga: I'm on queue for different reasons 15:41:27 tzviya: if anyone has opinions on what we should be telling systems about downloading then please stand up 15:41:39 brady_duga: other than best practices docs, there's not anything we tell people today 15:41:50 Jeff_Xu: maybe it's not in scope 15:42:10 ... when we download audio book or comic book it's really large 15:42:16 ... can be really slow 15:42:35 ... or maybe some other group should talk about this 15:42:45 brady_duga: this is covered by streamable and random access 15:42:52 Jeff_Xu: yes 15:42:54 tzviya: OK 15:43:11 brady_duga: do we need a packaging format? in some sense the answer is yes 15:43:17 ... we have one today 15:43:27 ... the question is, other than for portablility 15:43:52 ... do I need a package if I'm not transferrring between people 15:44:01 q+ 15:44:12 ... if I'm a reading system, I don't think we need a packaging format 15:44:29 ... we don't need random access if we're just transferring things betweeen people 15:44:52 ... but the reading system does need to support random access, but that could happen with expanded files 15:45:15 ... my real comment is, do we need a packaging format for anything other than transferring between entities? 15:45:34 ack iv 15:45:39 tzviya: more important for identity? So I can point to something in ten years. Maybe it's about archiving 15:46:04 ivan: the whole idea, conceptually, of this epub+web story, is that the two cases you refer to 15:46:12 ... I have book downloaded vs I have book on web 15:46:24 ... there should be no difference between these two situations 15:46:40 ... if book is completely online, then I agree for that purpose you don't need packaging 15:46:50 ... in the sense of a zip or tar on a disk 15:47:14 ... distinguish between physical packaging and logical entitiy 15:47:32 ... the logical entity is a colleciton of files which together make a publication 15:47:40 ... a "virtual package" 15:47:45 ... we need to have a URI 15:47:53 ... the discussion I started is around that 15:48:12 ... I would like to see a URI for the package, and for each of the constituents, whether the package is virtual or not 15:48:13 q? 15:48:17 ... and I"m not sure what that is 15:48:29 ... how that translates into the requirements, I'm not sure 15:48:45 brady_duga: the idea of this uri that's the same for server vs download, not sure how that works 15:48:56 ... are you envisioning the uris are the same? 15:49:01 s/I"m/I'm 15:49:03 ivan: the identification will be the same 15:49:19 brady_duga: in one case I have authority in my url, in one I don't 15:49:29 ivan: [crickets] :) 15:49:35 ... not sure what is possible 15:50:06 ... if one chapter refers to another, it should not be a problem with relative URIs 15:50:22 ... if I use annotations, and I want them to work online and offline, not sure how to solve that 15:50:29 ... what URI do I use for annotation? 15:50:45 brady_duga: your first example is not in requirements 15:50:56 ... on the 2nd case, I don't know how you solve that either 15:51:13 tzviya: let's make that a requirement, even though I tried not to make the impossible a requirement 15:51:33 brady_duga: this is already handled by OCF, require everything to be relative URLs 15:52:01 [discussion of exact language of new requirement] 15:52:14 Sorry, my call dropped 15:52:23 tzviya: links remain stable whether publication is online or offline 15:52:33 ... this seems more of an identifier requirement 15:52:40 ... but they are linked 15:52:43 q+ 15:52:50 ack Tim 15:52:56 TimCole: it's part of the annotation problem 15:53:08 ... do we envision that a package can be served at multiple places 15:53:22 ... get chapter 1 from server A, get chapter 2 from server B 15:53:32 ... in which case the relative URIs get very complex 15:53:44 tzviya: I did add this as functional requirement 15:53:48 https://www.w3.org/dpub/IG/wiki/Functional_Requirements#Functional_Requirements_for_Packaging_Spec 15:54:00 ... it's good there's a heated discussion 15:54:05 ... please take a look at the doc 15:54:17 ... the goal is to get a list together in the next few weeks 15:54:40 q+ 15:54:44 ack da 15:55:39 dauwhe: will post interesting links from public-web-perf mailing list on their review of packaging 15:55:51 tzviya: anything for next week? 15:56:13 ... might be education or outreach or identifiers 15:56:18 ???: I think identifiers 15:56:23 tzviya: we have four minutes 15:56:27 ... any last comments? 15:56:28 s/???/Heather/ 15:56:35 [explosions] 15:56:41 tzviya: thanks everyone 15:56:46 [beeping] 15:56:51 *LOL* 15:56:54 Jeff_Xu has left #dpub 15:57:03 rrsagent, draft minutes 15:57:03 I have made the request to generate http://www.w3.org/2015/06/01-dpub-minutes.html tmichel 15:59:40 clapierre has joined #DPUB 16:43:59 clapierre has left #dpub 17:09:40 dauwhe_ has joined #dpub 17:21:05 Karen has joined #dpub 17:43:54 plinss has joined #dpub 17:46:37 tzviya has joined #dpub 18:10:11 Zakim has left #dpub 19:36:09 dauwhe has joined #dpub 20:21:32 Bert has left #dpub 20:35:43 Karen_ has joined #dpub 20:48:49 dauwhe_ has joined #dpub 21:59:09 Karen has joined #dpub 22:21:29 Karen_ has joined #dpub