Scheduled calls for Topics

[leeronisrael]

We are holding regular phone calls, usually once a month, to resolve the details of the Topics proposal. These calls should be good places for a dedicated group to address open issues and suggest technical fixes.

The Topics W3C meeting takes place every 4 weeks on Monday at 11am US Eastern Time. You can see when the next meeting will take place in this doc.

The call will take place on Google Meet Video call link: meet.google.com/hdz-rbcp-rrb Or dial: ‪(US) +1 253-289-6906‬ PIN: ‪365 612 889 56‬# More phone numbers: tel.meet/hdz-rbcp-rrb?pin=8462125950122

Agenda proposals, attendance records, notes will happen in this doc.

For a speaker queue, we will use the Google Meet "Raise My Hand" feature.

If you want to participate in the call, please make sure you join the PATCG: w3.org/community/patcg.

[bmayd]

There is a PARAKEET call scheduled for the same time (11am eastern on January 11th); don't know if it is going to happen, but mentioning it as it may impact attendance. Apologize for mentioning so late, but just saw that this was scheduled.

[erik-anderson]

Thanks for the callout, Brian. This would indeed normally conflict but, as I just posted in https://github.com/WICG/privacy-preserving-ads/issues/3, we are cancelling the January 11th instance, so no conflict exists for this meeting.

[marksjc]

The current draft includes opt-in and opt-out discussion and a requirement to identify individuals "very difficult" based on this API. Any tracking must be opt-in or declared as to business practice need, the intent of EU standards, reading that as only applying to cookies will subject the API and adopters to sanction, my perspective. Sounds like others don't agree or don't understand the EU regulations: rather than debate it suggest a legal opinion would be good guidance, with both sides if possible. Any attempt to technologically re-enable and not disclose intent will cost a lot of time, hinder adoption, and for every single use suggested be contested in EU .

I propose opt-in only with full disclosure and auditing to ensure compliance. Opt-out is going to complicate already complex opt-out options in US, making them less manageable and driving opt-out all decisions.

The API must be designed to prevent any association to individuals without opt-in consent specifically to personal matching. Not very difficult, impossible. Any API that can be traced to user or machine is a tool for surveillance which consumers do not want and have not consented to. Consumers do not wish advertising, with personal advertising being the most invasive, no matter how they are identified. Storing topics locally meams they can be accessed and serve to identify a machine and login ID. If topics are opted in and reported cache 3 or any very low number and send them to a collection site for evaluation as to non specific location and browser version info.

Again, attempts to provide identification contrary to EU is creative yet sure to be found out and sanctioned.

[dmarti]

@marksjc Topics API provides a subset of the tracking capabilities of third-party cookies. A site that can get consent to third-party cookie tracking should, in theory, also be able to explain and obtain consent to the tracking provided by Topics API.

Existing consent management platforms have already adapted to obtain valid consent for third-party cookies in the EU, so would probably be a good place to look for how to do consent for Topics API.

More info on industry consent standards: IAB Tech Lab Finalizes Global Privacy Platform and Advises the Industry to Prepare for Updated US State-Level Signaling – IAB Tech Lab

[jaimonino]

Hi, will there be regular calls following a predicable path so we can plan them in our calendars ? (Julien Aimonino, Criteo, Product Manager)

[leeronisrael]

I apologize for the unpredictable schedule. We originally sought to A) hold the Topics call on a monthly basis, and B) avoid conflict with the biweekly ARA call. This, combined with multiple US public holidays, led to a bit of an erratic schedule. We will share an updated, hopefully more predictable schedule soon.

[eligrey]

I wasn't able to attend the Match 13th meeting. I have some feedback about opt-out signals that must not have been considered.

Chrome didn't even consider that I have "Do Not Track" enabled (a feature provided by Chrome) before automatically activating Topics tracking on my phone.

[leeronisrael]

Quick update - The Topics W3C call is to be held every 4th Monday at 11a US ET, beginning on 4/10 (followed by 5/8, 6/5, 7/3...and so on). Hopefully this provides a more predictable schedule for attendees. We welcome any feedback on the timing of the call.

[npdoty]

Is this subgroup planning to meet next Monday, July 3rd? That's part of the American holiday weekend for my org. I don't know if feedback/conversation is especially needed on the current timeline.

[leeronisrael]

Thanks for flagging @npdoty! We propose skipping the July 3rd meeting due to the US holiday. The next meeting would be Monday, July 31.

[leeronisrael]

Confirming that we will skip the July 3rd meeting.

[anderagakura]

The event was (is) still planned in the W3C calendar... hopefully I got the update here

[leeronisrael]

Hi All - We plan to skip the 9/25 scheduled call for Topics. There are many folks OOO and a limited agenda. Let us know if you have any concerns.

[anderagakura]

In the calendar, the meeting is still confirmed...

[dmarti]

Is there a call Monday 23 October (now)?

[seanturner]

Please let me know if we need to extend the scheduled meetings. Right now, the calls end in Dec.

[bmayd]

Will there be Topics meetings scheduled in 2024? The Topics W3C Calls Google Doc currently indicates:

The next meeting will be on January 15th, 2023 at 11:00 am US ET. The following meetings will be held on 2/12/24, 3/11/24 and so on.

[leeronisrael]

Hi @bmayd - That should read January 15th, 2024, not 2023. Thanks for flagging. We are cancelling Monday's meeting due to lack of agenda and the US holiday. I've sent out a message to the Chromium group here.