Re: Agenda for June 25 TPWG call

Please accept my regrets, I have a conflict and cannot attend today’s call.

Regards,
Sid

On Jun 24, 2014, at 8:18 AM, Ninja Marnau <ninja@w3.org> wrote:

> AGENDA: 
> ---------------------------------- 
> 
> Confirmation of scribe. Volunteers welcome! 
> 
> Offline-caller-identification (see end for instructions) 
> 
> ---------------------------------- 
> --- Issues for this Call --- 
> 
> 1. 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 25: M3 (announcement): Call for objections to validate / determine consensus 
> 
> 2. 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
> June 25: M2 (discussion): List of change proposals is frozen; Discussion whether clear consensus emerges for one change proposal 
> 
> 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
> 
> 3. Use of "tracking" in compliance
> 
> ISSUE-203: Use of "tracking" in third-party compliance
> https://www.w3.org/2011/tracking-protection/track/issues/203
> https://www.w3.org/wiki/Privacy/TPWG/Change_Proposal_Tracking_Third_Party_Compliance
> June 25: M1 (discussion): Initial change proposals have been submitted; Discussion on change proposals; Call for final list of change proposals 
> 
> 4. Link shorteners/ID providers
> 
> ISSUE-97: Re-direction, shortened URLs, click analytics -- what kind of tracking is this?
> https://www.w3.org/2011/tracking-protection/track/issues/97
> https://www.w3.org/wiki/Privacy/TPWG/Change_Proposals_on_link_shorteners_and_ID_providers
> June 25: M1 (discussion): Initial change proposals have been submitted; Discussion on change proposals; Call for final list of change proposals 
> 
> Together with:
> ISSUE-99: How does DNT work with identity providers?
> https://www.w3.org/2011/tracking-protection/track/issues/99
> 
> 5. Open Call for Objections: Data Append and First Parties
> 
> https://www.w3.org/2002/09/wbs/49311/tpwg-first-parties-170/
> July 2: M5 (deadline): Deadline for inputs to call for objections (2 weeks after M3); Analysis starts 
> 
> ================ 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.

Received on Wednesday, 25 June 2014 14:23:01 UTC