- From: Matthias Schunter (Intel Corporation) <mts-std@schunter.org>
- Date: Thu, 22 Sep 2016 12:09:58 +0100
- To: "public-tracking@w3.org (public-tracking@w3.org)" <public-tracking@w3.org>
(Editorial) Changes to TPE - Change fingerprinting section and extend it to a privacy and security section - Allow HTTP Equiv (change to section 5.2; proposed text by Mike ONeil) Paste from Mikes Document? - No change to "DNT Extensions" - leave it at risk but do nothing for now - Change definition of "enabled" to also include exceptions: Once you recorded an exception, you implicitly enabled the feature. - Check whether all fields in the tracking status object have actual value in real- life - Add question: on call-back mechanism for exception API. Site could be informed whether their request for an exception has been granted or declined or that the user agent chooses to give no indication. Maybe using promises? - We should mark the cookie-like wildcards in the exceptions as a feature at risk. - We should consider making explicit targets mandatory or else drop the features. Reason for this feature was that a company may have a list of companies with contractual relationships and would want to extend a site-wide exception only to those. - Ask Rob whether there are any changes required for GDPR compliance (e.g. terms definitions that are so broken they do not work) - An EU compliance document may need define a set of qualifiers that provide transparency for EU users.
Received on Thursday, 22 September 2016 11:10:33 UTC