15:37:38 <RRSAgent> RRSAgent has joined #pwg
15:37:38 <RRSAgent> logging to http://www.w3.org/2017/09/18-pwg-irc
15:37:39 <ivan> rrsagent, set log public
15:37:39 <ivan> Meeting: Publishing Working Group Telco
15:37:39 <ivan> Chair: Tzviya
15:37:39 <ivan> Date: 2017-09-18
15:37:39 <ivan> Regrets+ vlad, pkra, mattg, baldurbjarnason, ReinaldoFerraz, NickRuffilo, George
15:37:39 <ivan> Agenda: https://lists.w3.org/Archives/Public/public-publ-wg/2017Sep/0032.html
15:37:40 <ivan> ivan has changed the topic to: Meeting Agenda 2017-09-18: https://lists.w3.org/Archives/Public/public-publ-wg/2017Sep/0032.html
15:50:13 <Avneesh> Avneesh has joined #pwg
15:50:51 <dkaplan3> dkaplan3 has joined #pwg
15:55:15 <cmaden2> cmaden2 has joined #pwg
15:57:14 <ivan> present+
15:57:29 <timCole> timCole has joined #pwg
15:57:34 <tzviya> present+
15:58:13 <dauwhe> present+ dauwhe
15:59:28 <cmaden2> present+ Chris_Maden
15:59:50 <Avneesh> present+ Avneesh
15:59:55 <rachel> present+
15:59:57 <dkaplan3> present+
16:00:25 <rkwright> rkwright has joined #pwg
16:00:27 <ivan> present+ laudrain
16:00:44 <garth> garth has joined #pwg
16:00:44 <rkwright> present+
16:00:51 <lsullam> lsullam has joined #pwg
16:01:08 <rdeltour> rdeltour has joined #pwg
16:01:16 <laudrain> laudrain has joined #pwg
16:01:27 <laudrain> present+
16:01:34 <rdeltour> present+
16:01:52 <tzviya> zakim, pick a victim
16:01:52 <Zakim> Not knowing who is chairing or who scribed recently, I propose Avneesh
16:01:55 <ivan> present+ lsullam
16:02:09 <garth> present+ Garth
16:02:15 <ivan> present+ marisademeglio
16:02:17 <lsullam> present+
16:02:18 <BenSchroeter> BenSchroeter has joined #pwg
16:02:21 <marisa_demeglio> marisa_demeglio has joined #pwg
16:02:33 <ivan> present+ jpyle
16:02:36 <garth> (though largely lurking — over an hour traffic delay on bus to Ivrine this morning)
16:02:48 <ivan> present+ timCole
16:02:49 <dauwhe> scribenick: dauwhe
16:03:00 <ivan> present+ rdeltour
16:03:01 <BenSchroeter> present+
16:03:03 <dauwhe> tzviya: next week we may pre-assign scribes for TPAC
16:03:26 <dauwhe> tzviya: before we begin, we have at least one new member
16:03:29 <ben-dugas> ben-dugas has joined #pwg
16:03:42 <dauwhe> Josh: My name is Josh Pyle, I work at atypon
16:03:47 <dauwhe> ... before that I founded metapress
16:03:56 <dauwhe> ... been in scholarly pub for two decades
16:03:56 <ivan> scribejs, set Josy Josy Pyle
16:03:59 <ivan> scribejs, set Josh Josh Pyle
16:04:16 <dauwhe> ... we've adopted an epub-first strategy, and are trying to kill PDF
16:04:25 <dauwhe> tzviya: welcome Josh
16:04:31 <dauwhe> ... anyone else new?
16:04:36 <Bill_Kasdorf> Bill_Kasdorf has joined #pwg
16:04:41 <Bill_Kasdorf> present+
16:04:43 <dauwhe> ivan: I heard Gregorio
16:04:51 <dauwhe> (silence)
16:05:15 <dauwhe> laurent: Gregorio is from ??? in Italy
16:05:25 <tzviya> s/???/LIA
16:05:29 <duga> duga has joined #pwg
16:05:53 <dauwhe> ivan: he's not on official member of the WG
16:05:58 <dauwhe> tzviya: welcome Gregorio!
16:06:01 <tzviya> https://www.w3.org/publishing/groups/publ-wg/Meetings/Minutes/2017/2017-09-11-minutes.html
16:06:01 <ivan> guest+ Gregorio_Pellegrino
16:06:08 <dauwhe> tzviya: minutes from last week's meeting. Any comments?
16:06:20 <dauwhe> ... jyasskin talked about packaging
16:06:22 <ivan> RESOLVED: last minutes are fine
16:06:22 <josh> josh has joined #pwg
16:06:29 <duga> present+
16:06:31 <dauwhe> tzviya: we have a busy agenda
16:06:38 <jeffp> jeffp has joined #pwg
16:06:43 <dauwhe> ... will start with Marissa going over reqs for SMIL-lite
16:06:44 <ivan> Topic: Requirement for mini smil
16:06:45 <garth> “SMIL lite” == “grin”
16:06:46 <tzviya> https://github.com/w3c/publ-wg/wiki/Requirements-and-design-options-for-synchronized-multimedia
16:06:56 <rachel> present+ josh
16:07:05 <ivan> zakim, who is here?
16:07:05 <Zakim> Present: ivan, tzviya, dauwhe, Chris_Maden, Avneesh, rachel, dkaplan, laudrain, rkwright, rdeltour, lsullam, Garth, marisademeglio, jpyle, timCole, BenSchroeter, Bill_Kasdorf,
16:07:10 <Zakim> ... duga, josh
16:07:10 <Zakim> On IRC I see jeffp, josh, duga, Bill_Kasdorf, ben-dugas, marisa_demeglio, BenSchroeter, laudrain, rdeltour, lsullam, garth, rkwright, timCole, cmaden2, dkaplan3, Avneesh, RRSAgent,
16:07:10 <Zakim> ... Zakim, tzviya, dauwhe, Karen, rachel, ivan, plinss, wseltzer, jyasskin, github-bot, bigbluehat, ShaneM, astearns
16:07:11 <dauwhe> marisa_demeglio: link in GotoChat
16:07:24 <jeffp> present+ jeffp
16:07:25 <dauwhe> ... we've been looking at design reqs for syncronized multimedia
16:07:29 <rachel> https://github.com/w3c/publ-wg/wiki/Requirements-and-design-options-for-synchronized-multimedia
16:07:34 <ivan> s/mini smil/SMIL Lite/
16:07:38 <dauwhe> ... allowing talking books to talk
16:07:50 <dauwhe> tzviya: can you give a quick overview?
16:07:58 <clapierre> clapierre has joined #pwg
16:08:07 <dauwhe> marisa_demeglio: EPUB3 didn't have a lot of problems with media overlays
16:08:11 <clapierre> present+
16:08:17 <dauwhe> ... we can look at something lighter than SMIL
16:08:23 <dauwhe> ... we used a slim subset in EPUB3
16:08:33 <dauwhe> ... but SMIL adoption in the world at large hasn't been huge
16:08:39 <dauwhe> ... so we can look at other formats
16:08:45 <bigbluehat> present+
16:09:02 <dauwhe> ... we do need to link chunks of text with chunks of audio
16:09:11 <laurentlemeur> laurentlemeur has joined #pwg
16:09:15 <dauwhe> ... you still need structural semantics for navigation etc
16:09:31 <dauwhe> ... making video + text transcripts more accessible is a requirement
16:09:45 <dauwhe> ... and there are some things not included in media overlays
16:09:55 <dauwhe> ... I've been emailing with dweck
16:10:04 <david_stroup> david_stroup has joined #pwg
16:10:10 <dauwhe> ... like having multiple granularities of navigation--from para by para to word by word
16:10:15 <dauwhe> ... text + sign language
16:10:21 <dauwhe> ... video + descriptive audio
16:10:27 <dauwhe> ... all those are not covered by media overlays
16:10:32 <tzviya> q?
16:10:43 <dauwhe> ... our next step is deciding what format to do
16:10:47 <garth> That multi-resolution MO approach was discussed some years ago, and I think prototyped in Readium, I think.  It’s a cool idea.
16:10:53 <dauwhe> q+
16:11:04 <dauwhe> ... first question is about formats--XML or not XML
16:11:15 <Hadrien> Hadrien has joined #pwg
16:11:18 <tzviya> ack d
16:11:20 <ivan> q+
16:11:22 <Hadrien> present+
16:12:00 <dauwhe> dauwhe: what's the status of audio sync on the web at large?
16:12:07 <dauwhe> marisa_demeglio: I don't know of anything
16:12:14 <dauwhe> ivan: I don't know much more
16:12:25 <dauwhe> ... I love your understatement... SMIL adoption is terrible
16:12:43 <dauwhe> ... we will have to define a SMIL-lite which has any hope for implementation
16:12:48 <Bill_Kasdorf> is there an active SMIL WG?
16:13:07 <dauwhe> ... we will also have to ensure there will be several implementations on top of browsers
16:13:08 <laurentlemeur> q+
16:13:14 <tzviya> ack la
16:13:15 <garth> ack ivan
16:13:31 <dauwhe> laurentlemeur: I agree with Ivan when he says we'll have to create polyfills
16:13:32 <rkwright> q+
16:13:54 <dauwhe> ... if this is the case, if JS is the language that will use SMIL, then XML is not the best structure for that
16:14:02 <Avneesh> q+
16:14:06 <dauwhe> ... JSON has the lead, a structure JS loves
16:14:19 <dauwhe> ... SMIL is so complex, there are too many features
16:14:27 <dauwhe> ... we can track as JSON structure
16:14:27 <garth> Marisa is also correct, when saying MO/SMIL(lite) adoption in EPUB Reading Systems is pretty good.
16:14:29 <ivan> q+
16:14:48 <dauwhe> ... as for the requirements, we should make sure the structure we define doesn't prevent us from adding advanced features later
16:14:58 <tzviya> ack rk
16:15:16 <clapierre> q+
16:15:21 <dauwhe> rkwright: one other area is where there is a SMIL implemenation is for animation of SVG
16:15:27 <dauwhe> ... this has been implemented by browsers
16:15:37 <tzviya> ack av
16:15:37 <ivan> q-
16:15:53 <dauwhe> Avneesh: the main objective of this work was lack of support of SMIL on the web
16:15:59 <dauwhe> ... and then additional things came up
16:16:07 <dauwhe> ... that were not covered in EPUB3 MO
16:16:14 <BillM> BillM has joined #pwg
16:16:30 <dauwhe> ... media fragments is the one thing in the web which is used
16:16:43 <dauwhe> ... if we can find out groups in web who are trying to solve similar problems
16:16:50 <dauwhe> ... we can try to do it together
16:16:51 <tzviya> ack iv
16:17:00 <tzviya> ack cl
16:17:16 <dauwhe> clapierre: ETS and Mark Hakkonnen has done lots of work with SMIL
16:17:24 <dauwhe> ... they might have some insight
16:17:33 <dauwhe> ... they use this for assessments
16:18:00 <dauwhe> tzviya: the larger group should comment about requirements
16:18:17 <dauwhe> ... this is not part of our charter... so what should we do with these requirements? What are next steps?
16:18:21 <clapierre> s/Hakkonnen/Hakkinen
16:18:28 <dauwhe> ivan: as usual, this was the topic I wanted to put on the queue
16:18:33 <dauwhe> ... that's an admin problem
16:18:52 <dauwhe> ... this whole issue of SMIL lite is not in our charter, but is a necessary thing
16:19:10 <dauwhe> ... this would be rec-track work
16:19:22 <dauwhe> ... the traditional way to do something like this would be to form a separate CG
16:19:36 <dauwhe> ... that would look at an initial spec plus one or two polyfills, showing it is possible
16:19:56 <dauwhe> ... once the CG says we have this, it solves these requirements, it's polyfilled, it has users
16:20:06 <dauwhe> ... the most obvious way would be to then form a new WG
16:20:14 <garth> From charter: “This specification should generally be a functional superset of EPUB 3.1. Functional round-tripping to/from EPUB 3.1 considered highly desirable.”  So, would could argue it’s kinda in our charter, as it’s in EPUB 3.1.
16:20:31 <dauwhe> ... I still believe something like SMIL is still necessary for the web, and not only for WP
16:20:40 <marisa_demeglio> q+
16:20:40 <Avneesh> q+
16:20:41 <dauwhe> ... even if WP is driving this here
16:20:46 <dauwhe> ... the web in general would benefit
16:21:18 <dauwhe> ... we then could get experts from other places for a CG
16:21:30 <dauwhe> ... I have some colleagues in Amsterdam who worked on original SMIL
16:21:39 <dauwhe> ... some of them are still around; I can approach them
16:22:03 <dauwhe> ... but a WG would be too much for them
16:22:14 <dauwhe> tzviya: the next steps are to clean up requirements and share them
16:22:28 <dauwhe> ... we should pass this on to APA, and share with Janina
16:22:38 <dauwhe> ivan: there are some other media-related groups, like a video group
16:22:50 <dauwhe> ... they might have feedback
16:22:57 <dauwhe> ... and outside w3c there are other groups
16:23:06 <tzviya> q?
16:23:12 <tzviya> ack mar
16:23:23 <dauwhe> marisa_demeglio: to comment on SMIL
16:23:29 <dauwhe> ... DAISY was in smil WG
16:23:48 <dauwhe> ... we used SMIL more than anyone else, but used less of it
16:23:57 <dauwhe> ... our use case was really different from everyone else's
16:24:06 <dauwhe> ... they used it for short presos, annotations, etc.
16:24:12 <dauwhe> ... we used for entire books
16:24:33 <dauwhe> ... I'm not sure that reawakening the SMIL group would be good
16:24:57 <dauwhe> ... we might look elsewhere for overlap
16:25:17 <dauwhe> ivan: it's going to be very light, very concentrated
16:25:25 <dauwhe> tzviya: it might come down to how you position it
16:25:32 <Bill_Kasdorf> q+
16:25:34 <dauwhe> ... I can help with that
16:25:35 <tzviya> ack av
16:25:44 <dauwhe> Avneesh: that's a valid point from marisa_demeglio
16:25:59 <dauwhe> ... we need more strength to make it an implementable standard
16:26:17 <dauwhe> ... we need to strike a balance for something useful for our requirements as well as for others
16:26:39 <dauwhe> ... that IPTV was looking for something like SMIL
16:26:51 <dauwhe> ... ??? can be a liason
16:27:02 <dauwhe> ... and Mark H can also help
16:27:23 <dauwhe> tzviya: we have people volunteering to be liasons
16:27:44 <tzviya> ack bi
16:27:44 <dauwhe> ... joanie might know who to talk about at the browsers
16:27:59 <dauwhe> Bill_Kasdorf:
16:28:04 <dauwhe> ...
16:28:05 <dauwhe> ...
16:28:26 <ivan> Topic: Metadata PR
16:28:27 <dauwhe> tzviya: let's move on to the metadata pull request
16:28:28 <tzviya> https://github.com/w3c/wpub/pull/64
16:28:36 <ivan> github: https://github.com/w3c/wpub/pull/64
16:28:41 <Avneesh> I will contact Mark Hacknon and Hiroshi Kawamura
16:28:44 <Bill_Kasdorf> I was going to ask Marisa if there is a link she can share that documents the subset of SMIL that is actually used by DAISY
16:29:04 <dauwhe> tzviya: Luc, could you give us an overview
16:29:26 <dkaplan3> s/Hacknon/Hakkinen/
16:29:46 <dauwhe> laudrain: just back from holiday, so I can't give an update; I need to read some emails fist :)
16:29:51 <dauwhe> s/fist/first/
16:29:57 <ivan> q+
16:29:59 <dauwhe> tzviya: has anyone had a chance to read it
16:30:02 <tzviya> ac kiv
16:30:14 <dauwhe> ivan: I did read it, had some discussion with Baldur
16:30:22 <dauwhe> ... some of us did read it
16:30:46 <dauwhe> ... my overall opinion is we should merge this
16:31:02 <dauwhe> ... this doc 1. defines some additional terms that could go into the infoset
16:31:16 <marisa_demeglio> bill_kasdorf: http://www.idpf.org/epub/31/spec/epub-mediaoverlays.html#sec-overlays-def
16:31:21 <dauwhe> ... some are more "mays" than "shoulds"--authors publishers editors
16:32:00 <dauwhe> ... and 2. there's a small section that says whatever we do, we should link out to other vocabularies (like ONIX)
16:32:11 <dauwhe> ... and they are external to the manifest/infoset
16:32:13 <timCole> q+
16:32:18 <tzviya> q?
16:32:24 <tzviya> ack iv
16:32:39 <dauwhe> ... merging the PR and turning some Qs into issues is good
16:32:52 <tzviya> ack ti
16:33:00 <laudrain> q+
16:33:01 <dauwhe> timCole: I agree with Ivan about merging to get something in there
16:33:11 <dauwhe> ... one Q I haven't yet added
16:33:30 <Bill_Kasdorf> marisa: thanks, I didn't realize that the MO spec in EPUB 3.1 was the subset you were talking about. That's great to know because that is what folks are actually using in the publishing world.
16:33:45 <dauwhe> ... are we going to have a WPUB namespace, or will be borrow things from existing standards?
16:33:58 <dauwhe> ivan: can you give an example
16:34:19 <dauwhe> timCole: author, do we use DC or do we have our own concept of author?
16:34:29 <dauwhe> ... that wasn't clear from current language
16:34:39 <dauwhe> ivan: I don't know the answer
16:35:17 <tzviya> q?
16:35:17 <dauwhe> q?
16:35:25 <tzviya> ack la
16:35:32 <dauwhe> laudrain: reading the comments in the PR
16:35:48 <dauwhe> ... this job that Baldur did is very accurate with what we discussed
16:36:04 <dauwhe> ... some terms may be need more precision between may and should / must
16:36:13 <dauwhe> ... but it reflects our ideas
16:36:32 <tzviya> q?
16:36:40 <dauwhe> tzviya: sounds like we should accept the PR
16:36:42 <garth> +1
16:36:44 <Avneesh> q+
16:36:45 <dauwhe> ivan: and add some github issues
16:36:49 <tzviya> ack av
16:37:14 <dauwhe> Avneesh: if they need something from a11y task force, please let us know
16:37:58 <dauwhe> tzviya: I think the a11y metadata can fit right in
16:38:11 <dauwhe> laudrain: we created a slot for a11y metadata, but it needs to be more precise
16:38:19 <Avneesh> q+
16:38:40 <tzviya> ack av
16:38:47 <dauwhe> Avneesh: this is OK
16:39:09 <dauwhe> ... normally we talk about discovery metadata, but metadata is also good for user agent to invoke special features
16:39:18 <dauwhe> ... in those cases it might be a "must"
16:39:24 <dauwhe> tzviya: we can adjust after the first draft
16:39:35 <ivan> RESOLUTION: accept the PR and possibly create new issues around it into github
16:39:36 <laudrain> +1
16:39:43 <dauwhe> Topic: Identifiers
16:39:50 <tzviya> https://github.com/w3c/wpub/issues/44
16:39:56 <ivan> Topic: Identifiers
16:40:22 <dauwhe> timCole: our current draft has 3.5 and 3.6 about canonical identifier and identifier of doc as a whole
16:40:31 <dauwhe> ... but we also need to talk about fragments of a WP
16:40:51 <dauwhe> ... do we have any premises about our approach?
16:41:00 <dauwhe> ... we could use the CFI approach
16:41:09 <dauwhe> ... but what would replace package/spine?
16:41:24 <dauwhe> ... I think the stronger possibility is the selectors and states approach
16:41:35 <dauwhe> ... a WG note from the Web annotations group
16:41:48 <dauwhe> ... which allows an identifier for an arbitrary part of a web resource
16:42:00 <ivan> q+
16:42:04 <dauwhe> ... is the selector and state approach OK?
16:42:08 <tzviya> ?
16:42:11 <tzviya> q?
16:42:20 <Bill_Kasdorf> +1 to the selectors and states approach
16:42:34 <tzviya> ack iv
16:42:34 <dauwhe> ... also, do we need to tie together things back to the web pub itself?
16:42:53 <dauwhe> ivan: my only problem is that you and I know what is in that document
16:43:04 <dauwhe> ... but I dont think the rest of the group knows the selector note
16:43:15 <dauwhe> ... perhaps you could give an overview at some time
16:43:47 <dauwhe> timCole: there are various ways you can provide a mechanism for locating within a file (text and graphics)
16:43:51 <tzviya> q?
16:43:54 <dauwhe> ... here's a point range, and it calls selectors
16:43:59 <dauwhe> ... and it can identify versions
16:44:51 <dauwhe> tzviya: when we worked on EPUB 3.1, we did away with part of EPUB CFI
16:45:12 <dauwhe> ... (the hyperlinking part) and it turns out no one used it
16:45:13 <garth> Yep — removed in content.
16:46:09 <dauwhe> timCole: ivan, we can proceed with a first draft PR that assumes the web anno approach in order to make it more concrete
16:46:11 <rachel> this one: http://www.idpf.org/epub/31/spec/epub-changes.html#sec-epub31-cfi?
16:46:11 <dauwhe> +1
16:46:28 <dauwhe> timCole: because of the history with CFI, I think that's the better approach
16:46:48 <dauwhe> ... if you're talking about packaged web publications, taht might be different
16:46:53 <rachel> q+
16:46:59 <tzviya> ack r
16:47:02 <dauwhe> tzviya: is anyone able to talk about why CFI was so complicated
16:47:31 <ivan> q+
16:47:31 <dauwhe> rachel: we use CFI in order to create reading "chunks" to provide assignments for students in our LMS
16:47:48 <dauwhe> ... CFI must live within a single XHTML file, and couldn't work across files
16:48:06 <laudrain> http://www.idpf.org/epub/31/spec/epub-changes.html#sec-epub31-cfi
16:48:14 <tzviya> ack iv
16:48:15 <dauwhe> ... we usually chunk by a-head, but we couldn't create a link that included two a-heads
16:48:22 <dauwhe> timCole: that's an issue I raised
16:48:37 <dauwhe> ivan: the current version of notes gives only a partial answer to Rachel's problems
16:48:47 <timCole> q+
16:48:52 <duga> q+
16:48:54 <dauwhe> ... that may be an issue here, too
16:49:01 <tzviya> q?
16:49:13 <dauwhe> ... I"m fine putting it in the public draft
16:49:27 <Bill_Kasdorf> there appear to be two problems with CFI: 1) it's too complicated, and 2) it's not complicated enough
16:49:33 <dauwhe> ... I would be pleased if any CFI users would have an early look
16:49:46 <dauwhe> ... to see if this is a realistic "path"
16:50:02 <tzviya> https://www.w3.org/TR/selectors-states/
16:50:06 <rachel> +1 to review, also nominating jeffp to review
16:50:16 <dauwhe> ... the way the anno group worked, was not to create URLs, but to define JSON structures to anchor
16:50:35 <dauwhe> ... so the note talked about turning the JSON into a URL
16:50:48 <dauwhe> ... and this is not standardized, we'd need to go to IETF
16:51:10 <dauwhe> ... so early feedback is necessary
16:51:13 <tzviya> ack ti
16:51:24 <dauwhe> timCole: another thing about the difference
16:51:41 <dauwhe> ... the web anno approach gives us some flexibility--there's more than one way to do it
16:52:00 <dauwhe> ... you could use a phrase, or character/byte offset
16:52:02 <garth> q?
16:52:09 <dauwhe> ... and there are range selectors across files
16:52:25 <dauwhe> ... but a limitation is that it assumes that every component has a URL
16:52:34 <dauwhe> ... which might not be true in a packaged doc
16:52:38 <tzviya> ack du
16:52:57 <ivan> present+ duga, leslie, David_Stroup, bdugas
16:53:05 <tzviya> q?
16:53:06 <dauwhe> duga: CFI points at a thing; you just have to have a range to do it, you could specify a range that spans file
16:53:30 <dauwhe> ... its complicated because locatiing content that someone else wrote is intrinsically hard
16:53:36 <ivan> q+
16:53:48 <dauwhe> ... it's easy to reference your own content--just put in an anchor
16:53:57 <dauwhe> ... but with content you can't it's hard.
16:54:10 <dauwhe> ... if you use byte offset, then change encoding then it's hard
16:54:17 <tzviya> ack iv
16:54:26 <dauwhe> ... CFI is hard to generate, but it's hard to point into other people's content
16:54:48 <dauwhe> ivan: is the CFI specification usable with non-xml html? does it work wtih non-XML manifests?
16:54:58 <dauwhe> duga: it probably doesn't work
16:55:03 <dauwhe> ... it could probably be extended
16:55:09 <garth> CFI root if the EPUB manifest.
16:55:25 <garth> s/if/is/
16:55:32 <rkwright> +q
16:55:38 <tzviya> ack rk
16:55:53 <dauwhe> rkwright: I'm not volunteering
16:56:11 <dauwhe> ... we've experimented in readium, and we can get CFI to work with non-X HTML
16:56:25 <dauwhe> ... anyone on the systems side to look at web annos?
16:56:39 <dauwhe> duga: I would, but I don't have time in the next few times
16:56:57 <ivan> SUMMARY: people should look at the WA document, and prepare a PR on the topic
16:57:07 <ivan> github-bot, end topic
16:57:20 <dauwhe> tzviya: there's a lot of writing that needs to happen
16:57:23 <ivan> Topic: writing assignments
16:57:37 <dauwhe> ... we have a section on establishing a web pub; we'll volunteer matt
16:57:47 <dauwhe> ... we hope dweck can work on offline
16:57:56 <ivan> q+
16:58:00 <dauwhe> ... leonard is working on security
16:58:13 <dauwhe> ... we have a section on privacy, can we move it?
16:58:14 <tzviya> ack iv
16:58:28 <dauwhe> ivan: florian has done a PR on pagination
16:58:36 <dauwhe> ... lots of relations to CSS
16:58:39 <tzviya> https://github.com/w3c/wpub/pull/65
16:59:01 <dauwhe> OK to remove the privacy section?
16:59:06 <laurentlemeur> ok
16:59:08 <garth> +1 (to privacy sec removal)
16:59:08 <laudrain> ok
16:59:12 <timCole> +1
16:59:18 <ivan> RESOLVED: remove the privacy section
16:59:41 <dauwhe> tzviya: feel free to comment on issues and PRs in GitHub
16:59:44 <dauwhe> ... thanks all!
16:59:49 <laudrain> laudrain has left #pwg
16:59:56 <ivan> rrsagent, draft minutes
16:59:56 <RRSAgent> I have made the request to generate http://www.w3.org/2017/09/18-pwg-minutes.html ivan
16:59:58 <ivan> zakim, bye
16:59:58 <Zakim> leaving.  As of this point the attendees have been ivan, tzviya, dauwhe, Chris_Maden, Avneesh, rachel, dkaplan, laudrain, rkwright, rdeltour, lsullam, Garth, marisademeglio, jpyle,
16:59:59 <Zakim> Zakim has left #pwg
17:00:02 <Zakim> ... timCole, BenSchroeter, Bill_Kasdorf, duga, josh, jeffp, clapierre, bigbluehat, Hadrien, leslie, David_Stroup, bdugas
17:00:02 <marisa_demeglio> present+
17:00:09 <dkaplan3> dkaplan3 has left #pwg
17:00:17 <ivan> rrsagent, draft minutes
17:00:17 <RRSAgent> I have made the request to generate http://www.w3.org/2017/09/18-pwg-minutes.html ivan
17:00:22 <ivan> rrsagent, bye
17:00:22 <RRSAgent> I see no action items