ISSUE-239: Should tracking status representation include an array of links for claiming compliance by reference?

Should tracking status representation include an array of links for claiming compliance by reference?

State:
CLOSED
Product:
Tracking Preference Expression (DNT)
Raised by:
Roy Fielding
Opened on:
2013-12-08
Description:
I propose an optional member of the tracking status object that will allow the origin server to communicate what (if any) claims it wishes to make regarding compliance to certain behaviors, as defined by reference to other standard resources:

An origin server MAY send a member named compliance with an array value containing a list of URI references that identify specific regimes to which the origin server claims to comply for the designated resource. Communicating such a claim of compliance is presumed to improve transparency, which might influence a user's decisions or configurations regarding allowed tracking, but does not have any direct impact on this protocol.

compliance = %x22 "compliance" %x22
compliance-v = array-of-refs

Related to ISSUE-136
Related Actions Items:
No related actions
Related emails:
  1. Re: TPE Editorial Proposal to Remove Another Hard Dependency on the Compliance Specification (from jack@networkadvertising.org on 2014-03-06)
  2. Re: TPE Editorial Proposal to Remove Another Hard Dependency on the Compliance Specification (from mts-std@schunter.org on 2014-03-04)
  3. TPE Editorial Proposal to Remove Another Hard Dependency on the Compliance Specification (from jack@networkadvertising.org on 2014-02-27)
  4. Re: Agenda for February 5 call (from john@consumerwatchdog.org on 2014-02-04)
  5. Re: Agenda for February 5 call (from tien@eff.org on 2014-02-04)
  6. RE: Agenda for February 5 call (from wileys@yahoo-inc.com on 2014-02-04)
  7. Agenda for February 5 call (from ninja@w3.org on 2014-02-04)
  8. Subject: Issue-239 Consensus, to be closed (from cargill@adobe.com on 2014-01-24)
  9. issue-241 descriptively defining some qualifiers (from npdoty@w3.org on 2014-01-22)
  10. Re: Agenda for January 21 call (from singer@apple.com on 2014-01-22)
  11. Agenda for January 21 call (from ninja@w3.org on 2014-01-21)
  12. Re: Working Drafts (from jbrookman@cdt.org on 2014-01-17)
  13. Re: Working Drafts (from walter.van.holst@xs4all.nl on 2014-01-17)
  14. RE: Working Drafts (from wileys@yahoo-inc.com on 2014-01-17)
  15. Re: Working Drafts (from jbrookman@cdt.org on 2014-01-17)
  16. Re: Agenda for January 15 (from singer@apple.com on 2014-01-14)
  17. Agenda for January 15 (from ninja@w3.org on 2014-01-14)
  18. Re: ISSUE-239: Link to compliance document (from singer@apple.com on 2014-01-09)
  19. RE: ISSUE-239: Link to compliance document (from wileys@yahoo-inc.com on 2014-01-09)
  20. Re: ISSUE-239: Link to compliance document (from singer@apple.com on 2014-01-08)
  21. Re: ISSUE-239: Link to compliance document (from npdoty@w3.org on 2014-01-08)
  22. Re: Agenda for January 8, 2014 call (from rob@blaeu.com on 2014-01-08)
  23. Re: Agenda for January 8, 2014 call (from ninja@w3.org on 2014-01-08)
  24. Agenda for January 8, 2014 call (from ninja@w3.org on 2014-01-07)
  25. Re: ISSUE-239: Link to compliance document (from walter.van.holst@xs4all.nl on 2013-12-18)
  26. Re: ISSUE-239: Link to compliance document (from fielding@gbiv.com on 2013-12-18)
  27. Re: ISSUE-239: Link to compliance document (from fielding@gbiv.com on 2013-12-18)
  28. Re: ISSUE-239: Link to compliance document (from mts-std@schunter.org on 2013-12-18)
  29. Re: ISSUE-239: Link to compliance document (from npdoty@w3.org on 2013-12-17)
  30. Re: ISSUE-239: Link to compliance document (from fielding@gbiv.com on 2013-12-17)
  31. Re: ISSUE-239: Link to compliance document (from fielding@gbiv.com on 2013-12-17)
  32. Agenda for December 18, 2013 call (from ninja@w3.org on 2013-12-17)
  33. Re: ISSUE-239: Link to compliance document (from john@consumerwatchdog.org on 2013-12-16)
  34. RE: ISSUE-239: Link to compliance document (from michael.oneill@baycloud.com on 2013-12-16)
  35. Re: ISSUE-239: Link to compliance document (from walter.van.holst@xs4all.nl on 2013-12-16)
  36. Re: ISSUE-239: Link to compliance document (from jbrookman@cdt.org on 2013-12-16)
  37. RE: ISSUE-239: Link to compliance document (from wileys@yahoo-inc.com on 2013-12-16)
  38. Re: ISSUE-239: Link to compliance document (from john@consumerwatchdog.org on 2013-12-16)
  39. Re: ISSUE-239: Link to compliance document (from walter.van.holst@xs4all.nl on 2013-12-16)
  40. ISSUE-239: Link to compliance document (from mts-std@schunter.org on 2013-12-16)
  41. Re: Agenda for December 11, 2013 call (from jbrookman@cdt.org on 2013-12-10)
  42. Re: Agenda for December 11, 2013 call (from john@consumerwatchdog.org on 2013-12-10)
  43. RE: Agenda for December 11, 2013 call (from wileys@yahoo-inc.com on 2013-12-10)
  44. Agenda for December 11, 2013 call (from ninja@w3.org on 2013-12-10)
  45. 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)
  46. 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)
  47. Re: TPE status (from mts-std@schunter.org on 2013-12-08)
  48. 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)

Related notes:

Roy's proposed text was determined as WG consensus and will be integrated in TPE.

Ninja Marnau, 11 Mar 2014, 21:43:44

Closed on Feb 5 call. WG decision is to accept editor's text.

Roy Fielding, 12 Mar 2014, 17:18:10

Display change log ATOM feed


Matthias Schunter <matthias.schunter@intel.com>, Chair, Bert Bos <bert@w3.org>, 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: index.php,v 1.326 2018/10/13 17:29:51 vivien Exp $