W3C home > Mailing lists > Public > public-tracking@w3.org > December 2013

Agenda for December 18, 2013 call

From: Ninja Marnau <ninja@w3.org>
Date: Tue, 17 Dec 2013 19:16:14 +0100
Message-ID: <52B094EE.3060005@w3.org>
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- 16 Announcement of the result for the Call for Objections - 
Definition of Collect/Retain/Use/Share
https://www.w3.org/2002/09/wbs/49311/tpwg-collect-204/results
http://www.w3.org/2011/tracking-protection/track/issues/16
http://www.w3.org/wiki/Privacy/TPWG/Change_Proposal_Transience_Collection
December 18: M7 (announcement): Results are announced

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/153http://www.w3.org/wiki/Privacy/TPWG/Proposals_on_limitations_for_add-ons
December 18: Final discussion to see whether to proceed to Call for 
Objections
(Potentially M3 (announcement): Call for objections to validate / 
determine consensus)

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 18: M3 (announcement): Call for objections to validate / 
determine consensus
January 8: M5 (deadline): Deadline for inputs to call for objections (2 
weeks after M3); Analysis starts

ISSUE-240 Definition of context
This is a new issue resulting from the group’s decision on the 
definition of tracking.
December 18: M0 (announcement): Initial call for change proposals; All 
change proposals should be drafted
January 8: M1 (discussion): Initial change proposals have been 
submitted; Discussion on change proposals; Call for final list of change 
proposals

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
December 18: M1 (discussion): Initial change proposals have been 
submitted; Discussion on change proposals; Call for final list of change 
proposals
January 8: 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
December 18: M1 (discussion): Initial change proposals have been 
submitted; Discussion on change proposals; Call for final list of change 
proposals
January 8: M2 (discussion): List of change proposals is frozen; 
Discussion whether clear consensus emerges for one change proposal

AoB

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; 
Analysis starts
January 8: 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, 17 December 2013 18:16:35 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 17 December 2013 18:16:36 UTC