ISSUE-54: can first parties use declared data while in a 3rd party context?

can first parties use declared data while in a 3rd party context?

State:

CLOSED

Product:

Compliance Next

Raised by:

Opened on:

2011-09-22

Description:

Related Actions Items:

• ACTION-68 on Justin Brookman to Provide text on ISSUE-54 - due 2012-02-01, pending review
• ACTION-69 on Sean Harvey to Propose renaming issue-54 - due 2012-02-03, pending review
• ACTION-306 on Shane Wiley to Define "declared" data - due 2012-10-11, pending review
• ACTION-109 on Adrian Bateman to Draft text for issue-54: Can first party provide targeting based on registration information even while sending DNT - due 2012-02-13, closed

Related emails:

1. Agenda for May 22 call (from peter@peterswire.net on 2013-05-21)
2. issue and action cleanup proposals (from npdoty@w3.org on 2013-05-15)
3. Re: Mapping the "framework" to ISSUEs (from john@consumerwatchdog.org on 2013-05-07)
4. Mapping the "framework" to ISSUEs (from jmayer@stanford.edu on 2013-05-07)
5. Re: Agenda for 14 November 2012 call (from tlr@w3.org on 2012-11-14)
6. Re: Proposals for Compliance issue clean up (from david@networkadvertising.org on 2012-11-09)
7. RE: ACTION-306: Declared Data Definition (from wileys@yahoo-inc.com on 2012-10-17)
8. Re: ACTION-306: Declared Data Definition (from robsherman@fb.com on 2012-10-17)
9. RE: ACTION-306: Declared Data Definition (from wileys@yahoo-inc.com on 2012-10-17)
10. Re: ACTION-306: Declared Data Definition (from vigoel@adobe.com on 2012-10-17)
11. ACTION-306: Declared Data Definition (from wileys@yahoo-inc.com on 2012-10-16)
12. RE: Proposed agenda for Amsterdam F2F on October 03-05, 2012 (from wileys@yahoo-inc.com on 2012-09-23)
13. Proposed agenda for Amsterdam F2F on October 03-05, 2012 (from mts-std@schunter.org on 2012-09-21)
14. Agenda for 2012-Mar-21 call (from aleecia@aleecia.com on 2012-03-21)
15. RE: ACTION-69: Renaming ISSUE-54 (from jccannon@microsoft.com on 2012-02-25)
16. Re: ACTION-69: Renaming ISSUE-54 (from singer@apple.com on 2012-02-24)
17. RE: ACTION-69: Renaming ISSUE-54 (from jccannon@microsoft.com on 2012-02-24)
18. Re: ACTION-69: Renaming ISSUE-54 (from singer@apple.com on 2012-02-24)
19. Re: ACTION-69: Renaming ISSUE-54 (from karld@opera.com on 2012-02-23)
20. RE: ACTION-69: Renaming ISSUE-54 (from wileys@yahoo-inc.com on 2012-02-23)
21. Re: ACTION-69: Renaming ISSUE-54 (from karld@opera.com on 2012-02-23)
22. Re: ACTION-69: Renaming ISSUE-54 (from karld@opera.com on 2012-02-23)
23. RE: ACTION-69: Renaming ISSUE-54 (from wileys@yahoo-inc.com on 2012-02-23)
24. Re: ACTION-69: Renaming ISSUE-54 (from karld@opera.com on 2012-02-23)
25. RE: ACTION-69: Renaming ISSUE-54 (from Vincent.Toubiana@alcatel-lucent.com on 2012-02-15)
26. Re: ACTION-69: Renaming ISSUE-54 (from haakon.bratsberg@opera.com on 2012-02-14)
27. RE: ACTION-69: Renaming ISSUE-54 (from wileys@yahoo-inc.com on 2012-02-14)
28. Re: ACTION-69: Renaming ISSUE-54 (from v.toubiana@free.fr on 2012-02-14)
29. RE: ACTION-69: Renaming ISSUE-54 (from jccannon@microsoft.com on 2012-02-14)
30. RE: ACTION-69: Renaming ISSUE-54 (from wileys@yahoo-inc.com on 2012-02-14)
31. RE: ACTION-69: Renaming ISSUE-54 (from Vincent.Toubiana@alcatel-lucent.com on 2012-02-14)
32. RE: ACTION-69: Renaming ISSUE-54 (from Vincent.Toubiana@alcatel-lucent.com on 2012-02-14)
33. RE: ACTION-69: Renaming ISSUE-54 (from jccannon@microsoft.com on 2012-02-14)
34. RE: ACTION-69: Renaming ISSUE-54 (from wileys@yahoo-inc.com on 2012-02-14)
35. RE: ACTION-69: Renaming ISSUE-54 (from Vincent.Toubiana@alcatel-lucent.com on 2012-02-14)
36. RE: ACTION-69: Renaming ISSUE-54 (from wileys@yahoo-inc.com on 2012-02-14)
37. Re: ACTION-69: Renaming ISSUE-54 (from jeff@democraticmedia.org on 2012-02-14)
38. RE: ACTION-69: Renaming ISSUE-54 (from CPedigo@online-publishers.org on 2012-02-14)
39. RE: ACTION-69: Renaming ISSUE-54 (from Vincent.Toubiana@alcatel-lucent.com on 2012-02-14)
40. Re: ACTION-69: Renaming ISSUE-54 (from achapell@chapellassociates.com on 2012-02-14)
41. RE: ACTION-69: Renaming ISSUE-54 (from jccannon@microsoft.com on 2012-02-14)
42. RE: ACTION-69: Renaming ISSUE-54 (from jccannon@microsoft.com on 2012-02-14)
43. RE: ACTION-69: Renaming ISSUE-54 (from jccannon@microsoft.com on 2012-02-14)
44. RE: ACTION-69: Renaming ISSUE-54 (from jccannon@microsoft.com on 2012-02-14)
45. RE: ACTION-69: Renaming ISSUE-54 (from wileys@yahoo-inc.com on 2012-02-13)
46. Re: ACTION-69: Renaming ISSUE-54 (from jmayer@stanford.edu on 2012-02-13)
47. Re: ACTION-69: Renaming ISSUE-54 (from jmayer@stanford.edu on 2012-02-13)
48. Re: ACTION-69: Renaming ISSUE-54 (from jmayer@stanford.edu on 2012-02-13)
49. RE: ACTION-69: Renaming ISSUE-54 (from wileys@yahoo-inc.com on 2012-02-13)
50. RE: ACTION-69: Renaming ISSUE-54 (from jccannon@microsoft.com on 2012-02-13)
51. Re: ACTION-69: Renaming ISSUE-54 (from jmayer@stanford.edu on 2012-02-13)
52. RE: ACTION-69: Renaming ISSUE-54 (from jccannon@microsoft.com on 2012-02-13)
53. Re: ACTION-69: Renaming ISSUE-54 (from jmayer@stanford.edu on 2012-02-13)
54. RE: ACTION-69: Renaming ISSUE-54 (from jccannon@microsoft.com on 2012-02-13)
55. Re: ACTION-69: Renaming ISSUE-54 (from jmayer@stanford.edu on 2012-02-13)
56. RE: ACTION-69: Renaming ISSUE-54 (from jccannon@microsoft.com on 2012-02-13)
57. RE: ACTION-69: Renaming ISSUE-54 (from jccannon@microsoft.com on 2012-02-13)
58. Re: ACTION-69: Renaming ISSUE-54 (from john@consumerwatchdog.org on 2012-02-13)
59. Re: ACTION-69: Renaming ISSUE-54 (from ggieron@adtruth.com on 2012-02-13)
60. RE: ACTION-69: Renaming ISSUE-54 (from jccannon@microsoft.com on 2012-02-13)
61. Re: ACTION-69: Renaming ISSUE-54 (from jeff@democraticmedia.org on 2012-02-13)
62. RE: ACTION-69: Renaming ISSUE-54 (from jccannon@microsoft.com on 2012-02-13)
63. Re: ACTION-69: Renaming ISSUE-54 (from jeff@democraticmedia.org on 2012-02-13)
64. RE: ACTION-69: Renaming ISSUE-54 (from jccannon@microsoft.com on 2012-02-12)
65. Re: ACTION-69: Renaming ISSUE-54 (from john@consumerwatchdog.org on 2012-02-08)
66. Re: ACTION-69: Renaming ISSUE-54 (from john@consumerwatchdog.org on 2012-02-08)
67. Re: ACTION-69: Renaming ISSUE-54 (from jeff@democraticmedia.org on 2012-02-08)
68. Re: ACTION-69: Renaming ISSUE-54 (from jmayer@stanford.edu on 2012-02-08)
69. Re: ACTION-69: Renaming ISSUE-54 (from justin@cdt.org on 2012-02-08)
70. RE: ACTION-69: Renaming ISSUE-54 (from jccannon@microsoft.com on 2012-02-07)
71. Re: ACTION-69: Renaming ISSUE-54 (from dwainberg@appnexus.com on 2012-02-06)
72. RE: ACTION-69: Renaming ISSUE-54 (from wileys@yahoo-inc.com on 2012-02-06)
73. ACTION-69: Renaming ISSUE-54 (from sharvey@google.com on 2012-02-05)
74. Re: [ISSUE-5] What is the definition of tracking? (from jeff@democraticmedia.org on 2011-12-10)
75. [ISSUE-5] What is the definition of tracking? (from kevsmith@adobe.com on 2011-12-09)
76. Re: Compliance issues (from john@consumerwatchdog.org on 2011-12-07)
77. Compliance issues (from aleecia@aleecia.com on 2011-12-06)
78. Next steps on compliance issues (from aleecia@aleecia.com on 2011-12-03)
79. Agenda for 2011-09-28 TPWG call (from aleecia@aleecia.com on 2011-09-26)
80. ISSUE-54: Can first party provide targeting based on registration information even while sending DNT (from sysbot+tracker@w3.org on 2011-09-22)

Related notes:

Display change log