W3C home > Mailing lists > Public > public-tracking@w3.org > June 2012

agenda: 6 June 2012 call

From: Aleecia M. McDonald <aleecia@aleecia.com>
Date: Tue, 5 Jun 2012 16:05:37 -0700
Message-Id: <678ABBA2-4F9B-4E2C-9E48-BBFE2CE0DA37@aleecia.com>
To: "public-tracking@w3.org (public-tracking@w3.org)" <public-tracking@w3.org>
Chair:		Aleecia
Main topic:	Picking up the compliance for user agents concept from last week, plus "collection" if time allows

---------------------------
Administrative
---------------------------

1. Selection of scribe

2. Any comments on minutes: http://www.w3.org/2012/05/23-dnt-minutes

3. Quick check that callers are identified, which was wonderfully brief last time

---------------------------
Old business
---------------------------

4.  Review of overdue action items:  https://www.w3.org/2011/tracking-protection/track/actions/overdue

---------------------------
New business
---------------------------

5.   Reminders: 	2 weeks until F2F in Seattle. 
				1 weeks until registration closes (https://www.w3.org/2002/09/wbs/49311/tpwg-belle-f2f/)

6.  Continued discussion around new issue-149, Compliance section for user agents (https://www.w3.org/2011/tracking-protection/track/issues/149)
      Discussion will contain related issues and some of the email conversations around defaults

7.   If we time allows, Roy has proposed a new text for what "collection" should mean (action-166). Rather than:
		A party collects data if the data comes within its control.
		A party retains data if the data remains within the party's control.

	Roy proposes (http://lists.w3.org/Archives/Public/public-tracking/2012May/0282.html): 
		Data collection" (for the purpose of DNT) is the process of assembling data from or about one or more network interactions and retaining/sharing that data beyond the scope of responding to the current request or in a form that remains linkable to a specific user, user agent, or device.

	David proposes 
		1. "is exposed to": data that the service sees without taking any specific action,usually, the data arrives whether the service wanted it or not;
		2. "collects": the service takes specific action to acquire the data;
		3. "retains": the service holds the data after the immediate transaction is complete;

	Step 0: discussion of why the current split between "collects" and "retains" is insufficient. It may be that what we are really after here is replacing several occurrences of "collects" with "retains" but the current definitions are fine. I am reluctant to re-open this discussion until I have a better understanding of why there is a problem. (Yes, Roy, I have read your messages -- I am not seeing why you think "collects" is far away from a normal meaning when it appears far closer than the definition you suggest, which seems more like an attempt to define the scope of DNT than to define collection. It is likely I am missing something, so talking on the call will be useful.)

---------------------------

8. Announce next meeting & adjourn

================ Infrastructure =================

Zakim teleconference bridge:
VoIP:    sip:zakim@voip.w3.org
Phone +1.617.761.6200 passcode TRACK (87225)
IRC Chat: irc.w3.org, port 6665, #dnt

*****
Received on Tuesday, 5 June 2012 23:06:05 UTC

This archive was generated by hypermail 2.3.1 : Friday, 21 June 2013 10:11:30 UTC