Saturday, 30 March 2013
Friday, 29 March 2013
- Re: Moving "C"onsent from Tracking Status to Permitted Use?
- Re: Proposed California Law affecting DNT
- RE: Moving "C"onsent from Tracking Status to Permitted Use?
- Re: Moving "C"onsent from Tracking Status to Permitted Use?
- RE: Moving "C"onsent from Tracking Status to Permitted Use?
- RE: Moving "C"onsent from Tracking Status to Permitted Use?
- Re: Moving "C"onsent from Tracking Status to Permitted Use?
- RE: Moving "C"onsent from Tracking Status to Permitted Use?
- Re: Moving "C"onsent from Tracking Status to Permitted Use?
- RE: Moving "C"onsent from Tracking Status to Permitted Use?
- Re: Moving "C"onsent from Tracking Status to Permitted Use?
- RE: Moving "C"onsent from Tracking Status to Permitted Use?
- Re: Moving "C"onsent from Tracking Status to Permitted Use?
- RE: Moving "C"onsent from Tracking Status to Permitted Use?
- RE: Proposed California Law affecting DNT
- RE: Proposed California Law affecting DNT
- Re: Proposed California Law affecting DNT
- Re: Proposed California Law affecting DNT
- Re: Proposed California Law affecting DNT
- Re: Proposed California Law affecting DNT
Thursday, 28 March 2013
- Re: Proposed California Law affecting DNT
- Proposed California Law affecting DNT
- Re: Moving "C"onsent from Tracking Status to Permitted Use?
- RE: Moving "C"onsent from Tracking Status to Permitted Use?
- RE: Moving "C"onsent from Tracking Status to Permitted Use?
- Re: DNT:1 and "data append"
- RE: Moving "C"onsent from Tracking Status to Permitted Use?
- Moving "C"onsent from Tracking Status to Permitted Use?
- RE: Action 368 - Definition of Service Provider/Data Processor
Wednesday, 27 March 2013
- Re: MIME media type for tracking status resource
- Re: Action 368 - Definition of Service Provider/Data Processor
- MIME media type for tracking status resource
- Re: ACTION-372 service providers and debugging
- Re: DNT:1 and "data append"
- RE: Action 368 - Definition of Service Provider/Data Processor
- Re: Action 368 - Definition of Service Provider/Data Processor
- Re: ACTION-372 service providers and debugging
- ISSUE-25: New text for Aggregated data: collection and use for audience measurement research
- Re: DNT:1 and "data append"
- Re: DNT:1 and "data append"
- Re: DNT:1 and "data append"
- Re: DNT:1 and "data append"
- data append next W, not this
- Re: DNT:1 and "data append"
- Re: DNT:1 and "data append"
- RE: DNT:1 and "data append"
- Re: Action 368 - Definition of Service Provider/Data Processor
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: DNT:1 and "data append"
- Re: Action 368 - Definition of Service Provider/Data Processor
- Re: DNT:1 and "data append"
- Re: DNT:1 and "data append"
- DNT: financial accounting slides for Wednesday call
Tuesday, 26 March 2013
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- ISSUE-25: New text for Aggregated data: collection and use for audience measurement research
- DNT: Agenda for March 27 call
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: ACTION-372 service providers and debugging
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
Monday, 25 March 2013
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: DNT:1 and "data append"
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
Sunday, 24 March 2013
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
Friday, 22 March 2013
Saturday, 23 March 2013
- RE: TPE Handling Out-of-Band Consent (including ISSUE-152)
- RE: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- RE: TPE Handling Out-of-Band Consent (including ISSUE-152)
- RE: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- RE: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: ACTION-372 service providers and debugging
Friday, 22 March 2013
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- RE: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: ACTION-357: Add service provider option text (with jmayer) as an issue in the draft with an option box
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- RE: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: ACTION-357: Add service provider option text (with jmayer) as an issue in the draft with an option box
- Re: technical issues with multiple first parties
- Re: Proposed Resolution to ISSUE-151 : User Agent Requirement: Be able to handle an exception request
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: RE: Approach to ISSUE-167: Multiple site exception
- Re: ACTION-372 service providers and debugging
- Re: Next TPWG f2f meeting May 6-8, 2013
Thursday, 21 March 2013
- Re: DNT:1 and "data append"
- Re: ACTION-258: Propose 'should' for same-party and why
- Re: ACTION-258: Propose 'should' for same-party and why
- tracking-ISSUE-193 (Delta): Gap analysis on DNT:0 [Global Considerations]
- Re: RE: DNT:1 and "data append"
Wednesday, 20 March 2013
- RE: DNT:1 and "data append"
- Re: Issue-187
- RE: New text Issue 25: Aggregated data: collection and use for audience measurement research
- RE: New text Issue 25: Aggregated data: collection and use for audience measurement research
- Re: DNT:1 and "data append"
- Re: Batch closing of issues (ISSUE-144, ISSUE-187) [pls Respond by Mar 22]
- Re: DNT:1 and "data append"
- Re: RE: RE: ACTION-258: Propose 'should' for same-party and why
- Re: RE: DNT:1 and "data append"
- Re: New text Issue 25: Aggregated data: collection and use for audience measurement research
- Re: New text Issue 25: Aggregated data: collection and use for audience measurement research
- RE: DNT:1 and "data append"
- RE: New text Issue 25: Aggregated data: collection and use for audience measurement research
- RE: DNT:1 and "data append"
- Re: DNT:1 and "data append"
- RE: DNT:1 and "data append"
- Re: DNT:1 and "data append"
- Re: DNT:1 and "data append"
- Re: New text Issue 25: Aggregated data: collection and use for audience measurement research
- Re: New text Issue 25: Aggregated data: collection and use for audience measurement research
- Re: RE: DNT:1 and "data append"
- Re: New text Issue 25: Aggregated data: collection and use for audience measurement research
- Re: RE: ACTION-258: Propose 'should' for same-party and why
- RE: Issue-187
- RE: Approach to ISSUE-167: Multiple site exception
- Re: DNT:1 and "data append"
- RE: ACTION-258: Propose 'should' for same-party and why
Tuesday, 19 March 2013
- Re: Batch closing of issues (ISSUE-144, ISSUE-187) [pls Respond by Mar 22]
- Re: Batch closing of issues (ISSUE-144, ISSUE-187) [pls Respond by Mar 22]
- Re: DNT:1 and "data append"
- Re: Batch closing of issues (ISSUE-144, ISSUE-187) [pls Respond by Mar 22]
- Re: Batch closing of issues (ISSUE-144, ISSUE-187) [pls Respond by Mar 22]
- Re: DNT:1 and "data append"
- Re: DNT:1 and "data append"
- RE: DNT:1 and "data append"
- Re: Batch closing of issues (ISSUE-144, ISSUE-187) [pls Respond by Mar 22]
- Re: DNT:1 and "data append"
- Re: Batch closing of issues (ISSUE-144, ISSUE-187) [pls Respond by Mar 22]
- Re: Batch closing of issues (ISSUE-144, ISSUE-187) [pls Respond by Mar 22]
- Re: DNT: Agenda for March 20 call (revised)
- Re: DNT:1 and "data append"
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- RE: DNT:1 and "data append"
- Re: Proposed Resolution to ISSUE-151 : User Agent Requirement: Be able to handle an exception request
- Re: Batch closing of issues (ISSUE-144, ISSUE-187) [pls Respond by Mar 22]
- Re: DNT:1 and "data append"
- Re: DNT: Agenda for March 20 call
- Re: ACTION-372 service providers and debugging
- Re: New text Issue 25: Aggregated data: collection and use for audience measurement research
- DNT: Agenda for March 20 call
- Re: ACTION-372 service providers and debugging
- New text Issue 25: Aggregated data: collection and use for audience measurement research
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: Batch closing of issues (ISSUE-144, ISSUE-187) [pls Respond by Mar 22]
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: ACTION-372 service providers and debugging
- Re: Batch closing of issues (ISSUE-144, ISSUE-187) [pls Respond by Mar 22]
- RE: Approach to ISSUE-167: Multiple site exception
- Re: DNT:1 and "data append"
- RE: Proposed Resolution to ISSUE-151 : User Agent Requirement: Be able to handle an exception request
- Re: DNT:1 and "data append"
- Re: DNT:1 and "data append"
- Re: technical issues with multiple first parties
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: Proposed Resolution to ISSUE-151 : User Agent Requirement: Be able to handle an exception request
- the Flu (was: Proposed Resolution to ISSUE-151 : User Agent Requirement)
- Re: TPWG Public Comment on DNT Standard
Monday, 18 March 2013
- Re: technical issues with multiple first parties
- Re: DNT:1 and "data append"
- Re: DNT:1 and "data append"
- DNT:1 and "data append"
- ACTION-372 service providers and debugging
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- RE: Approach to ISSUE-167: Multiple site exception
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- RE: Approach to ISSUE-167: Multiple site exception
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: TPE Handling Out-of-Band Consent (including ISSUE-152)
- Re: Approach to ISSUE-167: Multiple site exception
- RE: Approach to ISSUE-167: Multiple site exception
- Re: Issue-187
- RE: Proposed Resolution to ISSUE-151 : User Agent Requirement: Be able to handle an exception request
- Batch closing of issues (ISSUE-144, ISSUE-187) [pls Respond by Mar 22]
- Approach to ISSUE-167: Multiple site exception
- RE: technical issues with multiple first parties
- Re: technical issues with multiple first parties
- RE: ACTION-364: Draft section on best practices for sites requesting exceptions
- TPE Handling Out-of-Band Consent (including ISSUE-152)
- RE: technical issues with multiple first parties
- Re: ACTION-364: Draft section on best practices for sites requesting exceptions
- Proposed Resolution to ISSUE-151 : User Agent Requirement: Be able to handle an exception request
- RE: technical issues with multiple first parties: TPE and compliance
- Re: technical issues with multiple first parties: TPE and compliance
- technical issues with multiple first parties
Saturday, 16 March 2013
- RE: Issue-187
- RE: ACTION-357: Add service provider option text (with jmayer) as an issue in the draft with an option box
Friday, 15 March 2013
- Re: Issue-187
- ACTION-357: Add service provider option text (with jmayer) as an issue in the draft with an option box
- RE: ACTION-371: text defining de-identified data
- Issue-187
- RE: ACTION-371: text defining de-identified data
- RE: ACTION-371: text defining de-identified data
- Re: ACTION-371: text defining de-identified data
- Re: GCTF: Conclusions and minutes
- Re: ACTION-371: text defining de-identified data
- GCTF: Conclusions and minutes
Thursday, 14 March 2013
- RE: ACTION-371: text defining de-identified data
- Re: ACTION-371: text defining de-identified data
- Re: ACTION-371: text defining de-identified data
- Re: ACTION-371: text defining de-identified data
- Re: ACTION-371: text defining de-identified data
- Re: ACTION-371: text defining de-identified data
- Re: TPWG Public Comment on DNT Standard
Wednesday, 13 March 2013
- RE: ACTION-371: text defining de-identified data
- Re: ACTION-371: text defining de-identified data
- Re: ACTION-371: text defining de-identified data
- RE: ACTION-371: text defining de-identified data
- Re: ACTION-371: text defining de-identified data
- Re: ACTION-371: text defining de-identified data
- RE: ACTION-371: text defining de-identified data
- RE: ACTION-371: text defining de-identified data
- RE: ACTION-371: text defining de-identified data
- RE: ACTION-371: text defining de-identified data
- Re: TPWG Public Comment on DNT Standard
- Re: Update on charter appeal and the work of our group
- Re: ACTION-371: text defining de-identified data
Tuesday, 12 March 2013
- Re: ACTION-371: text defining de-identified data
- Re: ACTION-371: text defining de-identified data
- RE: ACTION-371: text defining de-identified data
- No DNT call on 2013-03-13
- RE: ACTION-371: text defining de-identified data
- TPWG Public Comment on DNT Standard
- Re: ACTION-371: text defining de-identified data
- RE: ACTION-371: text defining de-identified data
- RE: ACTION-371: text defining de-identified data
- Re: Update on charter appeal and the work of our group
Monday, 11 March 2013
- Update on charter appeal and the work of our group
- Next TPWG f2f meeting May 6-8, 2013
- Re: ACTION-371: text defining de-identified data
- Re: DNT: Agenda for Call March 6 (deux)
- Re: New text Issue 25: Aggregated data: collection and use for audience measurement research
Sunday, 10 March 2013
- RE: New text Issue 25: Aggregated data: collection and use for audience measurement research
- Re: New text Issue 25: Aggregated data: collection and use for audience measurement research
- Re: New text Issue 25: Aggregated data: collection and use for audience measurement research
Saturday, 9 March 2013
- RE: New text Issue 25: Aggregated data: collection and use for audience measurement research
- Re: New text Issue 25: Aggregated data: collection and use for audience measurement research
- New text Issue 25: Aggregated data: collection and use for audience measurement research
- Re: New text Issue 25: Aggregated data: collection and use for audience measurement research
- New text Issue 25: Aggregated data: collection and use for audience measurement research
- New text Issue 25: Aggregated data: collection and use for audience measurement research
- Re: Fw: New text Issue 25: Aggregated data: collection and use for audience measurement research
Friday, 8 March 2013
- Re: Chair's comment on charter renewal objection
- Re: New text Issue 25: Aggregated data: collection and use for audience measurement research
- Re: New text Issue 25: Aggregated data: collection and use for audience measurement research
- Re: Chair's comment on charter renewal objection
- Re: Chair's comment on charter renewal objection
- RE: New text Issue 25: Aggregated data: collection and use for audience measurement research
- Re: New text Issue 25: Aggregated data: collection and use for audience measurement research
- New text Issue 25: Aggregated data: collection and use for audience measurement research
Thursday, 7 March 2013
- RE: a bit more on charter extension
- a bit more on charter extension
- Re: Fw: New text Issue 25: Aggregated data: collection and use for audience measurement research
- Re: Chair's comment on charter renewal objection
- Re: ISSUE-10 First party definition, ISSUE-60, ACTION-?
- Re: ACTION-371: text defining de-identified data
- Re: Chair's comment on charter renewal objection
- Re: Chair's comment on charter renewal objection
- Re: Chair's comment on charter renewal objection
- Re: Chair's comment on charter renewal objection
- Re: Chair's comment on charter renewal objection
- logistics: updating the compliance editors' draft
Wednesday, 6 March 2013
- Re: ACTION-371: text defining de-identified data
- Re: ISSUE-10 First party definition, ISSUE-60, ACTION-?
- Re: ACTION-371: text defining de-identified data
- Re: ISSUE-10 First party definition, ISSUE-60, ACTION-?
- Re: ACTION-273/ISSUE-181 (. . . multiple first parties) and ISSUE-10 (what is a first party?)
- Re: ACTION-273/ISSUE-181 (. . . multiple first parties) and ISSUE-10 (what is a first party?)
- RE: text defining de-identified data
- RE: ACTION-273/ISSUE-181 (. . . multiple first parties) and ISSUE-10 (what is a first party?)
- RE: ACTION-273/ISSUE-181 (. . . multiple first parties) and ISSUE-10 (what is a first party?)
- Re: text defining de-identified data
- Re: ACTION-273; ACTION-368; ISSUE-10; Definitions related to first party, multiple first party, service provider/data processor
- Re: ACTION-273/ISSUE-181 (. . . multiple first parties) and ISSUE-10 (what is a first party?)
- Re: text defining de-identified data
- RE: ACTION-371: text defining de-identified data
- Re: ACTION-273; ACTION-368; ISSUE-10; Definitions related to first party, multiple first party, service provider/data processor
- ACTION-371: text defining de-identified data
- RE: ACTION-273/ISSUE-181 (. . . multiple first parties) and ISSUE-10 (what is a first party?)
- RE: Action 368 - Definition of Service Provider/Data Processor
- ACTION-273; ACTION-368; ISSUE-10; Definitions related to first party, multiple first party, service provider/data processor
- Re: ACTION-273/ISSUE-181 (. . . multiple first parties) and ISSUE-10 (what is a first party?)
- Re: Fw: New text Issue 25: Aggregated data: collection and use for audience measurement research
- ACTION-273/ISSUE-181 (. . . multiple first parties) and ISSUE-10 (what is a first party?)
- Re: DNT: Agenda for Call March 6
- Re: DNT: Agenda for Call March 6
- Re: DNT: Agenda for Call March 6
- Re: DNT: Agenda for Call March 6
- Re: Fw: New text Issue 25: Aggregated data: collection and use for audience measurement research
- Re: New text Issue 25: Aggregated data: collection and use for audience measurement research
- Re: New text Issue 25: Aggregated data: collection and use for audience measurement research
- Re: Fw: New text Issue 25: Aggregated data: collection and use for audience measurement research
- Re: Fw: New text Issue 25: Aggregated data: collection and use for audience measurement research
- Re: Fw: New text Issue 25: Aggregated data: collection and use for audience measurement research
- Re: Fw: New text Issue 25: Aggregated data: collection and use for audience measurement research
- Re: Fw: New text Issue 25: Aggregated data: collection and use for audience measurement research
- Re: Fw: New text Issue 25: Aggregated data: collection and use for audience measurement research
- Fw: New text Issue 25: Aggregated data: collection and use for audience measurement research
- RE: DNT: Agenda for Call March 6
- Re: DNT: Agenda for Call March 6
- Re: DNT: Agenda for Call March 6
- RE: DNT: Agenda for Call March 6
- Re: DNT: Agenda for Call March 6
- Re: DNT: Agenda for Call March 6
- RE: DNT: Agenda for Call March 6
- Re: DNT: Agenda for Call March 6
- RE: DNT: Agenda for Call March 6
Tuesday, 5 March 2013
- Re: DNT: Agenda for Call March 6
- Re: DNT: Agenda for Call March 6
- Re: DNT: Agenda for Call March 6 (deux)
- Re: DNT: Agenda for Call March 6
- Re: DNT: Agenda for Call March 6
- Re: DNT: Agenda for Call March 6
- Re: DNT: Agenda for Call March 6
- Re: Chair's comment on charter renewal objection
- Re: DNT: Agenda for Call March 6
- history of action-273 (was Re: DNT: Agenda for Call March 6)
- Re: DNT: Agenda for Call March 6
- Re: DNT: Agenda for Call March 6
- Re: DNT: Agenda for Call March 6
- Re: DNT: Agenda for Call March 6
- Re: DNT: Agenda for Call March 6
- Chair's comment on charter renewal objection
- DNT: Agenda for Call March 6
- Fwd: Do Not Track and Beyond Workshop Report
Monday, 4 March 2013
- Charter Renewal Objection: The Tracking Protection Working Group
- a place in DC for call this Wednesday; Swire in Silicon Valley March 13-15
- text defining de-identified data
- CHINA DAILY INTERVIEW REQUEST
Sunday, 3 March 2013
Friday, 1 March 2013
- Re: ISSUE-10 First party definition, ISSUE-60, ACTION-?
- Re: ISSUE-10 First party definition, ISSUE-60, ACTION-?
- Re: ISSUE-10 First party definition, ISSUE-60, ACTION-?
- RE: RE: RE: ISSUE-10 First party definition, ISSUE-60, ACTION-?
- Re: ISSUE-10 First party definition, ISSUE-60, ACTION-?
- RE: RE: RE: ISSUE-10 First party definition, ISSUE-60, ACTION-?
- charter discussions