15:58:26 RRSAgent has joined #dnt 15:58:26 logging to http://www.w3.org/2013/04/17-dnt-irc 15:58:29 rrsagent, please make logs public 15:58:31 zakim, who is on the phone? 15:58:31 sorry, dwainberg, I don't know what conference this is 15:58:32 On IRC I see RRSAgent, Yianni, Richard_comScore, Zakim, Chris_IAB, dwainberg, jchester2, rigo, eberkower, npdoty, efelten, schunter, adrianba, tlr, hober, mischat, wseltzer, 15:58:32 ... trackbot 15:58:44 Zakim, this is TRACK 15:58:45 ok, npdoty; that matches T&S_Track(dnt)12:00PM 15:58:46 +eberkower 15:58:48 just joined the call via a private number 15:58:50 +jchester2 15:58:51 zakim, mute me 15:58:52 jchester2 should now be muted 15:59:05 +Yianni 15:59:16 Zakim, mute me 15:59:16 Yianni should now be muted 15:59:29 peterswire has joined #dnt 15:59:54 JC has joined #DNT 16:00:21 fielding has joined #dnt 16:00:23 + +44.772.301.aacc 16:00:27 phildpearce has joined #dnt 16:00:41 vinay has joined #dnt 16:00:43 +npdoty 16:00:50 hefferjr has joined #dnt 16:00:51 Zakim, who is on the phone? 16:00:51 On the phone I see ??P2, +1.646.845.aaaa, +1.609.258.aabb, ??P10, eberkower, jchester2 (muted), Yianni (muted), +44.772.301.aacc, npdoty 16:00:55 + +1.404.385.aadd 16:00:56 +Fielding 16:01:04 Zakim, ??P10 may be Chris_IAB 16:01:05 +Chris_IAB?; got it 16:01:12 + +1.917.934.aaee 16:01:16 +JeffWilson 16:01:17 zakim, aaee is vinay 16:01:17 +vinay; got it 16:01:19 + +1.202.222.aaff 16:01:23 justin has joined #dnt 16:01:24 +RichardWeaver 16:01:27 WaltM_Comcast has joined #DNT 16:01:34 philpearce: +44.772.301 16:01:40 Zakim, aacc is phildpearce 16:01:40 +phildpearce; got it 16:01:58 zakim, aaaa is dwainberg 16:01:58 +dwainberg; got it 16:02:06 Zakim, ??P2 is schunter 16:02:06 +schunter; got it 16:02:21 vincent has joined #dnt 16:02:25 +[Mozilla] 16:02:38 prestia has joined #dnt 16:02:47 sidstamm has joined #dnt 16:02:48 Zakim, please choose a volunteer 16:02:48 I don't understand 'please choose a volunteer', npdoty 16:02:49 +[CDT] 16:02:53 rvaneijk has joined #dnt 16:02:53 Zakim, pick a victim 16:02:54 Not knowing who is chairing or who scribed recently, I propose jchester2 (muted) 16:02:58 Zakim, Mozilla has sidstamm 16:02:58 +sidstamm; got it 16:03:00 moneill2 has joined #dnt 16:03:01 +[Microsoft] 16:03:06 zakim, [Microsoft] is me 16:03:06 +adrianba; got it 16:03:11 + +33.6.50.34.aagg 16:03:11 zakim, mute me 16:03:12 adrianba should now be muted 16:03:13 I can't do it today, but next week ok 16:03:15 +[Microsoft] 16:03:17 Zakim, pick a victim 16:03:17 Not knowing who is chairing or who scribed recently, I propose vinay 16:03:25 zakim, +aagg is vincent 16:03:25 sorry, vincent, I do not recognize a party named '+aagg' 16:03:32 zakim, aagg is vincent 16:03:32 +vincent; got it 16:03:33 vinay, can you scribe today? 16:03:34 i can't scribe today. i need to drop soon 16:03:38 Zakim, pick a victim 16:03:38 Not knowing who is chairing or who scribed recently, I propose +1.202.222.aaff 16:03:39 (that, and i scribed 3 weeks ago) 16:03:41 +[IPcaller] 16:03:41 + +1.215.480.aahh 16:03:41 Zakim, pick a victim 16:03:42 Not knowing who is chairing or who scribed recently, I propose jchester2 (muted) 16:03:44 +Aleecia 16:03:45 + +31.65.141.aaii 16:03:45 Zakim, pick a victim 16:03:46 Not knowing who is chairing or who scribed recently, I propose +1.404.385.aadd 16:03:49 Zakim, pick a victim 16:03:49 Not knowing who is chairing or who scribed recently, I propose vincent 16:03:53 Zakim, aaii is me 16:03:53 +rvaneijk; got it 16:03:56 sure 16:03:59 zakim, [IPCaller] is me 16:03:59 +moneill2; got it 16:04:07 scribenick: vincent 16:04:07 kj has joined #dnt 16:04:07 David_MacMillan has joined #dnt 16:04:21 + +1.202.787.aajj 16:04:25 Zakim, [215480] is WaltM_Comcast 16:04:25 sorry, WaltM_Comcast, I do not recognize a party named '[215480]' 16:04:27 Zakim, who is on the phone? 16:04:27 On the phone I see schunter, dwainberg, +1.609.258.aabb, Chris_IAB?, eberkower, jchester2 (muted), Yianni (muted), phildpearce, npdoty, +1.404.385.aadd, Fielding, vinay, 16:04:31 ... JeffWilson, +1.202.222.aaff, RichardWeaver, [Mozilla], [CDT], adrianba (muted), vincent, [Microsoft], moneill2, +1.215.480.aahh, rvaneijk, Aleecia, +1.202.787.aajj 16:04:31 [Mozilla] has sidstamm 16:04:35 Zakim, aabb may be efelten 16:04:35 +efelten?; got it 16:04:41 Zakim, aahh is WaltM_Comcast 16:04:41 +WaltM_Comcast; got it 16:04:51 +hefferjr 16:04:52 schunter: first task is going through working draft and identify change needed before publication 16:05:05 ... should be aligned with issue status 16:05:08 prestia has joined #dnt 16:05:15 ... shoudl reflect current state of the discussion 16:05:27 +SusanIsrael 16:05:28 sisrae000 has joined #dnt 16:05:30 ... quickly go through the document 16:05:39 Brooks has joined #dnt 16:05:43 + +1.202.347.aakk 16:05:51 kulick has joined #dnt 16:05:53 +Brooks 16:05:56 Zakim, aakk is prestia 16:05:56 +prestia; got it 16:06:12 jmayer has joined #dnt 16:06:18 + +1.650.465.aall 16:06:21 topic: TPE review for working draft 16:06:22 + +1.408.836.aamm 16:06:24 schunter: going chapter by chapter, say stop to go to sub-chapter 16:06:30 +Chris_Pedigo 16:06:33 http://www.w3.org/2011/tracking-protection/drafts/tracking-dnt.html#introduction 16:06:33 http://www.w3.org/2011/tracking-protection/drafts/tracking-dnt.html 16:06:34 susanisrael has joined #dnt 16:06:36 Zakim: aamm is kulick 16:06:43 ChrisPedigoOPA has joined #dnt 16:06:44 Zakim, aamm is kulick 16:06:44 +kulick; got it 16:06:58 +Rigo 16:07:11 Zakim, aall is David_MacMillan 16:07:11 +David_MacMillan; got it 16:07:16 Chapell has joined #DNT 16:07:25 +Jonathan_Mayer 16:07:36 q+ 16:07:41 aleecia: ok with introduction, jsut one question around the first paragraph; not sure the language capture what we're doing 16:07:45 JamesB has joined #dnt 16:07:49 ninjamarnau has joined #dnt 16:08:00 + +49.431.98.aann 16:08:04 q+ to ask isn't that about exceptions? 16:08:15 Zakim, aann is ninjamarnau 16:08:15 +ninjamarnau; got it 16:08:16 zakim, aann is Ninja 16:08:16 sorry, rigo, I do not recognize a party named 'aann' 16:08:29 + +1.646.666.aaoo 16:08:34 ... is IE10 still compliant with DNT, not clear based on the text 16:08:41 -[CDT] 16:08:47 I don't think we're asking for consensus on text to publish a Working Draft 16:08:50 zakim, aaoo is Chapell 16:08:50 +Chapell; got it 16:08:53 johnsimpson has joined #dnt 16:09:02 q+ 16:09:03 +q 16:09:05 -David_MacMillan 16:09:07 schunter: publishing does not mean that we have consensus on all point 16:09:15 +[CDT] 16:09:17 ... are you ok with publishing it as a WD 16:09:24 q- 16:09:26 + +1.650.365.aapp 16:09:34 aleecia: ok with publishing it as a working draft 16:09:41 Zakim, aapp is David_MacMillan 16:09:41 +David_MacMillan; got it 16:09:46 +1 Aleecia's points 16:09:54 ... but want to remark that there is no consesnus and should be reflected 16:09:55 I promise to remember that publishing a Working Draft does not mean group consensus 16:10:26 Joanne has joined #DNT 16:10:46 ... would be happy to help on the language, maybe we should add a note telling that there is not a consensu on everything yet 16:10:55 q+ to review Status of the Document 16:10:59 ... the rest of it, was quite happy with the introduction 16:11:07 +johnsimpson 16:11:16 "Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress." 16:11:23 +Joanne 16:11:33 q? 16:11:34 schunter: I changed my mind, it's an important point, if we put a disclamer we won't progress 16:11:48 +1 to Adrian's sentance 16:11:59 ... we'd better publish the document and say that when there are still open issues there is no consensus 16:12:01 +1, thanks Adrian 16:12:09 cOlsen has joined #dnt 16:12:30 ... we put a note saying that there is not a consensus on the paragraph 16:12:39 +[FTC] 16:12:40 ack dwainberg 16:13:11 dwainberg: raised issues with this previouosly, and had to wait until the discussion on the introduction 16:13:14 I don't think it's feasible to indicate every possible concern about every possible sentence depending on every possible outcome of the Working Group 16:13:21 I have difficulty adding visual distinctions evry time a single member of the group has a difference of opinion … having issue markers where an issue has been raised is fine. 16:13:45 +hwest 16:13:50 hwest has joined #dnt 16:14:10 ... if we don't create an issue to flag it as open, it will make it harder to come back on it later 16:14:20 ... reflect the introduction as needing revision 16:14:24 q? 16:14:31 schunter: other question 16:14:45 ack rv 16:15:03 in the Compliance document the editors have replaced the Introduction with a note explicitly noting that we'll have to come back to introductions 16:15:17 q? 16:15:24 ack jmayer 16:15:25 we also note ISSUE 136 (regarding dependencies) in the TPE introduction 16:15:30 xxx: it will be much cleaner to have an introduciton in the compliance doc and leave it empty in the TPE 16:15:47 s/xxx/rvaneijk/ 16:16:34 q+ 16:16:35 jmayer: 1 what the position of the next draft would be, caution on pushing to produce a document, not many consensus since last document 16:16:45 my point is not to have an introduction in the TPE due to 1. issue 136, which is about the inter dependencies., 2. Compliance doc deals with what DNT means. (This specification defines the meaning of a Do Not Track (DNT) preference and sets out practices for websites to comply with this preference. ) 16:17:01 ... not real change, concerned that people might be misunderstanding what we're adding 16:17:45 q? 16:17:53 ... just try to make it clear that all the document might change, from the last paragraph of the introduction to the specifics 16:18:11 ... unconfortable puyblishing another working draft 16:18:20 Wow 16:18:53 schunter: I'll go through the doc and would like to find the open issues and find how close we are 16:19:26 ... I believe we made good progress with this document, the process is important 16:19:36 q? 16:19:38 The last WD was 2 October 2012. We are required to publish every three months. 16:19:38 ... I hope we can publish a working draft 16:19:40 ack npdoty 16:19:41 npdoty, you wanted to review Status of the Document 16:20:40 npdoty: Working draft is a snapchot of the progress, showing where we are 16:21:02 ... does not mean that there is a consensus 16:21:09 We should specify in each section where there is no consensus 16:21:28 ... if people want to highlight where there are concern, would be happy to help with that 16:21:32 cvs diff -u -r 1.170 tracking-dnt.html 16:22:39 q? 16:22:43 zakim, unmute me 16:22:43 adrianba should no longer be muted 16:22:44 ack ad 16:22:48 ... I don't think it is usefull to mention where there is no consensus, would make the document unreadable (did I capture that ?) 16:22:52 http://www.w3.org/2005/10/Process-20051014/groups.html#three-month-rule 16:23:17 adrianba: will echo what npdoty, we have to publish a working draft every 3 months to show tha tthe group is alive 16:23:33 ... we should not be afraid about publishing a document 16:23:35 -Aleecia 16:24:53 ... in many WG, the draft is prpose by the editor without review of the working group 16:24:59 This is a consenus process and the editors must reflect the differences in the group. 16:25:41 +Aleecia 16:26:03 schunter: if there is a big issue with a section then it should be mark in the document, no need to look at the consensus in detail 16:26:06 zakim, mute me 16:26:06 adrianba should now be muted 16:26:13 ... the introduction need some revision 16:26:18 now discussion section 2 16:26:21 ... no concern 16:26:26 Suggestion/Analogy: Regulators update their privacy policies frequently based on feedback and new information to "fine tune"...thus TPE is likely to be updated based on public feedback: http://www.changedetection.com/log/uk/gov/ico/privacy_statement_log.html 16:26:30 +q 16:26:38 section 3 : determin user preference, concern or open issue about that section 16:26:44 q? 16:26:54 May I suggest that the W3C issue a "status update" document to the world-- at least to those who are following this initiative 16:27:08 that may take some "pressure" off of the working group to publish 16:27:28 q+ 16:27:42 The working group shouldn't publish documents just to evade pressure. It should actually make progress. 16:27:46 the protocol is not enabled, even in Europe, when no signal is being sent 16:27:48 sent to mailing list 3 minutes ago 16:28:05 aleecia: this section need to be reworked, section reflect what would happen in the US but not in the EU 16:28:10 q? 16:28:13 I disagree that we are not making progress 16:28:15 q+ 16:28:26 ... reflect that in different section of the world not sending DNT might have a different meaning 16:29:01 q? 16:29:02 schunter: suggestion is to synchronize it with the compliance spec 16:29:10 yes, issue 136 makes sense to apply to section 3 as well 16:29:14 issue-136? 16:29:14 ISSUE-136 -- Resolve dependencies of the TPE on the compliance specification -- open 16:29:14 http://www.w3.org/2011/tracking-protection/track/issues/136 16:29:15 note: regarding section 3, note possible inconsistency with the compliance spec regarding enabled/not-enabled and europe 16:29:29 +??P65 16:29:43 -npdoty 16:29:45 laurengelman has joined #dnt 16:29:50 Issue 136 also applies to section 1, ergo it is better to move the introduction as a whole to the compliance doc. 16:29:50 wow, dial-up! 16:29:58 zakim, who is making noise? 16:30:05 I hear nothing 16:30:10 rigo, listening for 10 seconds I heard sound from the following: Aleecia (79%), Fielding (56%), ??P65 (4%), Rigo (24%) 16:30:12 zakim, mute P65 16:30:12 sorry, sidstamm, I do not know which phone connection belongs to P65 16:30:17 zakim, mute ??P65 16:30:17 ??P65 should now be muted 16:30:21 augh 16:30:27 zakim, drop ??P65 16:30:27 ??P65 is being disconnected 16:30:29 -??P65 16:30:30 q? 16:30:33 is anyone hearing anything? 16:30:36 +npdoty 16:30:36 I am 16:30:37 zakim, who is making noise? 16:30:37 silence 16:30:43 -npdoty 16:30:47 rigo, listening for 10 seconds I heard sound from the following: schunter (4%), +1.404.385.aadd (25%), Fielding (26%), +1.202.787.aajj (5%), Rigo (24%) 16:30:47 okay, it gave up 16:30:50 that sound is a UA that doesn't have a good UI :) 16:30:51 hmm … we're back 16:30:59 BillScannell has joined #dnt 16:31:12 -[Microsoft] 16:31:14 zakim, mute me 16:31:14 Rigo should now be muted 16:31:22 schunter: in Section, I'm gonna mark issue 136 16:31:24 q? 16:31:24 q- 16:31:26 q? 16:31:29 q?ack jm 16:31:32 ack jm 16:31:33 +[Microsoft] 16:31:37 .. anything else on section 3? 16:31:52 Our robot overlords have completed the sending of their orders. 16:31:54 + +1.415.627.aaqq 16:31:55 jmayer: don't like the mode of conversation 16:32:05 +npdoty 16:32:12 I have no posted issues on this section. As such, there are no objections. 16:32:23 ... I don't think we've made progress on section 3 16:33:03 Zakim, ??aaqq is laurengelman 16:33:03 sorry, laurengelman, I do not recognize a party named '??aaqq' 16:33:08 ... on the specific of the section, I would not be in favor of publishing a working draft without a warning 16:33:13 Zakim, aaqq is laurengelman 16:33:13 +laurengelman; got it 16:33:26 thanks nick! 16:33:28 ... last working draft we saw comanies taking action based on what was on the text 16:33:42 Zakim, aadd may be peterswire 16:33:42 +peterswire?; got it 16:33:55 There are no changes to this section in over a year, IIRC. 16:33:56 q+ 16:33:58 +1 to Jonathan's general concern. However, I'm not sure how to address? Any suggestions? 16:34:06 ... I would want to see a very clear disclamer so there can not be misunderstading about consensus 16:34:28 There are no open issues on this section. 16:34:47 we can highlight document-wide that there is not general agreement. are there existing specific issues regarding this section? (as Roy noted, we closed issues on this section.) 16:34:48 schunter: it's a working draft and I'd like to understand what are the concern, we have agreement that DNT should reflect user preference 16:35:01 Zakim, who is making noise? 16:35:10 q? 16:35:12 npdoty, listening for 10 seconds I heard sound from the following: schunter (67%) 16:35:16 how can browser be compliant with something that isn't even a working draft? 16:35:31 we don't generally include implementation tests for all major browsers in public working drafts 16:35:49 this is a question about objections to publish a WD knowing that it is a work in progress - we already published this text as a WD - we know it isn't done but that shouldn't prevent publishing 16:35:49 kj has joined #dnt 16:35:58 zakim, unmute me 16:35:58 Rigo should no longer be muted 16:36:34 rigo: we're are here to define a target implementation 16:36:46 q+ 16:37:04 aleecia: reading the text I'd think that IE 10 is compliant 16:37:19 +1 to try for better text 16:37:41 +1 that better text is a good general goal 16:37:48 q? 16:37:55 ... having a lot of ambiguity such as that people in the group disagree in the meaning, that's not ok 16:37:56 It sounds like Aleecia and I are on the same page: we do not have agreement on how this current text about user agent DNT choice applies to the major browsers currently in use. 16:38:07 Matthias, I want to comment, we are not ready to move on yet 16:38:09 Matthias, I want to comment, we are not ready to move on yet 16:38:22 schunter: text is too vague, let take a not and move on 16:38:33 has it gone dead? 16:38:37 silence 16:38:42 ? 16:38:43 q? 16:38:44 back, kind of? 16:38:53 ack johnsimpson 16:39:19 johnsimpson: there was a lot of discussion about wether or not a UA should propose 3 choices 16:39:41 john is referring to third para of sec 3 16:39:49 ... I recall a formal objection to that standard and that making it's way through the W3C process and that should be noted in the document 16:39:58 q? 16:40:06 Zakim, who is making noise? 16:40:17 hwest, listening for 10 seconds I heard sound from the following: Fielding (34%) 16:40:19 Roy: formal objections are noted at the end 16:40:20 hearing only the xa trying to call 16:40:23 Zakim, drop fielding 16:40:23 Fielding is being disconnected 16:40:25 -Fielding 16:40:30 bummer 16:40:34 ack heff 16:40:45 is anyone speaking? 16:40:48 that was fun 16:40:54 -JeffWilson 16:40:54 q+ rvaneijk 16:40:55 q+ 16:40:58 - +1.202.222.aaff 16:41:00 weird 16:41:06 sorry, fielding, it seemed like that noise was coming from your line 16:41:17 yep, I am unable to even hang up 16:41:24 ack rvan 16:41:33 xxx: we can't say we're compliant witht he spec if the spec does not say what compliance is 16:41:40 Rob 16:41:43 s/xxx/hefferjr/ 16:41:57 +Fielding 16:42:14 rvaneijk: any lanaguage about the compliance shouldgo to the compliance document, for instance the discussion about the default 16:42:16 +1 to rvaneijk 16:42:22 should in general we have a pointer from this section to the corresponding Compliance section? 16:42:23 q? 16:42:28 Q? 16:42:42 schunter: let's have a look on section 4, more technical 16:42:43 I think we should shift the text to reflect UA interface requirements 16:42:55 ... has been stable for a long time 16:43:10 s/Rob/rvaneijk/ 16:43:10 fielding, do we still need this note about cookie behavior? 16:43:23 q? 16:43:24 ... javascript API has been revised 16:43:32 q? 16:43:32 no comment on section 4? 16:43:41 diff is now at http://lists.w3.org/Archives/Public/public-tracking/2013Apr/0157.html 16:44:06 npdoty: do we still need this comment on cookie behjavior? 16:44:31 fielding: David added that so ask him 16:44:32 dsinger not on the call today, unfortunately, I'll follow up via email 16:45:00 rigo: wether you can claim that a browser return DNT MUST accept third party cookies 16:45:23 q? 16:45:52 the next section is section 5 16:46:16 q+ 16:46:29 rigo: wether you can claim that a browser return DNT:0 (not just DNT) MUST accept third party cookies 16:46:53 schunter: are there issue that are not properly highlighted? 16:46:54 q? 16:46:57 ack rig 16:46:57 q+ 16:46:58 ack rigo 16:47:00 q+ 16:47:41 rigo: what we are lacking is a that we can not communicate that a first party accept to be subject to the DNT:1 restriction that also apply to 3rd party, it is something that is needed in EU context 16:47:52 Matthias -- just the issue I raised on the mailing list, and that you referenced earlier on the call: the "N" flag. 16:48:27 + +1.303.652.aarr 16:48:27 q+ 16:48:33 ... allow DPA to say if you collect data for this specific use you're fine, but if you want to collect more data, you need to receive DNT:0 16:48:40 schunter: I disagree 16:48:58 I'm not sure I understood rigo 16:49:01 ... : anybody can send the '3' signal, even a first party 16:49:22 although "designed for use within a third-party context" would be inaccurate if it were a first-party context that was conforming to third-party requirements 16:49:38 rigo: if yoou send this, the message is ambiguous, one can send 3 because it beleives it is in the 3rd party context 16:49:44 +q 16:49:44 "A tracking status value of 3 means that the origin server claims that the designated resource is designed for use within a third-party context and conforms to the requirements on a third party." 16:49:59 schunter: resource can not tell if it is loaded in a first or third party context 16:50:12 fielding, re:*and* -- does that mean a first-party can't use it? 16:50:13 q? 16:50:16 ... you can not say anything about who was loaded in what context 16:50:19 ack npdoty 16:50:25 ? 16:50:32 q? 16:50:43 npdoty, no -- it says the resource complies with the third-party requirements in Compliance 16:50:43 npdoty: follow up on dwainberg question, how should we be noting the issue there? 16:51:15 sissue-119? 16:51:16 q? 16:51:17 WaltM_Comcast has joined #dnt 16:51:23 ack hef 16:51:36 note: add issue 119 to 5.2.1 tracking status value regarding "N"/none 16:51:39 hef: we also have issue 155 and 162 16:51:56 issue-152? 16:51:56 ISSUE-152 -- User Agent Compliance: feedback for out-of-band consent -- pending review 16:51:56 http://www.w3.org/2011/tracking-protection/track/issues/152 16:52:00 issue-195? 16:52:00 ISSUE-195 -- Flows and signals for handling out of band consent -- open 16:52:00 http://www.w3.org/2011/tracking-protection/track/issues/195 16:52:03 -RichardWeaver 16:52:10 hef: issue 195 and 152 16:52:10 q? 16:52:10 I actually think it's just 195 16:52:27 q? 16:52:33 ack rv 16:53:24 rvaneijk: I'd liek to echo some of rigo comment, paragraph 5.1 would be a nice place to say that this can be used at a consitent consent mechanism 16:54:07 ... add a comment to 5.1 to echoesRigo comment: if DNT is going to play as a consent mechanism in the EU it should be mentioned explicitely 16:54:16 This section is not a consent mechanism. Maybe 6? 16:54:31 -Jonathan_Mayer 16:54:34 rvaneijk, do you want to take an action to propose additional text? 16:54:44 rvaneijk: DNT is going to be a consent mechanism or a mechanism that is going to limit use 16:55:25 rvaneijk, do you want to take an action to propose additional text? 16:55:26 schunter: that's a good not, saying that the technology can be used to collect consent for exception 16:55:33 q+ 16:55:35 q? 16:55:38 ack mo 16:55:43 s/good not/good note/ 16:56:31 ack fiel 16:56:32 although I don't think this is necessary for publishing a snapshot Working Draft, I agree with the question about the third party language 16:56:40 moneill: just to echo what rigo said about first party responding as 3rd parties 16:57:13 fielding: these comments have no connection with changes on the draft or any connection to discussion in the mailing list 16:57:22 What fielding is saying. 16:57:37 -[FTC] 16:57:45 q? 16:57:54 ... if you have text changes that you want in the document, send the text to the mailing list even if it has been discussed on the phone 16:58:20 schunter: fully agree with fielding, if you made a comment send it to the list after the call 16:58:27 q? 16:58:46 q? 16:58:55 q+ 16:59:00 schunter: moving to seciton 6, user granted exception 17:00:06 ... in the new model, the site is responsible to collect user granted exception, and if it is certain that it get the consent, it can register the consent in the browser 17:00:13 q+ 17:00:37 schunter: we still have to define the requirement for sites that are necessary in order to register the exception 17:00:53 -WaltM_Comcast 17:00:54 ... also fine tuning the API based on adrianba implementation experience 17:00:57 q? 17:01:03 q+ 17:01:06 q? 17:01:09 ack n 17:01:48 npdoty: could we clarify the section, remove the long option box, move the issue at the top 17:01:54 q- 17:02:02 i was going to say what nick said 17:02:06 have to go to a meeting, apologies 17:02:09 ack mo 17:02:10 -jchester2 17:02:14 I'll follow up with David or make that change myself 17:02:19 schunter: ok to remove the option box, in the doc issue 187 is noted as open but it is not 17:03:15 moneill2: question about the sub-domains, people may not realize that consent can be applied to sub-domains of a main domain 17:03:31 ... does not solve the issue of multiple domains owned by a same data controler 17:03:32 q? 17:03:56 I think per moneill2, we need to update the reference to ISSUE-112 and note the use of cookie-like rules for sub-domains as currently used in the text 17:04:14 note: update reference to issue 112 regarding subdomains and cookie rules 17:04:44 q+ 17:04:52 schunter: we completed the pass through the document, I'll do the update and depending on how the compliance document is doing we may decide to publsih another document 17:05:05 q- 17:05:46 peterswire: I have different comemnts to make before moving to the compliance spec 17:06:15 ... about the f2f, the meeting will begin mid-day on monday until wendseday mid afternoon 17:06:23 a lot of time gonna be on the compliance spec 17:06:29 f2f registration, by the way: https://www.w3.org/2002/09/wbs/49311/tpwgca2013/ 17:07:14 ... offiline disucssion on financial reporting, might be either to get agreement that we had expect 17:07:31 ... we'll have language by alan on education 17:07:55 ... today we have a discussion on non interactive user agent 17:08:29 peterswire: how to proceed with the compliance spec, we recognize the issues as important 17:08:40 ... we're trying to get to stable text 17:08:49 -hwest 17:09:03 ... it is important that we emerge froim the f2f of a good architecture of what the compliance spec will look like 17:09:43 ... many of the issue of how far the document will go on the privacy side and on the 3rd party & advertiser side 17:10:12 ... my own effort has been to play the mediator role, we're reaching a decision point 17:11:12 ... I encourage any of you to discuss to try to find a compromise on some packages 17:11:35 ... if we don't achieve that; then there are 2 or 3 ways the process can go 17:12:29 ... one solution is that we'll have a compliance with the privacy side 17:13:03 ... antoher solution is that DNT will be similar to the DAA principle 17:13:28 ... the third solution is to have a compromise, to have support from different parts of the group 17:13:39 q? 17:13:40 q+ 17:14:06 ... I'm inviting you to do is to think what's an overall package we should have 17:14:31 ... we might have some choices that are harsher that what we expect 17:15:44 ... think about what real privacy / user choices changes a proposal would made 17:15:56 ... think about what's likely to get real adoption from a critical mass 17:15:56 peterswire: I recognize how hard it is and that it might be hard to put a package together 17:16:17 q? 17:16:24 ack rvaneijk 17:16:25 ... think about what an overall approach would be that could get adoption from the working group 17:16:33 Q? 17:17:12 rvaneijk: first, I appraciate the effort, my first reaction is that the two positions are two far appart 17:18:04 ... the standard is more likely to go in one extrem direction or in the other 17:18:20 ... I really think the two positions are too far apprt 17:18:36 peterswire: antoher outcome would be it's a no go in general 17:19:17 ... I encourage you to think what the best way to build on the work that have been done so far 17:19:34 -phildpearce 17:19:52 ... one of the reason we should have a consensus is that we should avoid the arm race 17:20:07 q? 17:20:25 ... it'll result in an internet that is not useful for the user and not good for the industry (cookie mechanism broken) 17:21:10 q? 17:21:30 ... I want to chalenge you all about how far can you go on the issues, be ready to make choice when you get to that meeting 17:21:30 http://www.w3.org/2011/tracking-protection/drafts/tracking-compliance.html 17:21:36 Topic: Compliance draft 17:21:48 peterswire: justin any keypoint you'd liek to highlight 17:22:00 justin: not a lot of change since the barebon doc 17:22:17 ... did not have much agreement since the boston meeting 17:22:30 we're down to single text on first parties and multiple first parties 17:22:44 justin: I tried to put things as option (for instance audience measurement) 17:23:37 ... put together a provisional definition of "tracking" in Section 2 17:23:44 aleecia has joined #dnt 17:23:47 thanks npdoty 17:23:48 vincent, just note that Justin presents the changes 17:23:49 ... based on some conversations from Boston 17:24:06 q? 17:24:12 -[Mozilla] 17:24:13 justin: present changes in the compliance document 17:24:27 Defining the term "tracking" is a charter requirement. 17:24:43 (sorry about today - we had another death on the tracks, which made the commute more insane than normal) 17:24:56 q? 17:25:19 Roy - I'm *really* close to being able to live with Justin's text, and I think you can live with the changes I'd make. 17:25:35 peterswire: question to schunter, should we publish both docs at the same time, one way to go is that schunter make a pass based on today's comment and justin update the compliance doc based on email discussion 17:26:16 schunter: we can wait for the compliance spec to make a joint publication 17:26:59 aleecia, what definition would you propose? 17:27:04 Topic: TPE issues 17:27:22 schunter: I pointed 2 or 3 issues, e.g. what would be the tracking signal be 17:27:25 q? 17:27:31 -[Microsoft] 17:27:33 -dwainberg 17:27:34 -ninjamarnau 17:27:35 -Joanne 17:27:36 -Chris_Pedigo 17:27:36 -peterswire? 17:27:36 -[CDT] 17:27:36 - +1.202.787.aajj 17:27:36 -efelten? 17:27:37 -Aleecia 17:27:37 -adrianba 17:27:38 -hefferjr 17:27:38 -vinay 17:27:39 - +1.303.652.aarr 17:27:39 -rvaneijk 17:27:39 -moneill2 17:27:39 -Rigo 17:27:40 review those issues via email, to be discussed on a later call 17:27:41 -kulick 17:27:42 ... people should have a look on the agenda and be prepared to discuss those issues next week 17:27:44 -David_MacMillan 17:27:44 Zakim, please list the attendees 17:27:45 I don't understand 'please list the attendees', npdoty 17:27:45 -SusanIsrael 17:27:46 What I'd do is take the multi-party aspect out of the defn (strike one word) and then move to a second sentence, "While first parties can and do track users, other than (x-ref to sending a response, data append with section number, anything else, possibly the null set depending on what we do) first parties 17:27:46 -Fielding 17:27:46 -prestia 17:27:46 -Brooks 17:27:47 -johnsimpson 17:27:47 -laurengelman 17:27:49 -Yianni 17:27:49 -vincent 17:27:49 Zakim, list attendees 17:27:50 As of this point the attendees have been +1.646.845.aaaa, +1.609.258.aabb, eberkower, jchester2, Yianni, +44.772.301.aacc, npdoty, +1.404.385.aadd, Fielding, Chris_IAB?, 17:27:50 ... +1.917.934.aaee, JeffWilson, vinay, +1.202.222.aaff, RichardWeaver, phildpearce, dwainberg, schunter, [CDT], sidstamm, adrianba, +33.6.50.34.aagg, [Microsoft], vincent, 17:27:53 right, to the mailing list 17:27:54 ... +1.215.480.aahh, Aleecia, +31.65.141.aaii, rvaneijk, moneill2, +1.202.787.aajj, efelten?, WaltM_Comcast, hefferjr, SusanIsrael, +1.202.347.aakk, Brooks, prestia, 17:27:54 ... +1.650.465.aall, +1.408.836.aamm, Chris_Pedigo, kulick, Rigo, David_MacMillan, Jonathan_Mayer, +49.431.98.aann, ninjamarnau, +1.646.666.aaoo, Chapell, +1.650.365.aapp, 17:27:54 ... johnsimpson, Joanne, [FTC], hwest, +1.415.627.aaqq, laurengelman, peterswire?, +1.303.652.aarr 17:27:54 -schunter 17:27:57 -Chapell 17:27:58 -eberkower 17:28:08 Meeting: Tracking Protection Working Group teleconference 17:28:13 chair: schunter 17:28:22 rrsagent, please draft the minutes 17:28:22 I have made the request to generate http://www.w3.org/2013/04/17-dnt-minutes.html npdoty 17:29:00 -npdoty 17:29:26 -Chris_IAB? 17:29:27 T&S_Track(dnt)12:00PM has ended 17:29:27 Attendees were +1.646.845.aaaa, +1.609.258.aabb, eberkower, jchester2, Yianni, +44.772.301.aacc, npdoty, +1.404.385.aadd, Fielding, Chris_IAB?, +1.917.934.aaee, JeffWilson, vinay, 17:29:27 ... +1.202.222.aaff, RichardWeaver, phildpearce, dwainberg, schunter, [CDT], sidstamm, adrianba, +33.6.50.34.aagg, [Microsoft], vincent, +1.215.480.aahh, Aleecia, +31.65.141.aaii, 17:29:28 ... rvaneijk, moneill2, +1.202.787.aajj, efelten?, WaltM_Comcast, hefferjr, SusanIsrael, +1.202.347.aakk, Brooks, prestia, +1.650.465.aall, +1.408.836.aamm, Chris_Pedigo, kulick, 17:29:28 ... Rigo, David_MacMillan, Jonathan_Mayer, +49.431.98.aann, ninjamarnau, +1.646.666.aaoo, Chapell, +1.650.365.aapp, johnsimpson, Joanne, [FTC], hwest, +1.415.627.aaqq, 17:29:28 ... laurengelman, peterswire?, +1.303.652.aarr 17:29:53 rrsagent, please draft the minutes 17:29:53 I have made the request to generate http://www.w3.org/2013/04/17-dnt-minutes.html npdoty 17:52:30 rvaneijk has joined #dnt 18:31:12 BillScannell has joined #dnt 18:43:52 schunter has joined #dnt 19:00:31 schunter has joined #dnt 19:57:02 Zakim has left #dnt 21:37:24 schunter has joined #dnt 22:34:22 npdoty has joined #dnt