ISSUE-136: Resolve dependencies of the TPE on the compliance specification

depends

Resolve dependencies of the TPE on the compliance specification

State:
CLOSED
Product:
Tracking Preference Expression (DNT)
Raised by:
Matthias Schunter
Opened on:
2012-04-12
Description:
This issue will be used as marker for dependencies onto the compliance spec. Once the compliance document matures, we can then resolve these dependencies (which may or may not require changes to the TPE).
Related Actions Items:
No related actions
Related emails:
  1. Re: TPE Editorial Proposal to Remove Another Hard Dependency on the Compliance Specification (from dwainberg@appnexus.com on 2014-03-10)
  2. Re: TPE Editorial Proposal to Remove Another Hard Dependency on the Compliance Specification (from mts-std@schunter.org on 2014-03-08)
  3. Re: TPE Editorial Proposal to Remove Another Hard Dependency on the Compliance Specification (from dwainberg@appnexus.com on 2014-03-07)
  4. RE: TPE Editorial Proposal to Remove Another Hard Dependency on the Compliance Specification (from wileys@yahoo-inc.com on 2014-03-07)
  5. Re: TPE Editorial Proposal to Remove Another Hard Dependency on the Compliance Specification (from mts-std@schunter.org on 2014-03-07)
  6. RE: TPE Editorial Proposal to Remove Another Hard Dependency on the Compliance Specification (from wileys@yahoo-inc.com on 2014-03-07)
  7. RE: TPE Editorial Proposal to Remove Another Hard Dependency on the Compliance Specification (from wileys@yahoo-inc.com on 2014-03-07)
  8. Re: TPE Editorial Proposal to Remove Another Hard Dependency on the Compliance Specification (from jbrookman@cdt.org on 2014-03-06)
  9. Re: TPE Editorial Proposal to Remove Another Hard Dependency on the Compliance Specification (from fielding@gbiv.com on 2014-03-06)
  10. Re: TPE Editorial Proposal to Remove Another Hard Dependency on the Compliance Specification (from jack@networkadvertising.org on 2014-03-06)
  11. Re: tracking-ISSUE-239: Should tracking status representation include an array of links for claiming compliance by reference? [Tracking Preference Expression (DNT)] (from fielding@gbiv.com on 2013-12-08)
  12. RE: tracking-ISSUE-239: Should tracking status representation include an array of links for claiming compliance by reference? [Tracking Preference Expression (DNT)] (from michael.oneill@baycloud.com on 2013-12-08)
  13. Re: TPE status (from mts-std@schunter.org on 2013-12-08)
  14. TPE status (from fielding@gbiv.com on 2013-12-08)
  15. tracking-ISSUE-239: Should tracking status representation include an array of links for claiming compliance by reference? [Tracking Preference Expression (DNT)] (from sysbot+tracker@w3.org on 2013-12-08)
  16. RE: ACTION-326 and ACTION-327 BLOCKED on ISSUE-5 (from wileys@yahoo-inc.com on 2012-11-14)
  17. Re: ACTION-326 and ACTION-327 BLOCKED on ISSUE-5 (from tlr@w3.org on 2012-11-14)
  18. ACTION-326 and ACTION-327 BLOCKED on ISSUE-5 (from Brendan@iab.net on 2012-11-13)
  19. plain text of TPE spec as of 14 Sep 2012 (from fielding@gbiv.com on 2012-09-20)
  20. Re: RESENT: Batch Closing of Issues against TPE [Deadline for validating can-live-with consensus: August 20] (from fielding@gbiv.com on 2012-08-18)
  21. Re: Agenda for July 18, 2012 DNT WG Call on TPE (from fielding@gbiv.com on 2012-07-18)
  22. tracking-ISSUE-136 (depends): Resolve dependencies of the TPE on the compliance specification [Tracking Preference Expression (DNT)] (from sysbot+tracker@w3.org on 2012-04-12)

Related notes:

ISSUE-117 was closed, over my objection, based on the theory that this issue would encompass it. To be clear, we have a hard dependency in the protocol on the definition of tracking, for which there is no agreed definition, which means that nobody can implement this protocol as specified.

Roy Fielding, 18 Apr 2012, 01:14:32

Along the same thread: the TPE seems to generally avoid using 'consent' terminology and instead refers to 'expression of user preference'. While I personally prefer sticking to 'consent' as a touchstone, more important for clarity purposes is to stay consistent. So where the compliance/scope document means to say 'out of band consent MUST reflect an explicit expression of user preference', it instead says 'third parties may gain explicit and informed consent by other means'.

Matthias Schunter, 27 Aug 2012, 07:29:37

Closed as the TPE spec approaches Last Call

Ninja Marnau, 9 Apr 2014, 15:20:18

Display change log ATOM feed

Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 136.html,v 1.1 2019/02/01 09:32:29 vivien Exp $