- From: Rob Sherman <robsherman@fb.com>
- Date: Wed, 21 May 2014 14:41:17 +0000
- To: "public-tracking@w3.org (public-tracking@w3.org)" <public-tracking@w3.org>
- Message-ID: <CFA2323C.774F%robsherman@fb.com>
I see that ISSUE-170 (data append) is on the agenda for today and that one of the proposals listed in the wiki (Proposal 2) is an outdated suggestion that I’d made in an effort to clarify John Simpson’s proposal (Proposal 1). Since John didn’t accept my edit and the other proposals in the wiki now cover the range of approaches for this issue, to simplify matters I’ll withdraw Proposal 2 and we can work through the remaining options as a group. Thanks — look forward to talking through this today. Rob From: Ninja Marnau <ninja@w3.org<mailto:ninja@w3.org>> Date: Monday, May 19, 2014 at 5:23 PM To: "public-tracking@w3.org<mailto:public-tracking@w3.org> (public-tracking@w3.org<mailto:public-tracking@w3.org>)" <public-tracking@w3.org<mailto:public-tracking@w3.org>> Subject: Agenda for May 21 TPWG call Resent-From: <public-tracking@w3.org<mailto:public-tracking@w3.org>> Resent-Date: Monday, May 19, 2014 at 5:23 PM AGENDA: ---------------------------------- 1. Confirmation of scribe. Volunteers welcome! 2. Offline-caller-identification (see end for instructions) ---------------------------------- --- Issues for this Call --- 3. Service Providers ISSUE-206: Service Provider name and requirements https://www.w3.org/2011/tracking-protection/track/issues/206<https://urldefense.proofpoint.com/v1/url?u=https://www.w3.org/2011/tracking-protection/track/issues/206&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=Z08z%2F0RKK7k0ZWnWkl%2FVHThU6eMXcoJl9ldvo4wGeN0%3D%0A&m=YyCYl9ZhgH9DuAa3fHp8zEJGwP1dc6jzmx5pPbBnOk4%3D%0A&s=a6f848a257cdd4b56f0a8c5a34b927c9239581433fb721040f15fe143acc5a36> http://www.w3.org/wiki/Privacy/TPWG/Change_Proposal_Service_Provider<https://urldefense.proofpoint.com/v1/url?u=http://www.w3.org/wiki/Privacy/TPWG/Change_Proposal_Service_Provider&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=Z08z%2F0RKK7k0ZWnWkl%2FVHThU6eMXcoJl9ldvo4wGeN0%3D%0A&m=YyCYl9ZhgH9DuAa3fHp8zEJGwP1dc6jzmx5pPbBnOk4%3D%0A&s=e7c395b172dc4130fb1ec5f64bfe91a657b4735fcf918facfc137ec4c8f95091> May 21: M1 (discussion): Initial change proposals have been submitted; Discussion on change proposals; Call for final list of change proposals Together with: 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? https://www.w3.org/2011/tracking-protection/track/issues/49<https://urldefense.proofpoint.com/v1/url?u=https://www.w3.org/2011/tracking-protection/track/issues/49&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=Z08z%2F0RKK7k0ZWnWkl%2FVHThU6eMXcoJl9ldvo4wGeN0%3D%0A&m=YyCYl9ZhgH9DuAa3fHp8zEJGwP1dc6jzmx5pPbBnOk4%3D%0A&s=497fd6a2ec33c635b38bda1e04336c243cccdb33e9e7b119beb618ba8fc77291> 4. Data Append and First Parties ISSUE-170: Definition of and what/whether limitations around data append and first parties https://www.w3.org/2011/tracking-protection/track/issues/170<https://urldefense.proofpoint.com/v1/url?u=https://www.w3.org/2011/tracking-protection/track/issues/170&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=Z08z%2F0RKK7k0ZWnWkl%2FVHThU6eMXcoJl9ldvo4wGeN0%3D%0A&m=YyCYl9ZhgH9DuAa3fHp8zEJGwP1dc6jzmx5pPbBnOk4%3D%0A&s=76801c03ae6fb8fc4164b4ccee60cbcd1d8d3a8c89ca049254b7a6a85ab455dc> https://www.w3.org/wiki/Privacy/TPWG/Change_Proposal_First_Party_Compliance<https://urldefense.proofpoint.com/v1/url?u=https://www.w3.org/wiki/Privacy/TPWG/Change_Proposal_First_Party_Compliance&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=Z08z%2F0RKK7k0ZWnWkl%2FVHThU6eMXcoJl9ldvo4wGeN0%3D%0A&m=YyCYl9ZhgH9DuAa3fHp8zEJGwP1dc6jzmx5pPbBnOk4%3D%0A&s=a866c84a5ec9633a1e02f360b19d05ee62759caf1ff3f7380cd4ae5c2965fc28> May 21: M0 (announcement): Initial call for change proposals; All change proposals should be drafted 5. Context Separation ISSUE-219: Context Separation - Limitations on use in a 3rd party context of data collected in a 1st party context https://www.w3.org/2011/tracking-protection/track/issues/219<https://urldefense.proofpoint.com/v1/url?u=https://www.w3.org/2011/tracking-protection/track/issues/219&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=Z08z%2F0RKK7k0ZWnWkl%2FVHThU6eMXcoJl9ldvo4wGeN0%3D%0A&m=YyCYl9ZhgH9DuAa3fHp8zEJGwP1dc6jzmx5pPbBnOk4%3D%0A&s=5236fb6166c9f1df87dba77ccf5567da6772dc2f4d2d6858e1ef8fdaacc02a37> https://www.w3.org/wiki/Privacy/TPWG/Change_Proposal_Limitations_on_use_in_Third_Party_Context<https://urldefense.proofpoint.com/v1/url?u=https://www.w3.org/wiki/Privacy/TPWG/Change_Proposal_Limitations_on_use_in_Third_Party_Context&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=Z08z%2F0RKK7k0ZWnWkl%2FVHThU6eMXcoJl9ldvo4wGeN0%3D%0A&m=YyCYl9ZhgH9DuAa3fHp8zEJGwP1dc6jzmx5pPbBnOk4%3D%0A&s=1fec3bf5c508748c8e255bd3e83d56a4503e06d8ae2b3ac90e228517cf7b3594> May 21: M0 (announcement): Initial call for change proposals; All change proposals should be drafted ================ Summary Documentation on Resolving ISSUES ================= PHASES to resolve issues: M0 (announcement): Initial call for change proposals; All change proposals should be drafted M1 (discussion): Initial change proposals have been submitted; Discussion on change proposals; Call for final list of change proposals M2 (discussion): List of change proposals is frozen; Discussion whether clear consensus emerges for one change proposal M3 (announcement): Call for objections to validate / determine consensus M5 (deadline): Deadline for inputs to call for objections (2 weeks after M3); Analysis starts M7 (announcement): Results are announced ================ Infrastructure ================= Zakim teleconference bridge: VoIP: sip:zakim@voip.w3.org Phone +1.617.761.6200 passcode TRACK (87225) IRC Chat: irc.w3.org<http://irc.w3.org/><https://urldefense.proofpoint.com/v1/url?u=http://irc.w3.org/&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=Z08z%2F0RKK7k0ZWnWkl%2FVHThU6eMXcoJl9ldvo4wGeN0%3D%0A&m=YyCYl9ZhgH9DuAa3fHp8zEJGwP1dc6jzmx5pPbBnOk4%3D%0A&s=a8ba77d3a29a831c1647633533ea17d737578e2ccb133adc94df676f2c97dc12>, port 6665, #dnt OFFLINE caller identification: If you intend to join the phone call, you must either associate your phone number with your IRC username once you've joined the call (command: "Zakim, [ID] is [name]" e.g., "Zakim, ??P19 is schunter" in my case), or let Nick know your phone number ahead of time. If you are not comfortable with the Zakim IRC syntax for associating your phone number, please email your name and phone number to npdoty@w3.org<mailto:npdoty@w3.org><mailto:npdoty@w3.org><mailto:npdoty@w3.org>. We want to reduce (in fact, eliminate) the time spent on the call identifying phone numbers. Note that if your number is not identified and you do not respond to off-the-phone reminders via IRC, you will be dropped from the call. <https://urldefense.proofpoint.com/v1/url?u=https://www.w3.org/wiki/Privacy/TPWG/Change_Proposal_First_Party_Compliance&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=Z08z%2F0RKK7k0ZWnWkl%2FVHThU6eMXcoJl9ldvo4wGeN0%3D%0A&m=YyCYl9ZhgH9DuAa3fHp8zEJGwP1dc6jzmx5pPbBnOk4%3D%0A&s=a866c84a5ec9633a1e02f360b19d05ee62759caf1ff3f7380cd4ae5c2965fc28>
Received on Wednesday, 21 May 2014 14:41:45 UTC