15:48:22 RRSAgent has joined #dpub 15:48:22 logging to http://www.w3.org/2014/02/10-dpub-irc 15:48:24 RRSAgent, make logs public 15:48:24 Zakim has joined #dpub 15:48:26 Zakim, this will be dpub 15:48:26 ok, trackbot; I see DPUB_DPUBIG()11:00AM scheduled to start in 12 minutes 15:48:27 Meeting: Digital Publishing Interest Group Teleconference 15:48:27 Date: 10 February 2014 15:48:50 lizadaly has joined #dpub 15:50:17 I pointed to the wrong URL in the agenda, my apologies 15:51:26 We're discussing Pagination/DOM interaction under http://www.w3.org/dpub/IG/wiki/UseCase_Directory 15:53:10 fjh has joined #dpub 15:55:42 zakim, code? 15:55:42 the conference code is 3782 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), ivan 15:56:18 DPUB_DPUBIG()11:00AM has now started 15:56:25 +MIT531 15:56:47 zakim, MIT531 holds ivan, liza 15:56:47 +ivan, liza; got it 15:56:51 philm has joined #dpub 15:56:54 zakim, who is here? 15:56:54 On the phone I see MIT531 15:56:55 MIT531 has ivan, liza 15:56:56 On IRC I see philm, fjh, lizadaly, Zakim, RRSAgent, dauwhe, marilyn, cwdoh, ivan, liam, astearns, plinss, trackbot 15:57:29 +dauwhe 15:57:38 Zakim, unmute me 15:57:38 dauwhe was not muted, dauwhe 15:57:45 tzviya has joined #dpub 15:58:03 +Marilyn 15:58:23 +Philm 15:58:33 tmichel has joined #dpub 15:59:03 -Philm 15:59:20 Bill_Kasdorf has joined #dpub 15:59:25 Luc has joined #dpub 15:59:27 benjaminsko has joined #dpub 15:59:28 +azaroth 15:59:30 brady_duga has joined #dpub 15:59:37 azaroth has joined #DPUB 15:59:45 +Philm 15:59:45 zakim, am I muted? 15:59:47 I don't understand your question, azaroth. 15:59:52 zakim, who is muted 15:59:52 azaroth, you need to end that query with '?' 15:59:55 zakim, who is muted? 15:59:55 I see no one muted 15:59:57 +Tzviya 16:00:05 zakim, thanks for not muting us all! 16:00:05 I don't understand 'thanks for not muting us all!', azaroth 16:00:07 +Bill_Kasdorf 16:00:07 +duga 16:00:17 + +33.1.41.23.aaaa 16:00:19 zakim, you are not polite... 16:00:20 I don't understand 'you are not polite', ivan 16:00:44 regrets: Markus, Vlad, JeanKaplansky 16:00:53 SCRIIIIIIIIBE 16:01:03 +Stearns 16:01:09 + +1.917.447.aabb 16:01:21 karen has joined #dpub 16:01:28 zakim, aabb is benjaminsko 16:01:28 +benjaminsko; got it 16:01:45 zakim, pick a victim 16:01:45 Not knowing who is chairing or who scribed recently, I propose azaroth 16:01:51 thanks Zakim 16:02:06 +[IPcaller] 16:02:07 scribe: azaroth 16:02:08 zakim, IPcaller is me 16:02:08 +fjh; got it 16:02:10 scribenick: azaroth 16:02:34 +??P3 16:02:41 zakim, ??P3 is me 16:02:41 +tmichel; got it 16:03:00 Liza: Can we approve the previous minutes? 16:03:11 ... Assuming no objections? Okay... approved. 16:03:13 +Bert 16:03:17 Bert has joined #dpub 16:03:25 +LFowler 16:03:29 ... There were corrections that Karen missed in the previous set. Don't know if they've been updated or not 16:03:38 ???: They've not been updated, so we should leave 16:03:48 Liza: That's fine. Markus isn't back till next week 16:03:55 s/???/tmichel/ 16:03:59 s/???/tmichel 16:04:06 dshkolnik has joined #dpub 16:04:13 http://www.w3.org/dpub/IG/wiki/UseCase_Directory 16:04:23 ... Okay, there are use cases for pagination posted at the bottom of the use case directory. About 6 of them from Brady 16:04:33 http://www.w3.org/dpub/IG/wiki/UseCase_Directory#Pagination.2FDOM_interaction 16:04:39 ... he isn't going to lead the task force so one goal is to find an owner to shepherd them 16:04:54 ... Brady would you mind talking us through the goals for the TF? 16:05:13 + +1.415.832.aacc 16:05:21 brady: This game up in China. We talked a lot about how you style a page, Dave is doing latineq and lots of work being done in CSS 16:05:36 ... but for reading system we need to know more than just how to break it into pages, but also how to reference a page 16:05:40 Zakim, aacc is dshkolnik 16:05:40 +dshkolnik; got it 16:05:42 s/game/came/ 16:05:54 gcapiel has joined #dpub 16:05:58 Zakim, mute me 16:05:58 dshkolnik should now be muted 16:06:09 ... so have to trick things into thinking that they're pages. RS needs to know how many pages are in the document, how to change the page size, display multiple pages at the same time 16:06:18 ... some sort of object model for what a page is and how to refer to it 16:06:30 q+ 16:06:33 ... that's the use cases. In China I was asked to write up a few, which are now on the wiki 16:06:41 ... goes beyond style, into a model. 16:06:46 +??P28 16:07:00 Liza: Assumption is it's about how a RS would behave, not necessarily how it would be supplied? 16:07:16 Brady: Wrote as a RS implementer, but could be use cases from the publisher side 16:07:17 q+ 16:07:25 Zakim, ??P28 is Me 16:07:26 +gcapiel; got it 16:07:48 ... Publisher has lots of style issues, but also may need to know about where pages are and how they work. Esp if there's javascript 16:07:59 ack dauwhe 16:08:02 ... a JS widget that needs to know how many pages there are, the publisher would be interested 16:08:33 dauwhe: A couple of things from CSS point of view, some discussion about this sort of thing in CSS, important to be able to know what a page is and how to address it 16:09:00 ... work on fragmentation might help here. Publishers interested in styling things based on which page they're on and the position within the page 16:09:25 ... so far css isn't really addressing that issue. working on selecting the master page in the InDesign sense, but that doesn't select the content of the page 16:09:30 q+ 16:09:32 ack ivan 16:09:33 ... lots of pieces to this 16:09:38 q- 16:10:18 Ivan: Ran into a problem that relates -- a book that also had illustrations and caption of illustration was quote from the text. Quote said this is on page 622. And then it wasn't, depending on reflowing. 16:10:36 ... so publishers have to have some special way to encode it, so the RS can get it right. Can't completely forget about it 16:11:12 dauwhe: generated content for paged media module has that kind of page referencing property. Can retrieve the page number from the link and display it to have the right number 16:11:19 Ivan: Publishers have to know how to do that. 16:11:31 dauwhe: And it has to be implemented. Not sure of implementation outside of Random House 16:11:42 ???: It needs to be embedded in teh content? or working interactively? 16:11:50 s/Random House/Antenna House/ 16:12:00 ??? was Bill_Kasdorf 16:12:07 dauwhe: You can say link to a heading somewhere ... there's an illustration far away. THen you write CSS to say get the ID value and find the page value, display that here 16:12:08 ack tzviya 16:12:17 s/???/Bill_Kasdorf/ 16:12:18 s/???/Bill_kasdorf 16:12:49 tzviya: If we're working on implementing JS, we can call it a viewport or page, we don't know where things are going to land on the page. Eg a touch event, we want to contain it to a particular screen 16:13:11 lizadaly: I wasn't really considering publishers writing interactive components inside a book, not common now but should be 16:13:18 http://dev.w3.org/csswg/css-gcpm/#target-counter 16:13:21 ... they'll want a common way to reference pages 16:13:45 tzviya: page references in a cook book, you might say see recipe on page 72, but in academic work citations are more complicated 16:13:51 ... working with references across works 16:13:58 ... probably not in scope, but want to consider it 16:14:22 lizadaly: linking is important, but should probably confine it to pagination rather than the whole world of references 16:14:54 q+ 16:14:56 ... sounds like someone other than a RS vendor should come up with publisher centric use cases before we can say it's complete 16:14:57 In digital magazine world we see a lot of custom JavaScript from publishers. The contract between Adobe Content Viewer and the publishers content is that we call onAppear()/onDisappear() when page is displayed. 16:14:58 ack ivan 16:15:31 ivan: what's the next steps? in China we wondered whether it means we need changes or extensions to the current DOM model, or not? 16:15:42 ... that would be a very specific, heavy technical requirement 16:15:50 ... need to be careful before issuing such a requirement 16:15:59 ... is that where we're going, or can we get around it? 16:16:29 lizadaly: no way to reference a particular page in DOM other than with lots of JS hacks 16:16:40 q+ 16:16:41 ... can't even say what page you're currently on. 16:16:52 ... need a solution 16:17:13 +madi 16:17:21 brady_duga: Agree there isnt' a solution today. Two options -- modify the way DOM works or layer a solution on top of it 16:17:35 ... that might be possible without changing the dom, but some other way to map between elements in the DOM and pages 16:17:39 madi has joined #dpub 16:17:50 ... only want to show this portion of the DOM because that's the page we're on. DOn't know which is the way to go 16:17:55 ack dauwhe 16:18:35 dauwhe: Actually changing the DOM seems like an incredibly high hurdle. not an expert but lots of work on extensions to the DOM to talk about things not really in the dom like pseudo elements 16:18:59 ... wonder if there's possibility in that space to be able to manipulate the objects we want to talk about 16:19:02 q+ 16:19:09 ack astearns 16:19:28 astearns: one possibility for building on top of the dom is to use css regions. 16:19:51 ... when you fragment content with regions you have some scripting access to the region chain, you can find out which position the region is in the chain 16:20:09 ... so you can find out what page content is on, so long as you map regions to pages 16:20:22 ... so can build on top of that as it lets you do some of the things raised 16:20:41 lizadaly: Remember an early draft of the spec, excited that it gives that level of access. 16:20:53 q+ 16:20:55 astearns: the spec is moving along. Mozilla is not terribly interested 16:21:05 ... Chrome decided to take it out for now as mozilla aren't doing it 16:21:16 ack ivan 16:21:19 ... implementation in safari, and older version in IE. Need to wait for other browsers 16:22:02 ivan: good example. Don't know why mozilla isn't interested, but tells me that if it's a solution or main component for the publishing industry, then the IG should make it clear to the parties 16:22:10 ... that as far as we're concerned, this should have a high priority 16:22:25 q+ 16:22:37 ... as it solves a big problem. Alan you're on the CSS WG, what can this IG do to try to increase the priority of implementation? 16:22:46 ack dauwhe 16:22:51 lizadaly: Helpful to say that it's very important 16:22:53 zakim, code? 16:22:53 the conference code is 3782 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), karen 16:23:05 astearns: I think it would be good to talk about use cases rather than specific technology 16:23:26 ... knowing the page number, what content is on the page, etc. need to get that information from the reading system to act on 16:23:43 +Karen_Myers 16:23:44 ... noting regions has the capability built in. A better way to put pressure. 16:24:17 dauwhe: wondering if regions can address these kinds of issues? Can it do it behind the scenes without publishers writing in all the region machinery in CSS? 16:24:47 ... can it interpret pagination or something a RS could use to implement pagination and then expose hooks without publishers having to assign everything individualy 16:25:00 astearns: Good question. Goes to promoting use cases not technology 16:25:02 regrets+ Julie 16:25:16 ... believe it will be that there'll be JS libraries built on top of regions that gives the functionality 16:25:31 ... or we look at how regions and js interact, and find a lower level way in CSS to do the same thing 16:25:48 ... so regions+ js to me is the right way to address a lot of the use cases, but I could be wrong 16:26:17 lizadaly: when i first saw some region support in chrome, pagination and seeking to a page, can't say it would solve all the use cases here, but was very promising 16:26:21 ... better than previous solutions 16:26:31 astearns: Some limitations, when you get to very long documents 16:26:48 ... regions + script may not be performant enough. might inform where we need to work. 16:27:07 ... Brady and Rosen from MS were talking about the next steps and how to get a long pagination scenario working okay 16:27:24 lizadaly: agree that's been a problem with all the solutions I've seen so far -- they fall apart in long streams 16:27:30 q+ 16:27:34 ack ivan 16:27:59 ivan: not like trying to push anyone but this tells me it would be relatively urgent to get these use cases documented and published 16:28:06 ... could be the time when the pressure could work 16:28:21 ... if we are too late with the UCs then could be too late and will be pushed back to CSS4 16:28:29 +1 16:29:03 brady: Curious what the next steps are? Not sure I even proof read them. Need more people to add use cases? 16:29:08 q+ 16:29:27 ack dauwhe 16:29:30 ivan: At some point we need to publish working draft -- a more formal doc from the IG -- that we can put on the desks of appropriate people 16:29:49 dauwhe: another use case is the desire to style things on page position, eg recto/verso 16:29:57 ... do those use cases help? 16:30:09 +1 to r/v from medieval manuscript scholar 16:30:25 lizadaly: changing properties of the text based on pagination 16:30:34 dauwhe: a better foundation for pagination than currently 16:30:48 lizadaly: would like to see some publisher focused use cases listed 16:31:08 ... styling or js apis that publishers could make use of that understand pagination seems relevant 16:31:30 ... might want to be explicit that performance is important 16:31:40 I was thinking of Random and Simon 16:32:06 tzviya: Simon & Schuster, also Random House 16:32:17 dauwhe: wanting to do things particularly with a spread 16:32:29 ivan: who should reach out to Lisa ?Cachin? 16:32:35 Liisa 16:32:44 dauwhe: I will 16:33:02 dauwhe: action on Ivan to get them to join :) 16:33:07 -Karen_Myers 16:33:28 ivan: reaching out a good idea. 16:33:47 tzviya: S&S work on children's books a lot. but if Liisa has good examples that's probably sufficient 16:33:53 ... RH is a great start 16:34:17 ivan: what about STEM? mathematical text books with cross refs in pages, formulae etc was incredibly important 16:34:27 ... can also ask Jean 16:34:40 tzviya: can talk about over lunch at EduPub 16:34:49 +Karen_Myers 16:35:10 lizadaly: Another pass through the use cases would be good 16:35:20 brady_duga: I'll take another pass through them 16:35:35 lizadaly: publisher focused ones will take a little longer 16:35:47 ivan: brady are you in a position to lead the TF? 16:36:05 brady_duga: I think we should find someone else, if I take the leadership it won't get done 16:36:17 ... can't really take on anything much at this point and expect anything to happen with it 16:36:29 ... can help out 16:36:44 ivan: so next question is who? 16:36:58 lizadaly: I vote for Liisa :) 16:37:10 s/lizadaly/tzviya/ 16:37:15 ivan: There was a meeting last week but I don't think it would be appropriate at this moment 16:37:18 but +1 :) 16:37:31 karen: Don't want to discourage reaching out, but they don't see a compelling reason to participate at the moment 16:38:04 ivan: We'll reach out anyway for use cases regardless 16:38:12 karen: I think she'd be happy for use cases 16:38:22 ivan: Getting her as an IE probably not doable at the moment 16:38:27 ... so need someone else 16:38:44 brady_duga: would love to but am wildly overly committed 16:39:03 tzviya: have you heard from elsevier? 16:39:07 s/brady_duga/dauwhe/ 16:39:24 ivan: contact goes back 5 or 6 years. 16:40:07 ivan: oxford university press ... some contact but not the right person. OUP is a member as part of Oxford. 16:40:22 ... matter of finding the right person 16:40:34 lizadaly: we build their impelemntations so can talk to team and find the right person 16:40:49 ivan: I can reach out but several attempts would be good 16:40:59 lizadaly: we normally work with humanities and reference group 16:41:15 ivan: a problem we have to solve, but not necessarily right now 16:41:30 lizadaly: This was only thing on the agenda 16:41:32 q+ 16:41:39 ack azaroth 16:42:09 Sorry, I have to leave 16:42:12 azaroth: we discussed approving annotation use cases and added accessibility to use cases 16:42:19 - +33.1.41.23.aaaa 16:42:23 ...should i begin work on note? 16:42:33 ivan: starting to work on note will help to clean up use cases 16:42:37 (Thanks tzviya) 16:42:54 ... so I would start turning them into a real document. While doing that some issues will come up to discuss 16:43:06 ... you have the infrastructure? 16:43:09 azaroth: Yup 16:43:20 ivan: If you need help you know where to find it :) 16:43:24 lizadaly: AOB? 16:43:31 -LFowler 16:43:31 ... Okay, thanks every one 16:43:32 -madi 16:43:33 -fjh 16:43:33 -benjaminsko 16:43:34 -Philm 16:43:34 -Bill_Kasdorf 16:43:35 -MIT531 16:43:35 -Karen_Myers 16:43:35 -Tzviya 16:43:36 -duga 16:43:36 -dauwhe 16:43:38 -Stearns 16:43:39 -azaroth 16:43:41 -Bert 16:43:42 -dshkolnik 16:43:47 gcapiel has joined #dpub 16:43:55 -gcapiel 16:44:46 -tmichel 16:45:00 rrsagent, draft minutes 16:45:00 I have made the request to generate http://www.w3.org/2014/02/10-dpub-minutes.html tmichel 17:05:01 disconnecting the lone participant, Marilyn, in DPUB_DPUBIG()11:00AM 17:05:02 DPUB_DPUBIG()11:00AM has ended 17:05:02 Attendees were ivan, liza, dauwhe, Marilyn, Philm, azaroth, Tzviya, Bill_Kasdorf, duga, +33.1.41.23.aaaa, Stearns, +1.917.447.aabb, benjaminsko, fjh, tmichel, Bert, LFowler, 17:05:03 ... +1.415.832.aacc, dshkolnik, gcapiel, madi, Karen_Myers 17:05:13 Bert has left #dpub 18:01:13 cwdoh has joined #dpub 18:41:52 marilyn has joined #dpub 18:55:54 ivan has joined #dpub 19:00:35 gcapiel has joined #dpub 19:03:41 Zakim has left #dpub