15:56:48 RRSAgent has joined #dnt 15:56:48 logging to http://www.w3.org/2015/04/08-dnt-irc 15:56:49 trackbot, start meeting 15:56:50 RRSAgent, make logs world 15:56:50 Zakim has joined #dnt 15:56:52 Zakim, this will be TRACK 15:56:52 ok, trackbot; I see T&S_Track(dnt)12:00PM scheduled to start in 4 minutes 15:56:53 Meeting: Tracking Protection Working Group Teleconference 15:56:53 Date: 08 April 2015 15:56:55 RRSAgent, make logs world 15:56:57 Zakim, this will be TRACK 15:56:58 Meeting: Tracking Protection Working Group Teleconference 15:56:58 ok, trackbot; I see T&S_Track(dnt)12:00PM scheduled to start in 4 minutes 15:56:58 Date: 08 April 2015 15:57:06 chair: justin 15:57:26 regrets+ cargill, schunter 15:58:36 fielding has joined #dnt 15:58:50 dsinger has joined #dnt 15:58:54 justin has joined #dnt 15:59:13 T&S_Track(dnt)12:00PM has now started 15:59:22 +[Apple] 15:59:26 zakim, who is here? 15:59:26 On the phone I see [Apple] 15:59:28 On IRC I see justin, dsinger, fielding, Zakim, RRSAgent, npdoty, WaltMichel, adrianba, hober, walter, wseltzer, trackbot 15:59:37 zakim, [apple] has dsinger 15:59:38 +dsinger; got it 15:59:46 +[FTC] 15:59:53 +Fielding 15:59:56 +npdoty 16:00:08 +WaltMichel 16:01:04 + +1.202.407.aaaa 16:01:09 zakim, aaaa is me 16:01:11 +justin; got it 16:01:25 Can someone scribe what should hopefully be a very short call today? 16:01:54 +Wendy 16:02:12 WileyS has joined #dnt 16:02:19 ChrisPedigoDCN has joined #dnt 16:02:23 +Chris_Pedigo 16:02:35 +kulick 16:03:01 sure, I’ll do it 16:03:04 -kulick 16:03:11 scribenick: dsinger 16:03:13 scribenick: dsinger 16:03:30 justin: short call, only one issue. 16:03:32 +WileyS 16:03:35 https://lists.w3.org/Archives/Public/public-tracking/2015Apr/0002.html 16:03:47 https://lists.w3.org/Archives/Public/public-tracking/2015Apr/0002.html 16:03:57 justin: working off Roy’s email; we need to address ‘tracking data’ as we use the term and it’s not defined 16:04:19 … there are a handful of places in TCS. Walter has concerns on the changes 16:04:34 My concerns were that Walter's language expands scope 16:04:47 … today we’ll walk through this. This discussion include ‘de-identification’. 16:04:51 vincent has joined #dnt 16:05:07 these are non-normative considerations, I believe 16:05:24 … Roy wanted to remove ‘tracking data’ from the text, Walter objected, we would like to understand why. 16:05:25 +vincent 16:05:26 zakim, who is on the phone? 16:05:26 On the phone I see [Apple], [FTC], Fielding, npdoty, WaltMichel, justin, Wendy, Chris_Pedigo, WileyS, vincent 16:05:29 [Apple] has dsinger 16:05:34 q+ 16:05:35 +kulick 16:05:45 ack npdoty 16:05:50 …notes that Walter is not on the phone to explain. Nick volunteers to try 16:05:58 -kulick 16:06:30 npdoty: shares the confusion. Doesn’t see what the problem is; merging with ‘original tracking data’ changed seems to make sense 16:06:47 I'm fine with removing the text in that section, per fielding's latest email 16:06:51 justin: anyone else object to removing the term ‘tracking data’ from de-identification? 16:07:02 Yep, it is just another example (which happens to contradict the definition, which might lead people tp think they can retain the original tracking data) 16:07:23 … no-one seems to object for the other two changes: permitted uses (changed to ‘that data’)… 16:07:26 +1 16:07:49 … the other example was a qualifier for permitted uses: tracking data -> data about that activity 16:08:07 … neither seem controversial. 16:08:10 yeah, that was just an example I drafted; I'm fine with changing it. 16:08:25 … the other place is 3rd party compliance. “must not collect, share…tracking data” 16:08:53 … Roy found this vague or contradictory. Prefers to re-write. (we need a link to the email). 16:09:31 https://lists.w3.org/Archives/Public/public-tracking/2015Apr/0002.html 16:10:01 npdoty: “collecting data that would result in” seems problematic 16:10:23 q? 16:10:55 my concern is about the "*this* particular user's activity to have been collected across multiple distinct contexts" 16:10:56 … it’s not clear who is doing the tracking (it’s expressed in the passive): what happens if I convey data that doesn’t, to someone else, and the result is that they do? 16:11:13 so we should say "party" again? 16:11:36 justin: seems like that is addressed. you’re not allowed to share outside the context, and you’re not allowed to track cross contexts yourself. is there a hole? is there language to address that? 16:11:45 https://lists.w3.org/Archives/Public/public-tracking/2015Mar/0028.html 16:11:53 +kulick 16:12:03 Then they are the party responsible for honoring DNT signals, if any, as there was no way for the first party which responded they were not tracking to preconceive a future party to leverage shared data for a tracking purpose. 16:12:17 npdoty: what I suggested is to add a prohibition on sharing, to stop the 4th party problem 16:12:30 justin: but Roy does prohibit sharing (2nd bullet) 16:12:46 npdoty: maybe I am confused by retain…share 16:13:03 fielding: I am trying to use the same words as the definition 16:13:28 … if a 4th party (?) is collecting in a single context, that doesn’t violate tracking 16:13:56 justin: you can share within that context, but not with a random data broker out of context, 16:14:03 my understanding is that Roy's proposal would allow collection of different user's activities accross different context 16:14:12 fielding: and you can’t retain youself across multiple contexts 16:14:16 q+ 16:14:35 justin: to Vinecent 16:14:42 maybe fielding's second bullet could just be "share", and then it makes more sense to me 16:15:19 Vincent: my concern is about this user’s activity, doesn’t seem related to the current interaction. Not sure if you’re allowed to collect data about the user, but different activities in different contexts. 16:15:51 justin: you can’t collect data that results in you haveing data [about that user] about multiple contexts: that puts you in violation 16:16:02 … seems tighter than the use of the words ‘tracking data’ 16:16:13 … do you have an example that this does not prohibit? 16:16:41 vincent: for example if the user visits two web sites, two activities, that would seem allowed 16:16:43 I think there was confusion about the scope of "particular" 16:17:01 fielding: we have an english ambiguity, the scope of ‘activity’, so maybe say ‘activity by this user’? 16:17:17 justin: maybe I don’t fully understand the concern 16:17:32 "data regarding this particular user" -- do we even need "activity"? 16:17:41 fielding: depends on how you parse the sentence. 16:17:45 [silence] 16:17:46 regarding activuty by this particular user? 16:18:10 npdoty: how about “data from this particular user being associated across multiuple contextsa" 16:18:13 ? 16:18:20 collect data from this network interaction that would result in 16:18:20 > data regarding this particular user to have been 16:18:21 > collected across multiple distinct contexts 16:18:22 s/contextsa/contexts/ 16:18:36 sounds good to me 16:18:51 fielding: fine by me 16:19:29 justin: then we’ll do that 16:19:29 Its the mixing of the contexts that are the issue - not if the data is managed within only the context in which it was collected originally, correct? 16:20:15 dsinger: if I remember I served an ad to a user who visited say the NYT, isn’t that two contexts? 16:20:37 WileyS, I think the "share" bullet is about limiting the sharing of data about one context with other parties 16:20:38 Frequency capping is carved out 16:21:06 fielding: yes, but it’s a permitted use. 16:21:08 Nick, but this change is about "collected data...across multiple distince contexts" 16:21:56 dsinger: but generally, except for permitted use, an ad server can remember it served an ad to a user, but not that it was on the NYT; or it can remember the BYT and the ad, but not the user 16:22:18 npdoty: not sure that’s my understanding; 16:22:27 justin: is there an example of an ambiguity? 16:22:37 dsinger: list the thread in the process of scribing 16:22:37 npdoty: if I'm embedded in the NYT and remember the user's visit to the NYT, that's not by itself tracking, I think. 16:22:50 justin: we’ll send around the revised proposed edit 16:23:00 … no-one seemed to echo Walter’s concern 16:23:10 … otherwise, at least for this call, we seem aligned on the text 16:23:16 … any other substantive issues outstanding? 16:23:25 What is left on TCS? 16:23:28 … is everything ironed out, Nick? 16:23:34 npdoty: I think so 16:23:42 fielding, perhaps offline, I'm not sure I understand "retain, use or share" in that second bullet, rather than just "share" 16:23:53 justin: we can check that there is nothing outstanding 16:24:09 justin: sent out a list of issues that are either closed or superseded 16:24:20 Roy responded - and we agreed with his statements so didn't respond. 16:24:24 … only Roy responded, noting we are still dealing with user tracking 16:24:32 I'll mark 203 as pending review once I've made remaining changes about tracking data 16:24:35 … another can be closed, was open for future ref. 16:24:48 … what else do we need to do on TCS? 16:25:00 Should we do one full clean read like we did with the TPE? 16:25:15 Right that. 16:25:25 npdoty: I think when we were wrapping up TPE, we made the changes, and then we gave people 2 weeks to review for LC 16:25:25 We did a full read - then a few weeks wait - then went for public comment 16:25:31 npdoty, can we change the citation for TPE to [TPE] instead of [TRACKING-DNT]? It reads better. 16:25:44 justin: so we’ll send an email saying this is a LC candidate, give people 2 weeks to review 16:25:51 … timeframe when that will be ready? 16:26:01 sure, fielding, can you send me an email reminder about that 16:26:09 npdoty: no later than Monday next (apr 13) 16:26:14 What volume of meaningful comment/push-back will it take to abandon the TCS (and only move forward with the TPE)? 16:26:25 justin: we don’t need to do a call; we’ll send it out and invite comment to the list 16:26:28 I can do it myself if you like … easy global replace. 16:26:43 … will also send a summary of today’s call, to make sure Walter is informed 16:26:46 … AOB? 16:26:50 16:26:51 [silence] 16:26:58 -Chris_Pedigo 16:27:00 -[FTC] 16:27:00 -WaltMichel 16:27:00 … hearing none, we’ll talk again soon 16:27:01 -justin 16:27:02 -kulick 16:27:02 -WileyS 16:27:02 -vincent 16:27:04 -npdoty 16:27:04 adjourned 16:27:10 -Wendy 16:27:12 thanks dsinger for scribing 16:27:25 trackbot, end meeting 16:27:25 Zakim, list attendees 16:27:25 As of this point the attendees have been dsinger, [FTC], Fielding, npdoty, WaltMichel, +1.202.407.aaaa, justin, Wendy, Chris_Pedigo, kulick, WileyS, vincent 16:27:28 -[Apple] 16:27:33 RRSAgent, please draft minutes 16:27:33 I have made the request to generate http://www.w3.org/2015/04/08-dnt-minutes.html trackbot 16:27:34 RRSAgent, bye 16:27:34 I see no action items