Agenda for 21 January 2012 TPE call - V03

Hi Team,

- Corrected the date (sorry for the time-warp ;-)
- Added some pointers to discusions on the mailing list
- Added ISSUE-111 to the list of issues to be discussed



1. Selection of scribe

Old business

2. Review of overdue action items: 

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 oftime. If you are not 
comfortable with the Zakim IRC syntax for associating your phone number, 
please email your name and phone number tonpdoty@w3.orgby 8am PT 
tomorrow. 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.

4. ISSUES marked OPEN
Goal: review open issues at
and assign actions to them

ISSUE-153: What are the implications on software that changes requests 
but does not necessarily initiate them?
       Proposed text (by david and nick): "Software outside of the user 
agent that causes a DNT header to be sent (or modifies existing headers) 
    do so without following the requirements of this section; such 
software is responsible for assuring the expressed preference reflects 
the user's intent."

More input from David Wainberg and discussion by David Singer:>

ISSUE-144: User-granted Exceptions: Constraints on user agent behavior 
while granting and for future requests?
- Discussions:
     - Do we need any constraints on user agent behavior?
     - If yes:
        - What specific constraints should we specify for user-granted 
- Related discussions (probably not during call but rather at the F2F):
        - How can we "police" user agents?
        - How to handle "non-compliant" user agents?
- Response by David Singer:

ISSUE-137: Does hybrid tracking status need to distinguish between first 
party (1) and outsourcing service provider acting as a first party (s)
- Roy (ACTION-354) plans to provide input on ISSUE-137.
- David Singer: "Before you read all the long email, realize that Roy 
points out that the new first-party resource tells a system both (a) 
that my first-party is someone other than me, which is what the 
qualifier indicated, and (b) who that is, which the qualifier relied on 
something else for. So it may well be true (pending reading the text) 
that the qualifier is not needed."

ISSUE-111: Signaling state/existence of site-specific exceptions

As David Singer pointer out: Now that the new approach to exceptions  
and the Javascript API is stabilising, we can revisit ISSUE-111 (which I 
changed from POSTPONED to OPEN)


I have sent an email for batch closing of some ISSUES to the list.
Please review and respond as needed.


6. Announce next meeting & adjourn

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

Zakim teleconference bridge:
Phone +1.617.761.6200 passcode TRACK (87225)
IRC Chat: <>, port 6665, #dnt


Received on Tuesday, 22 January 2013 19:36:21 UTC