public-tracking@w3.org from May 2012 by subject

5.2.2 Policy representation

Action-157: Update logged-in consent proposal

ACTION-169 ISSUE-61 same-party relations

ACTION-172: Write up more detailed list of use cases for origin/origin exceptions

ACTION-175: Draft API method for sites to remove, a la removeTrackingException()

ACTION-177: Add an API to let a site request a web-wide exception

ACTION-179 -- Shane Wiley to draft section on seriousness of the request for a user-granted exception (with ninja) -- due 2012-04-19 -- OPEN

action-181, make language consistent, done (I claim)

ACTION-185: Draft specific field proposal for optional auditors

action-190

action-195: Clarify action items needed for issue-65

ACTION-202 Alternative to explicit/explicit API

ACTION-203 : Text for transitive model

Actions 176 (and dup. 183), updated

Actions 183 and 176 (which seem to be the same)

agenda 9 May 2012

Agenda for 02 May, 2012 call

Agenda for May 16, 2012 DNT WG Call

Agenda for May 23, 2012 DNT WG Call V01

agenda: 30 May 2012 call

Allowed uses of protocol data in first N weeks (ACTION-190)

An alternative to site-specific user granted exceptions (Issue-111)

Apologies

Article from NYT on tracking

Call for feedback on hybrid URI/header proposal

Dutch cookie clause

explicit-explicit exception pairs

explicit-explicit exception pairs [a proposed resolution to ISSUE-140]

Fwd: Ad Ops Speaks on DNT Community Group Proposed

Identifying yourself to Zakim for teleconferences

Industry Hosted Education/Feedback Event on DNT June 12th in NYC - W3C Working Group Invite

Initial feedback on the well-known URI Proposal

ISSUE-116: How can we build a JS DOM property which doesn't allow inline JS to receive mixed signals?

ISSUE-16, ACTION-166: define (data) collection

Leaving...

Media Access (ACTION-197)

minutes (was Re: Agenda for May 16, 2012 DNT WG Call)

Minutes backlog

REVISED Actions 176 (and dup. 183), also merged Shane's text and added Remove APIs

Summary of Discussions on user-granted Exceptions [consensus check on ISSUE-129 and ISSUE-130]

Support for ISSUE 143 - EDUCATED Consumer Choice Should Be REQUIRED

Tracking Preference Expression Spec Suggestion

tracking-ISSUE-143 (Reciprocal Consent): Activating a Tracking Preference must require explicit, informed consent from a user [Tracking Preference Expression (DNT)]

tracking-ISSUE-144: User-granted Exceptions: Constraints on user agent behavior while granting and for future requests? [Tracking Preference Expression (DNT)]

tracking-ISSUE-145: Attribute-set for the well-known URI [Tracking Preference Expression (DNT)]

tracking-ISSUE-146: Well-known URIs and maintainability for large sites [Tracking Preference Expression (DNT)]

tracking-ISSUE-147: Transporting Consent via the Exception / DNT mechanisms [Global Considerations]

tracking-ISSUE-148: What does DNT:0 mean? [Tracking Definitions and Compliance]

tracking-ISSUE-149: Compliance section for user agents [Tracking Definitions and Compliance]

tracking-ISSUE-150: DNT conflicts from multiple user agents [Tracking Definitions and Compliance]

Transitive third party exceptions

transitivity of DNT exceptions

Updated Server Response Section of TPE

W3C F2F logistics for Bellevue, WA

Well known URIs and large sites

Last message date: Thursday, 31 May 2012 23:48:30 UTC