- From: Ninja Marnau <ninja@w3.org>
- Date: Tue, 10 Dec 2013 01:31:41 +0100
- To: "public-tracking@w3.org (public-tracking@w3.org)" <public-tracking@w3.org>
----------------- 1. Confirmation of scribe. Volunteers welcome! 2. Offline-caller-identification (see end for instructions) ---------------------------------- ---- Issues for this Call --- Note: See more info at the end for details. ISSUE- 5 Announcement of the result for the Call for Objections - Tracking definition https://www.w3.org/2002/09/wbs/49311/twpg-tracking-5/results December 11: M7 (announcement): Results are announced ISSUE-10 Announcement of the result for the Call for Objections - Party definition https://www.w3.org/2002/09/wbs/49311/tpwg-party-10/results December 11: M7 (announcement): Results are announced ISSUE-239 Should tracking status representation include an array of links for claiming compliance by reference? This is a new issue raised by Roy Fielding on the enabling of multiple compliance regimes. http://www.w3.org/2011/tracking-protection/track/issues/239
 December 11: M0 (announcement): Initial call for change proposals; All change proposals should be drafted December 18: M1 (discussion): Initial change proposals have been submitted; Discussion on change proposals; Call for final list of change proposals ISSUE-153 What are the implications on software that changes requests but does not necessarily initiate them? (Matthias and Brad Kulick) http://www.w3.org/2011/tracking-protection/track/issues/153
 http://www.w3.org/wiki/Privacy/TPWG/Proposals_on_limitations_for_add-ons December 11: M2 (discussion): list of change proposals is frozen; Discussion whether clear consensus emerges for one change proposal ISSUE-151 User Agent Requirement: Be able to handle an exception request http://www.w3.org/2011/tracking-protection/track/issues/151 http://www.w3.org/wiki/Privacy/TPWG/Proposals_on_UA_requirement_to_handle_exceptions December 11: M2 (discussion): list of change proposals is frozen; Discussion whether clear consensus emerges for one change proposal Reminder: Open Call for Objections ISSUES-217, -228 (definition of network interaction and user interaction) https://www.w3.org/2002/09/wbs/49311/tpwg-interact-217/ http://www.w3.org/wiki/Privacy/TPWG/Change_Proposal_Revise_network_interaction_definition December 18: M5 (deadline): Deadline for inputs to call for objections (2 weeks after M3); Analysis starts AoB -------------------------------------------------------------------------- ---- Issues not for this Call but currently processed --- ISSUES-217, -228 (definition of network interaction and user interaction) (Carl) https://www.w3.org/2002/09/wbs/49311/tpwg-interact-217/ http://www.w3.org/wiki/Privacy/TPWG/Change_Proposal_Revise_network_interaction_definition December 18: M5 (deadline): Deadline for inputs to call for objections (2 weeks after M3); Analysis starts ISSUE-16, -204 What does it mean to collect, retain, use, and share data? (Carl or Justin) http://www.w3.org/2011/tracking-protection/track/issues/16 http://www.w3.org/wiki/Privacy/TPWG/Change_Proposal_Transience_Collection December 04: M5 (deadline): Deadline for inputs to call for objections (2 weeks after M3); Analysis starts December 18: M7 (announcement): Results are announced ================ 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 STATUS of the ISSUES: - OPEN During phases M0, M1, M2 - PENDING REVIEW: During phases M3, M5 - CLOSED after M7 All other issues are RAISED. ----- ================ 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 Tuesday, 10 December 2013 00:32:16 UTC