16:04:14 RRSAgent has joined #dnt 16:04:14 logging to http://www.w3.org/2017/05/22-dnt-irc 16:04:16 RRSAgent, make logs world 16:04:16 Zakim has joined #dnt 16:04:18 Zakim, this will be TRACK 16:04:18 ok, trackbot 16:04:19 Meeting: Tracking Protection Working Group Teleconference 16:04:19 Date: 22 May 2017 16:04:45 at has joined #dnt 16:04:51 vincent__ has joined #dnt 16:04:55 present+ 16:05:05 dsinger has joined #dnt 16:06:08 present+ dsinger 16:06:25 Here 16:08:08 https://github.com/w3c/dnt/issues/21 16:08:39 More important than the proposal is a review of the motivation of the additional TPE elments and their intended use by implementors - across all parties included expected handling by UAs 16:08:49 there 16:08:56 their 16:09:57 mikeoneill has joined #dnt 16:10:03 q+ 16:10:14 present+ 16:13:00 A site that registers an exception MUST publish... 16:13:39 nice change indeed 16:14:28 i will change that after this meeting 16:16:04 Well stated David! 16:16:31 The TSR is meant to be dynamic, i.e. could be dependant on DNT 0 or 1 16:17:42 Machine readable = Tracking Protection LIst 16:18:07 q? 16:18:09 Starts as optional until the EU Data Protection Board attempts to mandate it in some fashion 16:18:13 q- 16:18:16 q+ aleecia 16:18:17 q+ 16:18:26 ack alee 16:18:39 Not trying to state it is P3P 16:19:02 +q 16:19:47 Happy to answer those questions 16:20:22 To be fair this conversation is a bit out of scope of DNT 16:20:46 https://github.com/w3c/dnt/issues/22 16:20:52 Our goal is to simplify EU compliance. More transparency may be a useful part of it. 16:22:26 DNT is not the end-all-be-all solution to EU compliance 16:22:47 Sure. This is why we only discuss one field ;-) 16:23:12 So at some point we need to focus on the goal of the DNT signal itself and not be pulled into rabbit holes for Tracking Protection Lists (otherParty) 16:24:36 ack ale 16:25:07 Concern by shane: Mis-use of otherParties as whitelist for blocking 16:25:33 q+ to ask (a) which way the otherParties array can be wrong (by omission, by inclusion); (b) what statement/promise is being made about these otherParties (to distinguish them from (i) parties in any exception call and (ii) parties visited but not mentioned.) 16:25:48 I do NOT see the otherParties property as a quid-pro-quo approach, i.e. blocking when DNT:1 is ignored. 16:26:03 This WG's charter was extended with a specific focus on the viability of TPE to address the requirements for managing cookie and tracking consent that satisfies the requirements of EU privacy legislation. 16:26:09 The otheParties text proposed is - I believe - an important buidling block for consent. It allows publishers but also, e.g., embedded resources to make representations in a machine readable format. 16:26:15 I proposed an optional field. Yahoo! does not have to use the otherParties property, just as there is no obligation to use the sameParty property. 16:26:49 ptherParties is site-specific (it relates to the site). Tracking Protection Lists were web-wide as implemented by MS and FF (I beleive) 16:27:04 The list Shane is talkig about fits nicely in the sameParty/otherParty array. 16:27:22 fwagner has joined #dnt 16:27:24 ... in a (sub)domain format 16:28:30 ack mi 16:28:37 q- 16:29:34 ack d 16:29:34 dsinger, you wanted to ask (a) which way the otherParties array can be wrong (by omission, by inclusion); (b) what statement/promise is being made about these otherParties (to 16:29:37 ... distinguish them from (i) parties in any exception call and (ii) parties visited but not mentioned.) 16:30:28 And more importantly - what happens if the list is “wrong”? Does the DNT signal change in someway? Again, the otherParty list appears to have no utility with respect to the DNT signal. 16:30:43 q? 16:30:43 q? 16:31:39 What if my Site Specific exception list includes a domain not in the otherParty list? Or the other way around? How is the DNT signal impacted? 16:32:17 so, if present, the otherParties array MUST include all otherParties that might appear (recursively, by inclusion) on the site. 16:33:16 Q+ 16:35:05 can we see a precise proposed text, please (before a formal CfO)? 16:35:20 next week: final text proposals 16:35:31 in 2 weeks: objecttions (substantiated) 16:35:32 So conflict with the Site Specific exception list, no direct bearing on the DNT signal, and looks/feels/smells very much like a TPL 16:35:41 afterwards: chairs discuss and determine consensus 16:36:29 We support human readable lists 16:39:16 When does the charter run out? 16:41:29 wileys, the charter runs until end of the year. 16:44:16 RRSAgent, make minutes v2 16:44:16 I have made the request to generate http://www.w3.org/2017/05/22-dnt-minutes.html Bert 16:45:16 wileys has left #dnt 17:33:03 present+ Alan Toner, Matthias Schunter, Frank Wagner, Rob van Eijk, Brendan Riordan-Butterworth, Vincent Toubiana, Shane Wiley, Aleecia McDonald 17:33:06 RRSAgent, make minutes v2 17:33:06 I have made the request to generate http://www.w3.org/2017/05/22-dnt-minutes.html Bert 17:34:03 scribenick: nobody 17:34:04 RRSAgent, make minutes v2 17:34:04 I have made the request to generate http://www.w3.org/2017/05/22-dnt-minutes.html Bert 17:35:44 chair: Matthias Schunter 17:35:45 RRSAgent, make minutes v2 17:35:45 I have made the request to generate http://www.w3.org/2017/05/22-dnt-minutes.html Bert 18:00:35 at has joined #dnt 18:06:25 RRSAgent, bye 18:06:25 I see no action items