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

Re: Agenda 10.23.13 - Input on ISSUE-5

From: <mts-std@schunter.org>
Date: Wed, 23 Oct 2013 00:59:02 -0700
Message-ID: <d0b5f70846688a578b11a94877b666ca.squirrel@webmail.schunter.org>
To: "Justin Brookman" <jbrookman@cdt.org>
Cc: public-tracking@w3.org, public-tracking-announce@w3.org
Hi Team,

fyi: this is the latest text proposed for ISSUE-5 that I pulled from the
email thread:

> In general terms, Tracking is the retention or use after a network
transaction is complete, or sharing, of data that is, or can be,
associated with a specific user, user agent, or device.
>
> However, this recommendation recognizes that by choosing to visit a
site, users allow First Parties to retain and use tracking data they
collect directly, or indirectly via Service Providers (though there are
restrictions on sharing); and it allows Third Parties to claim
permission to retain tracking data under some specific conditions (e.g.
for security, auditing, or for deferred processing of raw data).

I suggest to start the discussion on ISSUE-5 from this text. FYI if we do
not reach consensus soon, the next step will be a call for objections with
the latest set of alternative texts as choices.


matthias


> Hi Team,
>
> Enclosed is an agenda for the Oct 23 call.
> Comments/questions are welcome.
>
> On the last call, Working Group members expressed considerable support for
> prioritizing work on the TPE specification.  Issues 5 and 10 are directly
> relevant to the TPE work (despite being currently against the Compliance
> document), so we will proceed to work on them and close those out.
> However, Issues 24 (security) and 25 (audience measurement) are more core
> compliance issues, however, so we are freezing them for the moment as the
> Chairs continue to process the Working Group's comments on the poll and
> last week's call.  We will queue up two other issues on the path toward
> resolution: another definitional issue that has relevance for both TPE and
> Compliance (define collect, use, retain, share) and to clarify the
> interplay between user-generated exceptions and out-of-band consent.
>
> Justin
>
> ------------------------------
>
> 1. Confirmation of scribe.  Volunteers welcome
>
> 2. Offline-caller-identification (see end for instructions)
>
> 3. Update on evolution of TPWG plan (Justin)
>
> 4.  Anyone who was unable to make the call last week who wishes to take up
> to three minutes to provide constructive suggestions for moving the group
> forward may do so! (Carl)
>
> ----------------------------------
> ---- issues for this Call ---
>
> Note: See more info at the end for details.
>
> 5. ISSUE-5  [Matthias/Carl]
>     http://www.w3.org/2011/tracking-protection/track/issues/5
>      http://www.w3.org/wiki/Privacy/TPWG/Change_Proposal_Tracking_Definition
>     DEADLINES for ISSUE-5:
>     October 23: M2 List of change proposals is frozen + Discussion whether
> clear consensus emerges for one change proposal
>     October 30: M3 (announcement): Call for objections to validate /
> determine consensus
>
> 6.  ISSUE-10 [Justin]
>      http://www.w3.org/2011/tracking-protection/track/issues/10
>      http://www.w3.org/wiki/Privacy/TPWG/Change_Proposal_Party_Definitions
>     DEADLINES for ISSUE-10:
>     October 23: M2 List of change proposals is frozen + Discussion whether
> clear consensus emerges for one change proposal
>     October 30: M3 (announcement): Call for objections to validate /
> determine consensus
>
> -------------------
>
> 7.  ISSUE-16 What does it mean to collect, retain, use, and share data?
> (Carl)
> http://www.w3.org/2011/tracking-protection/track/issues/16
> http://www.w3.org/wiki/Privacy/TPWG/Change_Proposal_Transience_Collection
>
>     DEADLINES for ISSUE-16:
>     Oct 23: M0: Initial call for change proposals; Submit all change
> proposals
>     Oct 30: M1 Discuss change proposals + Call for final list of change
> proposals
>
> 8.  ISSUE-201 Interplay between UGE and Out of Band Consent (Matthias)
> http://www.w3.org/2011/tracking-protection/track/issues/201
>
> DEADLINES for ISSUE-201:
>     Oct 23: M0: Initial call for change proposals; Submit all change
> proposals
>     Oct 30: M1 Discuss change proposals + Call for final list of change
> proposals
> ================ Summary Documentation on Resolving ISSUES
> =================
> Complete list of issues against the compliance-current spec:
>  http://www.w3.org/2011/tracking-protection/track/products/5
>
> 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.
> -----
> This URL
> As indicated in our plan, the following issues are currently OPEN for
> discussion in our calls.
> ================ 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, 23 October 2013 07:59:24 UTC

This archive was generated by hypermail 2.3.1 : Friday, 3 November 2017 21:45:19 UTC