15:34:25 RRSAgent has joined #pwg 15:34:25 logging to http://www.w3.org/2017/10/16-pwg-irc 15:34:26 rrsagent, set log public 15:34:26 Meeting: Publishing Working Group Telco 15:34:26 Chair: garth 15:34:26 Date: 2017-10-16 15:34:26 Regrets+ marisademeglio 15:34:26 Agenda: https://lists.w3.org/Archives/Public/public-publ-wg/2017Oct/0016.html 15:34:26 ivan has changed the topic to: Meeting Agenda 2017-20-16: https://lists.w3.org/Archives/Public/public-publ-wg/2017Oct/0016.html 15:50:24 MarthP has joined #pwg 15:53:36 George has joined #pwg 15:54:33 Avneesh has joined #pwg 15:54:56 present+ 15:55:21 present+ dauwhe 15:56:03 present+ George 15:56:03 present+ wolfgang 15:56:50 timCole has joined #pwg 15:57:39 Vlad has joined #pwg 15:58:22 jeffp has joined #pwg 15:58:27 present+ 15:58:45 present+ 15:59:02 present+ 15:59:11 present+ Tim_Cole 15:59:51 JunGamo has joined #pwg 15:59:54 present+ George 16:00:04 present+ JunGamo 16:00:13 baldurbjarnason has joined #pwg 16:00:22 rkwright has joined #pwg 16:00:27 laudrain has joined #pwg 16:00:29 LSullam has joined #pwg 16:01:09 present+ Chris_Maden 16:01:35 present+ Lillian Sullam 16:01:40 present+ baldurbjarnason 16:01:47 josh has joined #pwg 16:01:47 present+ 16:01:48 present+ 16:01:50 Zakim, who isn't here? 16:01:50 I don't understand your question, dauwhe. 16:01:58 present+ 16:02:00 regrets+ deborah 16:02:02 laurentlemeur has joined #pwg 16:02:04 Present+ Luc 16:02:09 regrets+ pkra 16:02:11 present+ 16:02:14 mateus has joined #pwg 16:02:21 present+ 16:02:21 present+ Laurent 16:03:02 scribenick: dauwhe 16:03:16 regrets+ leonard 16:03:17 Bill_Kasdorf has joined #pwg 16:04:06 tzviya: let's get started 16:04:13 [ping pong chime] 16:04:30 https://www.w3.org/publishing/groups/publ-wg/Meetings/Minutes/2017/2017-10-02-minutes.html 16:04:33 Topic: last minutes 16:04:39 present+ rachel 16:04:40 tzviya: any comments on the minutes? 16:04:45 present+ 16:04:45 RESOLVED: minutes approved 16:04:45 tzviya: minutes approved 16:04:47 present+ 16:04:54 present+ 16:04:54 tzviya: any new members this week? 16:04:58 Topic: new members 16:05:28 ???: this is Marty from Atypon, which is part of Wiley 16:06:01 Topic: spring f2f dates 16:06:14 tzviya: we have a form for possible dates for the spring F2F 16:06:15 s/???/Marty 16:06:19 https://www.w3.org/publishing/groups/publ-wg/Meetings/Minutes/2017/2017-10-02-minutes.html 16:06:29 ReinaldoFerraz has joined #pwg 16:06:34 https://docs.google.com/forms/d/e/1FAIpQLSc0YlroocKuvfP0bd5pNRFUChY7QJ2gYGOkE7zx-tSSpkBxkg/viewform?c=0&w=1&usp=mail_form_link 16:06:53 DarthVader: (unintelligible) 16:06:56 BenSchroeter has joined #pwg 16:07:01 tzviya: please fill out the form 16:07:05 present+ 16:07:53 garth: there's no time like the present, so if you haven't filled out the form please do so now! 16:08:13 duga has joined #pwg 16:08:14 ... we will probably discuss this on Wednesday, and have a final decision soon 16:08:15 Topic: Lifecylcle of a WP 16:08:20 present+ 16:08:22 present+ garth 16:08:54 mattg: the lifecycle is picking up from where we left off two weeks ago 16:09:03 ... we don't want to proscribe a solution for the FPWD 16:09:10 Garth has joined #pwg 16:09:15 present+ Garth 16:09:15 ... I'm just taking the issues that have surfaced all along 16:09:22 (on the right channel this time) 16:09:26 ... so I'm trying to lay out the general topics in an editor's note 16:09:36 ... so we don't have a big gap in our spec 16:09:48 ... the first part is basic principles... we're not trying to break or fork the web 16:09:59 ... and that a web publication shouldn't have to be it's own app 16:10:02 q? 16:10:12 ... the second part is a breakdown of what used to be in this section 16:10:21 ... the issues and problems around initializing the WP 16:10:22 The version of Matt's contribution in the PR: https://s3.amazonaws.com/pr-preview/w3c/wpub/lifecycle.html 16:10:49 GarthVader: it's in the IRC 16:11:05 mattg: taking it offline, searching across documents, how do you traverse history... 16:11:16 ... updating a manifest... these are issues we know we will face 16:11:23 ... this is what's on our plate 16:11:51 ... do we integrate this? Should we list more? How should we get feedback? Broad issues in GitHub haven't worked well in the past. 16:11:59 q? 16:12:01 ... we want a wide range of people to voice their opinions 16:12:14 ... we should put something in SOTD about what we want feedback on 16:12:21 q? 16:12:23 ... fin 16:12:33 q+ 16:12:37 Garth: any feedback right now for matt? 16:12:42 q+ 16:12:46 ... consensus to accept the PR? 16:12:50 q? 16:12:53 q? 16:13:07 Leslie has joined #pwg 16:13:07 ivan: first, I think the PR should be merged 16:13:18 s/MarthP/MartyP/ 16:13:19 ... as for getting more feedback, TPAC isn't far away, so we will discuss there 16:13:25 ack ivan 16:13:44 ... and then make a lot of noise when the FPWD is out, maybe right after TPAC 16:13:57 tzviya: I'm in the ship-it category 16:14:12 ... once we publish, we might want to contact specific people, and ask for feedback 16:14:16 q? 16:14:17 ... like the browserfolk 16:14:19 ack tzviya 16:14:27 Garth: that sounds good to me 16:14:34 +1 16:14:42 ... Matt, Make It So (in Picard voice) 16:14:59 Garth: Leonard is next? 16:15:04 ivan: He had an emergency 16:15:14 Hadrien has joined #pwg 16:15:20 Garth: we can move this to next week 16:15:23 present+ 16:15:34 https://docs.google.com/document/d/12J3Y3bb5fdPh1r2XH9YloINkNSxBJArocKY108sYCZ0/edit?usp=sharing 16:15:40 ... next is timCole on selectors 16:15:55 https://w3c.github.io/publ-loc/ 16:16:02 https://w3c.github.io/publ-loc/ 16:16:10 Topic: Locators 16:16:24 timCole: there's a PR associated with this discussion about internal locators 16:16:32 ... how to identify a fragment or location in a wp 16:16:43 ... we tried to put that in WPUB doc, but it was too long 16:16:49 ... so we started a new document 16:16:50 q? 16:16:58 ... so Ivan wants to introduce the context 16:17:08 ivan: for those who didn't read this or its predecessor 16:17:16 ... this is the selector model from the web anno WG 16:17:33 ... we should be able to point to an area in a resource that might not have an ID 16:17:42 ... bookmarking or annotation is the obvious example 16:17:48 ... that goal is the same as for epub cfi 16:17:56 ... but the group took a different approach 16:18:06 ... because a single solution wouldn't work 16:18:25 ... so the group developed a JSON object that included various ways of IDing a point 16:18:37 ... could be ID, could be text match, could be character index, could be range 16:19:06 ... the idea was that IDing these things as JSON, an annotator can handle that 16:19:15 ... we were looking at it for WP 16:19:23 ... we think it could solve the use cases 16:19:37 ... 2 issues: we had to expand the web anno model 16:19:51 https://github.com/w3c/publ-loc/issues 16:20:00 ... if we have a WP we might need a range spanning multiple docs 16:20:07 ... the other issue is more general 16:20:15 ... EPUB CFI was a fragment identifier 16:20:26 ... web anno is a json structure and not a fragment identeifier 16:20:39 ... there's a way to encode the JSON into a fragment identifier 16:20:47 ... the Q is, do we really need that? 16:21:02 ... those fragment identifiers are even harder to read than CFI 16:21:26 ... and we also have to go through an IANA registration... there are lots of admin hoops 16:21:41 ... for the use cases for WP, do we really need fragment identifiers 16:21:55 s/identeifier/identifier/ 16:21:58 ... or can we use the JSON structure, knowing that annotation systems already have adopted these 16:22:14 ... there are also some issues around details 16:22:22 q? 16:22:39 timCole: I want to go thru a couple of use cases in CFI 16:22:45 q+ 16:22:59 Guests+ Marty_Picco 16:23:16 rdeltour: to clarify, one of the reqs for CFI was that they could be sorted 16:23:28 ack rdeltour 16:23:29 ... you could tell if one was after the other, you could sort in doc order 16:23:31 q? 16:23:40 ... that isn't possible with this proposal 16:23:47 ... but I don't think it's important for our needs 16:23:52 q? 16:23:59 ivan: I agree with both--it cant be done, and it's not terribly important 16:24:07 timCole: the Q is how fixed is the reading order? 16:24:13 s/cant/can't/ 16:24:17 tzviya: why does it always come back to that? :) 16:24:32 Garth: we do have dependency on the reading order for ranges crossing docs 16:24:41 q+ 16:24:46 timCole: we suggest you just list the resources and their segments 16:24:57 guest+ rachel 16:24:58 q? 16:25:01 ... it assumes that there's some reason they are grouped 16:25:05 ack rachel 16:25:23 rachel: the issue across docs carries into the higher ed market, this is a problem we have with CFI 16:25:33 ... we can't make CFIs that cross HTML files 16:25:53 Garth: I remember that ranges were done with two pointers, which implies knowing the reading order 16:26:16 timCole: in the original webanno model, there was a range indicator for within a single file 16:26:39 ... we're looking now at multi-resource selector where you get identification thru any of the other selectors 16:26:55 ... I don't know how well this would work, because we haven't tried 16:27:20 Garth: so if you're starting in doc 3 and ending in doc ten, you'd have to reference (4..9) 16:27:26 timCole: yep 16:27:27 q? 16:27:33 ... that's new 16:27:52 q+ comment about index ranges and fragids 16:27:57 timCole: don't know if it will be good enough for Rachel's use case. We should talk at TPAC 16:28:07 q+ to comment about indexes and fragids 16:28:10 Garth: this is potentially problematic with multiple reading orders 16:28:18 q? 16:28:34 https://github.com/w3c/publ-loc/issues 16:28:41 timCole: if you go to the link, and look at the issues 16:28:49 Karen has joined #pwg 16:28:50 ... the frag ID question Ivan already mentioned 16:29:03 ... in the web anno model, we're always talking about a chunk of content 16:29:09 ... everything is a segment of a file 16:29:28 ... in CFI, there's location and there is side bias 16:29:57 ... do you need to specify a position between char 6 and 7, but bias to the start of 7 rather than the end of 6? 16:29:58 q? 16:30:02 ... is that a real use case? 16:30:07 Garth: I don't remember 16:30:16 tzviya: maybe SVG? 16:30:27 timCole: page breaks? 16:30:42 mattg: if the char boundary is a page boundary, you need to know where to stay 16:30:54 timCole: we havent figured out the side bias yet 16:31:08 tzviya: could you work around that with anno selectors 16:31:20 ivan: it's a matter of really understanding the use case 16:31:27 timCole: might require an additional property 16:31:30 q+ 16:31:37 ... my hope is that the anno model will fit 16:31:59 Garth: I do recall pagination as being one of the reasons 16:32:07 tzviya: I had 2 comments 16:32:16 ... one was about range, indexing is a use case 16:32:38 q? 16:32:42 ack tzviya 16:32:42 tzviya, you wanted to comment about indexes and fragids 16:32:42 ... people need page numbers, but even that has ranges, and may cross documents 16:33:01 ... the other comment is on fragment identifiers, would this be odd without a new media type? 16:33:08 ivan: odd is not a good term 16:33:15 ... formally speaking, it's not possible 16:33:19 ack ivan 16:33:23 ... frag IDs are defined for A media type 16:33:34 q+ 16:33:39 ... if we want to have frag IDs, then we have lots of administrative problems 16:33:49 ... and I don't want to go through that again :) 16:34:16 ... the range story... the way it works in one doc, is defining the start and the end of the range, using other selectors 16:34:26 ... its a continuous set 16:34:42 ... you may start in paragraph 1 and end in para 21, and it's the whole range 16:34:58 ... can you define those ranges over doc boundaries? We still have to discuss that 16:35:22 ... I want to emphasize that we've tried so far to be as close to the web anno model as possible 16:35:31 ... we shouldn't redefine anything 16:35:36 ... we might have to add stuff 16:35:52 ... there is already a REC and implementations 16:36:17 present+ bigbluehat 16:36:21 q? 16:36:23 ... and we don't want to break existing implementations 16:36:23 ack timCole 16:36:29 timCole: regarding fragment id 16:36:36 ... there is precedent in media fragments 16:36:46 ... which works for multiple mime types 16:37:04 ... CFI is tied to the manifest of an EPUB 16:37:45 ... you can be trying to talk about a segment of a resource that's inside another resource 16:37:58 ... like a segment of an image that is in an HTML page 16:38:07 ... but there is a scope, the embedding html page 16:38:23 ... so with web pubs we have an html file that's part of a WP 16:38:27 ... so again we have a scope 16:38:35 ... so we might need this idea 16:38:41 ... the last idea is kindof related 16:38:52 ... if I have a resource that appears in multiple places in a publication 16:39:14 ... do I need to specifiy which instance I'm talking about? the same image in ch5 vs ch9? 16:39:26 duga has joined #pwg 16:39:27 Garth: we didn't have that problem in CFI because we didn't allow it to happen 16:39:45 ... CFI postdated that requirement 16:39:58 ... the other Q 16:40:04 ... the proposal now works for WP 16:40:09 ... would this work for PWP? 16:40:30 timCole: I haven't thought about it 16:40:40 ... in WP, we think everything should have ULR 16:40:57 q+ 16:41:02 ... if in PWP, the identifiers are only available via the manifest, then we might have an issue 16:41:08 s /ULR/URL/ 16:41:13 ... we should use canonical identifiers 16:41:28 ... maybe it's a must 16:41:33 q? 16:41:34 q? 16:41:47 ack ivan 16:42:01 ivan: there's a concept of embedded resource selector 16:42:09 ... by default each resource has it's own URL 16:42:24 ... in some cases you want to say that this URL has to be understood in the context of a WP 16:42:35 ... so we have 2 diff ways of expressing that 16:42:49 ... if you use that, if it is the package a package has a URN 16:42:57 ... each constituent also has an identifier 16:43:09 ... this mechanism should be usable to solve this issue 16:43:10 q+ 16:43:18 ... one more thing 16:43:36 ... we would need to have an agreement that we merge the PR 16:43:44 https://github.com/w3c/wpub/pull/75 16:43:45 ... so that this is now integral part of the work 16:43:53 ... even if it's in a different doc 16:44:20 ack Bill_Kasdorf 16:44:22 q? 16:44:24 Bill_Kasdorf: we do have to keep a11y issues in mind 16:44:41 ... if you have a fragment of an image, how do you manage the alt text so it's still accessible 16:44:59 timCole: the fragment wouldn't include the description 16:45:05 ivan: I want to see the use case 16:45:22 ... this is to put annotations or create bookmarks, that's what it's all about 16:45:33 ... I don't think there's an a11y scenario here 16:45:38 Bill_Kasdorf: I think you're right 16:45:42 q+ 16:45:47 present+ gregorio 16:45:49 ivan: this did not come up in web anno for these reasons 16:45:55 ack duga 16:46:15 duga: it seems like the use here would be a picture, I draw a circle around someone's face, and say something 16:46:24 ... you'd want alt text to explain what's circled 16:46:35 ... if it's a photo of the class of 1987 16:46:35 q? 16:46:45 ivan: the alt text is in the document, part of the HTML 16:46:50 you'd need to annotate the alt text--not the photo 16:46:54 what ivan said 16:47:11 s/what ivan said// 16:47:12 duga: the alt text describes the entirety of the picture, not the fragment 16:47:16 q+ 16:47:24 q+ 16:47:36 ivan: you make an anno on the picture, and then you add the alt to the anno 16:47:47 q- 16:48:01 tzviya: I don't want to go too far down this rabbit hole 16:48:07 ack tzviya 16:48:12 ... brady, you're talking about the a11y of annotations 16:48:18 ... and we have two more items on the agenda 16:48:36 Garth: Tim, were there other issues? 16:48:39 timCole: no 16:48:58 Garth: going back to Ivan's suggestion of merging this PR 16:49:08 q? 16:49:11 ... seems like a good plan to me 16:49:14 +1 16:49:19 RESOLVED: merge PR #75 16:49:20 Garth: let's do that 16:49:31 timCole: I'm hoping to have this doc to discuss at TPAC 16:49:59 Topic: Pagination issues 16:50:42 https://github.com/w3c/wpub/pull/65 16:50:52 https://github.com/w3c/wpub/pull/85 16:51:31 Proposed: close #65 and merge #85 16:51:41 q? 16:51:52 q+ 16:52:08 q? 16:52:21 ack ivan 16:52:25 ivan: I saw Florian's comments 16:52:34 ... he was commenting on Dave's changes on his PR 16:52:50 ... I would be in favor of merging things 16:53:10 ... the comments of florian are valid and should be discussed 16:53:18 ... but it's good to have a complete FPWD 16:53:32 q? 16:53:40 Garth: I would agree with Ivan's proposal 16:53:48 ... any objections? 16:53:48 RESOLVED: close #65 and merge #85 16:54:08 Topic: TPAC Agenda 16:54:18 Garth: there are references to a fleshed-out agenda 16:54:26 ... now everyone can comment but not edit 16:54:47 ... I encourage folks to review and comment 16:55:15 zakim, who is here? 16:55:15 Present: ivan, dauwhe, George, wolfgang, Avneesh, mattg, tzviya, Tim_Cole, JunGamo, Chris_Maden, Lillian, Sullam, baldurbjarnason, rkwright, rachel, josh, Luc, rdeltour, mateus, 16:55:18 ... Laurent, Vlad, jeffp, Bill_Kasdorf, BenSchroeter, duga, garth, Hadrien, bigbluehat, gregorio 16:55:18 On IRC I see duga, Hadrien, Leslie, Garth, BenSchroeter, ReinaldoFerraz, Bill_Kasdorf, mateus, laurentlemeur, josh, LSullam, laudrain, rkwright, baldurbjarnason, JunGamo, jeffp, 16:55:18 ... Vlad, timCole, Avneesh, George, MarthP, RRSAgent, Zakim, wolfgang, cmaden2, mattg, rdeltour, rachel, tzviya, ivan, plinss, dbaron, github-bot, jyasskin, astearns, bigbluehat, 16:55:20 ... dauwhe, ShaneM, wseltzer 16:55:23 tzviya: We have more requests at joint meetings 16:55:29 present+ gregorio 16:55:32 q? 16:55:42 present+ hadrien 16:55:49 Garth: anything else to bring up? 16:55:54 (silence) 16:56:11 https://docs.google.com/forms/d/e/1FAIpQLSc0YlroocKuvfP0bd5pNRFUChY7QJ2gYGOkE7zx-tSSpkBxkg/viewform?c=0&w=1&usp=mail_form_link 16:56:11 present+ jpyle 16:56:12 Garth: everyone, take the last five minutes to fill out the form for the Spring F2F 16:56:21 present+ leslie 16:56:36 have a nice afternoon! 16:56:38 Garth: that's all, folks! 16:56:57 present+ reinaldo 16:57:02 present+ billk 16:57:21 present+ bdugas 16:57:35 zakim, who is here? 16:57:35 Present: ivan, dauwhe, George, wolfgang, Avneesh, mattg, tzviya, Tim_Cole, JunGamo, Chris_Maden, Lillian, Sullam, baldurbjarnason, rkwright, rachel, josh, Luc, rdeltour, mateus, 16:57:38 ... Laurent, Vlad, jeffp, Bill_Kasdorf, BenSchroeter, duga, garth, Hadrien, bigbluehat, gregorio, jpyle, leslie, reinaldo, billk, bdugas 16:57:38 On IRC I see Leslie, Garth, ReinaldoFerraz, Bill_Kasdorf, laurentlemeur, JunGamo, jeffp, timCole, George, MarthP, RRSAgent, Zakim, wolfgang, cmaden2, mattg, rdeltour, rachel, 16:57:38 ... tzviya, ivan, plinss, dbaron, github-bot, jyasskin, astearns, bigbluehat, dauwhe, ShaneM, wseltzer 16:57:57 cmaden2 has left #pwg 16:58:04 rrsagent, draft minutes 16:58:04 I have made the request to generate http://www.w3.org/2017/10/16-pwg-minutes.html ivan 16:58:22 rrsagent, draft minutes 16:58:22 I have made the request to generate http://www.w3.org/2017/10/16-pwg-minutes.html ivan