Agenda for January 21 call

Dear TPWG members,
we made good progress getting the TPE spec closer to Last Call, which is 
also reflected in tomorrow's agenda.
It got noticeable shorter and, hopefully, we will have a short and 
productive call.

For the document's advancement to Last Call the Working Group needs to 
take specific formal steps.
For more information please refer to: 
http://www.w3.org/2005/10/Process-20051014/tr.html#last-call
The Co-Chairs will talk about these steps next week (January 29).

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-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
http://www.w3.org/wiki/Privacy/TPWG/Proposals_on_status_URL_array_for_compliance_regimes 

The chairs would like to give this ISSUE one more week to flesh out the 
proposals and hopefully solve the ISSUE by consensus without CfO.
January 22: M2 (discussion): List of change proposals is frozen; 
Discussion whether clear consensus emerges for one change proposal
January 29: M3 (announcement): Call for objections to validate / 
determine consensus

ISSUE-240: Do we need to define context?
https://www.w3.org/2011/tracking-protection/track/issues/240
http://www.w3.org/wiki/Privacy/TPWG/Proposals_on_the_definition_of_context
January 22: M2 (discussion): List of change proposals is frozen; 
Discussion whether clear consensus emerges for one change proposal
January 29: M3 (announcement): Call for objections to validate / 
determine consensus

ISSUE-241: Distinguish elements for site-internal use and elements that 
can be re-used by others (1/3)
https://www.w3.org/2011/tracking-protection/track/issues/241
January 22: M1 (discussion): Initial change proposals have been 
submitted; Discussion on change proposals; Call for final list of change 
proposals
January 29: M2 (discussion): List of change proposals is frozen; 
Discussion whether clear consensus emerges for one change proposal

AoB

Reminder for open Calls for Objections:

ISSUE-151: User Agent Requirement: Be able to handle an exception request
https://www.w3.org/2002/09/wbs/49311/tpwg-exception-151/
Deadline - January 22

ISSUE-153: Limitations for add-ons
https://www.w3.org/2002/09/wbs/49311/tpwg-addons-153/
Deadline - January 29



================ 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, 21 January 2014 21:10:55 UTC