15:38:26 RRSAgent has joined #pwg 15:38:26 logging to https://www.w3.org/2018/08/20-pwg-irc 15:38:27 rrsagent, set log public 15:38:27 Meeting: Publishing Working Group Telco 15:38:27 Chair: Tzviya 15:38:27 Date: 2018-08-20 15:38:27 Regrets+ garth 15:38:27 Agenda: https://lists.w3.org/Archives/Public/public-publ-wg/2018Aug/0010.html 15:38:27 ivan has changed the topic to: Meeting 2018-08-20: https://lists.w3.org/Archives/Public/public-publ-wg/2018Aug/0010.html 15:54:39 present+ 15:56:32 Avneesh has joined #pwg 15:57:11 jbuehler has joined #PWG 15:57:31 present+ tzviya 15:57:38 gpellegrino has joined #pwg 15:57:47 wendyreid has joined #PWG 15:58:06 jasminemulliken has joined #pwg 15:58:28 present+ 15:58:48 cmaden2 has joined #pwg 15:58:49 present + 15:58:55 present+ 15:58:58 present+ 15:59:10 Makoto has joined #pwg 15:59:38 romain has joined #pwg 16:00:15 present+ jasminemulliken 16:00:24 Vlad has joined #pwg 16:00:27 present+ George 16:00:28 laudrain has joined #pwg 16:00:29 present+ 16:00:32 scribenick: Rachel 16:00:36 present+ 16:00:57 zheng_xu has joined #pwg 16:00:57 jasminemulliken has joined #pwg 16:00:58 present+ 16:01:01 present+ 16:01:03 present+ 16:01:06 gpellegrino_ has joined #pwg 16:01:36 regrets+ garth 16:01:45 present+ 16:01:50 George has joined #pwg 16:01:50 dkaplan3 has joined #pwg 16:02:00 present+ 16:02:23 Bill_Kasdorf has joined #pwg 16:02:24 present+ George 16:02:27 franco has joined #pwg 16:02:28 josh has joined #pwg 16:02:32 present+ makoto 16:02:34 present+ 16:02:35 Evan_Owens has joined #pwg 16:02:38 present+ franco 16:02:41 present+ 16:02:42 present+ 16:02:51 https://www.w3.org/publishing/groups/publ-wg/Meetings/Minutes/2018/2018-07-30-pwg.html 16:03:05 tzviya: approving minutes 16:03:18 resolved: minutes of july 30 accepted 16:03:24 ... minutes approved 16:03:26 clapierre has joined #pwg 16:03:28 present+ Chris_Maden 16:03:37 present+ 16:03:49 rkwright has joined #pwg 16:03:50 topic: Update on Update 16:04:04 Ivan: we have updated the webIDL to the new version 16:04:25 ... while doing this there were some issues that came up 16:04:40 ... some led to minor changes to make contents more precise 16:04:53 ... some issues are still open (ie table of contents) 16:05:03 duga has joined #pwg 16:05:12 present+ 16:05:16 tzviya: comments? 16:05:18 present+ 16:05:31 tzviya: so everyone is happy? 16:05:40 marisa has joined #pwg 16:05:44 Topic: Implementations 16:05:53 caitlingebhard has joined #pwg 16:06:01 Hadrien has joined #pwg 16:06:03 tzviya: several of you offered to begin work on implementations 16:06:04 q+ 16:06:08 ack ivan 16:06:12 ...any feedback or code samples to share? 16:06:17 derekjackson has joined #pwg 16:06:22 ivan: 2 things i know about 16:06:24 gpellegrino_ has joined #pwg 16:06:37 ... Hadrien worked on a JSON schema for the manifest 16:06:54 ...someof the issues around the webidl came from the JSON schema 16:07:08 https://github.com/w3c/wpub/tree/master/schema 16:07:28 juan_ccr has joined #pwg 16:07:34 ... the other one I know about is from me, which is a look at what it means to turn the manuscript into something a js library can use 16:07:47 but I still need to work on "accessibilityModeSufficient" 16:08:14 ...anyone is welcome to pick this up and use it, it was meant to cross check the webIDL 16:08:19 q? 16:08:27 JunGamo has joined #pwg 16:08:55 Hadrien: I linked the JSON schema; I think it will be useful for implementations and validations 16:09:07 tzviya: any questions on accessmodeSufficient? 16:09:08 q+ 16:09:36 Hadrien: initially I had something a bit too complex; I think if I look at the WebIDL I should be able to adapt the schema 16:09:45 ack ivan 16:10:16 https://github.com/w3c/wpub/pull/310 16:10:50 Jean_K has joined #pwg 16:10:52 Ivan: we had a discussion with several people and there is a pull request which I believe implements what I understood the syntax should be 16:11:02 ...I would like to merge this ASAP 16:11:25 Hadrien: there is one difference in the IDL and the schema in the type of validation 16:11:45 ivan: can I merge this pull request? 16:12:09 q+ 16:12:12 tzviya: not enough people on the call are familiar with this to decide if we can merge 16:12:14 ack Avneesh 16:12:34 timCole has joined #pwg 16:12:53 BenSchroeter has joined #pwg 16:12:53 Avneesh: the main issue was comma separated strings in the epub world (to fit in epub opf structure) 16:13:03 present+ 16:13:17 ... the final example had a nested list structure 16:13:27 present+ 16:13:31 ... and we should propose this list to shema.org as well 16:13:43 s/shema.org/schema.org 16:13:53 present+ Tim_Cole 16:14:33 ivan: who proposes this to schema.org? 16:15:20 tzviya: so there is an existing definition in schema.org 16:15:21 q+ 16:15:27 ack ivan 16:15:28 ...what are we doing in our spec? 16:15:30 present+ 16:16:30 ivan: there was a long discussion in the schema.org email list about what would be the final representation. The JSON examples posted to schema.org don't actually align with what was agreed to in that description 16:16:47 q+ 16:17:31 ivan: it is an array of text with a comma separated text in WP 16:18:17 ivan: what I put in WP is in line with what schema.org agreed to, but schema.org has not yet corrected their samples 16:18:29 https://pr-preview.s3.amazonaws.com/w3c/wpub/pull/310.html#accessibility 16:18:44 q- tzviya asked what I needed to know 16:18:44 ack Rachel 16:18:48 q- 16:19:49 tzviya: any other comments about this pull request? 16:19:54 ...are we ok to merge? 16:19:58 +1 16:20:02 +1 16:20:02 +1 16:20:03 +1 16:20:05 gpellegrino_ has joined #pwg 16:20:06 +1 16:20:07 +1 16:20:11 +1 16:20:19 tzviya: ivan, go ahead and merge 16:20:31 tzviya: any other implementations? 16:20:39 q+ 16:20:43 ack franco 16:21:17 franco: we're doing a 'frankepub' based WP 16:21:56 Rachel: frankenepub is a collection of textbook content 16:21:56 Comment about our work from an audiobook distributor: https://twitter.com/Luisterhuis/status/1030776054665895936 16:22:06 tzviya: friends from Kobo? 16:22:12 laurentlemeur has joined #pwg 16:22:20 present+ 16:23:37 ???: I did talk to people here about what work it would take to implement. They thought it would be easy to implement with FXL and DRM as potential issues. 16:23:53 tzviya: DRM is specifically out of scope 16:23:59 s/???/wendyreid/ 16:24:12 Regarding previous topic, the link to original schema.org discusion about accessModeSufficient 16:24:14 https://github.com/schemaorg/schemaorg/issues/1100 16:24:23 tzviya: Josh what about atypon? 16:24:51 josh: I focused primarily on what will be discussed next week in Japan - FXL 16:25:24 ...we've had some discussions about author and publisher hints for systems to use 16:25:41 ...I;ve written a set of user stories around this as well 16:26:28 ...it's a delicate line to say on one hand we want to give authors and publishers freedom to layout however they want to but also give reading system freedom for how they want to display to users 16:27:40 tzviya: we do have a spot in github for posting code 16:27:48 ...can someone post the link? 16:28:05 https://github.com/w3c/wpub/tree/master/experiments 16:28:09 Topic: Updates on Use Cases and integrating into spec 16:28:27 tzviya: Josh, how are yours coming 16:28:57 Josh: there's been some discussions about fixed layout as an issue 16:29:17 ...I merged locally, should I make pull requests to the master or merge every time? 16:30:01 ivan: I do branches on my local clone when I... ?? 16:30:36 tzviya: call for new use cases 16:30:53 gpellegrino_ has joined #pwg 16:30:53 Topic: Canonical Manifest 16:30:55 https://pr-preview.s3.amazonaws.com/w3c/wpub/pull/306.html#canonical-manifest 16:31:16 tzviya: ivan, can I ask you to give an overview 16:31:33 ivan: this is a relatively major thing 16:32:00 ...we are looking for the next logical step in the spec which is the lifecycle section 16:32:11 ... this is out of sync 16:32:40 ... how do I describe and specify the elements 16:33:08 ... we inherited from schema.org and the need to make authoring easier the manifest in JSONLD 16:33:39 ...I canhave a name but the value of the name can be an array (ie, the name in many languages) 16:34:13 ...the goal is to make this simple for the authors 16:35:14 q+ 16:36:33 Ivan: the first is a PR which defines the transformation steps to generate a canonical manifest 16:36:53 ... I have an implementation that uses the transformation 16:36:58 ack tzv 16:37:05 ack tzviya 16:37:29 tzviya: I think anything written in this algorithmic style is confusing 16:37:38 tzviya ++ 16:37:45 q+ to ask who will run this and where 16:38:04 ...we're creating this algorithm so we have data that can be useable by systems? I am confused about the why and how of this 16:38:42 ivan: we could specify exactly what the canonical manifest looks like - make it explicit that you can have a string, an object... 16:39:05 ... what the algorthm does is defines the steps to generate the canonical version of the manifest 16:39:39 ...if you want to implement this - take the manifest of a user and digest it in your environment - this must be done somewhere 16:39:40 q- 16:40:07 ...this makes it easier to produce the wpub to the specification with explicit directions 16:40:09 q+ 16:40:10 +1 to interoperability 16:40:12 ack bigbluehat 16:40:34 +1 I like what i'm hearing 16:40:46 bigbluehat: thanks ivan, I'm guessing this is a pre-req to any implementation? 16:40:48 ivan: yes 16:41:00 bigbluehat: and this is a reflection of the way we shaped the manifest? 16:41:22 ivan: we made the manifest flexible, this gives shape to the requirement 16:42:15 ivan: one more thing not yet in the PR; there are some diagrams in the spec that I made because Rachel made me do it 16:42:21 ... these need to be updated 16:42:36 q+ 16:42:42 ack zheng_xu 16:43:29 zheng_xu: can any provide an example of html...?? 16:44:27 gpellegrino_ has joined #pwg 16:44:27 +1 16:44:29 tzviya: shall we merge? 16:44:29 +1 16:44:33 +1 16:44:34 +1 16:44:35 +1 16:44:44 0 but only because I need pictures 16:44:53 lol 16:45:25 tzviya: consensus to merge 16:45:33 ivan: I will merge this then add examples 16:46:04 Topic: Issue 291 - TOC issues 16:46:06 https://github.com/w3c/wpub/issues/291 16:47:04 tzviya: do we need a more detailed TOC description. In EPUB the nav document was the structured machine readable TOC as well as the visual. 16:47:19 q+ 16:47:30 ...some people used it as the visual but others would create a standalone TOC as well 16:48:02 ...should the machine-readable TOC be more stylized? 16:48:09 ack dauwhe 16:48:20 ...will that hamper accessibility? machine readablity? 16:48:38 dauwhe: do you have examples of the external TOC structure? 16:49:08 regrets+ Teenya 16:49:14 s/ zheng_xu you broke up on my line - can you fill in what you said?/ or json data structure example that could give us a more clear image about what Canonical Manifest looks like? 16:49:26 exemple of a graphical ToC : https://about.canva.com/wp-content/uploads/sites/3/2016/11/table-of-contents-.png 16:49:39 dauwhe: are we conflating brief TOC and actual content? 16:50:04 q+ 16:50:08 ...are we basically going back to epub2 with an NCX 16:50:14 q+ 16:50:24 ack ivan 16:50:27 ...I'm concerned we're undoing work from epub3 16:50:45 +1 to dave's concerns 16:50:48 ivan: the current spec is silent on this 16:51:19 q+ 16:51:25 -1 to Dave’s concern, sorry 16:51:51 ...my feeling is that WP does not need to make any additional statement about this 16:51:56 q+ 16:51:58 ack duga 16:52:14 duga: Garth isn't here, so I'm going to speak for him 16:52:32 ...everyone gives us an NCX and NAV 16:52:51 ...I don't think it would be impossible for those books to make a machine readable TOC 16:53:01 q+ 16:53:09 ack tzviya 16:53:17 tzviya: the navigation is what makes the WP more accessible 16:53:19 ack Rachel 16:53:49 let's agree to disagree then, I don't think EPUB3 truly succeeded in creating something that's good for both rendering and machine readable use cases 16:54:15 q+ 16:54:52 +1 to rachel: complex navigation is part of the content (it actually often has text, explanation, enrichment) that would not be in a