tracking-ISSUE-150: DNT conflicts from multiple user agents [Tracking Definitions and Compliance]
- Re: tracking-ISSUE-150: DNT conflicts from multiple user agents [Tracking Definitions and Compliance]
- Re: tracking-ISSUE-150: DNT conflicts from multiple user agents [Tracking Definitions and Compliance]
- RE: tracking-ISSUE-150: DNT conflicts from multiple user agents [Tracking Definitions and Compliance]
- Re: tracking-ISSUE-150: DNT conflicts from multiple user agents [Tracking Definitions and Compliance]
- Re: tracking-ISSUE-150: DNT conflicts from multiple user agents [Tracking Definitions and Compliance]
- Re: tracking-ISSUE-150: DNT conflicts from multiple user agents [Tracking Definitions and Compliance]
- Re: tracking-ISSUE-150: DNT conflicts from multiple user agents [Tracking Definitions and Compliance]
- Re: tracking-ISSUE-150: DNT conflicts from multiple user agents [Tracking Definitions and Compliance]
- RE: tracking-ISSUE-150: DNT conflicts from multiple user agents [Tracking Definitions and Compliance]
- Re: tracking-ISSUE-150: DNT conflicts from multiple user agents [Tracking Definitions and Compliance]
- Re: tracking-ISSUE-150: DNT conflicts from multiple user agents [Tracking Definitions and Compliance]
- RE: tracking-ISSUE-150: DNT conflicts from multiple user agents [Tracking Definitions and Compliance]
- Re: tracking-ISSUE-150: DNT conflicts from multiple user agents [Tracking Definitions and Compliance]
- Re: tracking-ISSUE-150: DNT conflicts from multiple user agents [Tracking Definitions and Compliance]
- RE: tracking-ISSUE-150: DNT conflicts from multiple user agents [Tracking Definitions and Compliance]
- Re: tracking-ISSUE-150: DNT conflicts from multiple user agents [Tracking Definitions and Compliance]
- Re: tracking-ISSUE-150: DNT conflicts from multiple user agents [Tracking Definitions and Compliance]
Industry Hosted Education/Feedback Event on DNT June 12th in NYC - W3C Working Group Invite
action-195: Clarify action items needed for issue-65
ISSUE-116: How can we build a JS DOM property which doesn't allow inline JS to receive mixed signals?
Dutch cookie clause
ACTION-179 -- Shane Wiley to draft section on seriousness of the request for a user-granted exception (with ninja) -- due 2012-04-19 -- OPEN
agenda: 30 May 2012 call
tracking-ISSUE-149: Compliance section for user agents [Tracking Definitions and Compliance]
tracking-ISSUE-148: What does DNT:0 mean? [Tracking Definitions and Compliance]
action-190
ACTION-203 : Text for transitive model
ACTION-185: Draft specific field proposal for optional auditors
Leaving...
Support for ISSUE 143 - EDUCATED Consumer Choice Should Be REQUIRED
ISSUE-16, ACTION-166: define (data) collection
- Re: ISSUE-16, ACTION-166: define (data) collection
- Re: ISSUE-16, ACTION-166: define (data) collection
Apologies
Agenda for May 23, 2012 DNT WG Call V01
ACTION-202 Alternative to explicit/explicit API
Updated Server Response Section of TPE
REVISED Actions 176 (and dup. 183), also merged Shane's text and added Remove APIs
Actions 176 (and dup. 183), updated
action-181, make language consistent, done (I claim)
Apologies
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
Agenda for May 16, 2012 DNT WG Call
- RE: Agenda for May 16, 2012 DNT WG Call
- Re: Agenda for May 16, 2012 DNT WG Call
- Re: Agenda for May 16, 2012 DNT WG Call
Call for feedback on hybrid URI/header proposal
tracking-ISSUE-147: Transporting Consent via the Exception / DNT mechanisms [Global Considerations]
- Re: tracking-ISSUE-147: Transporting Consent via the Exception / DNT mechanisms [Global Considerations]
- Re: tracking-ISSUE-147: Transporting Consent via the Exception / DNT mechanisms [Global Considerations]
- Re: tracking-ISSUE-147: Transporting Consent via the Exception / DNT mechanisms [Global Considerations]
- Re: tracking-ISSUE-147: Transporting Consent via the Exception / DNT mechanisms [Global Considerations]
- Re: tracking-ISSUE-147: Transporting Consent via the Exception / DNT mechanisms [Global Considerations]
- Re: tracking-ISSUE-147: Transporting Consent via the Exception / DNT mechanisms [Global Considerations]
- Re: tracking-ISSUE-147: Transporting Consent via the Exception / DNT mechanisms [Global Considerations]
- Re: tracking-ISSUE-147: Transporting Consent via the Exception / DNT mechanisms [Global Considerations]
- Re: tracking-ISSUE-147: Transporting Consent via the Exception / DNT mechanisms [Global Considerations]
- Re: tracking-ISSUE-147: Transporting Consent via the Exception / DNT mechanisms [Global Considerations]
- Re: tracking-ISSUE-147: Transporting Consent via the Exception / DNT mechanisms [Global Considerations]
Re: explicit-explicit exception pairs [a proposed resolution to ISSUE-140]
Summary of Discussions on user-granted Exceptions [consensus check on ISSUE-129 and ISSUE-130]
Re: Tracking Preference Expression Spec Suggestion
Fwd: Ad Ops Speaks on DNT Community Group Proposed
tracking-ISSUE-146: Well-known URIs and maintainability for large sites [Tracking Preference Expression (DNT)]
tracking-ISSUE-145: Attribute-set for the well-known URI [Tracking Preference Expression (DNT)]
Media Access (ACTION-197)
- RE: Media Access (ACTION-197)
Transitive third party exceptions
- Re: Transitive third party exceptions
- Re: Transitive third party exceptions
- RE: Transitive third party exceptions
Well known URIs and large sites
agenda 9 May 2012
transitivity of DNT exceptions
Article from NYT on tracking
Re: An alternative to site-specific user granted exceptions (Issue-111)
Actions 183 and 176 (which seem to be the same)
- Re: Actions 183 and 176 (which seem to be the same)
- Re: Actions 183 and 176 (which seem to be the same)
5.2.2 Policy representation
ACTION-169 ISSUE-61 same-party relations
tracking-ISSUE-144: User-granted Exceptions: Constraints on user agent behavior while granting and for future requests? [Tracking Preference Expression (DNT)]
Re: tracking-ISSUE-143 (Reciprocal Consent): Activating a Tracking Preference must require explicit, informed consent from a user [Tracking Preference Expression (DNT)]
Re: Initial feedback on the well-known URI Proposal
Allowed uses of protocol data in first N weeks (ACTION-190)
- RE: Allowed uses of protocol data in first N weeks (ACTION-190)
- Re: Allowed uses of protocol data in first N weeks (ACTION-190)
- Re: Allowed uses of protocol data in first N weeks (ACTION-190)
- Re: Allowed uses of protocol data in first N weeks (ACTION-190)
- Re: Allowed uses of protocol data in first N weeks (ACTION-190)
- Re: Allowed uses of protocol data in first N weeks (ACTION-190)
- Re: Allowed uses of protocol data in first N weeks (ACTION-190)
- Re: Allowed uses of protocol data in first N weeks (ACTION-190)
- RE: Allowed uses of protocol data in first N weeks (ACTION-190)
- Re: Allowed uses of protocol data in first N weeks (ACTION-190)
- RE: Allowed uses of protocol data in first N weeks (ACTION-190)
- Re: Allowed uses of protocol data in first N weeks (ACTION-190)
- RE: Allowed uses of protocol data in first N weeks (ACTION-190)
- Re: Allowed uses of protocol data in first N weeks (ACTION-190)
- Re: Allowed uses of protocol data in first N weeks (ACTION-190)
- RE: Allowed uses of protocol data in first N weeks (ACTION-190)
- Re: Allowed uses of protocol data in first N weeks (ACTION-190)
- Re: Allowed uses of protocol data in first N weeks (ACTION-190)
Re: W3C F2F logistics for Bellevue, WA
Re: ACTION-172: Write up more detailed list of use cases for origin/origin exceptions
- Re: ACTION-172: Write up more detailed list of use cases for origin/origin exceptions
- Re: ACTION-172: Write up more detailed list of use cases for origin/origin exceptions
- Re: ACTION-172: Write up more detailed list of use cases for origin/origin exceptions
- Re: ACTION-172: Write up more detailed list of use cases for origin/origin exceptions
- Re: ACTION-172: Write up more detailed list of use cases for origin/origin exceptions
- Re: ACTION-172: Write up more detailed list of use cases for origin/origin exceptions
- RE: ACTION-172: Write up more detailed list of use cases for origin/origin exceptions
- Re: ACTION-172: Write up more detailed list of use cases for origin/origin exceptions
- Re: ACTION-172: Write up more detailed list of use cases for origin/origin exceptions
Identifying yourself to Zakim for teleconferences
Minutes backlog
Agenda for 02 May, 2012 call
Re: ACTION-172: Write up more detailed list of use cases for origin/origin exceptions
- Re: ACTION-172: Write up more detailed list of use cases for origin/origin exceptions
- Re: ACTION-172: Write up more detailed list of use cases for origin/origin exceptions
RE: ACTION-172: Write up more detailed list of use cases for origin/origin exceptions
Re: Action-157: Update logged-in consent proposal
- RE: Action-157: Update logged-in consent proposal
- Re: Action-157: Update logged-in consent proposal
- Re: Action-157: Update logged-in consent proposal
Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- RE: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- RE: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- RE: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- RE: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- RE: explicit-explicit exception pairs
- RE: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- RE: explicit-explicit exception pairs
- RE: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- RE:Re: explicit-explicit exception pairs
- RE: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- RE: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
- RE: explicit-explicit exception pairs