15:30:31 RRSAgent has joined #dnt 15:30:31 logging to http://www.w3.org/2013/06/26-dnt-irc 15:30:33 RRSAgent, make logs world 15:30:33 Zakim has joined #dnt 15:30:35 Zakim, this will be 15:30:35 I don't understand 'this will be', trackbot 15:30:36 Meeting: Tracking Protection Working Group Teleconference 15:30:36 Date: 26 June 2013 15:30:41 zakim, this will be TRACK 15:30:41 ok, tlr; I see T&S_Track(dnt)12:00PM scheduled to start in 30 minutes 15:38:38 ninjamarnau has joined #dnt 15:40:04 npdoty has joined #dnt 15:45:03 eberkower has joined #dnt 15:46:42 moneill2 has joined #dnt 15:48:00 Thomas_Schauf has joined #dnt 15:50:35 trackbot, start meeting 15:50:37 RRSAgent, make logs world 15:50:39 Zakim, this will be 15:50:39 I don't understand 'this will be', trackbot 15:50:40 Meeting: Tracking Protection Working Group Teleconference 15:50:40 Date: 26 June 2013 15:52:17 efelten has joined #dnt 15:55:36 T&S_Track(dnt)12:00PM has now started 15:55:45 + +1.609.258.aaaa 15:55:45 zakim, call thomas-781 15:55:45 ok, tlr; the call is being made 15:55:46 +Thomas 15:56:14 +RichardWeaver 15:56:19 zakim, drop thomas 15:56:19 Thomas is being disconnected 15:56:20 -Thomas 15:56:23 Zakim, aaaa is me 15:56:23 +efelten; got it 15:56:25 zakim, call thomas-781 15:56:25 ok, tlr; the call is being made 15:56:27 +Thomas 15:56:32 + +1.646.654.aabb 15:56:42 +npdoty 15:56:44 zakim, I am tomas 15:56:44 sorry, tlr, I do not see a party named 'tomas' 15:56:47 zakim, I am thomas 15:56:47 ok, tlr, I now associate you with Thomas 15:56:48 rachel_n_thomas has joined #dnt 15:56:50 zakim, mute me 15:56:51 Thomas should now be muted 15:56:52 aabb is eberkower 15:56:59 Zakim, aabb is eberkower 15:56:59 +eberkower; got it 15:57:01 ack thomas 15:57:05 Richard_comScore has joined #dnt 15:57:12 zakim, mute me 15:57:13 Thomas should now be muted 15:57:31 + +1.202.973.aacc 15:57:40 paulohm has joined #dnt 15:57:42 aerber has joined #dnt 15:57:53 Brooks has joined #dnt 15:58:02 + +1.202.478.aadd 15:58:11 Nick, Adam Phillips representing ESOMAR will be calling in from the UK - he is unsure how his number will show up, but if you see a strange/UK number, it's him 15:58:16 Yianni has joined #DNT 15:58:30 rvaneijk has joined #dnt 15:58:31 +Brooks 15:58:33 zakim, 1.202.478.aadd is rachel_n_thomas 15:58:33 sorry, rachel_n_thomas, I do not recognize a party named '1.202.478.aadd' 15:58:40 Zakim, aadd is rachel_n_thomas 15:58:40 +rachel_n_thomas; got it 15:58:46 thanks nick :) 15:58:49 (i'm rusty) 15:58:54 + +1.202.587.aaee 15:59:10 Zakim, aaee is yianni 15:59:10 +yianni; got it 15:59:15 zakim, mute me 15:59:16 yianni should now be muted 15:59:25 + +49.431.98.aaff 15:59:33 +Wendy 15:59:42 + +1.215.480.aagg 15:59:44 zakim, aaff is ninjamarnau 15:59:44 +ninjamarnau; got it 15:59:47 jchester2 has joined #dnt 15:59:49 + +1.202.326.aahh 15:59:50 + +1.917.934.aaii 15:59:57 zakim, aahh is paulohm 15:59:58 +paulohm; got it 15:59:59 susanisrael has joined #dnt 16:00:04 WileyS has joined #dnt 16:00:11 + +1.202.331.aajj 16:00:12 + +1.323.253.aakk 16:00:14 Zakim, aacc may be paul_glist 16:00:14 +paul_glist?; got it 16:00:18 +[Microsoft] 16:00:20 +[IPcaller] 16:00:26 +hefferjr 16:00:28 + +1.408.836.aall 16:00:35 +jchester2 16:00:38 kulick has joined #dnt 16:00:39 zakim, mute me 16:00:39 +WileyS 16:00:39 jchester2 should now be muted 16:00:44 Ari has joined #dnt 16:00:57 johnsimpson has joined #dnt 16:00:59 zakim. [IPCaller] is me 16:01:03 +JeffWilson 16:01:13 +??P22 16:01:18 + +31.65.141.aamm 16:01:24 jeffwilson has joined #dnt 16:01:26 Zakim, aamm is me 16:01:27 +rvaneijk; got it 16:01:37 robsherman has joined #dnt 16:01:41 +vinay 16:01:49 WaltMichel has joined #DNT 16:01:55 +[Apple] 16:01:57 zakim, [apple] has dsinger 16:01:57 +dsinger; got it 16:01:59 BillScannell has joined #dnt 16:01:59 vinay has joined #dnt 16:02:06 +hwest 16:02:09 Aleecia has joined #dnt 16:02:10 + +1.650.391.aann 16:02:11 + +1.202.629.aaoo 16:02:12 hwest has joined #dnt 16:02:12 justin has joined #dnt 16:02:15 zakim, aann is robsherman 16:02:15 +robsherman; got it 16:02:18 peterswire has joined #dnt 16:02:27 I'm calling in now; had a glitch 16:02:29 Joanne has joined #DNT 16:02:34 Zakim, 917.934.------ is me 16:02:34 sorry, susanisrael, I do not recognize a party named '917.934.------' 16:02:44 Jay_Jin has joined #dnt 16:02:45 + +1.212.844.aapp 16:02:46 sidstamm has joined #dnt 16:02:53 zakim, aaoo is johnsimpson 16:02:53 +johnsimpson; got it 16:02:57 jackhobaugh has joined #dnt 16:02:59 cOlsen has joined #dnt 16:03:07 zakim, who is making noise? 16:03:07 +[CDT] 16:03:19 dsinger, listening for 10 seconds I heard sound from the following: npdoty (6%), [Microsoft] (57%), +1.212.844.aapp (35%) 16:03:22 +Joanne 16:03:25 Chapell has joined #DNT 16:03:27 JC has joined #DNT 16:03:35 Zakim, ??P22 may be schunter 16:03:35 +schunter?; got it 16:03:38 + +1.301.365.aaqq 16:03:45 + +1.347.272.aarr 16:03:48 AdamP has joined #dnt 16:03:58 +[FTC] 16:04:00 +[Microsoft.a] 16:04:02 OK here, no noise 16:04:08 + +1.647.274.aass 16:04:18 peter-4As has joined #dnt 16:04:18 schunter has joined #dnt 16:04:26 +Chris_Pedigo 16:04:29 + +1.202.347.aatt 16:04:34 David_MacMillan has joined #dnt 16:04:34 ChrisPedigoOPA has joined #dnt 16:04:39 + +1.650.365.aauu 16:04:54 + +49.211.600.4.aavv 16:04:54 -[IPcaller] 16:04:54 -[Microsoft] 16:04:55 dstark has joined #dnt 16:04:56 Zakim, aatt is jackhobaugh 16:04:56 +jackhobaugh; got it 16:05:04 +??P74 16:05:34 + +1.646.666.aaww 16:05:36 + +1.202.787.aaxx 16:05:42 -rvaneijk 16:05:44 zakim, aaww is chapell 16:05:44 +chapell; got it 16:05:48 +[Microsoft] 16:05:54 I can scribe 16:05:55 scribenick: Yianni 16:06:08 YES 16:06:13 Peter: cannon can you scribe 16:06:14 yANNI is up 16:06:18 +rvaneijk 16:06:24 vincent has joined #dnt 16:06:35 Zakim, who is on the phone? 16:06:35 On the phone I see efelten, Thomas (muted), RichardWeaver, eberkower, npdoty, paul_glist?, rachel_n_thomas, Brooks, yianni (muted), ninjamarnau, Wendy, +1.215.480.aagg, paulohm, 16:06:35 ... susanisrael, +1.323.253.aakk, +1.202.331.aajj, hefferjr, +1.408.836.aall, jchester2 (muted), WileyS, JeffWilson, schunter?, vinay, [Apple], hwest, robsherman, johnsimpson, 16:06:40 Sure 16:06:40 ... +1.212.844.aapp, [CDT], Joanne, peterswire, +1.347.272.aarr, [FTC], [Microsoft.a], +1.647.274.aass, Chris_Pedigo, jackhobaugh, +1.650.365.aauu, +49.211.600.4.aavv, ??P74, 16:06:40 ... chapell, +1.202.787.aaxx, [Microsoft], rvaneijk 16:06:40 [Apple] has dsinger 16:06:42 jmayer has joined #dnt 16:06:44 Peter: Rob Sherman could you scribe starting at 1:30 16:06:51 Yes 16:06:51 Zakim, aarr is jay_jin 16:06:51 +jay_jin; got it 16:06:53 +Dan_Auerbach 16:07:02 Zakim, who is on the phone? 16:07:02 On the phone I see efelten, Thomas (muted), RichardWeaver, eberkower, npdoty, paul_glist?, rachel_n_thomas, Brooks, yianni (muted), ninjamarnau, Wendy, +1.215.480.aagg, paulohm, 16:07:06 okay 16:07:06 ... susanisrael, +1.323.253.aakk, +1.202.331.aajj, hefferjr, +1.408.836.aall, jchester2 (muted), WileyS, JeffWilson, schunter?, vinay, [Apple], hwest, robsherman, johnsimpson, 16:07:06 ... +1.212.844.aapp, [CDT], Joanne, peterswire, jay_jin, [FTC], [Microsoft.a], +1.647.274.aass, Chris_Pedigo, jackhobaugh, +1.650.365.aauu, +49.211.600.4.aavv, ??P74, chapell, 16:07:06 ... +1.202.787.aaxx, [Microsoft], rvaneijk, Dan_Auerbach 16:07:06 [Apple] has dsinger 16:07:12 Zakim, aass is dstark 16:07:12 +dstark; got it 16:07:19 Peter: Yianni first, JC 12:45, Heather at 1:30 16:07:20 dan_auerbach has joined #dnt 16:07:37 rvaneijk_ has joined #dnt 16:07:46 fielding has joined #dnt 16:07:49 ...introductory comments, lots of hardwork from people 16:07:57 + +1.646.827.aayy 16:07:58 ...goal has been to get one clear document in front of us 16:07:59 Thank you to w3c staff for coordinating 16:08:04 yes, big thanks to Nick for the incredible job he's done collecting and organizing all of these proposals! 16:08:06 ...clear to everyone what the changes are off of that 16:08:11 +BerinSzoka 16:08:22 ...actual number of issues is not in the hundreds range 16:08:28 +Fielding 16:08:29 [order of dicsussion for today: http://lists.w3.org/Archives/Public/public-tracking/2013Jun/0403.html ] 16:08:30 ...history of discussing many of these issues 16:08:40 ...challenges we always have is how to get some final round 16:08:59 ...US Senate doing this with immigration, and with the EU data protection regulation 16:09:07 ...at some point you need to slim down the issues 16:09:15 ...we are trying to do this with maximum transparency 16:09:35 ...Peter is recording the fac that he is meeting with people 16:09:50 ...my goal today is a human readable version 16:09:52 +Jonathan_Mayer 16:09:53 +[IPcaller] 16:09:55 zakim,[IPCaller] is me 16:09:55 +moneill2; got it 16:10:01 It's a rush to judgement--not a "slimming" done--thats a rationalization to justify a process that doesn't serve privacy well. 16:10:02 Zakim, aaxx is BillScannell 16:10:02 +BillScannell; got it 16:10:07 dwainberg has joined #dnt 16:10:08 ...give the people who proposed changes to briefly, a minute, what the changes are and why they should be in 16:10:20 ...I've grouped in ways that I thought made sense, but I am sure I made mistakes 16:10:31 ...hearing the basic reason for change of proposal 16:10:50 mecallahan has joined #dnt 16:10:50 ...what we are going to do is highlight presentation from people who have submitted change proposals 16:11:00 ...we are going to start moving forward 16:11:13 ack thomas 16:11:15 ...Thomas is there a problem on the bridge 16:11:18 zakim, mute me 16:11:18 Thomas should now be muted 16:11:23 Thomas: working on it 16:11:34 Peter: I am going to move through the list as stated 16:11:50 amyc has joined #dnt 16:11:55 ...first one is that the June draft did not contain public commitment 16:12:15 ...myself and W3C staff made a mistake in leaving this out of June Draft, we are inclined to put it back in 16:12:30 - +1.202.331.aajj 16:12:33 ...if you disagree with that, putting it in as an editorial change 16:12:34 PaulGlist has joined #dnt 16:12:37 Zakim, mute me 16:12:37 npdoty should now be muted 16:12:50 ...an editor process tries to have spelling correct and make language consistent 16:13:00 zakim, call thomas-skype 16:13:00 ok, tlr; the call is being made 16:13:01 +Thomas 16:13:06 q+ 16:13:06 ...we will bullet editorial changes, if you object or want different language, please respond 16:13:12 -Thomas 16:13:12 zakim, drop thomas 16:13:13 Thomas is being disconnected 16:13:13 -Thomas 16:13:17 ...we will not make editorial changes without you seeing 16:13:20 if somebody's stuck with dial-in, please retry now 16:13:24 ..that is number 1 16:13:26 q- 16:13:26 q+ 16:13:28 sidstamm and any others with connection challenges, dial *0 16:13:34 ...For geolocation many people comments 16:13:40 ...David could you explain your proposal 16:13:57 David: I suggested that we delete it 16:14:14 q- 16:14:21 ...I would be comfortably amending that this is a clear specific additional restriction 16:14:22 hefferjr has joined #dnt 16:14:27 +Aleecia 16:14:30 zakim, call thomas-781 16:14:30 ok, tlr; the call is being made 16:14:31 +Thomas 16:14:33 ...okay with either deleting or amending 16:14:38 tlr has changed the topic to: if you have connection challenges, dial *0 instead of a code 16:14:39 +1 to dsinger, clarifying that it's a separate additional restriction, existing agreement 16:14:48 zakim, I am thomas 16:14:48 ok, tlr, I now associate you with Thomas 16:14:50 zakim, mute me 16:14:50 Thomas should now be muted 16:14:57 q+ 16:15:02 s/sidstamm and any others with connection challenges, dial *0// 16:15:03 Peter: ask for in connection with this, if you plan on writing perfecting amendments in the spirit that David just mentioned, could you indicate by +1 16:15:23 +[Mozilla] 16:15:30 Propose to remvoe this section completely as this information is not "tracking" as its not extracted from "cross site" data collection and use. 16:15:32 Zakim, Mozilla has sidstamm 16:15:32 +sidstamm; got it 16:15:36 wseltzer, thanks. 16:15:38 ...expect to be offering text +1 that is consistent with David Singer, if you expect to do language different from David Singer hit -1 16:15:46 -1 16:15:49 +1 to help dsinger with the suggestion just made 16:15:53 we're still trying to digest all these proposals I don't know what I'll do 16:15:54 ...+1 is friendly, -1 is different from proposed change 16:16:12 /join #dnt 16:16:12 -1 16:16:19 I agree with John. Peter, I object. Ths process is confusing. 16:16:19 Shane, we've been at consensus to address geoip for over two years 16:16:22 ...the next part is various proposals around definitions of first parties 16:16:22 -1 16:16:29 I don't think Lee is on the call 16:16:31 dwainber_ has joined #dnt 16:16:32 ...Lee Tien had the first suggestion 16:16:34 he's on a plane 16:16:43 ...Lee is unable to make the call 16:16:49 -1 16:17:13 [Lee's email: http://lists.w3.org/Archives/Public/public-tracking/2013Jun/0407.html] 16:17:13 The text in the WD 16:17:22 *dsinger, peter collected names of people who want to comment. No resolution. 16:17:24 John Simpson: reading an email from Lee, the consumer side logic is simple, there is a lack of consensus. 16:17:29 Aleecia, I explained this in more detail on the mailing list. 2 years ago it made sense but now that we have a definition of tracking this clearly doesn't fit in -AND- considerable work is going on elsewhere to address precise geolocation in a much more thorough manner 16:17:37 Peter: part of today is understanding what the issues are 16:17:38 dsinger, I think the request was just to find the people who wanted to add friendly or counter amendments 16:17:47 John could you include the language in the minutes? 16:18:02 Peter: this is a debate at a big scale, rather than perfecting language 16:18:05 Lee, via email: 16:18:05 On first parties and affiliates, I think the consumer-side logic is obvious: expectations and data dispersion. Industry has its reasons for an expansive view, of course. 16:18:08 My purpose is not to argue but to reiterate what I see as a lack of consensus--as distinguished from convenience or being part of a large compromise. I have heard occasional complaints about how third parties are differentially affected, or how large first parties are advantaged by an expansive definition of first parties. 16:18:08 Include me in writing text on geo-location 16:18:12 JoAnn_Covington has joined #dnt 16:18:16 ...next one on definition of first party is Chris Pedigo 16:18:29 Chris: the current language requires a link on each page to a list of affiliates 16:18:44 That's a fine discussion of additional information for the chairs to evaluate re-opening if they choose to, but that is a decision point. 16:18:47 ...I do not know if that address questions of how data is used, restrictions are in place 16:18:56 ...it also does not capture how a use might be best educated 16:19:12 ...instead of listing companies in corporate unbrella, and instead list brands 16:19:25 ...in FTC report, common branding was also allowed 16:19:40 ...totally agree to have transparency, but what more user friendly transparency 16:19:45 ...amendment to do it better 16:19:53 Amy: very similar concerns to Chris 16:19:55 Unless and u til the chairs agree to reopen, geoip is closed at consensus 16:20:13 The language in specification did not get at heard of debate, think one click at all time is unworkable 16:20:21 ...can work with Chris on language 16:20:29 conference is full, no more parties can be added at this time. 16:20:44 ...very impressed you could organize, we are not in a position to make substantive suggestions to these proposals 16:20:49 Aleecia - I'll submit a formal objection and provide the required "material and new" arguments to consider to stay within the appropriate process. 16:20:51 ...more work to review and feedback in the future 16:21:00 Peter: that is exactly right, much of it will be on list 16:21:06 npdoty has joined #dnt 16:21:10 ...we will have more details of order of things discussed on list and on the calls 16:21:13 + +1.650.595.aazz 16:21:17 +1 16:21:18 +1 16:21:20 1? 16:21:21 +1 16:21:27 ...ask if others would want to work with CHris and Amy, please list 16:21:27 +1 16:21:29 1? 16:21:30 +1 16:21:39 +Rigo 16:21:48 ...we would see if we could consensus that way 16:21:49 Shane, thanks; formal objection isn't needed. But this is something for the co-chairs to choose to reopen or not 16:21:56 -BillScannell 16:22:03 zakim, aazz is probably BillScannell 16:22:03 +BillScannell?; got it 16:22:15 Peter: ALan could you speak first about use of 1st party data in a 3rd party context 16:22:21 to help with Chris/Amy on affiliates language: WileyS robsherman susanisrael vinay Yianni johnsimpson jchester2 16:22:26 Alan: sent something in at 11:30 this morning that gets to it 16:22:42 Aleecia - formal objection can force the issue open outside of co-chair agreement so I'm ready to go that route if necessary 16:23:02 ...current context suggests that a 1st party cannot use information in the 3rd party experience 16:23:06 + +1.650.787.bbaa 16:23:08 help on geolocation, friendly: npdoty, counter: ari, jeff, alan, shane 16:23:19 John: Yes you may while you are in a relationship with first party, there is a certain level of trust 16:23:22 That's fine, and if denied reopening, that's appropriate. I'm trying to save you some work is all. 16:23:30 ...no expectation that it would carry over when functioning as a third party 16:23:39 ...glad to work with Alan on language 16:23:52 +1 16:23:55 +1 16:23:57 +1 to participate in the discussion, not to agree on substance 16:23:58 Peter: gues is that people in first party context that would like to be engaged in discussion. please list a +1 16:23:58 +1 16:24:00 dwainberg has joined #dnt 16:24:07 -1 16:24:07 +1 16:24:10 Q+ 16:24:13 ...I think we understand that concept 16:24:19 Peter, I have a question about this one. 16:24:22 q? 16:24:36 ...to the extent Alan and John can work with others, please include Yianni 16:24:37 q- 16:24:42 help alan and john on first party restrictions: ChrisPedigoOPA, vinay, jchester2 dwainber_ ; counter: wileys, robsherman 16:24:49 ack justin 16:24:59 Justin: in previous versions we parked this issue, some thought it was okay to use first party data in this context 16:25:09 + +1.202.331.bbbb 16:25:23 ...Alan seems to think its prohibited under the June Draft. Peter do you have an oppinion 16:25:34 Peter: no language that explicitly says that, comfortable saying that 16:25:43 ...I am not sure I agree with Alan that it explicitly bars 16:25:55 John: we are adding that makes it clear and that it was left out 16:26:12 ...i think it is implicit that a first party can use information they get from a third party 16:26:18 ...why we need language on data append 16:26:30 ...it is the same we discussed some time back, all the same language 16:26:49 ...it has been extensively discussed, I answered all the questions in the list 16:26:52 -Aleecia 16:27:09 Peter: if people have language around John's proposal. A lot of people are not in favor of it 16:27:12 I think that there is substantive disagreement on append proposal 16:27:41 John: David Singer suggested use of the workd tracking data, so John may adjust proposal to incorporate tracking data in data append section 16:27:47 +1 16:27:54 0 to rejoin does not work; conference is full 16:28:03 aleecia, *0 16:28:04 Peter: anyone who would want to work with John to work on append language, please hit +1 16:28:04 John, we should also encourage first parties to submit themselves under 3rd party restrictions voluntarily 16:28:09 Yes, I suggested that if we call the spec "Do not track", and we define "track(ing)" we should connect the dots and say that what you don't do is 'track' (as defined) (in general, modulo consent and permitted uses) 16:28:12 agree with amy that there is substantial disagreement 16:28:14 Thank you 16:28:28 Peter: I understand that there is disagreement with proposal 16:28:40 Susan: language that agrees with them or has a response to proposal 16:28:49 +Aleecia 16:28:57 +1 16:29:01 Peter: on this one, I am asking for +1 language for people who would like to work with John on language 16:29:09 +q 16:29:10 ...I am guessing people who oppose will oppose the whole package 16:29:11 ack thomas 16:29:15 q? 16:29:30 THomas: if there are people that wish to work on counter proposal, something else that responds to the same issue 16:29:45 ...want to work on counter proposal, then click -1 16:29:55 ...could be as simple as no change or a paragraph of text 16:29:58 zakim, mute me 16:29:59 Thomas should now be muted 16:30:00 clarifying question?? 16:30:07 correct 16:30:11 Zakim, mute me 16:30:11 Aleecia should now be muted 16:30:14 Peter: Thomas, right now the base text is the June draft and does not contain language 16:30:20 ...that is there unless we accept a change 16:30:25 ack thomas 16:30:29 ...leaving June Draft in place is not a counter proposal 16:30:35 +q 16:30:38 Q? 16:30:42 ...counter proposal would be to address the issue in a different way 16:30:53 ...staying silent would keep June Draft in place 16:31:07 When you say "unless we accept a change," does that mean the TPWG, or does that mean leadership? 16:31:09 Thomas: a no change proposal does not require thought to complete 16:31:21 That is, who is "we"? 16:31:23 ...as we look at proposals, we may be in a situation that everyone agrees on a change proposal 16:31:32 ...June draft was bad and we all agree on that 16:31:41 ...that is called consensus 16:31:58 ...it would be useful to explicitly say that we prefer no change to the June Draft 16:32:11 ...if no change is on the proposal, you do not need to say anything 16:32:24 ...if there is no change proposal, then we stick to June draft 16:32:33 I think the June Draft shouldn't have special weight as against an alternative proposal. 16:32:43 ? 16:32:45 [no-change proposal] 16:32:46 *sorry to have been dense about the +1/-1. I felt like it wasn't consistent. didn't mean to create a distraction. 16:32:47 q? 16:32:48 ...if there is one change proposal, and they want to stick to June draft, please write a statement keep June Draft 16:32:52 jmayer, doesn't work. 16:33:00 ...if anyone gets confused, we will be able to fix 16:33:07 ...this is a point that is best explained in writing 16:33:37 ...for purposes of this call, focus on people who want to help people with a change proposal because they are on the same page or come up with a compromise, or people with a counter proposal 16:33:44 In taking up the June Draft, we used a default decision making process (i.e. no consensus alternative, so go to a default). That posed substantial legitimacy problems, and at minimum, certainly didn't reflect a group decision. 16:33:47 zakim, mute me 16:33:47 Thomas should now be muted 16:33:53 Peter: as chair, I will simplify this process. 16:34:05 Peter: +1 means you will help with change proposal 16:34:10 npdoty has joined #dnt 16:34:12 correct 16:34:13 +q 16:34:14 ...if you want to keep June Draft you do not have to say anything 16:34:19 -1 16:34:20 ack thomas 16:34:23 ...if you have a counter proposal, please do -1 16:34:28 zakim, mute me 16:34:28 Thomas should now be muted 16:34:33 ack johnsimpson 16:34:34 Thomas: consistent with what I said 16:34:46 John: we are talking about adding text that does not exist in the draft 16:35:10 as good as it gets, assessment is on chairs 16:35:28 ...what happens that we get to the point that we think this text is as good as it gets, but we have debate in the group how do we deal with 16:35:54 Peter: goal is to work through the list, second goal is to get people to draft text 16:36:08 OK 16:36:12 ...we are not having the conversation on how this comes together at the end of July, we need to get through the list of issues first 16:36:23 ...Issue 6, Roy had a proposal on service providers 16:36:42 This seems to me entirely backwards. We've just done a fire drill... without thinking through how it would bring us closer to consensus. 16:37:12 ...went back to previous discussion on service providers, parties other than first party owner that would have access to data who would not be considered another party 16:37:22 ...want to change from service provider to implementation provider 16:37:33 ...does not make a normative difference, that is editorial 16:37:34 on process, here's Nick's previous write-up of the process we will follow: http://www.w3.org/mid/4199CC86-BA3F-40BB-8C12-676ED0061320@w3.org 16:37:39 "paint on the bike shed" 16:37:40 ...the definition is changed 16:37:49 Peter: both substantive and label change 16:37:50 the bikeshed/name is a detail we could debate but does not make a substantive difference 16:38:09 Dan: I basically haven't been tracking the service provider issue as closely as others 16:38:25 ...wanted to make sure some previous text was not dropped on the floor because no one presented objections 16:38:39 ...we have two different proposals, if they both got support we would need to fit them together 16:38:56 16:38:58 Peter: if you would want to work with Roy, please hit +1 16:39:09 -1 16:39:10 +1 as we had 5 times already agreement on this service provider /implmentation partner issue 16:39:18 ...a -1, if you have a counter proposal to what Roy is doing, different substantive direction 16:39:19 +1 to rigo 16:39:21 -1 16:39:34 +1 for Dan's draft 16:39:38 paulohm has joined #dnt 16:39:42 ...Second, Dan brought language from Mozilla/EFF/Standord proposal, +1 would be to work with Dan to perfect 16:39:43 -1 16:39:51 Riffs and I've objected every bloody time, and for you to claim this is agreement is as frustrating as possible. 16:40:00 +1 16:40:01 ... a -1 would be to work on a counter proposal that is different from Dan's proposal and different from June Draft 16:40:05 where is Dan's proposal? 16:40:08 I think we have two +1 polls going on 16:40:08 ChrisPedigoOPA has joined #dnt 16:40:13 Peter: next thing is third party compliance, Amy had some text on 16:40:40 laurengelman has joined #dnt 16:40:42 helping roy: rigo; helping dan: jmayer, ninja, maybe moneill2 16:40:44 I haven't read Roy's service provider email yet so can't comment -- apologies 16:40:45 Amy: For both sections, signal to implementers, regarding the use of identifiers 16:40:58 npdoty, aleecia too? 16:41:04 ...add technically feasible, using no identifiers at scale 16:41:25 ...discussion about requiring third party auditors, I thought that it was about being internally verifiable 16:41:32 Peter: two distinct issues 16:41:45 ...first, adding technically feasible when it comes to not using unique identifiers 16:41:55 on service providers, helping roy: rigo; helping dan: jmayer, ninja, maybe moneill2, Aleecia 16:42:03 -! 16:42:06 ...if you want to perfect that language +1, a -1 would be a counter proposal 16:42:10 (unless moneill2 or Aleecia intended to work on a third proposal on service provider) 16:42:22 -1 16:42:26 ...second, on audits, internally verifiable rather than third party audits 16:42:40 ...please hit +1 if you want to work on internally verifiable language 16:42:43 -1, -1 16:42:43 -1 16:42:48 +1 16:42:49 ...hit -1 for any counter proposals 16:43:00 -1 16:43:03 No doty, I suspect I will, but if I can merge with Dan's so much the better. Not optimistic about that, but I'm happy to try 16:43:13 Peter: David Singer first on definition of tracking 16:43:25 Auto correct for the lose today, sorry 16:43:31 David: Did I make change proposal to the current document 16:43:43 ...Different agenda item on collection and retain 16:44:01 Peter: Roy you had language on tracking 16:44:20 http://www.w3.org/mid/0494E7A6-01BD-4A4A-8A80-C7BBEBEFB884@gbiv.com 16:44:21 Roy: yet another iteration to find a definition of tracking that fits the requirements 16:44:34 ...it would be nice to agree on what we are agreeing to standardize 16:45:00 Roy: the existing language describes tracking as data collection, it covers anything you might receive 16:45:02 friendly amendments to amyc: dwainberg, counter-proposals to amyc on audits: jmayer, dan_auerbach, moneill2 16:45:09 I'm ready to scribe 16:45:18 -1 to this one 16:45:21 We are talking about "Tracking is the retention or use, after a network interaction is complete, of data records that are, or can be, associated with a specific user, user agent, or device.", right? 16:45:23 ...my definitino is about following a specific persons accross distinct contexts 16:45:45 ...the retention, use, or sharing of data used outside the current context, covers profile building or anything like it 16:45:47 to Roy: that's nothing like all the data you might log. 16:45:47 yes to dsinger 16:45:49 because it doubles the first party/third party distinction 16:45:51 Thomas_Schauf_ has joined #dnt 16:46:01 Peter: DAA definition uses accross multiple sites 16:46:12 npdoty, i was referring to "technical feasilbility" 16:46:17 ...getting clarification about how multiple contexts and multiple sites is probably useful 16:46:32 Amy: notice same issues as Roy 16:46:38 Yes, JC you can take over 16:46:42 scribenick: JC 16:47:07 amyc: suggested a change to the Scope piece, rather than a broad view of tracking, focus on third parties 16:47:13 Amy's change proposal: http://www.w3.org/mid/81152EDFE766CB4692EA39AECD2AA5B61EB0AC4C@TK5EX14MBXC295.redmond.corp.microsoft.com 16:47:45 (is the call line full? my call will not go through) 16:47:49 that we allow first parties to 'track' doesn't mean its definition is wrong, by the way. 16:47:55 lauren, please call the bridge and dial *0. 16:48:00 (instead of entering the code) 16:48:00 -BerinSzoka 16:48:00 Peter: I think calling it tracking data may be editorial 16:48:03 operator will patch you in 16:48:14 ... it may be worth commented on by peoplej 16:48:21 +1 16:48:24 +1 16:48:27 ty! 16:48:28 +1 16:48:30 ... +1 if the term tracking data should be used 16:48:30 - +49.211.600.4.aavv 16:48:40 …and yes, I did have a CP to use 'tracking' in the document more 16:48:45 -1 16:48:47 I am neutral on using the term "tracking data", but the substance of what that term entails is important to me, so not sure if I am neutral or -1 16:48:48 -1 16:48:53 +1 16:48:53 ... -1 is stating that it is moving in the wrong substantive direction 16:49:03 ... Johnsimpson you have an imput 16:49:17 work with amy on changing data to tracking data: dsinger, justin, ChrisPedigoOPA; counter: johnsimpson 16:49:22 simpson's proposal: http://www.w3.org/mid/9755A9FB-5EFD-4B5A-B4B7-630125EB9B57@consumerwatchdog.org 16:49:30 Johnsimpson: As the standard develops some tracking will be allowed under permitted uses 16:49:40 work with amy on changing data to tracking data: Brooks, dsinger, justin, ChrisPedigoOPA; counter: johnsimpson, jchester 16:49:41 ... some servers won't participate in permitted uses 16:49:55 +1 16:49:59 ... there should be some compliance language that indicates how this works 16:50:11 ISSUE-119? 16:50:11 ISSUE-119 -- Specify "absolutely not tracking" -- pending review 16:50:11 http://www.w3.org/2011/tracking-protection/track/issues/119 16:50:15 ... compliance language should clarify what is said in TPI 16:50:18 TPI 16:50:21 TPE 16:50:27 s/TPI/TPE/ 16:50:37 q? 16:51:03 Peter: Add +1 if you want to work with johnsimpson 16:51:07 +1 (I think we already have agreed text, and may not need more) 16:51:09 +1 16:51:12 ... -1 if you have conflicting proposal 16:51:25 ack jmayer 16:51:28 phone trouble 16:51:28 Peter: jmayer could you address tracking definition 16:51:34 workng on fixing mute thingy 16:51:48 ... we will go to jmayer later 16:52:08 + 1 to work with Amy on her definition of Tracking 16:52:23 Jmayer: I propose a change indicating collection in the defintion 16:52:52 Peter: Jmayer lets go to defintion of protocol and transient data 16:52:59 working with john simpson on "not tracking": npdoty, ninjamarnau 16:53:05 Jmayer: I 'm concerned by transient data definition 16:53:07 -1 to jmayer's http://www.w3.org/mid/BC9995A702CF4B5BA0594DB9129D7C14@gmail.com 16:53:14 mayer's proposal on "tracking": http://www.w3.org/mid/BC9995A702CF4B5BA0594DB9129D7C14@gmail.com 16:53:28 ... the line I try to draw is between protocol information and info the website solicits 16:53:28 mayer's proposal on "transient": http://www.w3.org/mid/66CEC8712A44493FAB861745B971E520@gmail.com 16:53:56 ... they may have different privacy requirement vs. saying everything goes during a transcient period 16:54:09 Yes 16:54:11 s/transcient/transient/ 16:54:18 *transcient/s/transient 16:54:22 Peter: I have not lived through these discussions 16:54:23 (has been discussed) 16:54:25 -Joanne 16:54:30 q+ 16:54:47 Peter: Lee wrote something similar, any comments? 16:54:52 I also wrote something http://www.w3.org/mid/D55D460B-6E05-4AE7-86FB-2CE29CF7F4DE@apple.com 16:54:57 jmayer, that sounds like Lee's proposal on short-term 16:54:59 -npdoty 16:55:04 Roy: I haven't looked through Lee's proposals 16:55:15 q- 16:55:16 that was Dan 16:55:21 +1 16:55:22 Peter: +1 for work on protocol and trnasient data definitions 16:55:23 s/Roy: /Dan: / 16:55:26 +1 16:55:33 -1 16:55:33 *jc, i think that was dan auerbach not roy speaking 16:55:34 ... -1 for a counter proposal 16:55:35 rvaneijk has joined #dnt 16:55:43 This is a poll on substantive views, or on willingness to work on language? 16:55:50 willingness to work on language 16:55:55 -1 (cookie are obviously protocol data, so use a different name if you want to make that distinction) 16:56:03 Peter: jmayer do you have a definition of collection 16:56:09 -rvaneijk 16:56:12 Jmayer: I believe i sent one to the list 16:56:29 Peter: Amyc do you have language around collection and share? 16:56:38 i think this is a poll re: willingness to work on language consistent with vs. opposed to a given proposal 16:56:44 Amy's language on collect / retain / share: http://www.w3.org/mid/81152EDFE766CB4692EA39AECD2AA5B61344A1C9@TK5EX14MBXC295.redmond.corp.microsoft.com 16:56:51 Amyc: I submitted language on share to address concerns that current language is quite broad 16:57:09 ... I proposed language that more directly addresses concerns 16:57:18 Pedigo on "share": http://www.w3.org/mid/CEED5B1AC4405240B53E0330753999D320643B3A@mbx023-e1-nj-4.exch023.domain.local 16:57:24 +rvaneijk 16:57:30 ... other is editorial. Pass is used but not defined. We should fix that. 16:57:36 rvaneijk_ has joined #dnt 16:57:40 happy to work with Amy to merge our proposals 16:57:43 Peter: I have not looked at issue, but it makes since 16:57:51 s/since/sense/ 16:58:12 Amyc: Concern is about first party being held responsible for data sharing 16:58:14 zakim, call nick-mobile 16:58:14 I am sorry, tlr; I do not know a number for nick-mobile 16:58:18 zakim, call npdoty-mobile 16:58:18 I am sorry, tlr; I do not know a number for npdoty-mobile 16:58:20 zakim, call npdoty 16:58:20 I am sorry, tlr; I do not know a number for npdoty 16:58:26 Amyc: this is not about appending but sharing 16:58:40 Peter: The term share is broader than some may like 16:58:52 my language on collect/retain: http://www.w3.org/mid/9CEF4EC1-C051-4AE4-B986-8F107C103217@apple.com 16:58:54 q+ 16:59:04 Peter: Dsinger do you have language on sharing 16:59:06 I have a clarification question 16:59:33 Dsinger: The first talks about transient which is not defined. What does it have to do with sharing? 16:59:57 retaining == collection IMHO 17:00:06 I have a lot of background noise here, but the notes I sent from walking through the doc included a text suggestion from JC on this area 17:00:07 ... We should look at retain and not focus on transient period 17:00:09 q? 17:00:25 +1 17:00:26 Peter: Dsinger is this similar to Amy? 17:00:29 +1 17:00:30 +1 17:00:43 ... +1 work with Amy et. al. on proposal 17:00:51 ... -1 for a counter proposal 17:01:01 possible +1, need to read more carefully 17:01:11 Peter: Number 11 defintion of user agent from Chris Pedigo 17:01:20 Zakim, wseltzer has npdoty 17:01:20 sorry, npdoty, I do not recognize a party named 'wseltzer' 17:01:22 if we prefer no change, we don't write -1 right ? I think that's where I am 17:01:29 Pedigo on user agent: http://www.w3.org/mid/CEED5B1AC4405240B53E0330753999D320643B97@mbx023-e1-nj-4.exch023.domain.local 17:01:30 jchester2 has joined #dnt 17:01:41 dan, -1 = would contribute to a proposal in a different direction. 17:01:42 dan, if you prefer no change, you can just say that later -- not much of a point putting it out now 17:01:59 ah, we need to improve the section title and do some editorial cleanup 17:02:01 I'm -1 on this direction for sharing. 17:02:05 ChrisPedigo: The defintion meshes what a UA must be included and there are three statemtents that don't make since 17:02:15 ... I would like to add a separate section for websites 17:02:27 Peter: Were there others that made UA defintions? 17:02:37 My apologies to all, I have to drop off, so won't be able to walk through the CP to section 7 on existing privacy controls, but tried to include explanation as part of CP, please feel free to contact me directly with qs 17:02:39 ... UA compliance is next 17:02:51 -[Microsoft] 17:03:00 Chapell: my proposal was contained in industry proposal so look there 17:03:12 ... the idea is similar to what I have mentioned for a while 17:03:16 ack thomas 17:03:30 ... the UA must indicate clearly what it states 17:03:39 Chapell, is that a change from the editors' draft? 17:03:45 Tlr: I'm confused on what is stated 17:03:49 + +49.173.259.bbcc 17:03:52 this document? http://www.w3.org/mid/DCCF036E573F0142BD90964789F720E3140E17A7@GQ1-MB01-02.y.corp.yahoo.com 17:04:02 Dan: I was mentioning disclosure requirements 17:04:26 Tlr: can you help me find it? 17:04:28 rvaneijk has joined #dnt 17:04:58 Peter: Let's figure out how to work with text that came in before noon 17:05:00 alan's language is supposedly in here: http://www.w3.org/mid/170A573B-41D3-4645-B4A0-5226B14E9AE3@networkadvertising.org 17:05:07 ... Justin you have input 17:05:41 Justin: If the user uses private mode it is obvious the user does not want to be tracked 17:05:51 is there any marking in the PDF that notes what the edits are? 17:06:02 ... clear and prominent language can be controversial, but we need to be consistent 17:06:13 -rvaneijk 17:06:22 ... the June draft is prescriptive on UA side but not the user side 17:06:27 +1 to Nick -- a version that has changes tracked would be very useful. 17:06:34 ... I suggest what we have had in the TPE for a while 17:06:42 +1 to Justin; we previously agreed to rough parity 17:06:43 +rvaneijk 17:06:52 [pdf link: http://lists.w3.org/Archives/Public/public-tracking/2013Jun/att-0405/June26_Tracking_Compliance_and_Scope_Change_Submission.pdf ] 17:06:57 Peter: Amy you have input on privacy controls 17:07:05 Amyc is there 17:07:28 I think the UA side and the UGE must be the same, as they both claim to collect consent 17:07:42 q? 17:07:47 q- 17:08:12 Chapell, could you summarize the changes for us on UA Compliance that are represented in this PDF? (I can't see offhand what is different from the editors' draft) 17:08:13 Amy's proposal on existing privacy controls: http://www.w3.org/mid/81152EDFE766CB4692EA39AECD2AA5B61EB0AC76@TK5EX14MBXC295.redmond.corp.microsoft.com 17:08:58 JC: concern, how do we reconcile opt-out and DNT; multiple devices, user-granted exceptions depend on timing 17:09:12 ... how do we provide something that's not confusing users or providers 17:09:15 npdoty, will do on list later 17:09:18 ... slight changes to the tables 17:09:33 Peter: jamayer you have input 17:09:35 Jonathan on user agent: http://www.w3.org/mid/4E18BDC5E23E4992A1C66CEEA9430E89@gmail.com 17:09:50 Jmayer: Yes, I provided language on the standard language to use 17:10:05 dsinger and justin - i agree re: parity on disclosure standards for UA and UGE 17:10:10 Peter: on user agent compliance there are three things 17:10:26 ... +1 to work with Chapell and advertisers approach 17:10:28 ... however, the language in the current draft was unclear, IMHO 17:10:43 +2 17:10:44 ... +2 if you want to work with Justin on TPE direction 17:10:53 +2 17:10:57 + 17:11:01 +2 17:11:02 +2 17:11:05 +2 17:11:12 -jay_jin 17:11:16 ... +3 if you want to work with Amy and JC on tables to reconcile DNT vs. other standards 17:11:18 +4 17:11:22 +4 (sort of) I proposed my own language 17:11:32 .... +4 to work with Jonathan 17:11:37 +2 17:11:54 ... Let's go to security and fraud 17:11:56 work with Justin on TPE direction for UA compliance: johnsimpson ninjamarnau dsinger Aleecia jmayer 17:12:26 npdoty, +2 add me to the list 17:12:27 ack thomas 17:12:30 ... can someone explain Chris M proposal? 17:12:40 work with Justin on TPE direction for UA compliance: johnsimpson ninjamarnau dsinger Aleecia jmayer sidstamm 17:12:49 Tlr: can someone point to the draft? 17:12:54 http://www.w3.org/wiki/Privacy/TPWG/Change_Proposal_Security 17:12:57 zakim, mute me 17:12:57 Thomas should now be muted 17:12:59 Johnsimpson: It should be on the Wiki 17:13:19 Peter: I think there was substantial writing on the list John can you exaplain your approach 17:13:45 Johnsimpson: I looked at thread and liked proposal, but was concerned about the lack of graduated response 17:13:56 I suggested text on security and fraud too, along with all permitted uses 17:13:59 ... I wanted to make sure it got it, supporting Roy's input 17:14:13 Note - as discussed in Sunnyvale, a graduated response is not a workable solution and would lead to notfifying attackers that you suspect them. 17:14:17 Peter: I haven't reviewed this, was there language Roy? 17:14:29 jmayer_ has joined #dnt 17:14:32 Johnsimpson: it was the original language 17:14:51 Roy: There are changes to June draft and addtion of graduated response 17:14:55 dan_auerbach, Lee had proposed text from the earlier EFF proposal, that also referenced a concept of graduated response, do you think those could be combined? 17:14:58 There's been language on graduated response for over a year. 17:15:06 Peter: one subissue is around graduated response, is there new language 17:15:24 Johnsimpson: that original language came from April public draft 17:15:27 I believe the original definition of graduated response came from Ian Fette, several months ago 17:15:32 npdoty, yes, we can work on combining those 17:15:34 ... I believe Ian submitted it 17:15:42 ... it all mad sense to me 17:15:57 Peter: There is a proposal from Chris on this 17:16:08 ... +1 to work with Chris on this 17:16:26 ... +2 to work on graduated response with Roy or Ian's language as base 17:16:28 +2 17:16:29 -Rigo 17:16:40 -1 (remove graduated response) 17:16:42 http://lists.w3.org/Archives/Public/public-tracking/2013Jun/0129.html 17:16:44 +2 17:16:50 ... beyond that the issues are explained well in language 17:16:58 +2 17:17:02 ... -2 is you are against graduated response 17:17:04 +BillScannell.a 17:17:05 -2 17:17:06 - +1.650.787.bbaa 17:17:06 +2 17:17:12 -2 17:17:19 Still confused if these polls are asking for volunteers for drafting, or asking for positions on issues. 17:17:20 dan_auerbach_ has joined #dnt 17:17:21 -2 17:17:26 -1 17:17:27 +2 17:17:34 Peter: Jonathat you have other issues to raise? 17:17:42 I agree with Ed, the process is still confusing. 17:17:48 Jmayer: Yes, text around partial compliance 17:17:53 Ed Felten: I agree. I have no idea what we are doing. 17:18:05 work with John/Roy: dan_auerbach jmayer jchester2 dsinger; counter: WileyS JC hefferjr 17:18:12 ... if a website once to honor do not track it must say so 17:18:17 zakim, who is making noise? 17:18:22 Audio is going in and out on Jonathan - could everyone other than Jonathan hit mute? 17:18:27 dsinger, listening for 10 seconds I heard sound from the following: +49.173.259.bbcc (14%), johnsimpson (9%) 17:18:36 ... [breaking up for me] 17:18:37 when in doubt, it is always volunteering 17:18:44 efelten, the polls are intended to volunteer working on drafting (friendly amendments or counter proposals), not support 17:18:46 partial compliance: http://www.w3.org/mid/B8AD71B8D9BB415B82AFB6749AE945CD@gmail.com 17:18:48 Zakim, mute bbcc 17:18:48 +49.173.259.bbcc should now be muted 17:18:52 ... discussion around personalization, collecting user's browsing history 17:19:01 Confusion is because they're phrased as calls for positions. "If you're opposed …" 17:19:08 ... I would be in favor of getting rid of personalization 17:19:16 Mayer on personalization: http://www.w3.org/mid/CFFE63269F3147C1A8F3FF7F069F9FFF@gmail.com 17:19:21 Nick--But in essence, agreeing to help write is expressing support. Which is what's happening in my view. 17:19:22 Marc has joined #dnt 17:19:22 +1 to Jonathan on this one 17:19:35 Mayer on unknowing collection: http://www.w3.org/mid/012674A466274F50BAD76DBCF7AE6BB9@gmail.com 17:19:49 Ari has joined #dnt 17:20:00 ... there was an attempt to clarify June text to indicate when a website is in violation or what to do when determined in violation 17:20:05 jchester2, yes, but there might be lots of things you support that you aren't going to help write, since, for example, we all have limited time 17:20:06 + +1.202.835.bbdd 17:20:11 jchester, there's a piece of support / opposition implied in whether you're volunteering to help with a proposal or write a counterproposal 17:20:13 ... it could post it to website, but must tell someone 17:20:21 - +1.212.844.aapp 17:20:28 That's Marc 17:20:29 Peter: +1 if you want to work with Jonathan on any of the issues 17:20:35 ... clarify area with +1 17:20:35 TLR--yes. 17:20:39 +1 to remove Personalization language 17:20:39 212 835 - marc 17:20:40 Zakim, bbdd is Marc 17:20:40 +Marc; got it 17:20:43 ... Aleecia is next 17:20:48 Zakim, I mute me 17:20:48 I don't understand 'I mute me', Aleecia 17:20:49 but -- the point really is to organize the work 17:20:50 ack Aleecia 17:21:19 Aleecia: I felt that there were a number of issues that were dropped and were not in consensus. 17:21:28 -BillScannell? 17:21:36 ... the June draft is a wonderful addtion, but should not be a replacement 17:22:01 ... the June draft is very readable, but there are a number of issues that have been dropped on the florr. 17:22:08 I think this is very important, coming from the former co-chair. 17:22:09 ... I have heard that from others 17:22:17 Peter: which draft 17:22:27 Aleecia: date is in email and I don't remember 17:22:47 Peter: We are at 122 and we need to extend our time 17:22:56 the last public working draft of the Compliance doc is April 30th: http://www.w3.org/TR/2013/WD-tracking-compliance-20130430/ 17:23:05 apologies, I have to drop off 17:23:11 ... for audience measurement is cathy there? 17:23:20 -Dan_Auerbach 17:23:21 (Aleecia's email includes the pointer to the latest draft, which currently redirects to April 30th) 17:23:27 Could someone send his name 17:23:31 ESOMAR proposal: http://www.w3.org/mid/CDEA2BDE.24D56%25kathy@esomar.org 17:24:12 Name: what we have done is tightened up on the defintion of the data which is held and that profiles cannot be created or used for other purposes 17:24:39 ... we want to limit this purpose as far as we can to prevent AM data from being used for anything but AM 17:24:52 To be very, very clear: the coincidence that I once was a co-chair is not relevant. I am just a simple villager. That said, I think my point still stands. 17:25:03 Peter: To clarify changes, this data is used to callibrate, validate panel data 17:25:06 Thanks, nick 17:25:19 ... why was validate or calcualte through added 17:25:49 Name: Essentially you start with a panel of people and use count to reflect what is happening in the real world, callibration 17:26:00 s/Name:/Adam_Phillips:/g 17:26:16 ... you need to have some idea of who is in panel to know who has seen content 17:26:31 Adam_Phillips, calling in from ESOMAR, Kathy Joe is off 17:26:34 -[FTC] 17:26:44 ... so if 50% out of 1000 have seen content then there are 500 without knowing who they are 17:26:46 simpler just have dnt:0 for the panel 17:27:08 This needs further review. Because it appears new data sets are implicated 17:27:17 ... we are coming up with a set of numbers that in the end will not be based on the actual numbers in panel but projected on the group 17:27:22 Adam and Richard: would it be accurate to say that what is intended is that you extrapolate from the panel and apply the insights to the general data? 17:27:30 Why are consent and de-identified data not sufficient here? 17:27:33 Peter: how small can the number in the categories be? 17:27:57 Susan, you are correct 17:27:57 moneill2, I think the proposed permitted use is about collecting data from non-panel members 17:28:06 Adam_Phillips: Let suppose you have a group of people who live in the Chicago area that are female and shop at Neiman Marcus 17:28:14 moneill2, in order to calibrate a panel with a larger statistical sample 17:28:19 ... maybe 5% of people saw the ad. 17:28:39 yes I know, thats why I dont agreethis should be a permitted use 17:28:39 ... we don't know who they are. we would have to go on the street to ask people. 17:28:43 But you create personnas that in essence is the same. 17:28:43 If you can't link the data to an individual, then your data in unsinkable / de-identified. 17:28:52 s/unsinkable/unlinkable/ 17:28:57 ack rigo 17:28:59 ... there should not be a concern to single out individuals unless that have agreed so 17:29:00 ack thomas 17:29:08 Peter: Rigo do you have input? 17:29:27 Adam_Phillips: We have not had time to connec with Rigo 17:29:45 q+ 17:29:48 Tlr: the buckets used in this contact should be larger than 800, based on Rigo's email 17:29:58 ... small addtion to Cathy's note 17:30:08 +q 17:30:14 http://www.w3.org/mid/1455409.O2aSxzv7j6@hegel.sophia.w3.org 17:30:15 unmute me 17:30:24 zakim, unmute me 17:30:24 jchester2 should no longer be muted 17:30:29 Adam_Phillips: I don't see what that limit does. Even if there were only 800 people you still wouldn't know who they are 17:30:36 Zakim, mute me 17:30:36 schunter? should now be muted 17:30:49 Tlr: Rigo is willing to work with you to refine the text. You two should chat about this 17:31:04 q? 17:31:04 zakim, mute me 17:31:05 Thomas should now be muted 17:31:14 Adam_Philllips: I am happy to talk to talk to Rigo, but want to maintain our position 17:31:26 New scribe? 17:31:32 I was supposed to help facilitate discussion so I can do that. 17:31:40 +1 17:31:50 Peter: +1 to work with to work with Cathy 17:32:04 not a permitted use 17:32:11 should not be a permitted use 17:32:11 ... those against this as permitted use will be heard 17:32:12 let people express if they don't want to see a permitted use 17:32:16 zakim, mute me 17:32:16 jchester2 should now be muted 17:32:18 ... Rigo has concerns 17:32:25 john, jeff -- the place to express that will be a "no change" proposal 17:32:44 Yep, can take over here 17:32:55 ack thomas 17:33:01 Rob V. 17:33:02 don't want to see a permitted use 17:33:04 Thomas Schauf 17:33:12 zakim, mute me 17:33:12 Thomas should now be muted 17:33:14 q- 17:33:16 And then text from industry groups 17:33:19 +1 for working with ESOMAR on friendly amendments; -1 on different approach to audience measurement permitted use 17:33:20 working with ESOMAR on friendly amendments: susanisrael; different approach to audience measurement permitted use: rigo 17:33:24 Peter Swire: Language from Dan Aurbach, Roy, Rob V, Shane next. 17:33:25 Scribe: hwest 17:33:26 q? 17:33:28 scribenick: hwest 17:33:40 Next... 17:33:43 cannot hear 17:33:48 Peter Swire: We lost Dan, I realize we went over scheduled time 17:34:02 - +1.650.365.aauu 17:34:03 ack thomas 17:34:13 ... Summarizing, had language similar to two stage language that we had previously, added in non-norm text. 17:34:16 -RichardWeaver 17:34:19 -q 17:34:32 zakim, mute me 17:34:32 Thomas should now be muted 17:34:32 ... Rob, can you update? 17:35:23 robv: When do you consider data to be de-ident? What is missing is the actual answers, in my view, you include knowledge of the hashing. Because if de-ident is the end state and outside of DNT, need [lost this part] 17:35:50 ... Should include that data quality is no longer linkable. Stage approach. Tried to identify some arguments that a three-stage approach makes more sense. 17:36:02 hard to understand the speaker 17:36:09 people who don't want a permitted use on audience measurement: johnsimpson moneill2 jchester2? ninjamarnau -- we should talk offline about whether your preferences are represented in an alternate proposal or whether we need a "silence" proposal, etc. 17:36:14 .... Shane and I seem to share some views on that. Three state would allow for discussion on those states. 17:36:14 I believe this to be Rob's proposal: http://lists.w3.org/Archives/Public/public-tracking/2013Jun/0279.html 17:36:15 s/understand/hear/ 17:36:21 -rvaneijk 17:36:21 my de-id emails: http://www.w3.org/mid/BDDA1E11-4D69-4489-ADEF-2499273BCD20@apple.com and http://www.w3.org/mid/BDA5C0E8-8F7B-45D9-B8E5-D4D5FB3C6865@apple.com 17:36:29 lost phone conn 17:36:29 Peter: From before, language from David Singer and [who] 17:36:47 Auerbach's language: http://www.w3.org/mid/51C7E6CF.10806@eff.org 17:36:51 dsinger: Felt that the definition lacked strength in "reasonable level of justified confidence", but I think it was verbal in Sunnyvale 17:37:00 David - I like the current language - what more are you looking for here? 17:37:09 .... hold data not to identiify user or device, etc 17:37:17 +rvaneijk 17:37:41 another version of de-identified was posted after the deadline: http://www.w3.org/mid/EF36F5EBBFF0634BBAA37CF2B2DB2A42687A3A3B@BVDWDC1.dmmv.local 17:37:45 ... If de-ident, then should be in a state that we're no longer worried about. Propose the second statement. 17:37:59 3 States: raw -> deidentified but linkable -> deidentified and unlinkable 17:38:08 Roy: Proposal to define deident in terms of the data and the process of deident, tried to make it as short as possible. 17:38:13 I also agree with Roy: the definition should be results-based, not process-based 17:38:14 -??P74 17:38:21 Only in the final state is data finally out of scope 17:38:24 Peter: Some folks have argued for process. Why better to do it with state of the data? 17:38:43 -[Mozilla] 17:38:56 Roy: The way the term is used in the draft is talking about the state of data. Doesn't make sense to define as a process when the goal is to reach a certain state. 17:39:16 both the current text and Dan A's proposal included the "reasonable level of justified confidence" -- does anyone from EFF want to argue for the existing level of reasonableness? 17:39:31 I am somewhat concerned that my (early) CP on raw data (it should be a permitted use) seems to have dropped away? http://www.w3.org/mid/AF17E9C5-E7C4-442A-B796-80B073F41C0C@apple.com 17:39:54 BTW, I would also be fine with removing the definition and simply replacing its use with specific text applicable to that section. 17:39:57 Shane: We can go through a PDF sent out earlier, five slides, to help guide people through the conversation and giv context on this approach. Rob and I reached consensus on terms. 17:40:11 dsinger, ooops. 17:40:12 ... Add a few definitions and tie specific Permitted Uses to specific data states 17:40:15 ... Can run folks through that. 17:40:26 Peter: Is the doc in IRC? 17:40:41 http://lists.w3.org/Archives/Public/public-tracking/2013Jun/att-0406/W3C_DeID_Presentation_20130625.pdf 17:40:47 http://lists.w3.org/Archives/Public/public-tracking/2013Jun/0406.html 17:40:52 didn't hit list. 17:40:56 Shane: I sent it to the mailing list, it at 9:04am PT, Subjec tis W3C De-ID presentation 17:41:15 it did, just buried in another thread instead of properly subject 17:41:20 ack thomas 17:41:30 ... Rob and I submitted text to the public mailing list earlier in the week, then industry draft came through and supports some of this language, can be harmonized. 17:41:43 ... This is to give more context and explain the thought process here. 17:42:05 Shane: To give illustration. 17:42:20 Peter: Do you have a proposal that this would be non-norm example that would somehow show what the three stage means? 17:42:26 the concepts are the same, we need further discussion on permitted uses, and whether to use the word de-identified 17:42:32 ... we can reduce this to language. 17:42:37 ack thomas 17:42:44 The prepared presentation does not appear to discuss the proposed standards text. 17:42:58 Shane: This is one possible implementation within the construct. Helps folks understand the concepts. 17:43:15 We need to discuss the slides 17:43:37 tlr: Fundamental concept discussed in Sunnyvale, suggest that we focus on the things that are new since Sunnyvale and on very concrete proposals for tri-state environment. Also, can you explain how this relates to the text proposal? 17:43:46 s/it did, just/Shane's presentation pdf made it to the list, but/ 17:44:04 zakim, mute me 17:44:04 Thomas should now be muted 17:44:09 Peter: Go ahead to the PUs and the tri-state. 17:44:11 This seems like a major change of direction; even the definitions are very different. For example, 'Tracking' seems similar to the 'do not cross-site track' that I derived from Roy's suggestion, and that was firmly rejected by the group. 17:44:15 17:44:18 Would like to hear an explanation of the proposed text. 17:44:42 dsinger, no it was not firmly rejected by the group 17:44:57 Shane: So PUs in the tri-state. This is the conceptual framework of why you have three, WG has struggled with certain PUs. Holding in the raw state causes discomfort. This creates an additional state that is more protective than raw. 17:45:01 http://lists.w3.org/Archives/Public/public-tracking/2013Jun/0278.html 17:45:01 … it has never even been discussed by the group 17:45:02 [slide 5 of 7, on permitted uses in the tri-state] 17:45:16 ... So a middle state. In the raw/psuedonymous data, there would only be three and a half PUs allowed. 17:45:36 ... Raw data, where an operational ID is necessary. Reality is we need operational ID for some things. 17:46:11 ... Today's operational reality needs security/fraud, frequency capping, [which?], and some financial and audit - only where required for the last one. 17:46:49 ... Goal here within raw is shorter retention timeframes where possible, these PUs are there, but shouldn't be there for very long. I'm against arbitrary time frame, so comparatively to other states, should be shorter. 17:46:54 -rvaneijk 17:46:56 +rvaneijk 17:46:59 - +49.173.259.bbcc 17:47:30 ... New middle state. Between raw and unlinked. Individual has been deident internally, but still linkable across device but not linkable to device in the real world. One approach is a hash and administrative controls. 17:47:50 .... Should not be able to use it for production in any way, should not alter user experience. 17:47:51 This concept of "not altering experience" is not in the proposed text. 17:47:51 I understand the slides to be suggesting that DNT:1 should allow interest-based advertising based on browsing activity, but only after the browsing activity has been aggregated enough that it doesn't identify the visited sites 17:48:07 robsherman has joined #dnt 17:48:08 to fielding: I proposed a change to 'do not cross-site track', and what that meant, and at best, the group decided not to follow that direction, and stay with the 1st/3rd/do-not-track model 17:48:10 ... Gets us to the rest of financial audits, and PUs like product improvement and market research. 17:48:35 ... You're not done, you're still within the scope of DNT. ONly once you unlink the data do you move out of the scope of DNT. Many different ways to do that. 17:48:58 Shane: If state 2, are you saying that the info in any way cannot be used to subsequently target the user of someone who shares the qualities of the user? 17:49:00 ... Data should be able to be shared without risk of reident in the data set. 17:49:13 jchester2, yes, that's the goal 17:49:18 Jeff - yes 17:49:35 Thanks. Thats a goal--but also a requirement? 17:49:39 Peter: I encourage folks to read the slides. Are there other provisions in the recent doc to highlight? 17:49:46 jchester2, yes. 17:49:58 Shane: Delinked/deidentified, and added language around PUs being pushed into using only deid data where possible. 17:50:12 q+ 17:50:15 +q 17:50:15 We need to discuss the product improvement paradigm in the mid-state 17:50:17 ... I think those were the core edits to this proposal around deident as a midstate. 17:50:38 jchester2, but data can still be stored in a potentially reversible form, though operational controls are supposed to prevent that. It's designed to allow longitudinal reearch to be used in aggregate. 17:50:46 Shane: There are other changes throughout, redline to help group see the changes. 17:51:06 Jeff, product improvement doesn't seem to appear elsewhere in the document, so that seems like an inconsistency. 17:51:17 Peter: We've tried to highlight change proposals today. Are there other change proposals that we have not addressed? 17:51:20 yes, mine on raw data 17:51:26 q+ dsinger 17:51:32 ack dsinger 17:51:33 i.e., there isn't a product improvement permitted use in the document. 17:51:33 ack dsinger 17:51:35 seem to be inconsistencies between slides and the new industry document! 17:51:53 http://www.w3.org/mid/AF17E9C5-E7C4-442A-B796-80B073F41C0C@apple.com 17:52:04 dsinger: The June draft, retaining raw data should be a PU for the purpose of working it into data that you can retain for some reason. 17:52:04 http://www.w3.org/mid/AF17E9C5-E7C4-442A-B796-80B073F41C0C@apple.com 17:52:13 Peter: Missed that one. 17:52:15 Slide 6 is very important, given the growing use of invisible scoring on users. this requires a full discussion. 17:52:32 dsinger: Raw data is tracking data, certainly. By putting in a PU, constrained for retention and use. 17:52:36 I proposed a change to Section 1 - scope 17:52:46 +! 17:52:48 +1 17:52:48 q+ brooks 17:52:52 Peter: +1 means you want to work with DavidSinger on this 17:53:03 ... -1 means a different approach is better for this kind of raw data 17:53:21 Brooks Dobbs: http://www.w3.org/mid/CDF08782.DD37E%25brooks.dobbs@kbmg.com 17:53:25 ... Any other change proposals? 17:53:26 +q 17:53:53 work with dsinger on raw: justin; counter: 17:53:53 Brooks: Changed scope, first sentence currently is not consistent with what we actually do in the document. 17:53:54 ack brooks 17:54:00 moneil is next 17:54:29 But OOBC . . . 17:54:37 ... [reads existing language] - not consistent with the spec. We've gone out of our way in the UA requirements to not have UGEs or DNT0 be a compulsory requirement. Either change requrements or chang ethe scope. 17:54:52 +1 17:54:56 + +1.312.923.bbee 17:55:01 +1 17:55:03 +1 17:55:04 bbee mecallahan 17:55:07 +1 17:55:09 ack moneil 17:55:10 Peter: +1 to work with Brooks on this change of scope language, -1 if substantively different approach 17:55:16 +1 17:55:18 q+ 17:55:19 q? 17:55:28 zakim, bbee is mecallahan 17:55:28 +mecallahan; got it 17:55:29 dsinger, what you recall is the rejection of a specific proposal that limited first-party tracking as well as third-party tracking … the definition I provided last night is significantly different 17:55:57 moneill2: Two proposals, compliance spec changes on Thursday, some of the changes have been covered by others. Main thing is the deident issue, put in some persistent identifier. Maybe not unique, maybe just unique enough. 17:56:06 ... Tied to the idea that there's a duration on how long the identifier lasts 17:56:16 I believe Mike is talking about this one: http://www.w3.org/mid/009801ce6dfc$163e4950$42badbf0$@baycloud.com 17:56:21 ... Yellow tate for different PUs, different durations. 17:56:28 work with brooks on change of scope: Chapell, marc, dwainberg, dsinger, robsherman 17:56:43 Peter: Overlaps with rvaneijk and others? 17:56:47 moneill2: Yes, some overlap. 17:57:03 Peter and W3C Staff: Many people are out next week on vacation - is there a call next week? 17:57:06 -rachel_n_thomas 17:57:12 http://lists.w3.org/Archives/Public/public-tracking/2013Jun/0283.html 17:57:15 ... I will have a discussion, OOBC non-norm description of consent with cookies. Link from TPC to mention it. 17:57:33 Peter: We have three minutes. Will switch to talking about next steps. 17:57:50 Re: my proposal for User Agent compliance. we did not get to that 17:57:54 Could I ask a clarifying question about Shane's proposal? 17:58:09 ... so I would refer the WG to the discussion between myself and Alex Fowler on the list 17:58:17 ... Lots of folks who have volunteered to work on language. Wiki will stay updated (thanks Nick!) and can help you find each other and work with each other. Over next day, will get info out on that. 17:58:21 - +1.215.480.aagg 17:58:44 Jonathan - feel free to ask on the public list. I'm dropping in 2 mins so probably won't be able to reply here. 17:58:52 ... Also working on schedule for consideration on the merits of proposals. Need to get that out to you in the next day or so. Action will happen on the lists, since we're running out of calls. Will be clear about proposals. 17:58:54 .... I'm hopeful that it won't be controversial for reasons I've laid out on the list 17:59:02 We need a seperate discussion on Shane's proposal, inc on permitted uses. This deserves a session. 17:59:06 jmayer, I think we're running out of time, can you ask on the mailing list? 17:59:11 Peter and W3C Staff: Many people are out next week on vacation - is there a call next week? 17:59:27 Might there be extra calls? 17:59:31 shane, you will need to drup the aggregated scoring :) ! 17:59:38 s/drup/drop/ 17:59:39 .... Will use dates and if necessary go to a chairs' decision. There will continue to be a process, spend more time on most important issues, but will discuss all of them. 17:59:47 To follow up on Shane's comment, many many people are out next week. 17:59:51 -[CDT] 17:59:52 ack thomas 17:59:56 Rob - disagree - as that is de-linked from history so should be permitted. 17:59:57 -mecallahan 17:59:58 ... It's 2pm, I'm sure we could have lots of comments. Thank you for your hard work, will be working hard on our end. 17:59:58 -paul_glist? 17:59:58 - +1.646.827.aayy 18:00:00 -rvaneijk 18:00:00 -peterswire 18:00:01 -[Microsoft.a] 18:00:02 - +1.202.331.bbbb 18:00:03 whew! 18:00:03 -efelten 18:00:03 -hefferjr 18:00:03 -Thomas 18:00:04 -Aleecia 18:00:04 -dstark 18:00:04 -jackhobaugh 18:00:04 -vinay 18:00:04 -Chris_Pedigo 18:00:05 -chapell 18:00:07 -[Apple] 18:00:11 peterswire has left #dnt 18:00:12 -jchester2 18:00:12 Adjourned! 18:00:13 -JeffWilson 18:00:13 -WileyS 18:00:15 -robsherman 18:00:15 -eberkower 18:00:16 -ninjamarnau 18:00:17 -BillScannell.a 18:00:17 -susanisrael 18:00:18 - +1.408.836.aall 18:00:19 -Fielding 18:00:20 -Brooks 18:00:21 - +1.323.253.aakk 18:00:27 -hwest 18:00:31 -johnsimpson 18:00:32 -paulohm 18:00:32 -Marc 18:00:34 -yianni 18:00:36 -moneill2 18:00:38 -Jonathan_Mayer 18:00:39 -schunter? 18:00:47 johnsimpson has left #dnt 18:00:47 -Wendy 18:00:48 T&S_Track(dnt)12:00PM has ended 18:00:48 Attendees were +1.609.258.aaaa, Thomas, RichardWeaver, efelten, +1.646.654.aabb, npdoty, eberkower, +1.202.973.aacc, +1.202.478.aadd, Brooks, rachel_n_thomas, +1.202.587.aaee, 18:00:48 ... yianni, +49.431.98.aaff, +1.215.480.aagg, ninjamarnau, +1.202.326.aahh, +1.917.934.aaii, paulohm, +1.202.331.aajj, +1.323.253.aakk, paul_glist?, [Microsoft], hefferjr, 18:00:49 ... +1.408.836.aall, jchester2, WileyS, JeffWilson, +31.65.141.aamm, rvaneijk, vinay, dsinger, hwest, +1.650.391.aann, +1.202.629.aaoo, robsherman, +1.212.844.aapp, susanisrael, 18:00:49 ... johnsimpson, [CDT], Joanne, schunter?, +1.301.365.aaqq, +1.347.272.aarr, [FTC], +1.647.274.aass, Chris_Pedigo, +1.202.347.aatt, +1.650.365.aauu, peterswire, +49.211.600.4.aavv, 18:00:54 ... jackhobaugh, +1.646.666.aaww, +1.202.787.aaxx, chapell, jay_jin, Dan_Auerbach, dstark, +1.646.827.aayy, BerinSzoka, Fielding, Jonathan_Mayer, moneill2, BillScannell, Aleecia, 18:00:54 ... sidstamm, +1.650.595.aazz, Rigo, BillScannell?, +1.650.787.bbaa, +1.202.331.bbbb, +49.173.259.bbcc, +1.202.835.bbdd, Marc, +1.312.923.bbee, mecallahan 18:06:10 rrsagent, please draft minutes 18:06:10 I have made the request to generate http://www.w3.org/2013/06/26-dnt-minutes.html fielding 18:09:18 rrsagent, bye 18:09:18 I see no action items