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

DNT: financial accounting slides for Wednesday call

From: Peter Swire <peter@peterswire.net>
Date: Tue, 26 Mar 2013 21:56:13 -0700
To: Peter Swire <peter@peterswire.net>, "public-tracking@w3.org" <public-tracking@w3.org>
CC: Rena Mears <renamears@comcast.net>
Message-ID: <CD77F3BE.7439D%peter@peterswire.net>
Hello DNT folks:

Attached please find a few power points that are the outline for the financial auditing discussion in the last half hour of this Wednesday's call.

Thank you,

Peter



Professor Peter P. Swire
C. William O'Neill Professor of Law
    Ohio State University
240.994.4142
www.peterswire.net

From: Peter Swire <peter@peterswire.net<mailto:peter@peterswire.net>>
Date: Tuesday, March 26, 2013 12:53 PM
To: "public-tracking@w3.org<mailto:public-tracking@w3.org>" <public-tracking@w3.org<mailto:public-tracking@w3.org>>
Cc: Rena Mears <renamears@comcast.net<mailto:renamears@comcast.net>>
Subject: DNT: Agenda for March 27 call
Resent-From: <public-tracking@w3.org<mailto:public-tracking@w3.org>>
Resent-Date: Tuesday, March 26, 2013 12:54 PM

---------------------------
Administrative

Chair:  Peter Swire
---------------------------

1.  Confirmation of scribe – glad to accept volunteer in advance

2.  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.

---------------------------
TPE: Matthias Schunter
---------------------------

3.  TPE Handling Out-of-Band Consent (including ISSUE-152)

- Question is how to balance efficiency for the site with transparency for the users

4.  ISSUE-187: Approach to exception handling

- Goal is to ensure that the current text in the spec on consent collection addresses the need of all participants:
The current language in the spec that tries to constitute such a standard is in Section6.3.1:
"User Interaction
The call to store an exception MUST reflect the user's intention to grant an exception, at the time of the call. This intention MUST be determined by the site prior to each call to store an exception, at the time of the call. (This allows the user to change their mind, and delete a stored exception, which might then trigger the site to explain, and ask for, the exception again). It is the responsibility solely of the site making the call to determine that a call to record an exception reflects the user's informed consent at the time of thecall."

---------------------------
Compliance Spec: Peter Swire
---------------------------

 5.  Prepare to develop agenda for a Wednesday discussion of user education and user interface on April 10.  Initial proposed agenda items due to mailing list by the end of March.

6.   Recognizing the interdependence of many issues within the compliance spec, we are introducing a new issue category “Pending Review Stable.”  The category will fall between “Pending Review” and “Closed.”  “Pending Review Stable” means that discussions of the issue will cease until other issues are stable.  When the Editors decide to add proposed text to the Tracking Compliance and Scope, the issue will move from open to pending review.  When the Chairs decide the text is stable, a note will be added to the issue-tracker stating the issue is “Pending Review Stable.”  There could potentially be multiple stable options when the Chairs decide an issue is “Pending Review Stable.”  Discussion of an issue in “Pending Review Stable” can re-start if there is a new proposal that gains significant support.

7.  ISSUE-25, Audience Measurement. Last week, the group led by Kathy Joe explained its proposed permitted use for audience measurement.  This week, a significant discussion item is for the group to ask questions, comment, and suggest possible amendments to the proposal. The group is planning to revise the text slightly since last week, in response to that discussion.

8.  ACTION-371: De-identification.  Dan Auerbach has drafted text, with comments on the list.  Is the normative text ready to move to Pending Review–Stable?

9.  ACTION-372, service providers and debugging.  David Wainberg has submitted text, with Jonathan Mayer comments on the list.
---------------------------

Presentation onFinancial Auditing

---------------------------

10.  In the last half hour, Rena Mears and another expert will brief us on issues related to the financial auditing permitted use.  Until recently Rena was the global lead of the Privacy and Data Protection group at Deloitte and Touche.
---------------------------

11.  Announce next meeting & adjourn


================ Infrastructure =================

Zakim teleconference bridge:
VoIP:    sip:zakim@voip.w3.org<file://localhost/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

****


Professor Peter P. Swire
C. William O'Neill Professor of Law
    Ohio State University
240.994.4142
www.peterswire.net



Received on Wednesday, 27 March 2013 04:56:49 UTC

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