BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Sabre//Sabre VObject 4.5.8//EN
CALSCALE:GREGORIAN
LAST-MODIFIED:20260317T122503Z
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-MICROSOFT-CDO-TZID:13
BEGIN:STANDARD
DTSTART:20231105T090000
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
END:STANDARD
BEGIN:STANDARD
DTSTART:20241103T090000
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20240310T100000
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:713b3d1c-3cef-4d64-bd36-fb853400a6da
DTSTAMP:20260317T122503Z
SUMMARY:Deprecation is Hard to Do\, and We Can Do it Better
DTSTART;TZID=America/Los_Angeles:20240925T083000
DTEND;TZID=America/Los_Angeles:20240925T093000
DESCRIPTION:https://www.w3.org/events/meetings/713b3d1c-3cef-4d64-bd36-fb85
 3400a6da/\n\nDeprecating behavior on the web has to be done sparingly. Rem
 oving a behavior from the platform means that some websites that once work
 ed will no longer do so. For some sites and behaviors that may be a good t
 hing\, e.g if it improves security or privacy protections provided to the 
 user. However\, this needs to be weighed against the impact on existing we
 bsite deployments that don’t need or merit that protection and the impac
 t on the web ecosystem of removing that behavior. Failing to sufficiently 
 incorporate those website deployments' needs leaves the deprecation patern
 alistic at best.\n\nOne place this tension arises is in the similarity of 
 authentication and tracking to the browser. Privacy protections that rely 
 upon deprecating behavior\, like third-party cookies\, have had to work ar
 ound this tension.\n\nIn this session we will discuss principles for decid
 ing:\n- what behaviors are candidates for deprecation\,\n- when a deprecat
 ion should proceed\,\n- how to mitigate harm from those deprecations. \n\n
 Participants are encouraged to bring their own examples that reveal challe
 nges to provide concreteness. The chair will use third party cookie deprec
 ation\, storage access\, FedCM\, navigational tracking\, OpenID Connect\, 
 and SAML as a starting point and example that they are familiar with.\n\n*
 *Goal(s):**\nImprove consensus around deprecation of web platform behavior
 s\n\n**Track(s):**\n- Standards\n\nAgenda\n\n5-10 minutes of stage setting
 \, followed by discussion.\n\n**Materials:**\n- [slides](https://www.w3.or
 g/2024/Talks/TPAC/breakouts/deprecation-hard-to-do.pdf)\n- [minutes (initi
 al google doc)](https://docs.google.com/document/d/1DbmE_W5ShymGKCd_aQ8bkf
 UkDthgK5ToE7evW8adBTQ/edit)\n- [Session proposal on GitHub](https://github
 .com/w3c/tpac2024-breakouts/issues/20)
STATUS:CONFIRMED
CREATED:20240916T214951Z
LAST-MODIFIED:20260317T122503Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:-1 Lower Level - Catalina 7
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
END:VCALENDAR
