BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Sabre//Sabre VObject 4.5.8//EN
CALSCALE:GREGORIAN
LAST-MODIFIED:20241016T222602Z
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:f2deb029-f7d6-4407-a4d6-66dfde629f8e
DTSTAMP:20241016T222602Z
SUMMARY:What security guidance should we give web developers?
DTSTART;TZID=America/Los_Angeles:20240925T131500
DTEND;TZID=America/Los_Angeles:20240925T141500
DESCRIPTION:https://www.w3.org/events/meetings/f2deb029-f7d6-4407-a4d6-66df
 de629f8e/\n\nThere are a lot of web platform features that relate to secur
 ity\, and they generally have pretty comprehensive documentation on MDN. B
 ut there's not a lot of normative guidance: which features should people u
 se (and which should they avoid)\, why should they use them\, and how shou
 ld they use them?\n\nIn the [Security Web Application Guidelines Community
  Group](https://github.com/w3c-cg/swag/) (SWAG CG) we've been trying to un
 derstand these questions\, partly so we can update MDN with this sort of n
 ormative guidance for developers with deadlines. So this very open-ended s
 ession is proposed to gather input on security documentation requirements.
 \n\nAgenda\n\n**Chairs:**\nWill Bamberg\, Daniel Appelquist\n\n**Descripti
 on:**\nThere are a lot of web platform features that relate to security\, 
 and they generally have pretty comprehensive documentation on MDN. But the
 re's not a lot of normative guidance: which features should people use (an
 d which should they avoid)\, why should they use them\, and how should the
 y use them?\n\nIn the [Security Web Application Guidelines Community Group
 ](https://github.com/w3c-cg/swag/) (SWAG CG) we've been trying to understa
 nd these questions\, partly so we can update MDN with this sort of normati
 ve guidance for developers with deadlines. So this very open-ended session
  is proposed to gather input on security documentation requirements.\n\n**
 Goal(s):**\nSecurity documentation requirements.\n\n\n**Agenda:**\nhttps:/
 /wbamberg.github.io/web-security-w3c-breakouts-september-2024/Templates/Ov
 erview.html\n\n**Materials:**\n- [slides](https://www.w3.org/2024/Talks/TP
 AC/breakouts/web-security.html)\n- [minutes](https://www.w3.org/2024/09/25
 -mdn-security-minutes.html)\n- [Session proposal on GitHub](https://github
 .com/w3c/tpac2024-breakouts/issues/96)
STATUS:CONFIRMED
CREATED:20240916T220327Z
LAST-MODIFIED:20241016T222602Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:4 Concourse Level - Redondo
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
END:VCALENDAR