15:46:52 <RRSAgent> RRSAgent has joined #dpub
15:46:52 <RRSAgent> logging to http://www.w3.org/2016/10/31-dpub-irc
15:46:54 <trackbot> RRSAgent, make logs public
15:46:54 <Zakim> Zakim has joined #dpub
15:46:56 <trackbot> Zakim, this will be dpub
15:46:56 <Zakim> ok, trackbot
15:46:57 <trackbot> Meeting: Digital Publishing Interest Group Teleconference
15:46:57 <trackbot> Date: 31 October 2016
15:47:17 <ivan> Chair: Tzviya
15:47:21 <ivan> Agenda: http://www.w3.org/mid/ed59c8770634494d97c62b86eb2ee89a@AUS-WNMBP-005-n.wiley.com
15:47:37 <ivan> ivan has changed the topic to: Agenda 2016-10-31: http://www.w3.org/mid/ed59c8770634494d97c62b86eb2ee89a@AUS-WNMBP-005-n.wiley.com
15:48:34 <ivan> Regrets: Ayla, Luc, Romain, Laurent, NickRuffilo
15:48:47 <Florian> Florian has joined #dpub
15:50:42 <cmaden2> cmaden2 has joined #dpub
15:51:34 <Avneesh> Avneesh has joined #dpub
15:51:46 <pkra> pkra has joined #dpub
15:52:42 <George> George has joined #dpub
15:53:31 <George> present+ George
15:56:11 <dauwhe> present+ dauwhe
15:56:46 <Avneesh> present+ Avneesh
15:57:10 <dauwhe> scribenick: dauwhe
15:57:35 <astearns> present+
15:57:36 <ivan> Present+ Ivan
15:58:31 <HeatherF> HeatherF has joined #dpub
15:58:56 <HeatherF> present+ Heather_Flanagan
15:59:02 <pkra> present+ Peter Krautzberger
15:59:08 <Garth> Garth has joined #dpub
15:59:36 <tzviya> present+ Tzviya
15:59:48 <clapierre> clapierre has joined #DPUB
16:00:10 <dkaplan3> present+ Deborah_Kaplan
16:01:16 <cmaden2> present+ Chris_Maden
16:01:47 <bjdmeest> bjdmeest has joined #dpub
16:01:48 <Bill_Kasdorf> Bill_Kasdorf has joined #dpub
16:02:56 <bjdmeest> Present+ Ben_De_Meester
16:03:15 <Bert> present+
16:04:15 <clapierre> present+
16:04:22 <dauwhe> tzviya: Let's begin
16:04:26 <dauwhe> ... last week's minutes
16:04:27 <tzviya> https://www.w3.org/2016/10/24-dpub-minutes.html
16:04:30 <dauwhe> (silence)
16:04:34 <dauwhe> (silence)
16:04:40 <dauwhe> ... minutes are approved
16:05:02 <ivan> Topic: PWP-UCR review/questions
16:05:10 <ShaneM> present+ ShaneM
16:05:21 <leonardr> leonardr has joined #dpub
16:05:30 <dauwhe> tzviya: our ultimate goal is having a version of doc to send back out into the wild for feedback
16:05:32 <leonardr> present+ Leonard
16:05:43 <dauwhe> ... if we don't get that done today, we can work over email this week
16:05:44 <HeatherF> Is this formatting correctly for everyone else? http://w3c.github.io/dpub-pwp-ucr/
16:05:51 <dauwhe> ... I sent some questions and a PR
16:05:56 <ivan> https://lists.w3.org/Archives/Public/public-digipub-ig/2016Oct/0163.html : Tzviya's questions
16:05:59 <dauwhe> ... there was some email discussion
16:06:27 <dauwhe> tzviya: I proposed new language for manifests
16:06:54 <dauwhe> (fingertips found lacking)
16:07:24 <ivan> https://lists.w3.org/Archives/Public/public-digipub-ig/2016Oct/0177.html
16:07:26 <dauwhe> tzviya: leonard pointed out an issue with pointing outside the manifest
16:07:38 <dauwhe> ivan: what I posted is the latest version
16:07:49 <dauwhe> ... which is ok with leonard and myself
16:07:55 <dauwhe> tzviya: (reads definition)
16:08:15 <dauwhe> ... I find this confusing
16:08:24 <dauwhe> ... I don't know what "a mapping of the identification is"
16:08:31 <leonardr> q+
16:08:55 <dauwhe> brady: map between resource and resource in package
16:09:20 <dauwhe> tzviya: the publication should include a method to identify components in the package
16:09:32 <tzviya> q?
16:09:32 <dauwhe> leonardr: what you said is not what this is trying to address
16:09:33 <ivan> ack leonardr
16:09:37 <dauwhe> ... it's not about identification
16:09:41 <dauwhe> ... its about a mapping
16:09:44 <tzviya> ack l
16:10:05 <dauwhe> ... this URL that points out to the web, but in reality that means this resource should be inside
16:10:15 <dauwhe> ... the package can be self-contained
16:10:26 <dauwhe> tzviya: We have two requirements, we're talking about different requirements
16:10:38 <dauwhe> leonardr: I think yours is addressed under consituent resources
16:10:44 <dauwhe> ... mine isn't addressed anywhere else
16:10:55 <dauwhe> tzviya: I don't agree that it's covered under constituteent resources
16:11:14 <dauwhe> ... the use cases in manifests and links talk about pointing to indiv. theorems or citations
16:11:30 <dauwhe> leonardr: I see what youre saying
16:11:38 <brady_duga> brady_duga has joined #dpub
16:11:44 <dauwhe> tzviya: maybe we should clarify the first usage example, and make it within the publication
16:11:46 <brady_duga> present+ duga
16:12:05 <dauwhe> ... we could take out the phrase "in another publication"
16:12:15 <dauwhe> leonardr: you're right
16:12:21 <dauwhe> ... the two examples are different cases
16:12:24 <tzviya> q?
16:12:32 <dauwhe> ... the scholarly pub one isn't covered but needs to be
16:12:45 <dauwhe> ... if you're ok with 3.4 example, we should add text to address example 1
16:12:53 <dauwhe> tzviya: should we break this into two?
16:12:54 <dauwhe> ivan: yes
16:13:03 <leonardr> +1 to breaking them up
16:13:04 <dauwhe> ... it would be hard to merge the two things
16:13:27 <dauwhe> ivan: that is not a packaged requirement, it's a general requirement. Should be after 2.2
16:13:54 <dauwhe> ... Leonard, noting the text here, but in your email you refer to mona lisa, which is again another thing
16:13:58 <dauwhe> ... a resource not in the publication
16:14:05 <dauwhe> ... i'm not sure if we want to adresss
16:14:12 <dauwhe> leonardr: that's the 2nd example
16:14:21 <dauwhe> ... same as in the email
16:14:33 <Garth> q?
16:14:41 <dauwhe> ivan: we should cut it into two
16:14:48 <dauwhe> ... we have a formulation for 3.4 in the email
16:14:57 <leonardr> @bert - relative + base doesn't work because you could have resources that point to multiple sites (eg. the Mona Lisa example)
16:15:00 <dauwhe> ... we have to move first exmple into new one
16:15:04 <dauwhe> tzviya: I can do that
16:15:10 <dauwhe> ivan: let's not mix up all the PRs
16:15:38 <dauwhe> tzviya: going back to my email
16:15:44 <dauwhe> ... another Q:
16:15:52 <dauwhe> ... we've talked about the word versioning in section 3.1
16:15:57 <dauwhe> ... it's a very loaded word
16:16:04 <dauwhe> ... means different things in publishing and in web
16:16:12 <dauwhe> ... george talked about incantations
16:16:20 <dauwhe> ... we need better wording... iteration
16:16:22 <tzviya> q?
16:16:24 <dauwhe> ivan: iteration sounds good
16:16:27 <HeatherF> +1
16:16:28 <dauwhe> tzviya: anyone object?
16:16:30 <leonardr> +1
16:16:53 <dauwhe> tzviya: does iteration cover all our use cases?
16:16:58 <dauwhe> george: are iterations public?
16:17:05 <dauwhe> ivan: it's such a generic term
16:17:11 <dauwhe> ... so the question doesn't arise
16:17:18 <dauwhe> ... we  just don't want to use a loaded term
16:17:29 <dauwhe> leonardr: it's generic; may be public in 1 case, private in another
16:17:36 <dauwhe> (ding)
16:17:57 <dauwhe> tzviya: Section 4... 4.2 and 4.3
16:18:08 <dauwhe> ... it may be due to my lack of security knowledge
16:18:26 <dauwhe> ... are these sections not different enough from what's in the horizontal dependencys section
16:18:32 <leonardr> https://lists.w3.org/Archives/Public/public-digipub-ig/2016Oct/0165.html
16:18:37 <dauwhe> ... and if it's not clear to me, I'm a bit worried
16:18:39 <leonardr> ^^ my response back on the security items
16:18:53 <dauwhe> tzviya: I know leonard argued for including these
16:18:59 <dauwhe> ... we should sharpen the use cases
16:19:13 <dauwhe> leonardr: did you want to sharpen the use cases, or sharpen the descriptions?
16:19:18 <dauwhe> ... I thought use cases were clear
16:19:25 <dauwhe> tzviya: perhaps its the descriptions
16:19:34 <dauwhe> leonardr: I'm happy to take that on
16:19:37 <dauwhe> tzviya: thank you
16:19:45 <dauwhe> ... any other comments on security section
16:19:49 <dauwhe> ... is Baldur here?
16:20:00 <dauwhe> ivan: the only question i have
16:20:07 <dauwhe> ... if i look at the use case of 4.2
16:20:25 <dauwhe> ... is it any different from security issues taht are on the web?
16:20:35 <dauwhe> ... are we coming in with something that the web doesn't have?
16:21:02 <dauwhe> leonardr: with respect to publications, I don't think the publication itself is adding anything with 4.2
16:21:22 <dauwhe> ... but user agents that focused on publications may want to do more than standard web user agents
16:21:30 <dauwhe> ... we want potentially more capabilities
16:21:45 <dauwhe> tzviya: the examples are from the user perspective, not the user agent perspective
16:21:55 <dauwhe> ... maybe that's the source of confusion
16:22:00 <dauwhe> ... we
16:22:11 <dauwhe> ... have had success integrating a11y use cases
16:22:31 <dauwhe> ... we've also had pushback from the web community on differences from web security model
16:22:39 <dauwhe> leonardr: perhaps we can move 4.2
16:22:44 <dauwhe> ... we can't move 4.3
16:22:57 <dauwhe> ... I'll need to think about where
16:23:08 <dauwhe> ivan: you said 4.3 cannot be moved
16:23:17 <dauwhe> leonardr: 4.3 is where we are going beyond the web
16:23:35 <dauwhe> ... talking about the idea that a specific publication...
16:23:51 <dauwhe> ... we talked about a packaged publication, we don't have a trust model
16:23:57 <dauwhe> ... we don't have https certificates
16:24:09 <dauwhe> ... how do you establish trust in a portable publication
16:24:18 <dauwhe> tzviya: then it should go in the packaging section
16:24:23 <dauwhe> ivan: that sounds good
16:24:30 <dauwhe> ... access control remains
16:24:46 <dauwhe> tzviya: george had sent some editorial comments
16:24:50 <dauwhe> ivan: I'll take care of those
16:24:56 <dauwhe> ... I have one more question
16:25:16 <dauwhe> ... section 2, we moved some stuff, and I"m worried about the current order
16:25:22 <dauwhe> tzviya: I was going to do something
16:25:37 <dauwhe> ivan: we can discuss it here, or leave it to leonard and I
16:25:44 <dauwhe> ... i am happy to put in a more logical order
16:26:00 <dauwhe> ... constituent resource should be pushed up
16:26:23 <dauwhe> ... I'll think about it
16:26:26 <dauwhe> tzviya: thanks
16:26:37 <dauwhe> ... in section 3 we talked about manifests going before archiving
16:26:59 <dauwhe> ivan: I'm worried about having too many PRs
16:27:15 <dauwhe> tzviya: leonard, can you pick up my PR, edit it, and merge it?
16:27:21 <dauwhe> leonardr: should I keep them separate
16:27:27 <dauwhe> tzviya: depends on the timeline
16:27:33 <dauwhe> leonardr: today or tomorrow
16:27:43 <dauwhe> tzviya: do it all as 1 request, then I'll pick it up
16:27:54 <dauwhe> ivan: so I won't do anything tomorrow
16:28:00 <dauwhe> ... I'll take it up at the end
16:28:17 <dauwhe> ... I'll do editorial things, and then broadcast by the end of the week?
16:28:21 <dauwhe> HeatherF: I think so
16:28:32 <dauwhe> tzviya: the issues that leonard sent, do we want to talk about them as a group?
16:28:40 <HeatherF> s/HeatherF/Tzviya
16:28:52 <dauwhe> ivan: leonard and I agreed
16:29:02 <dauwhe> tzviya: I started to go through them
16:29:15 <dauwhe> ... i wanted to make sure we were looking at the same version
16:29:24 <dauwhe> leonardr: I was looking directly at github
16:29:37 <dauwhe> tzviya: if it's used only once, no need to remove it
16:30:09 <dauwhe> tzviya: there are lot of examples of books, we could change some of them
16:30:16 <dauwhe> leonardr: I'm fine with examples, but not outside examples
16:30:19 <dauwhe> tzviya: that's fine
16:30:25 <dauwhe> ... in section 2.2.6
16:30:30 <dauwhe> ... this is buffy
16:30:51 <pkra> still handles vampires just fine.
16:30:54 <dauwhe> ... buffy is deaf-blind, every morning she downloads a newspaper, doesn't want to waste bandwidth
16:30:59 <dauwhe> ... currently in personalization
16:31:13 <dauwhe> ... leonard wants to move to constituent resources
16:31:23 <dauwhe> dkaplan3: from a11y perspective, it's customization
16:31:36 <tzviya> q?
16:31:47 <dauwhe> ... this doc alternates willy-nilly between publisher focused, user focused, user agent focus
16:31:51 <leonardr> q+
16:32:09 <dauwhe> ... and this issue could be user-agent focused from one perspective, I wrote it as user issue
16:32:23 <tzviya> ack l
16:32:25 <dauwhe> leonardr: that's a good argument
16:32:32 <dauwhe> ... leaving it in personalization might be ok
16:32:42 <dauwhe> ... what threw me off was "building a custom publication"
16:32:53 <dauwhe> ... she just wants to consume parts of the whole pub
16:32:56 <dauwhe> ... she's filtering
16:33:10 <dauwhe> dkaplan3: I'd prefer to rewrite than move
16:33:24 <dauwhe> ... because a lot of people think of personalization as simple things like font size
16:33:37 <dauwhe> ... it's good to have a more complex case
16:33:45 <dauwhe> ... I'm ok rewriting
16:33:51 <dauwhe> ivan: I like leonard's proposal
16:33:59 <dauwhe> ... i was worried about building a new publication
16:34:13 <dauwhe> tzviya: since we're trying to keep fewer hands, can you tweak the wording
16:34:15 <dauwhe> leonardr: sure
16:34:19 <dauwhe> dkaplan3: that's fine
16:34:23 <ShaneM> This is definitely a p10n use case in that lots of users might not wwant the videos!
16:34:36 <dauwhe> tzviya: scanning through issues
16:34:56 <leonardr> sorry - @dkaplan3, though that was @heather who was raising the issue!
16:35:03 <dauwhe> ... in the last round, I put in a separate thing on manifest
16:35:26 <dauwhe> ... the requirement itself is relevant
16:35:28 <tzviya> q?
16:35:49 <dauwhe> ... it's part of the distribution, logically speaking, but it's also part of the publication
16:35:55 <dauwhe> ... keeping it in section 2 is better
16:36:00 <dauwhe> tzviya: OK
16:36:20 <dauwhe> ... my constituent resources thing might end up in this section
16:36:23 <dauwhe> ivan: I don't think so
16:36:39 <dauwhe> ... the other comments were more about rearranging
16:36:55 <dauwhe> tzviya: if anyone has additional comments, discuss on email
16:36:57 <HeatherF> Ha!
16:37:04 <HeatherF> Heather goes to Seoul for the IETF
16:37:05 <dauwhe> ivan: order is leonard, tzviya, myself
16:37:25 <dauwhe> tzviya: TOPIC: DPUB-ARIA draft for wide review
16:37:34 <dauwhe> ... I have a newer version than is in the agenda
16:37:38 <tzviya> https://rawgit.com/w3c/aria/dpub-cr/aria/dpub.html
16:37:55 <dauwhe> ... you might have to refresh
16:38:11 <dauwhe> ShaneM: It's OK. I didn't break it and I didn't fix it :)
16:38:19 <dauwhe> tzviya: still wonky in FF
16:38:27 <dauwhe> ShaneM: (expletive deleted)
16:38:40 <dauwhe> tzviya: work on this started two years ago
16:39:00 <dauwhe> ... this is a vocab for publishing industry using ARIA syntax
16:39:11 <dauwhe> ... with explicit mappings to a11y APIs
16:39:21 <dauwhe> ... used epub:type as starting point, narrowed to 30 terms
16:39:25 <dauwhe> ... we're ready for CR
16:39:27 <clapierre> Yeah!
16:39:32 <dauwhe> ... sending it here is part of "wide review"
16:39:40 <dauwhe> ... and we want implementations
16:39:47 <dauwhe> ... so we meet our exit criteria
16:39:57 <dauwhe> ... so tell us if you implement
16:40:35 <dauwhe> ... if you have the equivalent terms in epub:type, and you plan to transition when this hits PR, then that counts as implementation, according to THE DIRECTOR
16:40:44 <dauwhe> ... any questions?
16:41:01 <dauwhe> george: does the aria vocab and epub:type vocab need to be mutually exclusive?
16:41:06 <dauwhe> tzviya: no
16:41:09 <ivan>  q+
16:41:18 <dauwhe> ... it shouldn't affect anything
16:41:20 <tzviya> ack iv
16:41:45 <dauwhe> ivan: this set of terms is smaller than what IDPF has
16:41:54 <dauwhe> ... edupub has many more terms
16:41:58 <dauwhe> ... this is the first core
16:42:17 <dauwhe> ... we hope that it will be possible to add terms
16:42:41 <dauwhe> ... so that eventually, doc-aria values are replacing epub:type
16:42:49 <dauwhe> ... it's not yet done in this document
16:43:09 <dauwhe> tzviya: we've had lots of discussions on how to make this vocab extensible
16:43:58 <dauwhe> tzviya: TOPIC: task force update
16:44:06 <dauwhe> ... we haven't picked on the task forces in a long time
16:44:21 <dauwhe> ... let's start with A11Y task force
16:44:28 <dauwhe> ... what's up? how's it going?
16:44:40 <dauwhe> clapierre: we're working on several fronts
16:44:49 <dauwhe> ... first is a11y use cases
16:44:56 <dauwhe> ... I think we're finished with that
16:45:01 <tzviya> q?
16:45:03 <dauwhe> ... we meet once a week
16:45:14 <dauwhe> ... we've moved from Friday to Thursday
16:45:23 <dauwhe> ... we've also been talking with WCAG
16:45:32 <dauwhe> ... to talk about sucess criteria and techniques
16:45:44 <dauwhe> ... one concept is a collection of web pages
16:46:13 <dauwhe> ... we need navigation, reading order, a11y metadata
16:46:22 <dauwhe> ... we want these added to WCAG 2.1
16:46:32 <dauwhe> tzviya: can I ask a question?
16:46:46 <dauwhe> ... some of the work in EPUB and DPUB A11Y get blurred together
16:47:14 <dauwhe> ... it's not a problem, but for tidy note-taking etc. I imagine it might get confusing
16:47:24 <Karen> Karen has joined #dpub
16:47:25 <dauwhe> ... do we know what work wil happen in W3C vs IDPF
16:47:30 <dauwhe> clapierre: that's a good question
16:47:36 <dauwhe> ... there's lots of overlap
16:47:39 <Avneesh> q+
16:47:47 <dauwhe> ... but dealing with WCAG it was easier to do from W3C side
16:47:53 <tzviya> ack av
16:48:20 <dauwhe> Avneesh: WCAG work was done in EPUB because of EPUB a11y spec
16:48:35 <dauwhe> ... and it's mostly the same people
16:48:47 <dauwhe> dkaplan3: as one who isn't in EPUB
16:48:53 <dauwhe> ... I do get confused sometimes
16:49:23 <dauwhe> ... are there EPUB people who aren't in DPUB a11y
16:49:30 <dauwhe> Avneesh: we are in a bit of a hurry
16:49:32 <Florian> Florian has joined #dpub
16:49:41 <dauwhe> dkaplan3: this has been a problem for a while
16:49:47 <dauwhe> ... can groups share minutes?
16:49:50 <dauwhe> Avneesh: that's possible
16:50:06 <dauwhe> tzviya: it might be a good idea to have joint meetings
16:50:15 <dauwhe> ... especially if you're meeting with wcag
16:50:28 <dauwhe> ... dkaplan3 would be a great resource when meeting with wcag
16:50:39 <dauwhe> ... anything you need resource-wise?
16:50:47 <dauwhe> dkaplan3: we should continue meeting
16:50:55 <dauwhe> ... I don't believe we are under-resourced
16:51:05 <dauwhe> ... but once the UCR doc is done, we'll want to re-address
16:51:12 <dauwhe> ... what our next main purpose is
16:51:18 <dauwhe> clapierre: I agree with all of that
16:51:27 <dauwhe> ... we do have lots of people in our meetings, which is great
16:51:42 <dauwhe> ... we have lots we can do with
16:51:46 <dauwhe> tzviya: I can make a suggestion
16:51:57 <dauwhe> ... the WAI IG puts out calls for participation
16:52:04 <dauwhe> ... they want help with CSS a11y task force
16:52:12 <dauwhe> ... (cough, Deborah)
16:52:33 <dauwhe> George: one of the big items is with WCAG success criteria
16:52:40 <dauwhe> ... wer're introducing web publication as a term
16:52:47 <dauwhe> ... then the criteria apply to that term
16:52:53 <astearns> If you can help with CSS a11y Rossen Atanassov would be a good person to contact
16:53:00 <dauwhe> ... I think it's a good thing to do
16:53:12 <dauwhe> tzviya: sounds like you can work this out in your meetings
16:53:52 <dauwhe> dauwhe: I have a task force?
16:54:28 <leonardr> I'm also happy to volunteer...
16:54:48 <dauwhe> dauwhe: not much has happened recently
16:55:23 <George> George must leave, have a great day
16:55:33 <dauwhe> tzviya: is Tim here?
16:55:44 <dauwhe> ... are any archive folks here?
16:55:51 <dauwhe> leonardr: we have not met recently
16:55:58 <dauwhe> ... I'm not aware of action items
16:56:08 <dauwhe> ... I'd suggest putting it away
16:56:12 <dauwhe> tzviya: STEM
16:56:18 <dauwhe> pkra: we haven't met lately
16:56:25 <dauwhe> tzviya: shouldl you continue meeting?
16:56:33 <dauwhe> ... has work shifted to math on the web grou
16:56:39 <ivan> s/shouldl/should/
16:56:43 <dauwhe> pkra: I don't think there's enough interest right now
16:57:00 <dauwhe> tzviya: so we should close task force
16:57:04 <dauwhe> pkra: yes
16:57:19 <cmaden2> cmaden2 has left #dpub
16:57:27 <dauwhe> tzviya: I was leading the structural semantics task force, which led to dpub-aria vocab
16:57:34 <dauwhe> ... I want to close that down after that publishes
16:57:35 <ShaneM> yay on closing it down!
16:57:43 <ivan> q+
16:57:46 <tzviya> ack iv
16:57:48 <dauwhe> ... for new terms, like education, we can maybe work with a11y task force?
16:57:57 <clapierre> Sounds good to me :)
16:58:06 <dauwhe> ivan: that one is special because the work with ARIA WG will lead to formal REC
16:58:16 <dauwhe> ... in a sense, the discussion that we'll have to have
16:58:28 <dauwhe> ... if we want to charter a digital pub working group
16:58:43 <dauwhe> ... I wonder if this wg should have responsibility of co-editing new terms
16:59:01 <dauwhe> tzviya: that's fine; I just don't want perpetual meetings
16:59:14 <dauwhe> ivan: I'm not sure pushing the next version to ARIA WG is a good approach
16:59:17 <dauwhe> tzviya: that makes sense
16:59:34 <dauwhe> ... as part of chartering, we want to make sure the group is part of the authoring process
16:59:50 <dauwhe> ivan: maybe Shane knows; there have been other WGs with joint task forces with ARIA
16:59:58 <dauwhe> ... not sure what current status is
17:00:15 <dauwhe> ... joint deliverables of two working groups are always complicated
17:00:28 <dauwhe> tzviya: It was a hot topic with web apps charter
17:00:41 <dauwhe> ShaneM: so web apps is responsible for a11y deliverable
17:00:46 <dauwhe> ... for svg it's not done yet
17:00:55 <dauwhe> ... but I think the task force will go away
17:01:12 <dauwhe> ivan: things to remember when a-chartering-we-will-go
17:01:16 <dauwhe> tzviya: thanks everyone
17:01:31 <dauwhe> ivan: Europeans beware, the time changes in the US
17:01:48 <HeatherF> Thanks all!
17:02:02 <ivan> rrsagent, draft minutes
17:02:02 <RRSAgent> I have made the request to generate http://www.w3.org/2016/10/31-dpub-minutes.html ivan
17:02:24 <ivan> trackbot, end telcon
17:02:24 <trackbot> Zakim, list attendees
17:02:24 <Zakim> As of this point the attendees have been George, dauwhe, Avneesh, astearns, Ivan, Heather_Flanagan, Peter, Krautzberger, Tzviya, Deborah_Kaplan, Chris_Maden, Ben_De_Meester, Bert,
17:02:27 <Zakim> ... clapierre, ShaneM, Leonard, duga
17:02:32 <trackbot> RRSAgent, please draft minutes
17:02:32 <RRSAgent> I have made the request to generate http://www.w3.org/2016/10/31-dpub-minutes.html trackbot
17:02:33 <trackbot> RRSAgent, bye
17:02:33 <RRSAgent> I see no action items