- From: David Singer <singer@apple.com>
- Date: Tue, 10 Jun 2014 09:03:55 -0400
- To: Ninja Marnau <ninja@w3.org>
- Cc: "public-tracking@w3.org (public-tracking@w3.org)" <public-tracking@w3.org>
My regrets, I will be travelling back from the W3C AC meeting. On Jun 9, 2014, at 16:28 , Ninja Marnau <ninja@w3.org> wrote: > 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 > http://www.w3.org/wiki/Privacy/TPWG/Change_Proposal_Service_Provider > June 11: M3 (announcement): Call for objections to validate / determine consensus > > 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 > > 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://www.w3.org/wiki/Privacy/TPWG/Change_Proposal_First_Party_Compliance > June 11: M2 (discussion): List of change proposals is frozen; Discussion whether clear consensus emerges for one change proposal > > 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://www.w3.org/wiki/Privacy/TPWG/Change_Proposal_Limitations_on_use_in_Third_Party_Context > June 11: M2 (discussion): List of change proposals is frozen; Discussion whether clear consensus emerges for one change proposal > > 6. Data Minimization > This topic includes an array of related issues. > > ISSUE-31: Minimization - to what extent will minimization be required for use of a particular exemption? (conditional exemptions) > https://www.w3.org/2011/tracking-protection/track/issues/31 > https://www.w3.org/wiki/Privacy/TPWG/Change_Proposals_on_data_minimization > (All text proposals for this topic will be listed on this wiki page) > June 11: M1 (discussion): Initial change proposals have been submitted; Discussion on change proposals; Call for final list of change proposals > > Together with: > ISSUE-199: Limitations on the use of unique identifiers > https://www.w3.org/2011/tracking-protection/track/issues/199 > > ISSUE-211: Should we specify retention periods (extended with transparency) for permitted uses? > https://www.w3.org/2011/tracking-protection/track/issues/211 > > ISSUE-220: Proportionality should be across the board > https://www.w3.org/2011/tracking-protection/track/issues/220 > > ISSUE-233: Data Minimization, Retention and Transparency > https://www.w3.org/2011/tracking-protection/track/issues/233 > > > ================ 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/>, 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>. 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. David Singer Manager, Software Standards, Apple Inc.
Received on Tuesday, 10 June 2014 13:04:25 UTC