15:37:43 RRSAgent has joined #dnt 15:37:43 logging to http://www.w3.org/2014/04/09-dnt-irc 15:37:45 RRSAgent, make logs world 15:37:47 Zakim, this will be TRACK 15:37:47 ok, trackbot; I see T&S_Track(dnt)12:00PM scheduled to start in 23 minutes 15:37:48 Meeting: Tracking Protection Working Group Teleconference 15:37:48 Date: 09 April 2014 15:38:43 agenda? 15:49:32 chair: Carl Cargill 15:51:45 npdoty has joined #dnt 15:51:58 jeff has joined #dnt 15:55:08 Zakim, who is on the phone? 15:55:08 T&S_Track(dnt)12:00PM has not yet started, npdoty 15:55:10 On IRC I see jeff, npdoty, RRSAgent, Zakim, ninja, hober, walter, wseltzer, trackbot 15:55:21 T&S_Track(dnt)12:00PM has now started 15:55:28 +npdoty 15:55:43 JackHobaugh has joined #dnt 15:56:13 eberkower has joined #dnt 15:57:04 +Carl_Cargill 15:57:24 fielding has joined #dnt 15:57:25 zakim, call ninja-office 15:57:25 ok, ninja; the call is being made 15:57:26 +Ninja 15:57:32 +Wendy 15:57:50 +Fielding 15:58:35 Carl has joined #dnt 15:59:13 zakim, agenda? 15:59:13 I see 7 items remaining on the agenda: 15:59:14 1. Confirmation of scribe. Volunteers welcome! [from ninja] 15:59:14 2. Offline-caller-identification [from ninja] 15:59:14 3. Suggested editorial changes to the TPE Editor's draft [from ninja] 15:59:14 4. Announcement of two week call for consensus for TPE Last Call [from ninja] 15:59:14 5. Publication of TCS Public Working Draft [from ninja] 15:59:15 6. ISSUE-207: Conditions for dis-regarding (or not) DNT signals [from ninja] 15:59:15 7. AoB [from ninja] 15:59:19 dsinger has joined #dnt 15:59:21 sidstamm has joined #dnt 15:59:38 +[IPcaller] 15:59:39 hi all, I can't dial in today but will be watching irc 15:59:48 zakim, [ipcaller] is me 15:59:48 Zakim, who is on the phone? 15:59:49 +dsinger; got it 15:59:49 On the phone I see npdoty, Carl_Cargill, Ninja, Wendy, Fielding, dsinger 15:59:54 thanks, sidstamm! 16:00:03 regrets+ sidstamm 16:00:10 Ari has joined #dnt 16:00:16 + +1.312.340.aaaa 16:00:37 312.340 is Ari from Rocket Fuel 16:00:51 volunteers to scribe today? 16:01:02 dwainberg has joined #dnt 16:01:03 +Jack_Hobaugh 16:01:04 Chris_IAB has joined #dnt 16:01:05 WileyS has joined #dnt 16:01:15 kulick has joined #dnt 16:01:16 zakim, aaaa is Ari 16:01:16 +Ari; got it 16:01:18 +Mike_Zaneis 16:01:21 +eberkower 16:01:35 Zakim, please mute me 16:01:35 eberkower should now be muted 16:01:38 moneill2 has joined #dnt 16:01:38 Mike_Zaneis has joined #dnt 16:01:40 +dwainberg 16:01:49 +WileyS 16:02:11 +??P15 16:02:13 +Chris_Pedigo 16:02:14 +kulick 16:02:22 +[IPcaller] 16:02:42 zakim,[IPcaller] is me 16:02:42 +moneill2; got it 16:02:58 zakim, who is here? 16:02:58 On the phone I see npdoty, Carl_Cargill, Ninja, Wendy, Fielding, dsinger, Ari, Jack_Hobaugh, Mike_Zaneis, eberkower (muted), dwainberg, WileyS, ??P15, Chris_Pedigo, kulick, 16:03:02 ... moneill2 16:03:02 On IRC I see Mike_Zaneis, moneill2, kulick, WileyS, Chris_IAB, dwainberg, Ari, sidstamm, dsinger, Carl, fielding, eberkower, JackHobaugh, jeff, npdoty, RRSAgent, Zakim, ninja, 16:03:02 ... hober, walter, wseltzer, trackbot 16:03:03 +SusanIsrael 16:03:15 susanisrael has joined #dnt 16:03:19 zakim, please choose a scribe 16:03:20 Not knowing who is chairing or who scribed recently, I propose dsinger 16:03:22 matt has joined #dnt 16:03:30 \ 16:03:32 Marc_ has joined #dnt 16:03:33 +Jeff 16:03:40 +MattHayes 16:03:51 zakim, please choose a scribe 16:03:52 Not knowing who is chairing or who scribed recently, I propose Mike_Zaneis 16:03:54 kj has joined #dnt 16:03:54 +??P20 16:04:13 zakim, ??p20 is schunter 16:04:14 +schunter; got it 16:04:28 +Peder_Magee 16:04:45 <_3538> _3538 has joined #dnt 16:04:55 I'll scribe - I'll take bullet for the team 16:04:57 vinay has joined #dnt 16:05:05 scribenick: WileyS 16:05:13 +vinay 16:05:17 chair: Carl 16:05:21 fzakim, who is here? 16:05:32 zakim, who is here? 16:05:32 On the phone I see npdoty, Carl_Cargill, Ninja, Wendy, Fielding, dsinger, Ari, Jack_Hobaugh, Mike_Zaneis, eberkower (muted), dwainberg, WileyS, ??P15, Chris_Pedigo, kulick, 16:05:32 zakim, who is here? 16:05:33 Ninja: calls are now shorter - only 1 hour 16:05:36 ... moneill2, SusanIsrael, Jeff, MattHayes, schunter, Peder_Magee, vinay 16:05:36 On IRC I see vinay, _3538, kj, Marc_, matt, susanisrael, Mike_Zaneis, moneill2, kulick, WileyS, Chris_IAB, dwainberg, Ari, sidstamm, dsinger, Carl, fielding, eberkower, 16:05:36 ... JackHobaugh, jeff, npdoty, RRSAgent, Zakim, ninja, hober, walter, wseltzer, trackbot 16:05:36 http://www.w3.org/2011/tracking-protection/drafts/tracking-dnt.html 16:05:38 On the phone I see npdoty, Carl_Cargill, Ninja, Wendy, Fielding, dsinger, Ari, Jack_Hobaugh, Mike_Zaneis, eberkower (muted), dwainberg, WileyS, ??P15, Chris_Pedigo, kulick, 16:05:39 ... moneill2, SusanIsrael, Jeff, MattHayes, schunter, Peder_Magee, vinay 16:05:39 On IRC I see vinay, _3538, kj, Marc_, matt, susanisrael, Mike_Zaneis, moneill2, kulick, WileyS, Chris_IAB, dwainberg, Ari, sidstamm, dsinger, Carl, fielding, eberkower, 16:05:42 ... JackHobaugh, jeff, npdoty, RRSAgent, Zakim, ninja, hober, walter, wseltzer, trackbot 16:05:42 +hefferjr 16:05:51 Carl: Are we ready to start. Simple agenda today. Assuming everyone has the agenda 16:05:54 robsherman has joined #dnt 16:05:59 zakim, agenda? 16:05:59 I see 7 items remaining on the agenda: 16:06:00 1. Confirmation of scribe. Volunteers welcome! [from ninja] 16:06:00 2. Offline-caller-identification [from ninja] 16:06:00 3. Suggested editorial changes to the TPE Editor's draft [from ninja] 16:06:00 4. Announcement of two week call for consensus for TPE Last Call [from ninja] 16:06:01 5. Publication of TCS Public Working Draft [from ninja] 16:06:01 6. ISSUE-207: Conditions for dis-regarding (or not) DNT signals [from ninja] 16:06:01 7. AoB [from ninja] 16:06:05 zakim, take up agendum 3 16:06:05 agendum 3. "Suggested editorial changes to the TPE Editor's draft" taken up [from ninja] 16:06:17 +robsherman 16:06:22 ...suggest editorial changes to the draft, announcement of 2 weeks to Last Call 16:06:42 Could Roy step through the three changes he made this morning to the TPE? 16:06:46 ...quite a bit of discussion on the list on the Plug-In API issue 16:06:59 Brooks has joined #dnt 16:07:00 q+ 16:07:18 ...any editorial changes that people feel are vitally necessary to make this a viable document. 16:07:29 +Brooks 16:07:40 Ninja: still an unidentified IP caller - please identify or we'll drop you. Nick, please... 16:07:42 I joined from a private #, but not an IP # 16:08:01 Nick: Double checking - not referring to mine 16:08:02 Chapell has joined #DNT 16:08:18 Roy: MIME types is the antiquated term - have been called Media types for 15 years now 16:08:19 Chris_IAB, that's probably you 16:08:24 great, thanks. 16:08:34 Carl, that takes care of that. 16:08:35 q+ 16:08:37 q+ 16:08:41 "application/tracking-status+json" sounds good to me. 16:08:43 q- 16:08:48 q+ Chris_IAB 16:08:53 ack Chris_IAB 16:08:55 Just to confirm the edit we discussed in email (Nick's issue) 16:09:21 Chris M: Editorial speaking to have a working technical document - I don't believe we should have the definitions of Tracking and Context in the document. 16:09:24 +Chapell 16:09:27 q+ 16:09:30 Editorially speaking, I do not think we need the definitions of tracking or context in the TPE 16:09:46 robsherman has joined #dnt 16:09:51 Roy: Generally speaking, editorial changes dont alter decisions made by the working group. Issue-5 to be specific here 16:09:52 robsherman has joined #dnt 16:09:59 …in order to have a working TECHNICAL specification 16:10:03 issue-5 and issue-240, I believe we're referring to 16:10:04 Carl: So you are saying this is substantive change? 16:10:06 Roy: Yes 16:10:18 it would also take a very careful read to determine whether every instance of 'tracking' in the document was only using it in its normal english meaning 16:10:24 ack ninja 16:10:28 Roy: Unless there is new information offered we're not going to discuss it 16:10:40 that's right, they are COMPLIANCE related, not technical\ 16:10:42 I would guess that half of the people on this IRC agree with Chris, if not more. 16:10:44 WileyS has joined #dnt 16:10:52 q+ 16:10:54 ...it would be editorial only if the term were unused, alas 16:10:57 it would be an editorial change for a TECHNICAL document 16:11:05 cOlsen has joined #dnt 16:11:08 q? 16:11:09 and it is a closed issue, so this is not the time to discuss it. If it is still considered an objection, then a formal objection is called for at LC. 16:11:12 Ninja: I know you're not happy with these compliance terms in the TPE 16:11:15 By Committee, do you mean working group? 16:11:19 Carl: So these won't be changed 16:11:29 how is it a substantive change? 16:11:45 +[FTC] 16:12:02 Ninja: I wanted to bring up the UA Extensions discussion on the Mail List. I wanted to ask Roy for the outcome of these discussions. What text did he include. 16:12:12 WileyS has joined #dnt 16:12:28 Marc_, Carl sometimes using "committee" as a generic term for working groups, I think 16:12:28 User agents often include user-installable extensions, also known as add-ons or plug-ins, that are capable of modifying configurations and making network requests. From the user's perspective, these extensions are considered part of the user agent and ought to respect the user's configuration of a tracking preference. However, there is no single standard for extension interfaces. A user agent that supports extensions SHOULD also provide an appropriate mechanism for 16:12:29 such extensions to determine the user's tracking preference. 16:12:29 (the last sentence, in particular) 16:12:32 I keep getting disconnected - someone else will need to take over as Scribe. Not sure what the issue is. 16:12:32 (there are 283 occurrences of 'tracking' in the TPE!) 16:12:33 New text: A user agent that supports extensions SHOULD also provide an appropriate mechanism for such extensions to determine the user's tracking preference. 16:12:35 +q 16:12:46 scribenick: npdoty 16:12:59 ack ninja 16:13:02 fielding: new text; MUST to SHOULD, makes sense, a social requirement rather than a protocol requirement 16:13:38 Thank you Nick!!! So sorry - I was fully committed by my IRC client doesn't want to cooperate 16:13:43 ... instead of providing an API, "appropriate mechanism", variety of potential implementations 16:13:48 WileyS has joined #dnt 16:14:16 ... capacity for plugins to understand the UA-set preference for tracking, if they're not using the browser stack for making that request 16:14:29 ... seemed like that satisfied those who had previously commented 16:14:58 npd_not_scribe: +1 on fielding's revised text 16:15:04 rvaneijk has joined #dnt 16:15:04 ack JackHobaugh 16:15:11 hober has joined #dnt 16:15:19 I think we should open an issue on this question, so we don't lose track of it and think some more 16:15:26 * i think everyone owes npdoty a beer 16:15:26 JackHobaugh: a lot of emails back and forth on this topic yesterday, obvious that there's not a consensus on the issue in the WG 16:15:30 q+ 16:15:34 q- 16:15:39 everybody was fine with SHOULD 16:15:40 robsherman has joined #dnt 16:15:42 ... needs more discussion in the group before we make these types of changes 16:15:45 JackHobaugh, I am sorry, but most of the discussion was not ON topic 16:15:57 ... need to open this up for discussion within the group 16:16:00 This issue requires further discussion within the working group. 16:16:12 q+ 16:16:16 Let's record it as a non-last-call Issue? 16:16:18 fielding: lots of the conversation wasn't on topic; don't want to postpone because of irrelevant discussion 16:16:44 ... depends on the definition of user agent; I thought I was just rephrasing an existing requirement 16:17:04 ... david thought of UA as different, and so we found a better phrasing 16:17:05 It seems that implementation for User Agents is critical, no? 16:17:18 ... only affects UA implementations 16:17:25 JackHobaugh: can you explain the motivation? 16:17:31 Roy, Know vs. Set - I think that's the confusion. 16:17:36 fielding: we had a loosely phrased section before about plugins 16:17:53 ... had had several conversations before, we wanted some way to communicate to plugins, but plugin interfaces aren't standard 16:17:53 I think it used to say "User agents often include user-installable component parts, commonly known as plug-ins or browser extensions, that are capable of making their own network requests. From the user's perspective, these components are considered part of the user agent and thus ought to respect the user's configuration of a tracking preference. However, plug-ins do not normally have read access to the browser configuration." 16:18:19 -SusanIsrael 16:18:20 ... so when I merged in that section, I added a simple requirement to add an API for that purpose, without specifying the API itself 16:18:22 +rvaneijk 16:18:37 so, "ought to" became "should" and "respect the user" became "some mechanism"... 16:19:02 ... restatement of what we already say, that you must set the DNT header field when the user enables it for the user agent, but can only send it when you know 16:19:23 ... any browser that has extensions wouldn't be able to comply with the protocol, which is an outcome we wouldn't want 16:19:55 ... alternative would be separately setting the DNT header for every plugin installed (perhaps even by default) in their browser, or losing the universal choice 16:20:12 q? 16:21:12 -q 16:21:19 ... need a way to spread that throughout the user agent; adding this to the section is a note to developers that they should think about that and an implementation should consider that if they want plugins to use it 16:21:49 JackHobaugh: believe we need further discussion of the issue, not just the mailing list discussion, and go through the Call for Objections process 16:21:50 q+ on the must/should 16:22:17 fielding: if people disagree, should raise an objection; if people agree, don't need to 16:22:26 ... don't think an extra week will help us 16:22:41 JackHobaugh: object to the must being changed to a should as an editorial change 16:23:04 fielding: as editor, I'm not necessarily making purely editorial changes 16:23:24 yes 16:23:29 dwainberg: I thought we'd agreed as a group not to make any substantive changes, but have comments on other issue 16:24:07 dsinger: should open an ISSUE, but don't need to block Last Call on it; could discuss it during Last Call 16:24:19 Isn't the point not to discuss it in last call? 16:24:29 ... implementation experience from browsers/operating systems would be useful 16:24:32 q- 16:24:45 issue in our issue database 16:24:54 Disagree - that's the same as punting to v2 16:24:56 Do we do call for objections first and then proceed to last call? 16:24:56 Carl: as dsinger proposed, create an issue to address later. does anyone object to that? 16:25:04 q+ WileyS 16:25:14 q- support for dsinger's suggestion 16:25:17 to WileyS, no, we can make changes as a result of feedback in last call, for example 16:25:20 Somewhat related to the discussion at hand, does anyone see the outcome from ISSUE-153 (option B from https://www.w3.org/2002/09/wbs/49311/tpwg-addons-153/) in the TPE (http://www.w3.org/2011/tracking-protection/drafts/tracking-dnt.html) ? 16:25:25 q- 16:25:28 ack WileyS 16:25:49 like I said, the MUST already existed (and still exists) since the user agent was already required to send DNT on all HTTP requests when DNT:1 or DNT:0 is enabled 16:26:00 WileyS: dsinger, your suggestion would automatically punts this to version 2. won't work on any open issues for this during Last Call 16:26:15 dsinger: we can choose to work on issues that we choose to 16:26:17 No, Shane is correct. That is what was stated before. Let's be clear. 16:26:33 vincent has joined #dnt 16:26:44 WileyS: if we're not working on any open issues during Last Call, then I'd object to pushing it to v2 16:26:44 I think going to last call with this open issue is a bad idea. 16:27:22 I don't believe we can move to Last Call with this significant of an Open Issue 16:27:26 I agree that going to last call with this open issue is a bad idea 16:27:40 ninja: had said before that we wouldn't have open issues into Last Call; editors' draft we can work on, but Last Call Working Draft is stable for the two months of the public review period for Last Call 16:27:57 WileyS has joined #DNT 16:28:03 wseltzer: goal is substantial agreement upon in order to release for public comment; no up front that it's not perfect 16:28:30 ... one word change doesn't seem blocking 16:28:31 Wendy, it was a “MUST” to a “SHOULD” 16:28:35 we are clearly going to continue to realize things we ought to discuss 'at some point of our choosing'. We'll never bail the boat completely dry 16:28:38 +vincent 16:29:15 wseltzer: an "ought to" to a "MUST" was noticed; then to a "SHOULD" scaling back a normative requirement; clarification of language that already existed 16:29:28 fielding: basically, yes 16:29:47 Understood Wendy, but the “MUST” is what we reviewed last week as the document going to Last Call, correct? 16:29:49 David, loved how you used "ought" in that statement :-) 16:30:05 carl: achieved an understanding if not an agreement; change was a clarification 16:30:15 so rephrasing a must to a should is not substantive, it's just a clarification? That makes no sense at all in the context of this document. 16:30:23 -robsherman 16:30:23 Carl - a formal objection has been raiseed. Are you able to close that defacto? 16:30:24 ... want to declare this closed for the moment, can continue with dsinger's proposal regarding issue 16:31:03 Carl - Does this mean we're going to return to the "MUST" for now? 16:31:06 ... if further discussion is merited, we can have that. would like to move to other comments on the q 16:31:09 ack dwainberg 16:31:11 q- 16:31:17 jeff, the LC document says SHIULD currently 16:31:31 WileyS, A formal objection can only be raised after we decide to go to LC without changing the text, and that FO would go to the Director for resolution. 16:31:39 dwainberg: follow-up to Chris_IAB; shouldn't call this a "technical specification" because it's not a purely technical specification 16:32:27 dwainberg, we created the need to incorporate definitions, when the group decided to separate the two documents 16:32:46 ... charter describes a technical document and a compliance document that are separate; while I disagree with that, I think we should be careful when we discuss this in public to call it a "technical plus compliance document" 16:32:54 At least 8 people on this IRC agree with David Wainberg's point. 16:33:08 +9 16:33:15 +10 16:33:21 Roy, thank you for the clarification. 16:33:31 +11 16:33:43 carl: would take that under advisement; w3c works on technical specifications 16:33:57 dwainberg: agree, but this isn't a technical specification 16:34:29 fielding: documents (like HTTP) describe semantics, require definitions 16:34:52 paras 3 and 4 of which section? 16:35:04 dwainberg: my second point, as an editorial change suggest that we pare down the Introduction, specifically paragraphs 3 and 4 16:35:05 q? 16:35:15 section 1, para 3 and 4, to be replaced by what? 16:35:21 David, are you refering to these two paragraphs? 16:35:27 carl: we will consider that proposal 16:35:28 It has become common for Web site owners to collect data regarding the usage of their sites for a variety of purposes, including what led the user to visit their site (referrals), how effective the user experience is within the site (web analytics), and the nature of who is using their site (audience segmentation). In some cases, the data collected is used to dynamically adapt the content... 16:35:30 ...(personalization) or the advertising presented to the user (targeted advertising). Data collection often occurs through the insertion of tracking elements on each page. A survey of these techniques and their privacy implications can be found in [KnowPrivacy]. 16:35:31 People have the right to know how data about them will be collected and how it will be used. Empowered with that knowledge, individuals can decide whether to allow their online activities to be tracked and data about them to be collected. Many Internet companies use data gathered about people's online activities to personalize content and target advertising based on their perceived interests. Whil 16:35:33 e some people appreciate this personalization of content and ads, others are troubled by what they perceive as an invasion of their privacy. For them, the benefit of personalization is not worth their concerns about allowing entities with whom they have no direct relationship to amass profiles about their activities. 16:35:40 +[Microsoft] 16:35:49 -dwainberg 16:35:58 16:36:01 amyc has joined #dnt 16:36:06 can we be clear about what edit is being proposed, please? 16:36:09 carl: would look for some documentation 16:36:33 q? 16:36:48 q+ 16:37:23 what does that mean Wendy? 16:37:44 wseltzer: as a process, continuing to ask for technical objections, but seem to hear challenges that aren't technical objections but don't like the content of the document 16:37:44 Wendy - this is a technical specification - any objection to the text within the document is at its nature technical. 16:37:50 technical only objects are fine in a techical only spec 16:37:55 objections 16:38:01 Chris_IAB: how is that determined? 16:38:10 wseltzer: that is the open question, to be put before the group 16:38:17 q? 16:38:25 What is being put before the group? Please clarify that Wendy. 16:38:27 +q 16:38:39 ack kulick 16:38:46 Wendy, how will a call for consensus to go to last call be put before the group? 16:39:02 q? 16:39:08 q+ kulick 16:39:18 ack WileyS 16:39:44 WileyS: to wseltzer, we are talking about a technical specification and requirements in the technical specification 16:40:07 ... talking about plugin support; what should or shouldn't be in place 16:40:19 q+ 16:41:08 ... wseltzer, you and others interpret fixing things as delays; would rather have a good standard 16:41:27 I think we have tried to make the TPE spec about the protocol and punt compliance to the compliance document. If we missed somewhere, let's get it pointed out. 16:41:30 ... especially for server-side implementers; it's not helpful if browsers do something and servers don't do anything in response 16:42:11 carl: well put. all arguments have to be considered. i agree on being careful 16:42:22 q+ 16:42:33 thank you marissa 16:42:42 issue-153? 16:42:42 issue-153 -- What are the implications on software that changes requests but does not necessarily initiate them? -- closed 16:42:42 http://www.w3.org/2011/tracking-protection/track/issues/153 16:42:55 WileyS: to follow up, regarding issue-153 was to address this; we're not finding the text 16:43:12 q- 16:43:13 The outcome from ISSUE-153 (option B from https://www.w3.org/2002/09/wbs/49311/tpwg-addons-153/) does not appear to be presented in the TPE (http://www.w3.org/2011/tracking-protection/drafts/tracking-dnt.html). 16:43:21 ... if we can clear that up, would ease the discussion 16:43:41 here is the text: "A user agent that permits an extension or plug-in to configure or inject a DNT header is jointly responsible, with the plug-in or extension, for ensuring compliance to the extent possible." 16:43:56 < checking which editor was adding what > 16:44:05 this was after june 16:44:06 I don't think the edit made it into the document 16:44:10 this was way more recent 16:44:24 dsinger: comments from June, but has been edited 16:44:34 http://www.w3.org/2011/tracking-protection/drafts/tracking-dnt.html#determining 16:44:39 fielding: yes, has been edited since then, incorporated into changes we discussed last week 16:45:08 A user agent extension MUST NOT alter the tracking preference expression or its associated configuration unless the act of installing and enabling that extension is an explicit choice by the user for that tracking preference, or the extension itself complies with all of the requirements this protocol places on a user agent. 16:45:33 -Peder_Magee 16:45:42 ISSUE 153 results are here: http://www.w3.org/2014/02/12-dnt-minutes#item02 16:45:51 WileyS: had agreement from some browsers and us; responsibility to the extent possible ; but can't find that part of the text 16:46:31 ... have been looking through the editors' draft on the side 16:46:36 fielding: 9th para of section 3 16:46:50 but this was option B of 153 16:46:52 "A user agent that permits an extension or plug-in to configure or inject a DNT header is jointly responsible, with the plug-in or extension, for ensuring compliance to the extent possible." 16:47:01 WileyS: don't think that's the agreement from issue 153 16:47:24 it went to CFO and was decided 16:47:30 fielding: reframed language to put requirements on particular actors, the user agent, in this sense 16:47:33 +SusanIsrael 16:47:44 susanisrael has joined #dnt 16:48:21 fielding: wasn't that part for the compliance spec? 16:48:35 ISSUE-153 went through the call for objections process and there was a result found. 16:48:39 WileyS: it was a TPE discussion 16:48:59 fielding: not sure where we would put it in the TPE, if it's about user agent compliance 16:49:04 JackHobaugh, this CfO addressed another subquestion 16:49:37 WileyS: everyone agreed in v1 about as much as possible for the browser to be the source of the signal 16:50:15 fielding: not sure June Draft text is relevant 16:50:20 WileyS: but the concept is agreed upon 16:50:44 +1 16:50:52 q+ 16:51:00 q+ 16:51:00 around paragraph 7 or 8 16:51:10 fielding: don't think it adds anything, but don't mind adding it if we know where 16:51:28 dsinger: in section 3, among the plugins paragraphs 16:51:49 q? 16:51:51 https://www.w3.org/2002/09/wbs/49311/tpwg-addons-153/ 16:52:00 Chairs, please consider, that with respect to Roy's rebuttal to David Wainberg's point that "we didn't do that in the HTTP spec", I would say, sure, THAT working group hadn't decided to specifically bifurcate their compliance from their tech spec, WE HAVE. Accordingly, David W. is right-- all that stuff belongs in a compliance spec, not in the TECH spec. 16:52:14 dsinger: should doublecheck the history, but if we have agreement, then yes, we should add it 16:52:15 q+ 16:52:39 WileyS, isn't your point that we already decided this as a group? 16:52:48 fielding: confusion is that the extension is part of the user agent already; not sure what jointly responsible would mean 16:53:00 ... I think it's covered already 16:53:16 respectfully Roy, why was this not brought up in the CFO then 16:53:21 this was a decided issue 16:54:03 WileyS: extensions can add headers of their own; align settings about conflicting or double headers, that this was supposed to address 16:54:07 if this was already agreed to by the group, why are we having this debate now (on the substantive point of this issue)? 16:54:28 ... as opposed to rogue extensions doing something completely on their own, not coordinating the settings 16:54:47 ... not about compliance, just about turning on the signal and not sending mixed messages 16:54:57 Roy is right on terminology; the UA is the entire bundle of software. we don't have a word for the 'base' other than 'browser', but we've been criticized for being 'browser specific' before 16:55:35 fielding: if there's a requirement on the user agent, it's responsible to do so as a whole, however it's implemented or number of extensions 16:55:54 fielding, do you object the inclusion of this sentence? 16:56:13 "If the user-agent can be assembled from parts (e.g. using a base and plug-ins or extensions), and the extensions can ...." 16:56:18 222 16:56:21 ... "an implementation that invokes external processes is responsible for that" 16:56:31 s/222/ 16:56:41 WileyS: fine with using your alternate terms 16:56:50 ... agreement in the group, didn't even have to go to Call for Objections 16:57:16 WileyS: fielding, if you can just find the right words for it, that would be great 16:57:26 why are we re-hashing something that was already decided 16:57:46 didn't we just say that was not appropriate on the last discussion we just had 16:57:58 why would that apply there, but not here? 16:58:17 Wileys: we have user interface requirements, sometimes the business requirements are sufficient 16:58:37 schunter: could we just rephrase to say "user agent and its extensions" in place of "user agent" 16:58:54 good point Shane: this is a slippery slope, and some folks want to draw the lines on compliance vs. tech one way, and others differently. I've been pointing this fundamental flaw out ever since we made the decision to bifurcate the docs. 16:59:09 [Sounds to me that there is a need for "non-normative text" that the user agent includes plug-ins, etc.] 16:59:18 dsinger: "user agent" is the entire assembly, so we can get the same concept but with technically correct text 16:59:21 q? 16:59:23 -Ari 16:59:34 npdoty, was this a closed issue, by the working group? 16:59:41 kulick, I don't recognize this as a decided issue -- there was merely agreement to include a non-normative statement, which was later edited by me to be something that makes sense. 17:00:11 -hefferjr 17:00:12 ... if you assemble your user agent from pieces, need to make responsibility for all the pieces 17:00:18 CHAIRS: are we discussing a closed issue, or was it left open? 17:00:19 … that doesn't mean I did it right 17:00:46 npdnotscribe: Chris_IAB, yes issue-153 is closed, but we're discussing editorial changes to make sure we're using terms correctly 17:00:55 I'd like to see the text before we agree 17:01:01 action: dsinger to work with Roy to find the right sentence for issue-153 17:01:01 Created ACTION-447 - Work with roy to find the right sentence for issue-153 [on David Singer - due 2014-04-16]. 17:01:09 +1 17:01:28 Thank you Ninja 17:01:29 sure, Roy and I will circulate text as soon as we emerge (watch for smoke) 17:01:33 dsinger: make we sure add that sentence, but with the right terminology 17:01:37 worksforme 17:01:49 q? 17:01:49 Chris_IAB: want to see the text before agreeing 17:02:21 ninja: not asking for a Last Call decision today, about finishing the text and then ask to go to Last Call 17:02:24 npdoty, why in some cases, are we told that we can't discuss closed issues, but in other cases, the Chairs and staff allow substantive debate on other closed issues? 17:02:35 kulick: just want to make sure we don't lose track of this 17:02:44 q- 17:02:47 q- 17:02:50 ack kulick 17:03:10 -kulick 17:03:33 npdoty, that was not an editorial discussion 17:03:33 zakim, take up agendum 4 17:03:33 agendum 4. "Announcement of two week call for consensus for TPE Last Call" taken up [from ninja] 17:03:38 notscribe: Chris_IAB, kulick and WileyS raised it because they though the text didn't reflect the closed decision 17:03:42 Chris, I think we both discussed closed issues that the Chairs did not want to discuss, as well as closed issues that the Chairs wanted to discuss. 17:03:49 Carl and Team - Today's call was only scheduled for 60 mins and that ended 3 minutes ago 17:04:11 Chris, in the latter case, there was a difference between the decision that was made and what is in the draft - which caused the need for more discussion. 17:04:28 jeff, we were shut down previously on my proposed editorial change, because it was noted that the issue was previously closed and decided on by the working group 17:04:40 ninja: include these remarks from today; send out updated document as soon as possible, to ask you for group consensus to go to Last Call, ask by April 23 17:05:14 jeff, the process isn't being managed fairly-- that's plain to see 17:05:16 Chris, which one? Was that the one that the Chairs took under advisement? 17:05:31 carl: objections again, are based on technical issues, make the document unimplementable, for example 17:05:36 jeff, no, the one I made at the outset of the call 17:05:37 I still don't understand why the two paragraphs in section 3 do not satisfy the actual issue (without using the original text), but I don't have an opinion on adding more editorial text about joint responsibility (even though responsibility is a legal issue, not a technical one). 17:05:52 we were not allowed to discuss it further, per Carl 17:06:03 ... issues we're discussing aren't closed ones, but questions that prevent implementation 17:06:03 Chris, sorry. I forgot which one. Could you remind me - either here or in a separate channel? 17:06:21 q+ 17:06:24 ... consensus is not unanimity or economic factors (with legal implications) but questions for implementation/adoption 17:06:30 ack fielding 17:06:56 fielding: previous agenda item: one editorial change, to move 2.3 into introduction, existing introduction into a subsection 17:07:08 ... doesn't change any text, just moves things around in the document 17:07:24 ... so that the terms are available in the introduction, rather than a later section; want the terms up front 17:07:35 Jeff, sure, I asked for the editorial change to remove the definitions of tracking and context (and move them to a compliance document)-- this is not a substantive change, for a TECHNICAL document, which is supposed to be accompanied in practice, by a compliance document 17:07:48 carl: any comments or objections? 17:08:22 dsinger: seems atypical for formal terminology to be before the explanation of the document, but if the terms are used 17:08:24 Jeff, there is no technical/procedural requirement in a tech spec for these definitions 17:08:34 Chris_IAB, we discussed this decision extensively: It is necessary to define the scope and meaning of the signal sent by the user 17:08:47 fielding: section 2 is notational conventions, which usually doesn't have important terms 17:08:50 Jeff, if you removed them, folks could still follow the implementation guidelines without them 17:08:53 Chris, I looked back at the IRC notes. It does not seem to me that there was no discussion. It seems that there was a discussion, and it was pointed out that this input from you contradicted a previous WG decision. Am I mis-reading it? 17:09:14 ninja, I completely disagree that is is technically "necessary" 17:09:22 zakim, agenda? 17:09:22 I see 7 items remaining on the agenda: 17:09:23 1. Confirmation of scribe. Volunteers welcome! [from ninja] 17:09:23 2. Offline-caller-identification [from ninja] 17:09:23 3. Suggested editorial changes to the TPE Editor's draft [from ninja] 17:09:23 4. Announcement of two week call for consensus for TPE Last Call [from ninja] 17:09:23 5. Publication of TCS Public Working Draft [from ninja] 17:09:23 < listing of numbering of the sections > 17:09:24 6. ISSUE-207: Conditions for dis-regarding (or not) DNT signals [from ninja] 17:09:24 7. AoB [from ninja] 17:09:24 zakim, take up agendum 5 17:09:26 agendum 5. "Publication of TCS Public Working Draft" taken up [from ninja] 17:09:37 carl: we are over time 17:09:47 ninja: can we point to agendum 5 briefly 17:10:08 Jeff, that's because IRC was acting up 17:10:10 The TCS was a mess when we last left it. Are we going with the June Draft or the original Editors Draft of the TCS? 17:10:13 q+ 17:10:15 so I made my request verbally 17:10:21 ChrisPedigoOPA has joined #dnt 17:10:24 it should have been scribed 17:10:34 in any case, my point is certainly in the record now 17:10:37 carl: TPE would be Last Call WD; TCS would be a working draft to start with 17:10:45 I prefer the Editors Draft - but others may want the June Draft. How are we going to make a decision? 17:10:59 The definitions can go into either one 17:11:09 ninja: the document has been a mess, but chairs asked Nick to make updates based on group decisions 17:11:11 Fair - but we still need to decide which one to put forward 17:11:17 q+ 17:11:19 It doesn't answer my question 17:11:23 q+ 17:11:29 ack ninja 17:11:29 cOlsen has joined #dnt 17:11:51 WileyS: agree to put new definitions, even if I don't agree with all the definitions 17:11:58 "Latest editor's draft: 17:12:00 http://www.w3.org/2011/tracking-protection/drafts/tracking-compliance.html" 17:12:23 ... doesn't answer the basic question of, if we push a new Working Draft, are we going to go with the June draft or the latest editors' draft? 17:12:45 ack wseltzer 17:12:55 ... need to make a decision if publishing again 17:13:07 Decision on what base text to use: http://www.w3.org/2011/tracking-protection/2013-july-explanatory-memo/ 17:13:14 I believe the decision was made for us to be the one published as a WD. ;-) 17:13:31 Jeff, "It seems that there was a discussion, and it was pointed out that this input from you contradicted a previous WG decision." -- yes, that's how it went down, but when the same thing happened later, but it was Roy arguing the point, the Chairs let the substantive conversation go… THAT'S what I'm pointing out. Seems biased to me. 17:13:38 wseltzer: think we already made that decision, editors' draft, where nick has made updates 17:14:03 WileyS: doesn't represent the WG's position, but w3c staff and co-chairs of the time position 17:14:35 ... at the time, closed many of the issues we had opened, and then created new issues, did that all on their own, without the WG's participation 17:14:40 Chris, the reason it went on in the later case was because the current text in the draft disagreed with the WG decision. We were not debating the WG decision. We were trying to find the language to implement that decision in the draft. 17:14:52 ... why we had an uprising, a messy starting point 17:14:59 q? 17:15:33 carl: with metaphors, wasn't good, and we should make it less bad 17:15:35 q? 17:15:47 I object to the text in par 5.3.5 "Expecting further text on audience measurement. " 17:15:51 Jeff, that's exactly what Roy was arguing… he said things like, "it doesn't make sense to me", etc. He was arguing against the POINT that had been closed. Same same, but different treatment my friend. 17:15:57 Are there issues in the split can't be addressed in open issues against the current Editors' draft 17:16:02 WileyS: continental divide 17:16:05 s/draft/draft?/ 17:16:06 q+ 17:16:11 q+ 17:16:21 carl: need a lot of work to get it in shape 17:16:29 Carl, wseltzer, completely agree with Swiley on his current point 17:16:37 Chris, I agree - but the difference is that the editor controls the pen, so we needed to help him find words he could pen. That's what took longer. 17:16:50 WileyS: they sort of developed this consensus on their own 17:16:51 q? 17:17:10 Chris_IAB, the intent of the current draft is to encompass whatver decision was made, but that doesn't mean I understood that decision and the text that was proposed to close it. As editorial NON-NORMATIVE text, it is subject to my redrafting as editor based on my knowledge of the rest of the document. Again, that doesn't mean I redrafted it correctly. 17:17:15 jeff, I respectfully disagree with your assessment 17:17:21 q- 17:17:36 carl: start with draft wendy linked to, need to talk with co-chairs 17:17:39 q? 17:17:45 Chris, I respectfully accept your disagreement and likewise :) 17:18:03 ... discuss with the chairs if there is a mitigation 17:18:08 q+ 17:18:11 < more metaphors > 17:18:17 fielding, my point is that we didn't get to discuss other proposed changes in the same way you discussed this one. It's about fair play in consensus building. 17:18:24 Well done, Shane 17:18:36 -Mike_Zaneis 17:18:45 ack npdoty 17:19:24 June Draft + Changes 17:19:45 q- 17:19:50 Chris_IAB, you know full well that the definition of tracking is not editiorial and that the decision on ISSUE-5 specifically directs me to include it in TPE, so your suggestions otherwise are false,. 17:20:10 q- 17:20:12 Official editorial request before moving to last call: please remove the definitions of "tracking" and "context" from the TPE. 17:20:17 Nick, the discussion on audience measurements is too far from consensus to assume that "Expecting further text on audience measurement. 17:20:37 fielding, I no of no such thing, other than we disagree on it. 17:20:37 +1 to Rob 17:20:48 s/no of no/know of no/ 17:21:15 npdoty: < tried to explain current status, previous working draft publications, editorial changes; group consensus comes from working through issues and change proposals > 17:21:26 http://en.wikipedia.org/wiki/Excelsior_(Longfellow) 17:21:32 fielding, I also point out that the subsequent decision to include these definitions was in direct conflict with the earlier group decision to bifurcate the documents. 17:21:41 -SusanIsrael 17:21:42 -[FTC] 17:21:44 -rvaneijk 17:21:52 Have a great weekend everyone... 17:21:52 -Chris_Pedigo 17:21:54 -MattHayes 17:21:55 carl: close the call for today. fielding and dsinger to finish edits. ask for consensus on TPE Last Call. 17:21:56 -Wendy 17:21:58 thanks npdoty 17:21:58 -Ninja 17:21:58 [adjourned.] 17:21:59 -moneill2 17:21:59 -Carl_Cargill 17:22:00 -WileyS 17:22:00 -Jack_Hobaugh 17:22:02 -vinay 17:22:02 -Chris_IAB 17:22:02 -[Microsoft] 17:22:03 -vincent 17:22:04 -npdoty 17:22:06 Zakim, list attendees 17:22:06 -Brooks 17:22:06 As of this point the attendees have been npdoty, Carl_Cargill, Ninja, Wendy, Fielding, dsinger, +1.312.340.aaaa, Jack_Hobaugh, Ari, Mike_Zaneis, eberkower, dwainberg, WileyS, 17:22:06 ... Chris_Pedigo, kulick, moneill2, SusanIsrael, Jeff, MattHayes, schunter, Peder_Magee, vinay, hefferjr, robsherman, Brooks, Chris_IAB, Chapell, [FTC], rvaneijk, vincent, 17:22:06 ... [Microsoft] 17:22:13 rrsagent, please draft the minutes 17:22:13 I have made the request to generate http://www.w3.org/2014/04/09-dnt-minutes.html npdoty 17:22:22 -Jeff 17:22:53 -dsinger 17:22:55 -eberkower 17:24:33 -Chapell 18:30:50 JackHobaugh has joined #dnt 18:38:15 jeff_ has joined #dnt