W3C home > Mailing lists > Public > public-web-adv@w3.org > February 2020

Re: [web-adv] minutes and next meeting, 13 February

From: Achim Schlosser <achim.schlosser@enid.eu>
Date: Thu, 13 Feb 2020 17:50:31 +0000
To: "Zucker-Scharff, Aram" <Aram.Zucker-Scharff@washpost.com>, "public-web-adv@w3.org" <public-web-adv@w3.org>
Message-ID: <70C7B9C1-BC1F-4BFF-AB68-5F9E92194918@enid.eu>
Dear Aram,


Thanks for pushing into that direction, this is clearly an area that needs a closer look. From a European perspective, it would naturally be mainly interesting to discuss the interdependencies to Frameworks like the IAB Europe TCF (2.0) which is much more extensive than the CCPA Framework (as it needs to cover much more ground).

TCF has the advantage here that it actually drills down into specific data processing purposes and is quite extensively documented. One could actually link those to Sandbox Use-Cases (having that said it will most probably change quite a lot in a Sandboxed world). 

Unrelated to details one has to agree as you said how those could be integrated into a Sandbox API. Won't make to call today, but wanted to express my interest in this topic. 

Best


Achim Schlosser 
CTO | Member of the executive board
 
European netID Foundation
Elgendorfer Str. 57 - D-56410 Montabaur
www.enid.foundation <http://www.enid.foundation/>
 


´╗┐On 13.02.20, 18:02, "Zucker-Scharff, Aram" <Aram.Zucker-Scharff@washpost.com> wrote:

    Hi all,
    
    Thanks for this dashboard, it's very helpful to see it all laid out. I wanted to share a proposal I've been working on with this group. As we've talked about in the past the CCPA work that is ongoing has been very clear about needing to respect a signal from a browser or extension level, but has not provided any particular technical framework to do so. The IAB's CCPA Framework seems to be the most popular approach to CCPA compliance, and it is the one we are currently using, so I wrote an extension to it that should allow interaction with the existing framework API to indicate a Do Not Sell signal, with the goal of having as small an impact on the existing specification as possible. Unfortunately, the IAB has declined to make their framework documentation available anywhere but via PDF on their own website, so I had to rewrite it in order to discuss it with vendors on launch. And I've gone forward with making my proposal as a pull request against that repo, since I lack anywhere else to put it. I'd be interested in this group's feedback - https://github.com/AramZS/IAB-CCPA-Framework-Implementation-Notes/blob/setUSPData-proposal/setUSPData-proposal.md 
    
    -- Aram Zucker-Scharff
    Ad Engineering Director, RED
    The Washington Post
    +1-703-829-0532
     
    
    On 2/11/20, 2:25 PM, "Wendy Seltzer" <wseltzer@w3.org> wrote:
    
        CAUTION: EXTERNAL SENDER
        
        Hi Web Advertising BG,
        
        Draft minutes from 6 February:
        https://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_2020_02_06-2Dweb-2Dadv-2Dminutes.html&d=DwIDaQ&c=RAhzPLrCAq19eJdrcQiUVEwFYoMRqGDAXQ_puw5tYjg&r=4ydXbc7IBUz-Cc0XwXf-b8xnEAdZxMjj-0KISFR0cBw&m=nGF2aKCPdEUHw50eWzZLEt03B4a5U6pFgqnILwhPkwE&s=ADR8y1hvRY8Gwh--HRS-nsJ19OogcFgQ4Oy4zsndxz8&e=
        
        The group's minutes should be available to BG participants and W3C
        members, once you log in with your W3C account.
        
        Thanks Alan for chairing a discussion that included aggregate reporting
        APIs, opt-in advertising, and F2F.
        
        I had an action to look into document management, and got help from
        Philippe to set up a dashboard collecting issues from across the repos
        we've reviewed: https://urldefense.proofpoint.com/v2/url?u=https-3A__w3c.github.io_web-2Dadvertising_dashboard_&d=DwIDaQ&c=RAhzPLrCAq19eJdrcQiUVEwFYoMRqGDAXQ_puw5tYjg&r=4ydXbc7IBUz-Cc0XwXf-b8xnEAdZxMjj-0KISFR0cBw&m=nGF2aKCPdEUHw50eWzZLEt03B4a5U6pFgqnILwhPkwE&s=Z9qRv5cb3UtsLLHrIhLL4L_gq_8BjFiizfIgMYfW3TI&e=
        (Note that the order of repo and issue display is currently random, and
        different across views or viewers.)
        
        Let's discuss 1) issue-management and group work, including a quick
        stock-taking of the dashboard issues. 2) Possibilities for F2F meeting
        and outreach event(s), such as 3-day BG working meeting, and targeted
        outreach at existing events.
        
        Next Meeting: Thursday, 13 Feburary, 2pm Eastern.
        
        Draft agenda:
        * Agenda-curation, introductions
        * Issue management and dashboard of repos:
         https://urldefense.proofpoint.com/v2/url?u=https-3A__w3c.github.io_web-2Dadvertising_dashboard_&d=DwIDaQ&c=RAhzPLrCAq19eJdrcQiUVEwFYoMRqGDAXQ_puw5tYjg&r=4ydXbc7IBUz-Cc0XwXf-b8xnEAdZxMjj-0KISFR0cBw&m=nGF2aKCPdEUHw50eWzZLEt03B4a5U6pFgqnILwhPkwE&s=Z9qRv5cb3UtsLLHrIhLL4L_gq_8BjFiizfIgMYfW3TI&e=
        * F2F and outreach events?
        * AOB
        
        
        Call-in info at:
        https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.w3.org_Archives_Member_internal-2Dweb-2Dadv_2018Aug_0000.html&d=DwIDaQ&c=RAhzPLrCAq19eJdrcQiUVEwFYoMRqGDAXQ_puw5tYjg&r=4ydXbc7IBUz-Cc0XwXf-b8xnEAdZxMjj-0KISFR0cBw&m=nGF2aKCPdEUHw50eWzZLEt03B4a5U6pFgqnILwhPkwE&s=xYzClEl5PLN34IXlLFi01UX2yVex8uZpDYw3SvxxlaI&e=
        (let me know if you need me to send it to you directly).
        
        irc is https://urldefense.proofpoint.com/v2/url?u=http-3A__irc.w3.org&d=DwIDaQ&c=RAhzPLrCAq19eJdrcQiUVEwFYoMRqGDAXQ_puw5tYjg&r=4ydXbc7IBUz-Cc0XwXf-b8xnEAdZxMjj-0KISFR0cBw&m=nGF2aKCPdEUHw50eWzZLEt03B4a5U6pFgqnILwhPkwE&s=l5klBOp3hHnnEmUlVWtDao1xpWF-1v2O724pTpR_nt0&e=  #web-adv
        Github repo: https://github.com/w3c/web-advertising
        
        
        Thanks,
        --Wendy
        --
        Wendy Seltzer -- wseltzer@w3.org +1.617.715.4883 (office)
        Strategy Lead and Counsel, World Wide Web Consortium (W3C)
        https://urldefense.proofpoint.com/v2/url?u=https-3A__wendy.seltzer.org_&d=DwIDaQ&c=RAhzPLrCAq19eJdrcQiUVEwFYoMRqGDAXQ_puw5tYjg&r=4ydXbc7IBUz-Cc0XwXf-b8xnEAdZxMjj-0KISFR0cBw&m=nGF2aKCPdEUHw50eWzZLEt03B4a5U6pFgqnILwhPkwE&s=uCZ6UWqlVE5v3urdmM_cP9qkxmxGIBcXioRrchMUl_c&e=         +1.617.863.0613 (mobile)
        
        
        
        
        
        
    
    

Received on Thursday, 13 February 2020 17:53:47 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 13 February 2020 17:53:48 UTC