Re: tracking data (was Re: [TCS] comments on 17 Feb 2015 editors draft)

I think everyone needs to look carefully at the message I wrote. Please comment specifically on the usage within the two specs, not your assumptions about what the phrase might mean.

Of the nine occurrences of that phrase, two are in TPE and are replaceable, four in TCS are contradicting the normative definition they are supposed to explain and will be removed, and the rest in TCS are redundant, IIRC.

There is no need to define a term that isn't used, so that seems to be the easiest way forward. There certainly is no justification to invent yet another definition of tracking that contradicts the one we already have.

Unfortunately, I just boarded a flight to DC and won't be able to attend a teleconference  tomorrow if we have one.

....Roy


> On Mar 31, 2015, at 9:53 AM, Mike O'Neill <michael.oneill@baycloud.com> wrote:
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> [I posted this to the wrong list - here it is again]
> 
> Roy,
> 
> I am sure it is possible to rewrite the documents to remove references to “tracking data”, but I do not think this necessarily improves clarity. A developer needs to know what data his application should be designed to discard (or not collect) when DNT:1, and the answer should not be “check with your legal department”.
> 
> I think clarity would be better serviced getting the definition right. 
> 
> Your amendments describe it as both “data collected while tracking” and “data that enables tracking”, so why not make the definition that.
> 
> How about:
> 
> Tracking data is any information that enables a specific user agent to be recognised in different contexts, or which contains the user’s personal data collected in other contexts. 
> 
> If we need a definition of personal data, here is a reasonable one from the UK’s 1998 Data Protection Act:
> 
> “personal data” means data which relate to a living individual who can be identified— 
> (a)    from those data, or 
> (b)    from those data and other information which is in the possession of, or is likely to come into the possession of, the data controller, 
> and includes any expression of opinion about the individual and any indication of the intentions of the data controller or any other person in respect of the individual;
> 
> 
> Mike
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.13 (MingW32)
> Comment: Using gpg4o v3.4.103.5490 - http://www.gpg4o.com/
> Charset: utf-8
> 
> iQEcBAEBAgAGBQJVGtEFAAoJEHMxUy4uXm2JsEMH/AyINdeKAL8HYhtqF/1OmpTH
> gX76ORRQjm0h7Wp92k1fp9+ILLDshtiEMrWl8S6ogiH+2QTisIcdK/YINRJ+V4xg
> 3butvu1G68+ALzd0evWTLzPYK7OHABsXr8DNrBUaHbJKGEqrouZvxlH2guGHgYiC
> 1SmdQQf47y3d6D9RyXxTuQ6YvrLsDfiTOg21C8zbn9NILIWtYrJC6Bpnlkaq1wK6
> V5keqayNo6gRdogv4c7GYpq2+xSfGkcoFWDX+G0XH5YH06SgWbNLuGhcggDeDL2/
> lF73PICXuuf4qn11un2w0I16Xsa8LvGVm1HU0Kdr6asXV/9tZrdd1ESp4RDZiEA=
> =zcJX
> -----END PGP SIGNATURE-----
> 
>

Received on Tuesday, 31 March 2015 17:54:41 UTC