An update on ISSUE-111: How user-agent can signal DNT exceptions to the site (ACTION-188)
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
W3C F2F logistics for Bellevue, WA
on users and user-agents and parties
tracking-ISSUE-143 (Reciprocal Consent): Activating a Tracking Preference must require explicit, informed consent from a user [Tracking Preference Expression (DNT)]
next face-to-face meeting: June 20-22, Seattle
F2F logistics
ISSUE-142: How should protocol data be allowed to be used in the first N weeks?
notes from TPE breakout section
Action-157: Update logged-in consent proposal
- Re: Action-157: Update logged-in consent proposal
- Re: Action-157: Update logged-in consent proposal
ISSUE-49: Third party as first party - is a third party that collects data on behalf of the first party treated the same way as the first party?
Geolocation compliance (ACTION-165)
explicit-explicit exception pairs
- Re: explicit-explicit exception pairs
Agenda for 24 April, 2012 call
CVS commit email list
Minutes from DC, April 2012
reminder: doodle poll for f2f
Scheduling for additional meeting -- prompt responses requested
post-call housekeeping & upcoming discussions
agenda: 18 April 2012 call
tracking-ISSUE-141: Do a review of the Tracking Protection WG deliverables according to http://www.w3.org/TR/qaframe-spec [Tracking Preference Expression (DNT)]
Media requests
An alternative to site-specific user granted exceptions (Issue-111)
- RE: An alternative to site-specific user granted exceptions (Issue-111)
- Re: An alternative to site-specific user granted exceptions (Issue-111)
AW: Re: Behavior of user agents after granting exceptions
Behavior of user agents after granting exceptions
- Re: Behavior of user agents after granting exceptions
Permitted behavior of third parties under user-granted exceptions?
tracking-ISSUE-140: Do we need site-specific exceptions? [Tracking Preference Expression (DNT)]
Clarification for ACTION-170: What is the use case?
ISSUE-139: Should we have Web-Wide Exception via a Well-Known URI?
tracking-ISSUE-138: Web-Wide Exception Well Known URI [Tracking Preference Expression (DNT)]
Notes from the Exception Working Group [ISSUE-113, ISSUE-128, ISSUE-129, ISSUE-130]
Tracking Preference Expression Spec Suggestion
ISSUE-137: Does hybrid tracking status need to distinguish between first party (1) and outsourcing service provider acting as a first party (s)
tracking-ISSUE-136 (depends): Resolve dependencies of the TPE on the compliance specification [Tracking Preference Expression (DNT)]
Wish you a successful f2f meeting!
Re: action-159 Draft shorter language to describe conditions for consent
- RE: action-159 Draft shorter language to describe conditions for consent
Privacy Harms
Possible User Harms Through Multi-Site Data Collection (Group 2)
Re: ISSUE-130: Web-wide exceptions - iare there objections to permitting those?
Fwd: Impromptu Tech Policy Happy Hour - Weds 4/11
ISSUE-135: Draft Global Considerations document
ISSUE-60: proposed to close
ISSUE-134: Would we additionally permit logs that are retained for a short enough period?
Use cases for consideration as "Ongoing Security Concerns" for 3rd parties
navigator.doNotTrack
Alternative 6
first party resource
ISSUE-133: What effect does legal liability or consistent data practices between affiliates have on the definition of breadth of a party?
ISSUE-152: Write up logged-in-means-out-of-band-consent
table of 5 proposals
ISSUE-132: Should the spec speak to intermediaries or hosting providers to modify any responses/statements about DNT compliance?
Issues mentioned in the TPE document, or non-closed in the database and applying to TPE
ISSUE-131: What should implementations look like to satisfy our exit criteria for CR?
social: drinks & dinners
is a site-wide exception 'safe'?
tree killer version: all 5 compliance proposals
Updated response to Aleecia's Template, Issue-10, Issue-17, Issue-19, Issue-22, Issue-24, Issue-25, Issue-31, Issue-49, Issue-73
deeper look at agenda items
EFF/Mozilla/Stanford Proposal
Parties and Necessary Business Uses
- RE: Parties and Necessary Business Uses
CDT's proposals re: template for parties and business uses
'do not cross-site track' response to Aleecia's outline
Fwd: ACTION-120 Web Wide Exemptions and JavaScript
Aleecia's Template for Issue-10, Issue-17, Issue 19
reporters and observers
Re: on negotiating site exceptions
- RE: on negotiating site exceptions
- RE: on negotiating site exceptions
- Re: on negotiating site exceptions
Tracking Status Hybrid
process clarifications
Re: Parties and First Party vs. Third Party (ISSUE-10)
Re: ISSUE-130: Web-wide exceptions - iare there objections to permitting those?
W3C TPWG Process Follow UP
AW: Data mining as a means to protect privacy in social networks
TPE: Input for our discussions in DC
TPE Call for text proposals: ISSUE-128: HTTP error status code to signal that tracking is required?
Agenda for 2012-04-04 call
f2f logistics and agenda, please indicate if you're attending
Re: Are blanked exceptions usable in the EU? [ISSUE-129]
Fw: ACTION-152 - Write up logged-in-means-out-of-band-consent
Re: ACTION-152 - Write up logged-in-means-out-of-band-consent
- Re: ACTION-152 - Write up logged-in-means-out-of-band-consent
- Re: ACTION-152 - Write up logged-in-means-out-of-band-consent
- RE: ACTION-152 - Write up logged-in-means-out-of-band-consent
- Re: ACTION-152 - Write up logged-in-means-out-of-band-consent
- RE: ACTION-152 - Write up logged-in-means-out-of-band-consent
- Re: ACTION-152 - Write up logged-in-means-out-of-band-consent
- RE: ACTION-152 - Write up logged-in-means-out-of-band-consent
- Re: ACTION-152 - Write up logged-in-means-out-of-band-consent
- RE: ACTION-152 - Write up logged-in-means-out-of-band-consent
- Re: ACTION-152 - Write up logged-in-means-out-of-band-consent
- Re: ACTION-152 - Write up logged-in-means-out-of-band-consent
- RE: ACTION-152 - Write up logged-in-means-out-of-band-consent
- Re: ACTION-152 - Write up logged-in-means-out-of-band-consent
- RE: ACTION-152 - Write up logged-in-means-out-of-band-consent
- Re: ACTION-152 - Write up logged-in-means-out-of-band-consent
- RE: ACTION-152 - Write up logged-in-means-out-of-band-consent
- Re: ACTION-152 - Write up logged-in-means-out-of-band-consent
- RE: ACTION-152 - Write up logged-in-means-out-of-band-consent
- RE: ACTION-152 - Write up logged-in-means-out-of-band-consent
- Re: ACTION-152 - Write up logged-in-means-out-of-band-consent
- Re: ACTION-152 - Write up logged-in-means-out-of-band-consent
- Re: ACTION-152 - Write up logged-in-means-out-of-band-consent
- RE: ACTION-152 - Write up logged-in-means-out-of-band-consent
- Re: ACTION-152 - Write up logged-in-means-out-of-band-consent
- Re: ACTION-152 - Write up logged-in-means-out-of-band-consent
- RE: ACTION-152 - Write up logged-in-means-out-of-band-consent
- RE: ACTION-152 - Write up logged-in-means-out-of-band-consent
- RE: ACTION-152 - Write up logged-in-means-out-of-band-consent
- RE: ACTION-152 - Write up logged-in-means-out-of-band-consent
- RE: ACTION-152 - Write up logged-in-means-out-of-band-consent
- RE: ACTION-152 - Write up logged-in-means-out-of-band-consent
- RE: ACTION-152 - Write up logged-in-means-out-of-band-consent
- Re: ACTION-152 - Write up logged-in-means-out-of-band-consent