- From: Aleecia M. McDonald <aleecia@aleecia.com>
- Date: Sat, 29 Sep 2012 22:48:43 -0700
- To: Justin Brookman <jbrookman@cdt.org>, Nick Doty <npdoty@w3.org>
- Cc: "public-tracking@w3.org (public-tracking@w3.org)" <public-tracking@w3.org>
- Message-Id: <6C2A37A2-808B-41FF-ADD0-C8FDF6087C9C@aleecia.com>
My only question on Justin's text below is about the wording "communication to a third party" -- that suggests communication to a first party or a service provider is permissible. I think the intent is "communication to another party." If so, is that an acceptable change? Nick, in particular: does Justin's language capture what you had intended? If we have agreement that Justin's edits are a better reflection, I suggest we also rework the second text option to mirror this as well, replacing only "6 weeks" with "They MUST provide public transparency of their data retention period, which MUST have a specific time period (e.g. not infinite or indefinite.)" to reflect the second view we have heard, and possibly replacing "6 weeks" with "2 weeks" for a third option if John continues with that path. Normally we would do a quick discussion on the next phone call, or nail this down via email in short order. However, I recognize many of us are traveling for the f2f, and asking for quick turn around times will not work this week when people are on flights. We do not have a time on the f2f agenda specifically for this issue. However, we may just be a five minute conversation away from being ready to revise the texts. I will see if I can find a few minutes for a quick sense of the room to make sure the revisions reflect the options before us. We will not agree to texts in Amsterdam and then go straight to a call for written objections -- we will still build in at least two days for comments on the revisions. Aleecia On Sep 28, 2012, at 6:59 PM, Justin Brookman <jbrookman@cdt.org> wrote: > I would expand Option 1 to say (something like): > > Operators MAY retain data related to a communication in a third-party context for up to 6 weeks. During this time, operators may render data unlinkable (as described above), perform processing of the data for any of the other permitted uses, or perform any other processing that does not result in the transfer of information related to the particular user or communication to a third party, or alteration of the user's individual experience. > > (I believe this is more consistent with Ian's original formulation, though it's possible he has since changed his mind. Obviously, as David Wainburg points out, this language is contingent upon the scope permitted uses and the definition of whatever replaces unlinkable.) > From: Aleecia M. McDonald [mailto:aleecia@aleecia.com] > To: public-tracking@w3.org (public-tracking@w3.org) [mailto:public-tracking@w3.org] > Sent: Tue, 25 Sep 2012 18:20:57 -0500 > Subject: Poll text call: final text by 28 September > > From the call on 12 September, we discussed topics where we have increasing clarity on options for permitted uses. I want to make sure we have the text right to reflect our options prior to doing a decision process with a poll calling for objections, which is responsive to Ian's feedback. We also want to move quickly, as Roy suggests. > > Please propose specific alternative text if you believe that the two texts given below do not reflect the options before us by Friday, 28 September. We will briefly review these texts on the call tomorrow, just to make sure no one misses anything, and here we are on the mailing list, for those who cannot make the call. > > Aleecia > > ----- > Log files: issue-134 > ---- > > This normative text fits into the section on Third Party Compliance, subsection 6.1.1.1, Short Term Collection and Use, <http://www.w3.org/2011/tracking-protection/drafts/tracking-compliance.html#short-term>. We will also want non-normative text, and have some suggested, but that will be clearer once we have the normative text settled. (Options for definitions of unlinkable data are in section 3.6, Unlinkable Data, <http://www.w3.org/2011/tracking-protection/drafts/tracking-compliance.html#def-unlinkable>.) > > Option 1: > Operators MAY retain data related to a communication in a third-party context for up to 6 weeks. During this time, operators may render data unlinkable (as described above) or perform processing of the data for any of the other permitted uses. > > Option 2: > Operators MAY retain data related to a communication in a third-party context. They MUST provide public transparency of their data retention period, which MUST have a specific time period (e.g. not infinite or indefinite.) During this time, operators may render data unlinkable (as described above) or perform processing of the data for any of the other permitted uses.
Received on Sunday, 30 September 2012 05:49:33 UTC