15:42:17 RRSAgent has joined #dnt 15:42:17 logging to http://www.w3.org/2013/07/03-dnt-irc 15:42:19 RRSAgent, make logs world 15:42:19 Zakim has joined #dnt 15:42:21 Zakim, this will be 15:42:22 Meeting: Tracking Protection Working Group Teleconference 15:42:22 Date: 03 July 2013 15:42:22 I don't understand 'this will be', trackbot 15:42:27 Zakim, this will be 87225 15:42:27 ok, npdoty; I see T&S_Track(dnt)12:00PM scheduled to start in 18 minutes 15:42:39 chair: peterswire 15:50:01 efelten has joined #dnt 15:51:30 peterswire has joined #dnt 15:53:06 rvaneijk has joined #dnt 15:53:07 T&S_Track(dnt)12:00PM has now started 15:53:12 dwainberg has joined #dnt 15:53:16 + +49.172.147.aaaa 15:55:24 jackhobaugh has joined #dnt 15:55:30 WaltMichel has joined #DNT 15:56:11 + +31.65.141.aabb 15:56:12 +npdoty 15:56:16 + +1.215.480.aacc 15:56:18 Zakim, aabb is me 15:56:18 +rvaneijk; got it 15:56:27 + +1.202.347.aadd 15:56:45 215 is WaltMichel 15:56:45 eberkower has joined #dnt 15:56:51 Zakim, aacc is WaltMichel 15:56:51 +WaltMichel; got it 15:56:56 Zakim, aadd is jackhobaugh 15:56:56 + +1.202.262.aaee 15:56:56 +jackhobaugh; got it 15:57:25 PaulGlist has joined #dnt 15:57:25 zakim, call thomas-781 15:57:26 ok, tlr; the call is being made 15:57:26 +Thomas 15:57:36 +Wendy 15:57:44 dsinger has joined #dnt 15:57:59 zakim, I am thomas 15:57:59 ok, tlr, I now associate you with Thomas 15:58:05 zakim, mute me 15:58:05 Thomas should now be muted 15:58:09 zakim, mute dsinger 15:58:09 sorry, tlr, I do not know which phone connection belongs to dsinger 15:58:11 jchester2 has joined #dnt 15:58:15 - +49.172.147.aaaa 15:58:19 Ari has joined #dnt 15:58:25 + +972.8.979.aaff 15:58:38 schunter has joined #dnt 15:58:39 +jchester2 15:58:41 zakim, mute me 15:58:41 jchester2 should now be muted 15:58:43 + +1.609.258.aagg 15:58:43 + +1.202.478.aahh 15:58:45 BillScannell has joined #dnt 15:58:46 Zakim, aaff is omertene 15:58:46 + +49.172.147.aaii 15:58:46 +omertene; got it 15:58:50 Zakim, aagg is me 15:58:51 +efelten; got it 15:58:51 +dwainberg 15:58:53 - +1.202.478.aahh 15:58:54 + +1.646.654.aajj 15:58:57 Zakim, aaee is PaulGlist 15:58:57 rachel_n_thomas has joined #dnt 15:58:57 +PaulGlist; got it 15:59:00 Zakim, aajj is eberkower 15:59:00 +eberkower; got it 15:59:26 + +1.323.253.aakk 15:59:38 zakim, aaii is schunter 15:59:38 +schunter; got it 15:59:46 + +1.813.732.aall 15:59:49 Zakim, who is on the phone? 15:59:49 On the phone I see rvaneijk, npdoty, WaltMichel, jackhobaugh, PaulGlist, Thomas (muted), Wendy, omertene, jchester2 (muted), efelten, schunter, dwainberg, eberkower, 15:59:52 ... +1.323.253.aakk, +1.813.732.aall 16:00:02 + +1.202.257.aamm 16:00:06 + +1.202.478.aann 16:00:06 mecallahan has joined #DNT 16:00:21 zakim, aann is rachel_n_thomas 16:00:21 +rachel_n_thomas; got it 16:00:25 + +1.202.697.aaoo 16:00:35 Yianni has joined #DNT 16:00:47 +Aleecia 16:00:59 + +1.303.746.aapp 16:01:01 moneill2 has joined #dnt 16:01:03 ninjamarnau has joined #dnt 16:01:04 + +1.202.587.aaqq 16:01:12 +[Microsoft] 16:01:13 adrianba has joined #dnt 16:01:14 Zakim, aapp is paulohm 16:01:14 +paulohm; got it 16:01:26 +[Apple] 16:01:29 + +1.301.365.aarr 16:01:33 zakim, [apple] has dsinger 16:01:33 +dsinger; got it 16:01:35 +BerinSzoka 16:01:43 + +44.186.558.aass 16:01:45 Zakim, aarr is Yianni 16:01:45 +Yianni; got it 16:01:47 zakim, [IPCaller] is me 16:01:47 sorry, moneill2, I do not recognize a party named '[IPCaller]' 16:01:49 sidstamm has joined #dnt 16:01:50 +[Mozilla] 16:01:55 +Keith_Scarborough 16:01:59 Zakim, Mozilla has sidstamm 16:02:00 +sidstamm; got it 16:02:06 justin has joined #dnt 16:02:08 +Brooks 16:02:10 amyc has joined #dnt 16:02:12 -schunter 16:02:15 Zakim, who is on the phone? 16:02:15 On the phone I see rvaneijk, npdoty, WaltMichel, jackhobaugh, PaulGlist, Thomas (muted), Wendy, omertene, jchester2 (muted), efelten, dwainberg, eberkower, +1.323.253.aakk, 16:02:18 ... +1.813.732.aall, +1.202.257.aamm, rachel_n_thomas, +1.202.697.aaoo, Aleecia, paulohm, +1.202.587.aaqq, [Microsoft], [Apple], Yianni, BerinSzoka, +44.186.558.aass, [Mozilla], 16:02:18 ... Keith_Scarborough, Brooks 16:02:18 [Mozilla] has sidstamm 16:02:18 [Apple] has dsinger 16:02:21 + +1.202.603.aatt 16:02:23 - +44.186.558.aass 16:02:29 + +1.646.278.aauu 16:02:37 +[Microsoft.a] 16:02:40 zakim, [Microsoft.a] is me 16:02:40 zakim aamm is mecallahan 16:02:41 Brooks has joined #dnt 16:02:43 +adrianba; got it 16:02:44 Marc_ has joined #dnt 16:02:49 +[CDT] 16:02:52 zakim, aaqq is Yianni 16:02:52 +Yianni; got it 16:02:55 schunter has joined #dnt 16:02:55 johnsimpson has joined #dnt 16:03:03 Chapell has joined #DNT 16:03:03 Richard_comScore has joined #dnt 16:03:04 +Rigo 16:03:04 Zakim, aaoo is Peter_4As 16:03:05 +Peter_4As; got it 16:03:10 zakim, mute me 16:03:11 + +49.431.98.aavv 16:03:11 Rigo should now be muted 16:03:11 + +44.186.558.aaww 16:03:13 zakim, aamm is mecallahan 16:03:13 +mecallahan; got it 16:03:15 +schunter 16:03:16 zakim, mute me 16:03:16 adrianba should now be muted 16:03:18 zakim. [IPCaller] is me 16:03:23 Keith has joined #dnt 16:03:24 scribenick: justin 16:03:27 zakim, aavv is probably ninja 16:03:27 +ninja?; got it 16:03:29 + +1.571.213.aaxx 16:03:30 jmayer has joined #dnt 16:03:34 +RichardWeaver 16:03:35 zakim, aavv is ninjamarnau 16:03:36 sorry, ninjamarnau, I do not recognize a party named 'aavv' 16:03:41 zakim, [IPCaller] is me 16:03:41 sorry, moneill2, I do not recognize a party named '[IPCaller]' 16:03:42 zakim, ninja is really ninjamarnau 16:03:42 +ninjamarnau; got it 16:03:43 zakim, aavv is Ninja 16:03:43 sorry, rigo, I do not recognize a party named 'aavv' 16:04:00 zakim, aatt is probably Suzanne 16:04:00 +Suzanne?; got it 16:04:02 -Peter_4As 16:04:04 +johnsimpson 16:04:21 + +1.650.365.aayy 16:04:33 zakim, who is on the phone? 16:04:33 On the phone I see rvaneijk, npdoty, WaltMichel, jackhobaugh, PaulGlist, Thomas (muted), Wendy, omertene, jchester2 (muted), efelten, dwainberg, eberkower, +1.323.253.aakk, 16:04:36 ... +1.813.732.aall, mecallahan, rachel_n_thomas, Aleecia, paulohm, Yianni.a, [Microsoft], [Apple], Yianni, BerinSzoka, [Mozilla], Keith_Scarborough, Brooks, Suzanne?, 16:04:36 ... +1.646.278.aauu, adrianba (muted), [CDT], Rigo (muted), +44.186.558.aaww, ninjamarnau, schunter, +1.571.213.aaxx, RichardWeaver, johnsimpson, +1.650.365.aayy 16:04:36 [Mozilla] has sidstamm 16:04:36 [Apple] has dsinger 16:04:40 +Chris_Pedigo 16:04:44 JC has joined #DNT 16:04:45 zakim aauu is chapell 16:04:51 David_MacMillan has joined #dnt 16:04:52 Zakim, aauu is Chapell 16:04:55 +Chapell; got it 16:04:59 peterswire: How the call will go --- lots of people have vacay 16:05:00 Yianni has joined #DNT 16:05:17 ... This call will help identify and talk through issues, but opportunity to revisit on next call. 16:05:23 +Peter_4As 16:05:23 ChrisPedigoOPA has joined #dnt 16:05:26 +Jonathan_Mayer 16:05:28 ... Two key deadlines in my emails this week. 16:05:38 +[Microsoft.a] 16:05:38 +q 16:05:40 ... Noon next Tuesday: perfecting amendments to DAA approach. 16:05:56 + +1.202.787.aazz 16:05:59 +Peder_Magee 16:05:59 zakim, aaww is me 16:05:59 +moneill2; got it 16:06:19 I am getting a sense of whiplash. Are we working off the old compliance document, the June draft, or the DAA? Does the DAA even have a redline, let alone reasons for change, offered? 16:06:27 pm2023263538 has joined #dnt 16:06:31 Say this again. When is the deadline for comments to the DAA draft. Are you saying one week only, to review everything and resubmit? 16:06:33 Zakim, aazz is BillScannell 16:06:33 +BillScannell; got it 16:06:41 ... A week from Friday, [interference] is deadline for opinions on which should be base text: June draft or DAA? 16:06:49 aleecia has joined #dnt 16:06:49 ... Likely a chair's opinion on that by end of July. 16:06:54 +q 16:06:54 + +49.211.600.4.bbaa 16:06:54 q+ 16:07:02 I would like to ask a clarifying question about procedure, please. 16:07:15 ... Today's call --- let the DAA present their package. 16:07:21 TS has joined #dnt 16:07:23 I don't want the DAA to talk about it, I want them to write it down 16:07:40 ... DAA sees all these amendments as linked together, so they should be considered together. 16:07:51 zakim, bbaa is probably TS 16:07:51 +TS?; got it 16:07:54 I agree with David. We need to discuss this now, Peter. You are rushing througn a process here. 16:07:59 I would like the DAA to explain the rationale for their de-identification approach, in writing, as a start. 16:08:01 Zakim, who is making noise? 16:08:13 ... Want input from rvaneijk and [someone else] on unique identifiers, de-ID, Yianni's language on branded first party in third-party context. 16:08:13 npdoty, listening for 10 seconds I heard sound from the following: Yianni (42%) 16:08:34 q? 16:08:36 Zakim, Yianni has peterswire 16:08:36 +peterswire; got it 16:08:40 zakim, who is on the phone? 16:08:40 On the phone I see rvaneijk, npdoty, WaltMichel, jackhobaugh, PaulGlist, Thomas (muted), Wendy, omertene, jchester2 (muted), efelten, dwainberg, eberkower, +1.323.253.aakk, 16:08:44 ... +1.813.732.aall, mecallahan, rachel_n_thomas, Aleecia, paulohm, Yianni.a, [Microsoft], [Apple], Yianni, BerinSzoka, [Mozilla], Keith_Scarborough, Brooks, Suzanne?, Chapell, 16:08:44 ... adrianba (muted), [CDT], Rigo (muted), moneill2, ninjamarnau, schunter, +1.571.213.aaxx, RichardWeaver, johnsimpson, +1.650.365.aayy, Chris_Pedigo, Peter_4As, Jonathan_Mayer, 16:08:44 ... [Microsoft.a], BillScannell, Peder_Magee, TS? 16:08:45 [Mozilla] has sidstamm 16:08:45 Yianni has peterswire 16:08:48 [Apple] has dsinger 16:08:53 Zakim, who is making noise 16:08:53 I don't understand 'who is making noise', npdoty 16:08:54 Can someone tell Peter there are people on the que. 16:08:54 Zakim, who is making noise? 16:09:04 zaneis: I'm happy to walk through industry proposal. 16:09:05 npdoty, listening for 10 seconds I heard sound from the following: +1.571.213.aaxx (9%), Yianni (97%) 16:09:21 peterswire: maybe skip de-id as that's been discussed before. 16:09:22 Peter, when is the appropriate time to clarify the procedure you just walked us through? 16:09:27 schunter has joined #dnt 16:09:35 We have not discussed the DAA's de-id proposal before. 16:09:39 -Jonathan_Mayer 16:09:53 q? 16:09:54 i expect to return to procedure before the end of the call 16:09:58 I hope that the FTC and the EU are noting the lack of good process here, esp for the NGOs. 16:10:01 fpf has joined #dnt 16:10:03 Zakim, who is making noise? 16:10:05 +Jonathan_Mayer 16:10:11 Who participated in writing this draft? 16:10:14 kj has joined #dnt 16:10:16 npdoty, listening for 10 seconds I heard sound from the following: schunter (31%) 16:10:18 zaneis: We only had a week to pull this together. 16:10:21 Thanks, Peter. 16:10:24 +Craig_Spiezle 16:10:35 who participated in writing the draft, please? 16:10:38 ... Take a look at what W3C is trying to achieve --- reach consensus on implementable standard. 16:10:45 schunter has joined #dnt 16:10:53 ... Keys are "consensus" and "implementable" 16:10:54 do we have (a) a redline or (b) explanation of what was changed, the degree (major, minor, editorial) and the rationale? 16:11:00 For the record, I object to the following three things: (1) our starting points are either what the co-chair wrote, or what DAA has in mind, rather than our group consensus starting point. (2) We have no text from DAA; slides are not a substitute. (3) We are not even allowed to discuss these issues. 16:11:13 Zakim, who is making noise? 16:11:24 npdoty, listening for 10 seconds I heard sound from the following: schunter (9%), Yianni.a (4%) 16:11:33 A copy of the DAA proposal with changes highlighted is here: 16:11:33 http://lists.w3.org/Archives/Public/public-tracking/2013Jun/att-0466/NAI-DAA-DMA_June_26_draft_compared_to_June_22_Tracking_Compliance_and_Scope_copy.pdf 16:11:36 zaneis: trying to figure out what we can get 100s of companies to agree to. 16:11:39 redline: http://lists.w3.org/Archives/Public/public-tracking/2013Jun/att-0466/NAI-DAA-DMA_June_26_draft_compared_to_June_22_Tracking_Compliance_and_Scope_copy.pdf 16:11:49 cOlsen has joined #dnt 16:11:54 zakim, mute me 16:11:54 schunter should now be muted 16:11:58 ... Sorry that we didn't follow exact protocol --- want to explain why we did what we did with more specificity. 16:12:01 This is disrespectful to the group and to our time. 16:12:07 Who is "We"? 16:12:08 I concurr with Aleecia. 16:12:11 CraigSpiezle-OTA has joined #dnt 16:12:22 +[FTC] 16:12:24 I concurr with Aleecia. 16:12:33 ... Wanted it to be simple. And wanted to show how this effort would intersect with broader industry self-reg. 16:12:36 I am shocked that W3C is allowing this to happen without objection, when it violates every process we have had in place. 16:13:00 I'll say it again: no justification has been offered for the DAA's de-identification *language*. 16:13:07 ... Shane had done a lot of technical work on how deidentification might work in this space. 16:13:14 Zakim, who is making noise? 16:13:16 vincent has joined #dnt 16:13:18 I feel I have spent the last two weeks working down one road, and now we're on a different one. How much are we supposed to tolerate this?\ 16:13:19 ... [interference] 16:13:25 npdoty, listening for 10 seconds I heard sound from the following: +1.571.213.aaxx (68%), Yianni (33%) 16:13:29 It is not at all clear to me how Shane's slides relate the DAA document. 16:13:30 I have no faith that time I put into working on DNT is anything but a waste 16:13:42 Zakim, aaxx may be mike_zaneis 16:13:43 +mike_zaneis?; got it 16:13:54 I agree with David Singer 16:13:56 ... When we say down to draft, we know there had been two approaches: (1) focusing on the DNT signal, and the user interface, what is appropriate response, etc. 16:14:12 ... reality is that environment has changed since this group was created. 16:14:23 I have no faith that members of the TPWG are actually participating in this process. Rather, it appears to be a set of back-room discussions then brought forward for the fiction that the group is involved. 16:14:39 ... We had thought this was all about DNT signals being sent by *browsers* --- now marketplace has progressed, we're seeing up to 20% of DNT flags for all internet users. 16:15:04 schunter has joined #dnt 16:15:16 While I am entirely frustrated with meta conversations about process, let me document: this is not a process that leads to consensus decisions from members of the group. 16:15:26 ... My members seeing 20-25% of user base sending flag. Early on, our position had been: perhaps the W3C could standardize the DNT signal, and we would treat that as an industry opt-out. 16:15:32 ... That is no longer tenable. 16:15:44 ... We expect DNT:1 signals to approach 50% in short-term. 16:15:47 you have 25 percent DNT flags because people do not want to be tracked. 16:15:49 + +33.6.50.34.bbbb 16:16:01 ... No longer want to try to distinguish between what DNT:1 signals are legitimate and which are not. 16:16:04 I also agree with David. We worked *very* hard to quickly compile issue-by-issue proposals and rationales, as the chairs requested. The stakeholders who declined to follow that constructive and substantive process are being rewarded with extra time and focus. 16:16:06 zakim, bbbb is me 16:16:06 +vincent; got it 16:16:32 ... Now, within industry, we've decided to take a different approach, and focus on deidentification. Hope that could be a way to make consensus. 16:17:09 ... Yes, we had fought tooth and nail on the default and UI issue, and we're now willing to take those off the table in the name of progress. Now the question is what level of deidentification is appropriate and implementable. We want to have that discussion. 16:17:34 I don't see a reason to see a reason than other change proposal to june draft. Broken down issue by issue with justification and discussion. I am completely opposed to use the DAA proposal as a basis to find consensus. 16:17:49 ... The industry approach trying to get a meaningful DNT standard. And then the DAA would pick up the W3C standard and require its members to publicly assert compliance thereto. 16:17:56 ... BBB would then enforce against our member companies. 16:17:58 + +1.202.587.bbcc 16:18:14 This not only does harm to the idea we might reach a group decision on Do Not Track, for the first time I seriously question the legitimacy of W3C as an organization to perform multi-stakeholder work. 16:18:23 ... We thought that only by putting all that stuff together, that was the only want to present this to the group. 16:18:27 Who is "we" the Mike keeps referring to. Who drafted the DAA document?????????? 16:18:42 ... And that could lead to implementation in the ecosystem and enforceability. 16:18:46 Can we please talk about the content of the proposal? 16:19:07 This is a filibuster. 16:19:10 yes 16:19:26 ... Would like to see this group work on permitted uses, to limit the permitted uses in the DAA code. Like market research --- we're willing to try to adopt that language and be informed by that, 16:19:30 s/,/. 16:19:32 -Suzanne? 16:19:34 The Better Business Bureau is a member of the DAA--not really an effective body on privacy: http://www.bbb.org/us/interest-based-advertising/ 16:19:55 zaneis: This is not a Grand Bargain. This is a way to get consensus [?] 16:20:25 ... We've gotten criticism that this doesn't advance privacy. We disagree --- the enhancements to de-ID, etc. are a way to get real progress for consumers. 16:20:41 peterswire: Let's skip to clarifying question. Thanks for background. 16:20:43 These all sound like lovely goals for DAA to work on internally, and I support those goals. But this is not a W3C DNT spec. 16:21:01 s/question/questions 16:21:03 I thought the DAA proposal still kept the same UA requirements, on when to send the flag at all 16:21:07 peterswire: Who is the "we" here? 16:21:39 zaneis: It's a broad industry submission. Specifically, presented by DAA,IAB, NAI, DMA, and the DAA trade associations representign the whole supply change: ad nets, publishers, agencies, &c. 16:21:41 I think I missed which TPWG members were involved. 16:21:49 Seeing as that's the group we're in. 16:21:51 I'd also like to get back to substance. Perhaps we could start with the questions that Thomas so helpfully compiled? http://lists.w3.org/Archives/Public/public-tracking/2013Jul/0005.html 16:21:52 ... They all support this in principle. 16:21:56 Can we please have specific names? 16:22:00 ... Comcast, Yahoo! and a few others put their names to it. 16:22:06 ack thomas 16:22:09 Are any of them members of the working group? 16:22:12 q+ 16:22:15 Were there ANY other TPWG members involved? 16:22:25 -q 16:22:30 peterswire: Let's get back to normative text --- thomas could you help us with the questions you put out to the list? 16:22:30 -moneill2 16:22:31 Mike identified DAA, DMA, IAB, Yahoo, and Comcast as supporters of the proposal. 16:22:47 But not a single person. 16:22:54 Also NAI. 16:22:56 I have no idea if Yahoo means Shane, or not 16:22:59 &c 16:23:01 thomas: I heard you speak about the broad consistuency --- you mentioned DAA, IAB, and DMA? 16:23:04 q- 16:23:12 Jules_Polonetsky has joined #DNT 16:23:14 zaneis: Yes, certainly them and others, along with some companies. 16:23:29 thomas: Can the companies say that for the record? 16:23:47 We need the companies? 16:23:49 zakim 202/587 is Jules Polonetsky 16:23:56 thomas: I sent a set of questions on July 1 that did not draw an answer. Here are the questions, the first from efelten: 16:24:15 thomas: What is the difference between deidentified and delinked, and where does delinked ever get used in the document? 16:24:17 Zakim, bbcc is Jules_Polonetsky 16:24:17 +Jules_Polonetsky; got it 16:24:30 zaneis: Shane has walked though a lot of these use cases, and last week on a group call. 16:24:55 ... One example is the Red/Yellow/Green proposal. And I think there is flexibility here. 16:24:56 Nobody has offered a justification for the proposed *language*. 16:24:56 Shane showed a bunch of slides. There is no clear way that the slides relate to the prosed text. 16:25:00 ... [interference] 16:25:36 zakim, mute me 16:25:36 Thomas should now be muted 16:25:41 -q 16:25:44 thomas: Agreed, there are a lot of names for all those states. The real question is what in the proposal is different between de-id'd and delinked. 16:25:57 you document doesn't to that 16:26:21 zaneis: We presented a deidentification *principle* and then identified examples of what would work. But meant to allow a fair amount of flexibility of how to get to that principle. 16:26:24 +q 16:26:43 ack thomas 16:26:54 ... Think of the deidenification language as the normative, and think of Shane's examples as non-normative. 16:27:02 peterswire: Is delinked every used in the document? 16:27:18 Shane's PowerPoint doesn't answer this question. 16:27:30 +MikeO 16:27:34 zaneis: There are different use cases. I don't have Shane's PPT in front of me, and I'm not qualified to get into the operational issues. Everyone's on vacay! 16:27:40 Not even clear what requires de-identified data.. 16:27:46 zakim, mute me 16:27:46 sorry, moneill2, I do not know which phone connection belongs to you 16:27:48 I'd like to understand the deidentification principle. We can get to the technical implementation after. 16:28:11 it's used "after there are no remaining permitted uses ... data must be de-identified and de-linked" 16:28:12 zakim, MikeO is me 16:28:12 +moneill2; got it 16:28:16 thomas: I looked at this specific point --- I tried to find where delinked used. In the permitted uses, you have delinked show up once. Just on retention. Seemed inconsistent with other parts of the doc. 16:28:23 zakim, mute me 16:28:23 moneill2 should now be muted 16:28:40 ... Two q's: (1) What is difference between two states, and (2) Where are de-ID and delinked used? 16:28:50 rachel_n_thomas: This is very clearly laid out in the document 16:29:11 ... This discussion is best had with the technical adops folks are available. 16:29:13 q? 16:29:19 If it's clear in the definition text, then somebody should be able explain it to us. 16:29:53 peterswire: More questions. In the June draft, there was language that there should be no unique IDs is reasonably available [not to use?]. 16:29:58 ... why not leave in spec? 16:30:41 basically DAA says "no" 16:30:49 zaneis: We don't know what's "reasonably available." Cookies have been the building block for a long time. We don't have a sense of what people want or mean, so we couldn't commit to a theoretical mechanism. We don't understand what's being asked of us. 16:31:02 can someone tell me what the legal threshold of 'reasonable' means? Is this commercially reasonable efforts? best efforts? 16:31:04 Privacy is what is being asked. 16:31:26 ... Rather than focus on certain technologies, we wanted to have a broad definition of tracking. Shouldn't matter if it's cookie based or statistical identification. 16:31:33 tracking is unique ids 16:31:56 peterswire: What about permissibility of retargeting? 16:32:16 ... Under the DAA code, is that allowed --- for site B to use behavior from site A? 16:32:20 zakim, mute me 16:32:20 Thomas should now be muted 16:32:32 -Chapell 16:32:37 zaneis: Not comparing apples to apples. Difference between DAA program and DNT with 50% opt out. 16:32:41 -Peter_4As 16:32:49 -moneill2 16:32:52 ... That retargeting practice is likely not allowed if DAA opt-out. 16:32:57 +moneill2 16:33:08 zaneis: Generally accepted but not a lot of case law. 16:33:34 On privacy-preserving technologies, researchers have offered to collaborate with DAA member companies for years. The companies have declined. Any lack of understanding is, at this stage, attributable to willful ignorance. 16:33:39 ... But without getting into specificity of Shane's proposal, some of that might be allowed if the data is really deidentified first. 16:33:40 is it possible to single out without being associated to connected to a specific user, computer, device? Text is unclear to me. Text is unclear IMHO. See the letter of Dix who says "erase last segment of the IP address". IMHO non normative text should examplify what all this text means 16:33:48 +Chapell 16:33:57 ... More about a data hygiene practice. DAA program though would still exist. 16:34:10 ... which would probably opt you out of retargeting. 16:34:11 So the DAA text proposal would allow retargeting? 16:34:31 "safe" tracking 16:34:58 + +1.650.595.bbdd 16:34:59 peterswire: So the industry proposal seems more like a data hygiene proposal. So you'd turn on DNT:1 to opt for data hygiene, and then go to DAA to opt out of what you allow opt out of. 16:35:02 zaneis: That's right. 16:35:15 JoAnn_Covington has joined #dnt 16:35:17 that's a useful clarification, as I hadn't understood from the normative language that re-targeting and other profiling was consistent with DNT: 1 in the proposal 16:35:39 tlr, i think i was dropped 16:35:43 rvaneijk: I tried to bring delinking into Shane's proposal, and to explain where we differ in our views. 16:35:48 zakim, who is on the phone? 16:35:48 On the phone I see rvaneijk, npdoty, WaltMichel, jackhobaugh, PaulGlist, Thomas (muted), Wendy, omertene, jchester2 (muted), efelten, dwainberg, eberkower, +1.323.253.aakk, 16:35:52 ... +1.813.732.aall, mecallahan, rachel_n_thomas, Aleecia, paulohm, Yianni.a, [Microsoft], [Apple], Yianni, BerinSzoka, [Mozilla], Keith_Scarborough, Brooks, adrianba (muted), 16:35:52 ... [CDT], Rigo (muted), ninjamarnau, schunter (muted), mike_zaneis?, RichardWeaver, johnsimpson, +1.650.365.aayy, Chris_Pedigo, [Microsoft.a], BillScannell, Peder_Magee, TS?, 16:35:52 ... Jonathan_Mayer, Craig_Spiezle, [FTC], vincent, Jules_Polonetsky, moneill2, Chapell, +1.650.595.bbdd 16:35:56 [Mozilla] has sidstamm 16:35:56 Yianni has peterswire 16:35:56 [Apple] has dsinger 16:36:08 ... We need a good definition of deidentification --- trying to get to the gold standard: FTC's "do not collect" language! 16:36:40 The argument is that DNT will be too pervasive to be able to limit tracking, hence the move to "data hygiene." And maybe that's so. But that means we cannot get to consensus for Do Not Track. That would be extraordinarily unfortunate. 16:36:52 q? 16:36:53 ... I added a friendly correcting amendment that could get closer to that. Deidentification shouldn't just be around third parties down the line like service providers. This is my first proposal geraed at fixing def of de-id. 16:37:11 ... My other proposals have been to fix either the 3 state or 2 state approach. I am agnostic as to which of those we should use. 16:37:20 ... Article 29 is looking at this as well. 16:37:46 ... My proposal for 3 state: Red data is linkable. Yellow data can still be linkable, but let's not call it deidentified. 16:38:04 ... On the two state approach, there's a linkable stage and a deidentified stage. 16:38:31 ... In the deidentified stage, you have to make sure that the data can't be linked back. 16:38:50 -q 16:39:06 ... That's a short summary of the proposals I submitted: (1) fix def of deidentified. Let's not call hashes deidentified. The key needs to be the ability to link. 16:39:10 +??P88 16:39:18 Perhaps there is a need for a different WG on "data hygiene," with a different charter, and likely different group members. It would move faster and better. 16:39:21 laurengelman has joined #dnt 16:39:37 peterswire: Making sure I understand. Sounds like your neutral between 2 and 3 states. Other is that hashing doesn't get you to delinking. 16:39:41 yes! 16:39:42 rvaneijk: Right. 16:39:47 zakim, ??P88 is probably lauren 16:39:47 +lauren?; got it 16:39:50 ty 16:39:58 http://www.w3.org/wiki/Privacy/TPWG/Change_Proposal_Deidentification 16:40:02 lauren, note you can do that yourself 16:40:29 Thomas_Schauf: Want to discuss about hashed identifiers can't be deidentified. If tied just to cookie, it's not tied to a particular user. 16:40:31 yes. was abt too. 16:41:08 ... I like Roy's language that you need "justified confidence" (I tried to make more legalistic) that it can't be tied to a data subject ... 16:41:13 q+ 16:41:21 the cookie is stored in the user's device and can identify them. 16:41:29 public has joined #dnt 16:41:46 ... without additional information without disproportionate time or effort. You can't identify the natural person , though there would be some sort of remaining list of undoing de-ID (government request) ... 16:41:50 Thomas, sorry, but we are not doing legal things here, it is a technical approach for a technical standard...!! 16:41:55 ... but for tracking purposes, not tied to real person. 16:42:32 peterswire: To help us clarify, previously we had had langauge similar to FTC and from Dan Auerbach. 16:42:59 -paulohm 16:43:05 ... Do you see this proposal as similar to FTC/Dan, or could you clarify how it's different? 16:43:47 if the distinction is about connecting to a natural person, does that mean all existing uses of cookies that don't have real names attached are already "de-identified"? 16:44:09 Thomas_Schauf: I haven't looked at that recently, I was just working off of fielding's language. 16:44:30 mecallahan now scribing 16:44:32 scribenick: mecallahan 16:44:34 npdoty, his proposed language says that the data *cannot* be attributed to a data subject. 16:44:47 eberkower_ has joined #dnt 16:44:56 justin: thought FTC /DAA language was sufficiently strong and allowed flexibility to accomplish to be the exisiting standard 16:45:06 q? 16:45:08 q? 16:45:12 .... yellow standard not sufficiently robust 16:45:30 ...under common understanding of tracking, still allow tracking in DNT! which is inappropriate 16:45:32 Which state is "yellow" in the DAA proposal? Is de-identified yellow, or is de-linked yellow? 16:45:34 q? 16:45:34 efelten, well, unless the data to make the connection to a real-name has distinct technical and organizational controls 16:45:47 ACK rvaneijk 16:45:47 ...justin not wedded to DAA language but best alternative so far 16:45:52 q- 16:46:04 peterswire: anything to be added? 16:46:05 q+ 16:46:10 efelten, deidentified is yellow under industry proposal. 16:46:15 ... the queue on deid 16:46:16 Thx 16:46:34 You could at least stop targeting :) 16:46:40 ok, then we are done. 16:46:40 zaneis: same statement as 2 years ago, it is impossilbe to stop tracking consumers [inaudible] 16:46:53 q? 16:46:56 +q 16:46:58 s/consumers [inaudible]/from a consumer perspective/ 16:47:12 ...we keep going down same worm hole, i hope in next 3 weeks, trying to be achievable and have substantive discussions 16:47:13 Well, no, this is important: if we cannot stop tracking users than we cannot have a consensus standard. 16:47:17 Are you saying you won't honor DNT? 16:47:34 ... we narrowed the issues, inc issues we really care about 16:47:38 Rigo should ask Mike to explain, please. 16:47:39 close q 16:47:43 It is important to understand that. And I appreciate the honesty. 16:47:50 q? 16:47:52 Zakim, please close the queue 16:47:52 ok, npdoty, the speaker queue is closed 16:48:05 ack aleecia 16:48:12 peterswire goes to queue re de-id, promises process discussions at end of call 16:48:33 Can Rigo place on the record why he thinks this is so, please. 16:48:40 -q 16:48:45 aleecia: keeping on de-id. if take unique ID and you replace with another randomly generated unique ID, bad for privacy 16:48:46 q? 16:48:57 ...if you change the link, that could be good for privacy 16:49:11 ...only way to be viable is guidelines on how long they can be linked 16:49:20 in addition to ALeecia, WP29 is working on guidance on anonymisation techniques. 16:49:33 ...that is minimum o fwhat Aleecia needs to be useful. otherwise privacy risks are the same. 16:50:14 peter: we are asking for various submissions by this coming tuesday 16:50:15 Thomas--is the translation of what Rigo is saying is let DAA bury themselves 16:50:17 +q 16:50:37 Zakim, please open the queue 16:50:37 ok, npdoty, the speaker queue is open 16:50:38 Peter: You are now discussing process, yet didn't want to discuss process. 16:50:39 q+ jchester2 16:50:42 Zakim, please close the queue 16:50:42 ok, npdoty, the speaker queue is closed 16:50:51 q? 16:50:55 peterswire: w3c asking for subm ission by week from friday. in addition, there is written public record on these issues, chair will be mindful of that dialog/record, will look at record to make sure all issues addressed, not playing gotcha. [foresadow procedure] 16:51:13 zaneis asks to respond. he will go after the q. 16:51:18 Dan´s approach: Data can be considered de-identified if it has been deleted, modified, aggregated, anonymized or otherwise manipulated in order to achieve a reasonable level of justified confidence that the data cannot reasonably be used to infer information about, or otherwise be linked to, a particular user, user agent, or device. Thomas´ approach: Data is considered de-identified when data that has been collected is altered or otherwise processed so that it can 16:51:27 jmayer asks question on de-id: 16:51:29 ack jmayer 16:51:47 -BerinSzoka 16:51:52 cannot be attributed to a data subject without the use of additional data which is subject to separate and distinct technical and organisational controls to ensure such non attribution, or when such attribution would require a disproportionate amount of time, expense and effort. Differences: Dan´s approach force us to define the word anonymize. The reasonable level of justified confidence is in my view pretty weak. The “German” idea is quite stronger as the link to 16:51:59 a data subject (user as a natural person) is prohibited per definition. And my proposal also reflects some remaining risk that such data could be linked and this reflects a debate we had in Cambridge in Feb 2013. 16:52:27 ...trying to understand/reconcile DAA proposal. how do the two pieces mesh? data should be able to reassocaited to user? yellow state we heard does not have those privacy properties. would the yellow states be de-id? 16:52:46 peterswire: shane uses the word deid to apply to yellow state 16:53:20 ...under propsoed langauge is de-id, the normative language, and mike says cd be examples of implementing that cd be shane's appraoch/examples. 16:53:22 when yellow = de-identified, is where we disagree on the definition 16:53:34 mike you're breaking up 16:53:37 If I may, that didn't answer my question. 16:54:08 the question is how much is allowed then under yellow state. If it is treated like "not personal data", then I personally do not find this acceptable 16:54:14 I think Jonathan's question is that the normative text doesn't seem to agree with what Shane has presented about real-time bucketing 16:54:17 jmayer: gets the notion that yellow and deid are supposed to lien up. but how are they supposed to line up? 16:54:34 and agree with Aleecia that it is not convincing to replace one uniqueID by another 16:54:36 ...i dont see how the text allows this. 16:55:12 look at point 1, "taken reasonable steps to ensure"... as we know from data science, in fact pseudonymous datA can be linked to a specific device. 16:55:25 ...does this text have a different meaning? 16:55:38 q+ 16:55:49 Zakim, unmute me 16:55:49 jchester2 should no longer be muted 16:55:54 ack jchester2 16:56:05 peterswire: it would be helpful if zaneis can answer in writing to jmayer's questions, on the list. 16:56:25 I wonder if anybody on this call understands the DAA's proposed text. 16:56:26 ...scribe did not get the question right, see, clarifications. 16:56:39 So to try earnestly to be productive, one way to get to "yellow" could be to specify hashing with a new key every month. 16:56:48 zakim, mute me 16:56:48 jchester2 should now be muted 16:56:49 jchester2: questions on process/procedure. Jeff feels he is being railroaded. 16:56:58 ack thomas 16:57:05 peterswire promises 15 minutes re process at end of meeting 16:57:09 I do not understand the DAA text. The DAA reps clearly don't understand it. 16:57:19 Zakim, please open the q 16:57:19 I don't understand 'please open the q', npdoty 16:57:24 Zakim, please open the queue 16:57:24 ok, npdoty, the speaker queue is open 16:57:30 aleecia, You are arguing into the wind, industry has said repeatedly they're not willing to put those sorts of numbers into text. 16:57:38 I know. 16:57:43 I had some questions that were never answered as well. 16:57:44 ThomasR a little frustrated about lack of details to his questions, requests written responses to his Monday questions from DAA 16:57:49 But I'm trying to find a way, any way, to save this. 16:57:50 Yes, written answers and time for discussion on next week's call. 16:57:51 alleecia, so if you visit the same site within a month they can still track you? 16:57:57 Aleecia, that particular technical design would still not ensure that "the data cannot reasonably be re-associated or connected to a specific user" in a plain meaning. 16:57:59 Where "this" is Do Not Track 16:58:03 s/ThomasR/tlr: / 16:58:07 ...apprciate the context, but DAA has not answered the questions. seeking written responses. 16:58:09 zakim, mut me 16:58:10 I don't understand 'mut me', tlr 16:58:12 zakim, mute me 16:58:12 Thomas should now be muted 16:58:16 If there's a way, that's probably not it. 16:58:36 jmayer, in some cases you are correct. In some it would help, maybe by enough 16:58:47 To whom do we address questions about the DAA proposal? 16:58:53 yianni -- please put URL into IRC for your 1st party/3d party language 16:58:57 tlr's fingers are used to mutt :-) 16:59:00 zaneis: quick rapup: DAA happy to provide detailed answers to jonathan's questions, and to Thomas;s. Aleecia's comment very helpful on when de linking occurs, and how do we get there, we need a conversation/discussion. that wd be productive. 16:59:06 DAA, please respond in writing to Rob's proposal. We need a public discussion on the issue he has raised. 16:59:15 http://lists.w3.org/Archives/Public/public-tracking/2013Jul/0050.html 16:59:18 ...DAA will provide comments when people get back, DAA will be diligent. 17:00:05 ...re: jmayer question, how the stds marry up with shane's proposal. that is good disucssion too, lets have that disucssion. we are trying to not have too much non normative text, but if that helps clarify the picture, DAA open to doing that as well. 17:00:08 I think an informative document/annex would be a great step (mining the old compliance document, DAA text, and so on) 17:00:08 thanks, and apologies, Peter, for talking over you. 17:00:11 I'm seeing three paths: (1) toss out the red-yellow-green approach. (2) tighten down what it means for data to become "yellow" which right now is nearly useless. (3) tighten down what can happen with data in "yellow" state, which right now is nearly everything, including serving targeted ads. 17:00:12 zakim, mute me 17:00:12 Thomas was already muted, tlr 17:00:19 Topic: First in Third Context 17:00:19 I was working on (2) 17:00:22 peterswire: new topic, first party in 3rd party context 17:00:38 ...yianni, can you explain new language/proposal. 17:01:05 Yianni's proposal is here: http://lists.w3.org/Archives/Public/public-tracking/2013Jul/0050.html ; and other change proposals on this question: http://www.w3.org/wiki/Privacy/TPWG/Change_Proposal_First_Party_Compliance 17:01:05 yianni: dont know if a lot of agreement on the new proposed langugae, but looking for some agreement 17:01:08 Right now, we have a proposal for DNT that allows no less tracking than for users who do not send DNT:1 17:01:17 ...primary issues is transparency 17:01:34 ...when first party uses infor in thrid party context, not transparency 17:02:07 Can you give some examples please of what kind of branding would be required? 17:02:11 ...this proposal wd allow clear branding so that the consumer wd know it was from first party, who "to blame" 17:02:17 I appreciate Mike's points -- and calm tone -- around what industry can willingly agree to. But it should be pretty obvious that if tracking stays the same with and without DNT:1, it's going to be hard to get others on board. 17:02:20 is a facebook 'like' button considered to be 'prominent branding'? 17:02:50 q? 17:02:53 q+ 17:02:57 peterswire: language proposed would not allow first party to use data in 3rd paty context UNLESS there is some clear statement. 17:02:58 +q 17:03:05 to aleecia: yes, the major change to the definition of tracking is troublesome, and a major change of direction. 17:03:09 dsinger, I think a "Facebook" logo on a Like button might suffice 17:03:12 ack Chapell 17:03:23 achapell: thanks to yianni. how does transparency work differently than in DAA code? 17:03:30 BillScannell has left #dnt 17:03:41 ...DAA code is transparency model as well. is this AdChoices icon, or more? 17:03:46 BillScannell has joined #dnt 17:03:55 schunter has joined #dnt 17:03:55 ...if about transparency, couldnt thrid parties take advantage of that as well? 17:04:09 q+ 17:04:12 +[Apple.a] 17:04:13 Yianni: now first parties can collect all the data they want in first party context. 17:04:15 Zakim, Apple.a has me 17:04:15 +hober; got it 17:04:17 q? 17:04:36 ...as far as third party context, yianni doesnt see how 3rd parties can collect using this formula 17:04:45 ...this proposal is about USE, not about COLLECTION 17:04:50 zakim, unmute me 17:04:50 jchester2 should no longer be muted 17:05:01 ...this proposal is differnet from DAA collection and use icon/adchoices 17:05:13 This seems to require more branding than a mere icon. 17:05:21 chapell: how is DAA and Yianni prposal different? 17:05:21 If not, it should. 17:05:32 peterswire: recommends follow up off line. 17:05:49 Yianni: will think about what "prominent branding" examples/non normaative 17:05:49 q+ 17:05:56 ack jchester 17:06:05 jchester2: wants to know what prominent branding means. 17:06:15 + +1.202.257.bbee 17:06:28 zakim, mute me 17:06:28 jchester2 should now be muted 17:06:33 q+ to ask whether prominent branding would not lead to two first parties on the same site as proposed by Rob Sherman? 17:06:34 yianni: prominent branding in spec rigfht now with multiple parties as well 17:06:40 Here is my concern. If browsers implement DNT as DAA proposes, it crosses deceptive practices, since it does not change tracking. 17:06:40 ...to think more about it 17:06:40 q? 17:06:44 UAs should send cookies: to 3rd parties when DNT:1 17:06:55 *not* 17:07:01 justin: in the past, justin had been supportive of first data in 3rd context, 17:07:01 close q 17:07:08 Zakim, bbee may be [Facebook] 17:07:08 +[Facebook]?; got it 17:07:12 Zakim, please close the queue 17:07:12 ok, npdoty, the speaker queue is closed 17:07:23 ack justin 17:07:24 ...branding approach is a clever way to do that than unidentifed icon 17:07:35 The browsers could pull the feature completely, or could implement their own view of what DNT is, neither of which is a good outcome. 17:07:56 ...one idea occurring is that if DNT1 can use first party data in 3rd context, need own 1st party opt out 17:08:04 ...not sure good idea, but recommend considering it. 17:08:10 schunter has joined #dnt 17:08:28 ...if indicate a desire to not be tracked, the first party publisher should consider own opt out 17:08:30 -1 for creating another two-layer opt-out, if it makes people confused about DNT being an opt-out 17:08:56 +1 to Nick 17:09:10 chapell: larger issue: if w3c is going to take this approach, need to communicate what DNT means 17:09:12 TS has left #dnt 17:09:22 ack ri 17:09:22 rigo, you wanted to ask whether prominent branding would not lead to two first parties on the same site as proposed by Rob Sherman? 17:09:23 ...and large entities can do whatever they want. 17:09:32 npdoty, Yeah, I get the limitations, but at least there are first-party relationships in place, as opposed to market research industry. 17:09:34 Chapell, I think in the proposal that large parties couldn't collect data in a third-party context, the same way that other third parties couldn't 17:09:38 zakim, unmute me 17:09:38 Rigo should no longer be muted 17:09:38 rigo: cant hear rigo 17:09:41 -TS? 17:10:07 rigo: as soon as good into "branding" issue, create two competing rule sets for similar use sets 17:10:15 ...what happens w two parties on one side? 17:10:19 -[Mozilla] 17:10:27 ...give first party privilelges back in 17:10:36 +1 17:10:39 If DNT turns out to be: a) eliminating third-party tracking and b) large first parties can do whatever they want so long as they meet branding requirements --- then we have a requirement to disclose this in both our w3c docs and in the UA disclosure guidelines 17:10:41 +1 17:10:44 ...creates complexity within the rule set, destroys the clarity of hte rule set 17:11:10 peterswire: to the extent the standard is sets of rules around 1st party and different sets of rules around 3rd parties 17:11:23 public has joined #dnt 17:11:32 ...third parties express concern about 1st/3rd impact, disparate impact 17:11:44 I would be curious to understand what our colleagues who are regulators think about the potential anti-competitive impact of this approach 17:11:49 Ed? Rob? 17:11:55 Chapell, but you recognize that large first parties would face the same limits about collecting data in the third party context (for example, Facebook and Google collect data in third-party contexts now as well as in their first-party context), right? 17:11:56 ...patrolling this line bw the 1st/3rd and related roles, quite important to consider 17:12:17 ...which is why peterswire asked yianni to draft this proposal. 17:12:19 +q 17:12:21 Topic: Procedure 17:12:24 Zakim, please open the queue 17:12:24 ok, npdoty, the speaker queue is open 17:12:25 peterswire moving to procedure. 17:12:29 q+ jchester2 17:12:38 q- Chapell 17:12:38 ...working w w3c staff, important end of july deadline. 17:12:54 ...trying to get substantial sense of where we are by end of july 17:13:03 ...last call may have some things left open 17:13:09 npdoty, i recognize that there migth be some limits on first parties under this standard - whether they are significant or not is an open question 17:13:23 ...end of july is basic sense of where we are heading. 17:13:41 ...june draft a pretty good sense of what kind of standard june draft cd be. 17:13:51 ...june daft is one direction. 17:14:13 ...another path supported by a set of actors that have a lot of websites and eco participation, and working group participation, is DAA/Zaneis 17:14:19 that wd look different than june draft. 17:14:33 ...hopefully todays convo helps understand, along with answering questions 17:14:39 +q 17:14:51 +q 17:14:52 ...head towards perfecting amendments by Tuesday on DAAA 17:15:05 ....call next wednesday work through these issues 17:15:14 ...point is, clarify the two basic directions 17:15:18 are you asking the group the question "should we take the DAA proposal as the baseline text?" (and dump the old compliance and the June draft)???? 17:15:25 ...clarify reasons to support or not support, 17:15:32 ...issues such as deid 17:15:56 ...in nine days, submit objections on the record/written views on where we are 17:16:17 ...the two choices before you are a strong record for a Chairs Decision 17:16:22 ...that is basic approach 17:16:32 record for a chair's decision on what? 17:16:37 ...peterswire doesnt see a way to avoid such a Chairs Decision 17:16:40 zakim, unmute me 17:16:40 jchester2 should no longer be muted 17:16:50 ...swire has record that has been created already. 17:16:54 q? 17:16:56 I'll echo dsinger's question 17:16:59 ...the written response/next 9 days will also help. 17:17:03 DAA proposal should be broken down into the relevant issues and put on the wiki IMHO 17:17:03 q? 17:17:11 ack jchester2 17:17:12 jchester2: what kind of record will you have? 17:17:15 q+ 17:17:19 +1 to rvaneijk 17:17:28 ...how was the decision to have DAA draft presented as one of the two options? 17:17:37 do we have the 'why' for each change in the DAA draft? 17:17:41 ...lots of efforts editing june draft, short time period. 17:17:45 +1 to rvaneijk as that is what we do 17:17:57 ...we had a week, and now it sounds until Tuesday to respond to DAA draft. 17:18:16 ...recommend structuring convo with appropriate specialists, etc., to have a good conversation. 17:18:17 q? 17:18:27 ...that issue (deid) alone could take 2 hrs. 17:18:35 zakim, mute me 17:18:35 jchester2 should now be muted 17:18:43 ...repeat question on decision on DAA draft as one of 2 options 17:18:47 q+ 17:18:53 ack jmayer 17:18:57 petersiwre: his decision in consultation w w3c stafff. 17:19:04 The answer on how you reached a decision is that you reached the decision? I don't get that answer. 17:19:19 jmayer: having spent time on issue by issue on june draft, could we carry over hard work to the DAA draft? 17:19:56 petersiwre: every submission on change/rationale, statements, etc., so for lots of issues, recent, clear views of issues. that in many instances will be highly relevant 17:20:04 That didn't answer my question. 17:20:07 Peter is dropping out 17:20:20 ...hope that work will be highly useful for any decision on how to sum up/end work in july. 17:20:20 aleecia, not here 17:20:30 tlr thanks 17:20:50 jmayer: asked for text responses from DAA. will the existing text responses be sufficient, or do we have to generate a new fresh set of responses for DAA? 17:21:01 are you asking (a) 'should we take the DAA proposal as basis?' or (b) 'what changes would you want on the DAA text if we were to take it as basis?' 17:21:02 peterwire asked npdoty to answer 17:21:06 q? 17:21:10 Do I have to document all the times I *didn't* object to language in the June draft? 17:21:11 s/from DAA/to DAA proposal/ 17:21:14 npdoty: lots of proposals come through, w3c documenting. 17:21:32 ...DAA might be a package that CANNOT be broken up, how they work togehter as a piece 17:21:39 q? 17:21:43 ...recommend addressing DAA as a package 17:21:57 ack efelten 17:21:58 Yet we've done that and have two drafts along those lines that we incorporated in a consensus document 17:22:05 efelten: proces going forward is chair decision on DAA v juen draft? 17:22:13 ...and then after that what happens? 17:22:30 peterswire: chair's decision, then the group in its wisdom meets. 17:22:38 efelten: and then after that? 17:22:40 bad connection, recalling 17:22:47 ..what if switch to DAA? 17:22:47 -Aleecia 17:22:57 +q 17:23:03 q+ 17:23:05 peterswire: fair question, hasnt worked it out fully yet. 17:23:16 q- 17:23:18 could someone please augment scribing? 17:23:19 efelten: is there going to be opportunitiy to propose changes to draft? 17:23:22 I think most of the already documented change proposals would still apply 17:23:34 How can we hold an informed vote on the DAA proposal if we don't know the extent to which it can be revised? 17:23:42 +Aleecia 17:23:46 peterswire: DAA would not be final standard, wd need additional work 17:24:09 efelten: text proposals would be considered or thrown out? 17:24:19 peterswire: even if a decision on either the DAA or the June draft, would still need to address the change proposals already documented 17:24:30 s/if a decision/after a decision/ 17:24:31 If the DAA proposal is a all or nothing package we might as well do a vote today 17:24:41 peterswire: DAA proposed package, there would be process to test that out, clarity about fundamentally after july 17:24:51 q? 17:24:51 efelten: issue by issue? 17:24:55 peterswire: yes 17:25:09 So, first *perfecting* friendly amendments to DAA text, and then arguments on which text, and THEN we work through whichever draft. I think. 17:25:21 johnsimpson: chairs decision is on which of the two baselines? 17:25:35 peterswire: yes, and reasons given why elements are positive/negative. 17:25:50 johnsimpson: need formal explanations on DAA proposal. 17:25:59 Yes, and "work through" means going area-by-area where we have had text proposals against the current draft. 17:26:03 ...DAA is completely murky. who is part of the DAA team? 17:26:16 q? 17:26:20 (That's my understanding of what Peter said.) 17:26:22 peterswire: we had a scribed conversation and asked for help. 17:26:34 ack johnsimpson 17:26:38 ack aleecia 17:26:40 aleecia: quite a few issues about where we are 17:26:42 We need to know exactly who endorsed the DAA proposal and which ones have contributed to paying for Peter's work on DNT. 17:27:02 ...as she understands, two paths: Chair draft, DAA soon to be final draft of proposal. 17:27:16 ...two complete proposals which we had in a consensus draft, side by side. 17:27:34 ...aleecia resubmitted text before deadline. why not considering that version? 17:27:38 ? 17:27:45 petersiwre: lots of people asking for lots of things. 17:27:57 q? 17:28:05 q+ 17:28:05 aleecia: DAA proposal has trumped the consensus proposal that has been worked on for two years. 17:28:12 peterswire: ok. 17:28:18 q- 17:28:18 So Peter made the decision to ignore the consenus proposal, I would like him to explain this in writing please, which should be distributed to the news media. 17:28:20 -[CDT] 17:28:21 ...we are not consdiering the consensus proposal at this time. 17:28:36 q? 17:28:40 I don't see why the DAA gets standing for its proposal 17:28:42 aleecia: i appreicate that clarity that consensus proposal as off the table. 17:28:42 I believe that the 'old' consensus document is still a source of text, idea, issues, and history, no matter what basis we use going ahead 17:28:48 +1 to David 17:29:12 jmayer: question about what the impact of selecting a baseline is? 17:29:29 ...is it a document about w3c conversation/template for submitting issue by issue rationales? 17:29:41 or some impact of selecting a baseline on substative and procedural issues? 17:30:01 ...if there isnot consensus, does baseline trump? presumption of baseline stds? 17:30:02 Just to get this clear: Peter has just explained that my proposal to include consensus text from prior drafts, submitted on time, has been summarily discarded. The work of the group is discarded. Our options are DAA or Peter's own text, with no oportinities for other texts. 17:30:11 aleecia, not discarded. 17:30:20 Thomas... please. 17:30:41 -[Microsoft] 17:30:47 peterswire: the core points are picking a direction. beyond that, in DAA, there are specific issues in there. if DAA text were picked as baseline, there is an overall structure and logic. 17:31:04 ... amendments tested to see if they make sense /logic to the DAA proposal. 17:31:12 Ok, so the suggestion is that certain amendments to the DAA document would be impermissible? 17:31:19 Which amendments, then? 17:31:20 ...if june text, the amendments will also be considered. 17:31:29 ...there are lots of proposed edits to June text. 17:31:40 It might also have helped to have some notion that brand new approaches were invited, rather than changes to Peter's draft. That was not announced either. 17:31:43 ...other options include consensus draft, or another option. 17:31:49 And it might have helped to have more than a week. 17:32:10 .peterswire: basic decision bw two paths. 17:32:11 The group *has* reached consensus on the draft I submitted, which is the entire point. 17:32:20 ...there are areas that are clearly different. 17:32:28 Yes, it had alternatives in it. But that was where the options were. 17:32:36 chair will try to write up reasonable decision, and then decide what to do next. 17:32:41 This still doesn't answer my question. We don't have clarity on the proposed decision. 17:32:46 If I had known that 'replace X with Y' was a reasonable change proposal, I might also have tried to write one (or get a team to) 17:32:46 ..end of july intended to be meaningful, not to be punt. 17:32:58 dsinger, +1 17:33:02 Peter, please place on the record--prior to your decision--the specific names of the working group members who have contributed to paying your salary and expenses. Thanks, 17:33:09 If this is intended to be derailing, it's succeeding. Thanks so much 17:33:09 though again would have needed more than 7 days 17:33:18 +1 to David 17:33:20 peterswire: 132pm, gone thorugh the queue. please read emails re work plan. 17:33:25 This is so painful 17:33:33 The proposal it to agree to a new baseline. With no clarity on what having a new baseline means. 17:33:33 -Yianni 17:33:34 -adrianba 17:33:34 -[FTC] 17:33:35 -eberkower 17:33:35 -Rigo 17:33:37 -PaulGlist 17:33:37 -Aleecia 17:33:37 - +1.813.732.aall 17:33:38 -rvaneijk 17:33:38 - +1.323.253.aakk 17:33:38 -WaltMichel 17:33:39 -omertene 17:33:39 -mike_zaneis? 17:33:40 -jackhobaugh 17:33:40 -Thomas 17:33:40 -efelten 17:33:41 -Brooks 17:33:41 -RichardWeaver 17:33:41 -[Facebook]? 17:33:41 end call. 17:33:42 -Craig_Spiezle 17:33:42 -Yianni.a 17:33:42 -vincent 17:33:43 -Jules_Polonetsky 17:33:43 -[Apple.a] 17:33:43 -johnsimpson 17:33:44 -moneill2 17:33:44 - +1.650.595.bbdd 17:33:45 -Chris_Pedigo 17:33:46 -BillScannell 17:33:48 -[Apple] 17:33:49 -Wendy 17:33:49 -jchester2 17:33:50 -ninjamarnau 17:33:51 -rachel_n_thomas 17:33:55 -schunter 17:34:00 -dwainberg 17:34:04 -Peder_Magee 17:34:42 Zakim, list attendees 17:34:42 As of this point the attendees have been +49.172.147.aaaa, +31.65.141.aabb, npdoty, +1.215.480.aacc, rvaneijk, +1.202.347.aadd, WaltMichel, +1.202.262.aaee, jackhobaugh, Thomas, 17:34:45 ... Wendy, +972.8.979.aaff, jchester2, +1.609.258.aagg, +1.202.478.aahh, +49.172.147.aaii, omertene, efelten, dwainberg, +1.646.654.aajj, PaulGlist, eberkower, +1.323.253.aakk, 17:34:45 ... schunter, +1.813.732.aall, +1.202.257.aamm, +1.202.478.aann, rachel_n_thomas, +1.202.697.aaoo, Aleecia, +1.303.746.aapp, +1.202.587.aaqq, [Microsoft], paulohm, +1.301.365.aarr, 17:34:49 ... dsinger, BerinSzoka, +44.186.558.aass, Keith_Scarborough, sidstamm, Brooks, +1.202.603.aatt, +1.646.278.aauu, adrianba, [CDT], Rigo, Peter_4As, +49.431.98.aavv, 17:34:49 ... +44.186.558.aaww, mecallahan, ninja?, +1.571.213.aaxx, RichardWeaver, ninjamarnau, Suzanne?, johnsimpson, +1.650.365.aayy, Chris_Pedigo, Chapell, Jonathan_Mayer, 17:34:52 ... +1.202.787.aazz, Peder_Magee, moneill2, BillScannell, +49.211.600.4.bbaa, TS?, peterswire, Craig_Spiezle, [FTC], mike_zaneis?, +33.6.50.34.bbbb, vincent, +1.202.587.bbcc, 17:34:52 ... Jules_Polonetsky, +1.650.595.bbdd, lauren?, [Apple], hober, +1.202.257.bbee, [Facebook]? 17:34:52 -Keith_Scarborough 17:35:21 -[Microsoft.a] 17:35:51 -npdoty 17:35:55 rrsagent, please draft the minutes 17:35:55 I have made the request to generate http://www.w3.org/2013/07/03-dnt-minutes.html npdoty 17:35:59 -Chapell 17:36:04 johnsimpson has left #dnt 17:45:22 -mecallahan 18:00:36 -lauren? 18:04:11 -Jonathan_Mayer 18:06:39 - +1.650.365.aayy 18:06:40 T&S_Track(dnt)12:00PM has ended 18:06:40 Attendees were +49.172.147.aaaa, +31.65.141.aabb, npdoty, +1.215.480.aacc, rvaneijk, +1.202.347.aadd, WaltMichel, +1.202.262.aaee, jackhobaugh, Thomas, Wendy, +972.8.979.aaff, 18:06:40 ... jchester2, +1.609.258.aagg, +1.202.478.aahh, +49.172.147.aaii, omertene, efelten, dwainberg, +1.646.654.aajj, PaulGlist, eberkower, +1.323.253.aakk, schunter, +1.813.732.aall, 18:06:41 ... +1.202.257.aamm, +1.202.478.aann, rachel_n_thomas, +1.202.697.aaoo, Aleecia, +1.303.746.aapp, +1.202.587.aaqq, [Microsoft], paulohm, +1.301.365.aarr, dsinger, BerinSzoka, 18:06:41 ... +44.186.558.aass, Keith_Scarborough, sidstamm, Brooks, +1.202.603.aatt, +1.646.278.aauu, adrianba, [CDT], Rigo, Peter_4As, +49.431.98.aavv, +44.186.558.aaww, mecallahan, 18:06:45 ... ninja?, +1.571.213.aaxx, RichardWeaver, ninjamarnau, Suzanne?, johnsimpson, +1.650.365.aayy, Chris_Pedigo, Chapell, Jonathan_Mayer, +1.202.787.aazz, Peder_Magee, moneill2, 18:06:45 ... BillScannell, +49.211.600.4.bbaa, TS?, peterswire, Craig_Spiezle, [FTC], mike_zaneis?, +33.6.50.34.bbbb, vincent, +1.202.587.bbcc, Jules_Polonetsky, +1.650.595.bbdd, lauren?, 18:06:45 ... [Apple], hober, +1.202.257.bbee, [Facebook]? 19:08:13 schunter has joined #dnt 20:36:10 jamie has joined #dnt 20:53:54 schunter has joined #dnt 21:14:50 npdoty has joined #dnt 21:40:05 Zakim has left #dnt 21:44:19 schunter1 has joined #dnt 22:35:09 npdoty has joined #dnt