- From: Ninja Marnau <ninja@w3.org>
- Date: Wed, 08 Jan 2014 00:27:38 +0100
- To: "public-tracking@w3.org (public-tracking@w3.org)" <public-tracking@w3.org>
I resend the agenda for January 8 to add the issue link and wiki page for ISSUE-240 on “context”. Please feel encouraged to add more text proposals for this issue as it is central for the current definition of tracking in the TPE. Ninja ---------------------------------- 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-153 What are the implications on software that changes requests but does not necessarily initiate them? http://www.w3.org/2011/tracking-protection/track/issues/153 http://www.w3.org/wiki/Privacy/TPWG/Proposals_on_limitations_for_add-ons January 8: M3 (announcement): Call for objections to validate / determine consensus January 22: M5 (deadline): Deadline for inputs to call for objections (2 weeks after M3); Analysis starts 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 January 8: M3 (announcement): Call for objections to validate / determine consensus January 22: M5 (deadline): Deadline for inputs to call for objections (2 weeks after M3); Analysis starts ISSUE-240 Definition of context https://www.w3.org/2011/tracking-protection/track/issues/240 http://www.w3.org/wiki/Privacy/TPWG/Proposals_on_the_definition_of_context This is a new issue resulting from the group’s decision on the definition of tracking. January 8: M1 (discussion): Initial change proposals have been submitted; Discussion on change proposals; Call for final list of change proposals January 15: M2 (discussion): List of change proposals is frozen; Discussion whether clear consensus emerges for one change proposal ISSUE-239 Should tracking status representation include an array of links for claiming compliance by reference? http://www.w3.org/2011/tracking-protection/track/issues/239 January 8: M1 (discussion): Initial change proposals have been submitted; Discussion on change proposals; Call for final list of change proposals January 15: M2 (discussion): List of change proposals is frozen; Discussion whether clear consensus emerges for one change proposal ISSUE-197 How do we notify the user why a Disregard signal is received? http://www.w3.org/2011/tracking-protection/track/issues/197 January 8: M2 (discussion): List of change proposals is frozen; Discussion whether clear consensus emerges for one change proposal January 15: M3 (announcement): Call for objections to validate / determine consensus Current status of TPE spec: Signals for internal / external usage of site elements (the signals formerly called "1" and "3") Email by Matthias http://lists.w3.org/Archives/Public/public-tracking/2014Jan/0000.html AoB ================ 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, 7 January 2014 23:28:07 UTC