BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Sabre//Sabre VObject 4.5.8//EN
CALSCALE:GREGORIAN
NAME:TPAC 2024 Calendar
X-WR-CALNAME:TPAC 2024 Calendar
LAST-MODIFIED:20260317T123819Z
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:d7c4fa27-06fc-4ef0-be27-487d0ab4173a
DTSTAMP:20240923T150844Z
SUMMARY:Accessibility Guidelines Working Group
DTSTART;TZID=America/Los_Angeles:20240923T090000
DTEND;TZID=America/Los_Angeles:20240923T180000
DESCRIPTION:https://www.w3.org/events/meetings/d7c4fa27-06fc-4ef0-be27-487d
0ab4173a/\n\n\n\nAgenda\n\n| Start | End | Session Title |\n| --------
| ------- |------- |\n| 9:00 | 9:30 | Welcome\, Introductions\, and Logist
ics |\n| 9:30 | 12:30 | Retrospective |\n| 12:30 | 13:30 | Lunch |\n| 13:3
0 | 17:30 | Conformance exercises |\n\nBreaks will be included within the
main sessions
STATUS:CONFIRMED
CREATED:20240614T163337Z
LAST-MODIFIED:20240923T150844Z
SEQUENCE:9
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Accessibility Guid
elines Working Group:mailto:public-ag-admin@w3.org
LOCATION:4 Concourse Level - Palos Verdes
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:76c7e7a2-7fc9-4498-bdab-ae61cb573696
DTSTAMP:20240923T203719Z
SUMMARY:Accessible Rich Internet Applications Working Group
DTSTART;TZID=America/Los_Angeles:20240923T090000
DTEND;TZID=America/Los_Angeles:20240923T180000
DESCRIPTION:https://www.w3.org/events/meetings/76c7e7a2-7fc9-4498-bdab-ae61
cb573696/\n\n\n\nAgenda: https://github.com/w3c/aria/wiki/TPAC-2024-ARIA-M
eetings
STATUS:CONFIRMED
CREATED:20240614T161711Z
LAST-MODIFIED:20240923T203719Z
SEQUENCE:5
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Accessible Rich In
ternet Applications Working Group:mailto:public-aria@w3.org
LOCATION:4 Concourse Level - Redondo
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:29989aad-dcba-4bef-9167-76cbc6fc4d3d
DTSTAMP:20241011T152640Z
SUMMARY:Decentralized Identifier Working Group
DTSTART;TZID=America/Los_Angeles:20240923T090000
DTEND;TZID=America/Los_Angeles:20240923T180000
DESCRIPTION:https://www.w3.org/events/meetings/29989aad-dcba-4bef-9167-76cb
c6fc4d3d/\n\n\n\nAgenda\n\n| Start | End | Session Title |\n| --------
| ------- |------- |\n| 9:00 | 9:30 | Welcome\, Introductions\, and Logist
ics |\n| 9:30 | 10:00 | State of the Industry |\n| 10:00 | 10:30 | A short
history of DIDs |\n| 10:30 | 11:00 | Break |\n| 11:00 | 11:30 | DID Metho
d Standardization |\n| 11:30 | 11:45 | Self-Describing DID Methods |\n| 11
:45 | 12:00 | DID DHT |\n| 12:00 | 12:15 | BTCR lessons learned and improv
ements |\n| 12:15 | 12:30 | Work Item Inventory |\n| 12:30 | 13:30 | Lunch
|\n| 13:30 | 14:00 | DID Registry Process |\n| 14:00 | 14:30 | DID Metho
ds |\n| 14:30 | 15:00 | DID Extensions |\n| 15:00 | 15:30 | DID Rubric |\n
| 15:30 | 16:00 | DID Traits (Feature Sets) |\n| 16:00 | 16:30 | Break |\n
| 16:30 | 17:30 | Controller Document |\n| 17:30 | 18:00 | What's Interope
rability? How can we test/demonstrate it |
STATUS:CONFIRMED
CREATED:20240614T163331Z
LAST-MODIFIED:20241011T152640Z
SEQUENCE:7
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Decentralized Iden
tifier Working Group:mailto:public-did-wg@w3.org
LOCATION:4 Concourse Level - Capistrano
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:900ac419-eda7-404d-9750-d87b8c83dc05
DTSTAMP:20240921T233032Z
SUMMARY:Internationalization Working Group
DTSTART;TZID=America/Los_Angeles:20240923T090000
DTEND;TZID=America/Los_Angeles:20240923T180000
DESCRIPTION:https://www.w3.org/events/meetings/900ac419-eda7-404d-9750-d87b
8c83dc05/\n\nThis is the I18N WG's TPAC 2024 first meeting. We will also h
ave a half-day on Friday.\n\nObservers are welcome\, subject to approval b
y the chair. Bring your internationalization issues to us!\n\nAgenda\n\n##
## BE PREPARED \nThings to do before the meeting:\n\n\n#### AGENDA\n\n**To
pic: Agenda Review**\n\n**Topic: Planning for this week**\n_Let's review t
he joint meetings we have in the calendar\, the meetings we wish to have\,
and what we'd like to accomplish as a group._\n* Meeting with Payments. T
hey'd like to revive (postal) address.\n* Meeting with CSS.\n* Meeting wit
h WHATWG. We have _many_ issues to review with them.\n* Meeting with WCAG/
A11Y.\n* Hallway with Privacy and/or a meeting with PING.\n\n**Topic: Docu
ment Work in Progress Review**\n_Time to review the work we have "in progr
ess" and discuss work on it._\n* [STRING-META](https://github.com/w3c/stri
ng-meta) _<- need to finalize_\n* [TIMEZONE](https://github.com/w3c/timezo
ne)\n* [STRING-SEARCH](https://github.com/w3c/string-search)\n* [SPECDEV](
https://github.com/w3c/bp-i18n-specdev/)\n* [GLOSSARY](https://github.com/
w3c/i18n-glossary/)\n* [LANGUAGE-NEGOTIATION](https://github.com/w3c/i18n-
drafts/pull/581)\n* Others?\n\n**Topic: Language Enablement WIP**\n_Let's
review work on language enablement and gap analysis. This is especially a
time for Richard to share his thoughts._\n\n\n**Topic: AOB?**\n\n---\n\n\n
\n#### Chair's Link Farm\n* [I18N-ACTIONS](https://github.com/w3c/i18n-act
ions/issues)\n* [RADAR](https://github.com/orgs/w3c/projects/91/views/1)\n
* [Pending Issues](https://github.com/w3c/i18n-activity/issues?q=is%3Aissu
e+is%3Aopen+label%3Apending)
STATUS:CONFIRMED
CREATED:20240614T153919Z
LAST-MODIFIED:20240921T233032Z
SEQUENCE:13
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Internationalizati
on Working Group:mailto:public-i18n-core@w3.org
LOCATION:4 Concourse Level - La Jolla
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:5c40f321-6905-4690-9d10-3bd09c5313f0
DTSTAMP:20240924T190555Z
SUMMARY:Media and Entertainment Interest Group
DTSTART;TZID=America/Los_Angeles:20240923T090000
DTEND;TZID=America/Los_Angeles:20240923T103000
DESCRIPTION:https://www.w3.org/events/meetings/5c40f321-6905-4690-9d10-3bd0
9c5313f0/\n\n\n\nAgenda: https://github.com/w3c/media-and-entertainment/is
sues/109
STATUS:CONFIRMED
CREATED:20240614T161734Z
LAST-MODIFIED:20240924T190555Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Media and Entertai
nment Interest Group:mailto:public-web-and-tv@w3.org
LOCATION:4 Concourse Level - San Clemente
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:12a090ec-425d-4163-b14b-2fca1bb19fa4
DTSTAMP:20240923T234849Z
SUMMARY:Publishing Maintenance Working Group
DTSTART;TZID=America/Los_Angeles:20240923T090000
DTEND;TZID=America/Los_Angeles:20240923T160000
DESCRIPTION:https://www.w3.org/events/meetings/12a090ec-425d-4163-b14b-2fca
1bb19fa4/\n\n\n\nAgenda: https://github.com/w3c/pm-wg/wiki/TPAC-2024-Agend
a\n\nAgenda\n\n* 09:00 - 10:00 PDT / 16:00 - 17:00 UTC / 01:00 - 02:00 JST
: Making substantial changes to EPUB\n * What kinds of changes will the
industry accept? \n * HTML5 Serialization - challenges for reading sys
tems\, publishers\, tooling\n * Rechartering \n * Issue to track dis
cussion: https://github.com/w3c/pm-wg/issues/6\n* 10:00 - 11:00 PDT / 17:0
0 - 18:00 UTC / 02:00 - 03:00 JST: Scrolled content / web toons\n * htt
ps://github.com/w3c/epub-specs/pull/2602\n* 11:00-11:30 PDT / 17:00 - 17:3
0 UTC / 03:00 - 03:30 JST: Break\n* 11:30 - 12:30 PDT / 18:30 - 19:30 UTC
/ 03:30 - 04:30 JST: Locators and Annotations\n * Locators Draft: https
://docs.google.com/document/d/11GypOjE9xOTaINATl5bxVIA3Mc9jzNBGCr6GT_KNaQ4
/edit#heading=h.gbsmtjlkuon\n * EPUB CFI: https://w3c.github.io/epub-sp
ecs/epub33/epubcfi/\n * Web Annotations: \n * https://www.w3.org
/TR/annotation-protocol/\n * https://www.w3.org/TR/annotation-model
/\n * https://www.w3.org/TR/annotation-vocab/\n * https://w3c.gi
thub.io/wpub-ann/\n * https://www.w3.org/TR/selectors-states/\n * Is
sue to track discussion: https://github.com/w3c/pm-wg/issues/7\n* 12:30 -
13:30 PDT / 19:30 - 20:30 UTC / 04:30 - 05:30 JST: Lunch Break\n* 13:30 -
14:30 PDT / 20:30 - 21:30 UTC / 05:30 - 06:30 JST: Legislation (world wide
) and Accessibility\n * European Accessibility Act - what we need to do
about it\n * ADA Title II - Publishing Requirements\n* 14:30 - 14:45 P
DT / 21:30 - 21:45 UTC / 06:30 - 06:45 JST: Break\n* 14:45 - 15:30 PDT / 2
1:45 - 22:30 UTC / 06:45 - 07:30 JST: Audiobooks accessibility\, TTS\n
* Do we need an Audiobooks Accessibility document (like EPUB Accessibility
)?\n * Issue to track discussion: https://github.com/w3c/pm-wg/issu
es/8\n * TTS\n * https://wicg.github.io/speech-api/\n * h
ttps://github.com/w3c/publishingcg/issues/69\n * Issue to track dis
cussion: https://github.com/w3c/pm-wg/issues/9\n* 15:30 - 16:00 PDT / 22:3
0 - 23:00 UTC / 07:30 - 08:00 JST: AOB / Wrap up (time adjustment)\n *
Republish EPUB 3.3\n * Move to ISO
STATUS:CONFIRMED
CREATED:20240614T163424Z
LAST-MODIFIED:20240923T234849Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Publishing Busines
s Group:mailto:public-publishingbg@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Publishing Communi
ty Group:mailto:public-publishingcg@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Publishing Mainten
ance Working Group:mailto:public-pm-wg@w3.org
LOCATION:-1 Lower Level - Catalina 3
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:9447a964-6de6-4540-9f49-481f1067f563
DTSTAMP:20240923T134509Z
SUMMARY:Technical Architecture Group
DTSTART;TZID=America/Los_Angeles:20240923T090000
DTEND;TZID=America/Los_Angeles:20240923T123000
DESCRIPTION:https://www.w3.org/events/meetings/9447a964-6de6-4540-9f49-481f
1067f563/\n\n
STATUS:CONFIRMED
CREATED:20240614T163414Z
LAST-MODIFIED:20240923T134509Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Technical Architec
ture Group:mailto:tag@w3.org
LOCATION:4 Concourse Level - Manhattan
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:dccfa810-ac8b-4894-9e94-a27eeaa5b84e
DTSTAMP:20240923T191201Z
SUMMARY:Web Application Security Working Group
DTSTART;TZID=America/Los_Angeles:20240923T090000
DTEND;TZID=America/Los_Angeles:20240923T123000
DESCRIPTION:https://www.w3.org/events/meetings/dccfa810-ac8b-4894-9e94-a27e
eaa5b84e/\n\n\n\nAgenda: https://github.com/w3c/webappsec/blob/main/meetin
gs/2024/2024-09-TPAC-agenda.md\n\nAgenda\n\n_WIP\, still some flexibility
based on feedback and availability._\n\n[23.09.2024\, 9:00 - 12:30](https:
//www.w3.org/events/meetings/dccfa810-ac8b-4894-9e94-a27eeaa5b84e/): [2 Ba
llroom Level - California B](https://www.w3.org/2024/09/TPAC/schedule.html
#map)\n---------------------------------------------------------\n\n* **9:
00 - 9:15**: ☕ and agenda bashing.\n* **9:15 - 9:45**: Crypto\n * (~15m
) Web Crypto (@twiss)\n * Algorithms (modernizing\, post-modernizing)\n
* Curve 25591\n * Streaming\n * Feature Detection\n * (~15m) [R
emote cryptokeys](https://github.com/WebKit/explainers/tree/main/remote-cr
yptokeys) (@marcoscaceres\, @estark37)\n* **9:45 - 10:30**: Application In
tegrity/Transparency (@ddworken)\n * (~25m) Extensions to SRI\n * Addi
tional content types\n * Additional assertion types ([signatures](https
://github.com/mikewest/signature-based-sri)\, etc))\n * `require-sri-fo
r` (@yoavweiss)\n * (~20m) Signing / Packaging\n* **10:30 - 11:00**: ☕
& 🍰 @ [Lanai Deck\, Fifth Floor](https://www.w3.org/2024/09/TPAC/schedu
le.html#map)\n* **11:00 - 12:00**: CSP\n * (~15m) Should the threat mod
el include exfiltration? (@yoavweiss)\n * (~20m) How can we improve ado
ption? (@simoneonofri\, @johnwilander)\n * Docs & recommendations?
\n * [CSP Next](https://github.com/WICG/csp-next)?\n * (~15m) C
ould we [require injection mitigation](https://mikewest.github.io/injectio
n-mitigated/) for interesting APIs? (@mikewest)\n * (~10m) What's left
before putting CSP into "living CR" mode?\n* **12:00 - 12:10**: https://gi
thub.com/w3c/webappsec-permissions-policy/issues/273 (@sanketj)\n* **12:10
- 12:30**: **Breakout pitch session**. There are a number of breakout ses
sions ([grid](https://www.w3.org/2024/09/TPAC/breakouts.html#grid)\, [deta
ils](https://www.w3.org/2024/09/TPAC/breakouts.html#intro)) on 25.09.2024
that are relevant to this community. Let's talk about them a bit so folks
can plan accordingly.
STATUS:CONFIRMED
CREATED:20240614T163317Z
LAST-MODIFIED:20240923T191201Z
SEQUENCE:5
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Web Application Se
curity Working Group:mailto:public-webappsec@w3.org
LOCATION:2 Ballroom Level - California B
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:2ef1efa3-3d0d-4a7b-8202-5d5c11657733
DTSTAMP:20240923T230205Z
SUMMARY:Web Applications Working Group
DTSTART;TZID=America/Los_Angeles:20240923T090000
DTEND;TZID=America/Los_Angeles:20240923T180000
DESCRIPTION:https://www.w3.org/events/meetings/2ef1efa3-3d0d-4a7b-8202-5d5c
11657733/\n\n\n\nAgenda: https://github.com/w3c/webappswg/wiki/TPAC-2024
STATUS:CONFIRMED
CREATED:20240614T161705Z
LAST-MODIFIED:20240923T230205Z
SEQUENCE:7
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Web Applications W
orking Group:mailto:public-webapps@w3.org
LOCATION:4 Concourse Level - Laguna
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:6c3dd4cb-e1bf-432c-92f8-fd938188a426
DTSTAMP:20240925T000835Z
SUMMARY:Web Machine Learning Working Group
DTSTART;TZID=America/Los_Angeles:20240923T090000
DTEND;TZID=America/Los_Angeles:20240923T180000
DESCRIPTION:https://www.w3.org/events/meetings/6c3dd4cb-e1bf-432c-92f8-fd93
8188a426/\n\n\n\nAgenda: https://github.com/webmachinelearning/meetings/is
sues/25
STATUS:CONFIRMED
CREATED:20240614T163334Z
LAST-MODIFIED:20240925T000835Z
SEQUENCE:8
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Web Machine Learni
ng Working Group:mailto:public-webmachinelearning-wg@w3.org
LOCATION:4 Concourse Level - Oceanside
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:2162efdd-653e-43ab-8b91-6570e1791853
DTSTAMP:20240923T205828Z
SUMMARY:Web Payments Working Group
DTSTART;TZID=America/Los_Angeles:20240923T090000
DTEND;TZID=America/Los_Angeles:20240923T160000
DESCRIPTION:https://www.w3.org/events/meetings/2162efdd-653e-43ab-8b91-6570
e1791853/\n\n\n\nAgenda: https://github.com/w3c/webpayments/wiki/Agenda-TP
AC2024
STATUS:CONFIRMED
CREATED:20240614T161642Z
LAST-MODIFIED:20240923T205828Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Web Payments Worki
ng Group:mailto:public-payments-wg@w3.org
LOCATION:4 Concourse Level - Huntington
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:99ceb3a1-3240-42b0-90c8-2771033325a5
DTSTAMP:20240923T204804Z
SUMMARY:Web Performance Working Group
DTSTART;TZID=America/Los_Angeles:20240923T090000
DTEND;TZID=America/Los_Angeles:20240923T160000
DESCRIPTION:https://www.w3.org/events/meetings/99ceb3a1-3240-42b0-90c8-2771
033325a5/\n\n\n\nAgenda: https://bit.ly/webperf-tpac24\n\nAgenda\n\n* Intr
os\, CEPC\, agenda review\, meeting goals\, introspection\n* Container Tim
ing Status Update\n` `\n* Network Error Logging: Happy Eyeballs and Pa
rtial Failures \n* TTFB—what does it mean and why’s it so messy?\n\nLu
nch\n\n* Cross-origin caching of pervasive assets\n* Long Animation Frames
: Status & what’s next
STATUS:CONFIRMED
CREATED:20240614T163420Z
LAST-MODIFIED:20240923T204804Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Web Performance Wo
rking Group:mailto:public-web-perf@w3.org
LOCATION:-1 Lower Level - Catalina 5
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:f000ded1-5f74-4eb4-ac91-2328c44bb90a
DTSTAMP:20240919T221006Z
SUMMARY:WebExtensions Community Group
DTSTART;TZID=America/Los_Angeles:20240923T090000
DTEND;TZID=America/Los_Angeles:20240923T123000
DESCRIPTION:https://www.w3.org/events/meetings/f000ded1-5f74-4eb4-ac91-2328
c44bb90a/\n\n\n\nAgenda: https://github.com/w3c/webextensions/wiki/TPAC-20
24-Coordination#monday
STATUS:CONFIRMED
CREATED:20240704T125805Z
LAST-MODIFIED:20240919T221006Z
SEQUENCE:4
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=WebExtensions Comm
unity Group:mailto:public-webextensions@w3.org
LOCATION:-1 Lower Level - Catalina 7
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:0adef6b7-aa86-4dfe-9541-caa5b0b8839a
DTSTAMP:20240923T180151Z
SUMMARY:Spatial Data on the Web Working Group\, Dataset Exchange Working Gr
oup Joint Meeting
DTSTART;TZID=America/Los_Angeles:20240923T110000
DTEND;TZID=America/Los_Angeles:20240923T123000
DESCRIPTION:https://www.w3.org/events/meetings/0adef6b7-aa86-4dfe-9541-caa5
b0b8839a/\n\n\n\nAgenda: https://lists.w3.org/Archives/Public/public-sdw-w
g/2024Sep/0008.html
STATUS:CONFIRMED
CREATED:20240614T163434Z
LAST-MODIFIED:20240923T180151Z
SEQUENCE:5
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Dataset Exchange W
orking Group:mailto:public-dxwg-wg@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Spatio-temporal Da
ta on the Web Working Group:mailto:public-sdw-wg@w3.org
LOCATION:-1 Lower Level - Catalina 2
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:de4e327e-f0b4-4c18-ae57-c1abe20625fc
DTSTAMP:20240924T190842Z
SUMMARY:Timed Text Working Group\, Media and Entertainment Interest Group J
oint Meeting
DTSTART;TZID=America/Los_Angeles:20240923T110000
DTEND;TZID=America/Los_Angeles:20240923T123000
DESCRIPTION:https://www.w3.org/events/meetings/de4e327e-f0b4-4c18-ae57-c1ab
e20625fc/\n\n\n\nAgenda: https://github.com/w3c/media-and-entertainment/is
sues/109\n\nAgenda\n\n* TTWG status update\n* Dubbing and Audio Descriptio
n Profiles of TTML2\n* Timed Text support in MSE
STATUS:CONFIRMED
CREATED:20240614T163400Z
LAST-MODIFIED:20240924T190842Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Media and Entertai
nment Interest Group:mailto:public-web-and-tv@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Timed Text Working
Group:mailto:public-tt@w3.org
LOCATION:4 Concourse Level - San Clemente
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:6c6c9aea-70cd-4d1d-bc92-7f2cb4a45a47
DTSTAMP:20240924T190604Z
SUMMARY:Web Platform Incubator Community Group
DTSTART;TZID=America/Los_Angeles:20240923T110000
DTEND;TZID=America/Los_Angeles:20240923T123000
DESCRIPTION:https://www.w3.org/events/meetings/6c6c9aea-70cd-4d1d-bc92-7f2c
b4a45a47/\n\n\n\nAgenda: https://github.com/WICG/admin/issues/194#issuecom
ment-2333970845
STATUS:CONFIRMED
CREATED:20240614T163020Z
LAST-MODIFIED:20240924T190604Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Web Platform Incub
ator Community Group:mailto:public-wicg@w3.org
LOCATION:2 Ballroom Level - California A
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:7ebe7dd6-d484-4360-b3d4-a71b4ec14311
DTSTAMP:20240923T222833Z
SUMMARY:Audio Working Group
DTSTART;TZID=America/Los_Angeles:20240923T140000
DTEND;TZID=America/Los_Angeles:20240923T180000
DESCRIPTION:https://www.w3.org/events/meetings/7ebe7dd6-d484-4360-b3d4-a71b
4ec14311/\n\n\n\nAgenda: https://bit.ly/audiowg-tpac-2024
STATUS:CONFIRMED
CREATED:20240614T163417Z
LAST-MODIFIED:20240923T222833Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Audio Working Grou
p:mailto:public-audio@w3.org
LOCATION:4 Concourse Level - Manhattan
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:0d46a38e-0a71-42c6-a750-4cacc4bf6247
DTSTAMP:20240924T190558Z
SUMMARY:Media and Entertainment Interest Group
DTSTART;TZID=America/Los_Angeles:20240923T140000
DTEND;TZID=America/Los_Angeles:20240923T160000
DESCRIPTION:https://www.w3.org/events/meetings/0d46a38e-0a71-42c6-a750-4cac
c4bf6247/\n\n\n\nAgenda: https://github.com/w3c/media-and-entertainment/is
sues/109
STATUS:CONFIRMED
CREATED:20240911T133653Z
LAST-MODIFIED:20240924T190558Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Media and Entertai
nment Interest Group:mailto:public-web-and-tv@w3.org
LOCATION:4 Concourse Level - San Clemente
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:b9ef22f7-13b4-4dc6-96f6-fa27006f9add
DTSTAMP:20240923T222317Z
SUMMARY:Privacy Interest Group
DTSTART;TZID=America/Los_Angeles:20240923T140000
DTEND;TZID=America/Los_Angeles:20240923T160000
DESCRIPTION:https://www.w3.org/events/meetings/b9ef22f7-13b4-4dc6-96f6-fa27
006f9add/\n\n\n\nAgenda: https://github.com/w3cping/administrivia/issues/4
9
STATUS:CONFIRMED
CREATED:20240614T163325Z
LAST-MODIFIED:20240923T222317Z
SEQUENCE:5
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Privacy Interest G
roup:mailto:public-privacy@w3.org
LOCATION:-1 Lower Level - Catalina 7
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:1a8409fc-3cb7-4202-b589-d0943761abfd
DTSTAMP:20240924T044741Z
SUMMARY:Spatial Data on the Web Working Group\, JSON-LD Working Group\, JSO
N for Linked Data Community Group Joint Meeting
DTSTART;TZID=America/Los_Angeles:20240923T140000
DTEND;TZID=America/Los_Angeles:20240923T160000
DESCRIPTION:https://www.w3.org/events/meetings/1a8409fc-3cb7-4202-b589-d094
3761abfd/\n\n\n\nAgenda\n\nMeeting initiated by Spacial Data on the Web\,
who was a no-show. Ended up discussing issues with JSON-LD contexts\, part
icularly when loading into SPARQL.
STATUS:CONFIRMED
CREATED:20240614T163432Z
LAST-MODIFIED:20240924T044741Z
SEQUENCE:5
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=JSON for Linked Da
ta Community Group:mailto:public-json-ld@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=JSON-LD Working Gr
oup:mailto:public-json-ld-wg@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Spatio-temporal Da
ta on the Web Working Group:mailto:public-sdw-wg@w3.org
LOCATION:-1 Lower Level - Catalina 2
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:2242698c-a055-4745-bc2b-91355eaaf1c3
DTSTAMP:20240919T195734Z
SUMMARY:WHATWG\, Cascading Style Sheets (CSS) Working Group Joint Meeting
DTSTART;TZID=America/Los_Angeles:20240923T140000
DTEND;TZID=America/Los_Angeles:20240923T160000
DESCRIPTION:https://www.w3.org/events/meetings/2242698c-a055-4745-bc2b-9135
5eaaf1c3/\n\n\n\nAgenda: https://github.com/whatwg/meta/issues/326
STATUS:CONFIRMED
CREATED:20240614T161725Z
LAST-MODIFIED:20240919T195734Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Cascading Style Sh
eets (CSS) Working Group:mailto:www-style@w3.org
LOCATION:2 Ballroom Level - California B
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:456057ed-2184-4870-86a4-f01c8158d3c0
DTSTAMP:20240923T221812Z
SUMMARY:WICG: Digital Credentials API
DTSTART;TZID=America/Los_Angeles:20240923T140000
DTEND;TZID=America/Los_Angeles:20240923T160000
DESCRIPTION:https://www.w3.org/events/meetings/456057ed-2184-4870-86a4-f01c
8158d3c0/\n\n\n\nAgenda: https://docs.google.com/document/d/1MseGjT5yGidJw
ypVjN03mMiRZsQSD7Ep2I4F9GYtTXE/edit?usp=sharing
STATUS:CONFIRMED
CREATED:20240617T141206Z
LAST-MODIFIED:20240923T221812Z
SEQUENCE:4
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Web Platform Incub
ator Community Group:mailto:public-wicg@w3.org
LOCATION:2 Ballroom Level - California A
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:c7fff076-c85e-4a09-a769-e5053df41385
DTSTAMP:20240919T064402Z
SUMMARY:Cascading Style Sheets WG\, Accessible Platform Architectures WG Jo
int Meeting
DTSTART;TZID=America/Los_Angeles:20240923T163000
DTEND;TZID=America/Los_Angeles:20240923T180000
DESCRIPTION:https://www.w3.org/events/meetings/c7fff076-c85e-4a09-a769-e505
3df41385/\n\n[😷 Covid protocols](https://wiki.csswg.org/planning/tpac-2
024#covid-protocols)\n\nAgenda\n\n* Any general issues CSS WG would like t
o raise (edit from Alan Stearns - possibly these?)\n \n - [css-display-4]
Should the reading-order-items property apply to tables in addition to fle
x and grid layouts? https://github.com/w3c/csswg-drafts/issues/9922\n - [
css-display-4] Define how reading-flow interacts with focusable display: c
ontents elements. https://github.com/w3c/csswg-drafts/issues/9230\n - [cs
s-view-transitions] Users need to be able to disable view transitions htt
ps://github.com/w3c/csswg-drafts/issues/10267\n\n* Query on CSS Speech: bl
ockers to implementation\; possibility of implementing a 'core' subset?\n
- Context: relating to Pronunciation TF's work\, there are a few things t
hat\, if present in CSS\, we could build on to more effectively solve the
problems identified by this TF.\n - We have identified different facets o
f the problem of pronunciation: some we feel are more apt for CSS (largely
user-controlled)\; others relate directly to the content (hence we are pr
oposing markup for them).\n - Many of our use cases come from education.
Background info: [Pronunciation Gap Analysis and Use Cases](https://w3c.gi
thub.io/pronunciation/gap-analysis_and_use-case/)
STATUS:CONFIRMED
CREATED:20240614T161658Z
LAST-MODIFIED:20240919T064402Z
SEQUENCE:5
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Accessible Platfor
m Architectures Working Group:mailto:public-apa@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Cascading Style Sh
eets (CSS) Working Group:mailto:www-style@w3.org
LOCATION:2 Ballroom Level - California B
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:1d158e51-91b3-497d-a2f5-ac140d18a835
DTSTAMP:20240925T143800Z
SUMMARY:Federated Identity Working Group\, Federated Identity Community Gro
up Joint Meeting
DTSTART;TZID=America/Los_Angeles:20240923T163000
DTEND;TZID=America/Los_Angeles:20240923T180000
DESCRIPTION:https://www.w3.org/events/meetings/1d158e51-91b3-497d-a2f5-ac14
0d18a835/\n\n\n\nAgenda: https://github.com/fedidcg/meetings/blob/main/202
4/2024-09-23-TPAC.md
STATUS:CONFIRMED
CREATED:20240614T161720Z
LAST-MODIFIED:20240925T143800Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Federated Identity
Community Group:mailto:public-fed-id@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Federated Identity
Working Group:mailto:public-fedid-wg@w3.org
LOCATION:2 Ballroom Level - California A
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:47b69f98-794f-4aa4-9aa5-b8a9f0c1473e
DTSTAMP:20240923T232315Z
SUMMARY:Web Payments WG: Digital Credentials and Payments
DTSTART;TZID=America/Los_Angeles:20240923T163000
DTEND;TZID=America/Los_Angeles:20240923T180000
DESCRIPTION:https://www.w3.org/events/meetings/47b69f98-794f-4aa4-9aa5-b8a9
f0c1473e/\n\n\n\nAgenda: https://github.com/w3c/webpayments/wiki/Agenda-TP
AC2024
STATUS:CONFIRMED
CREATED:20240909T164000Z
LAST-MODIFIED:20240923T232315Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Web Payments Worki
ng Group:mailto:public-payments-wg@w3.org
LOCATION:4 Concourse Level - Huntington
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:c7c77f55-b92a-4c81-a3c5-cf58c25a0cf1
DTSTAMP:20240923T230437Z
SUMMARY:WebAuthn Adoption Community Group
DTSTART;TZID=America/Los_Angeles:20240923T163000
DTEND;TZID=America/Los_Angeles:20240923T180000
DESCRIPTION:https://www.w3.org/events/meetings/c7c77f55-b92a-4c81-a3c5-cf58
c25a0cf1/\n\n
STATUS:CONFIRMED
CREATED:20240625T155510Z
LAST-MODIFIED:20240923T230437Z
SEQUENCE:5
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=WebAuthn Adoption
Community Group:mailto:public-webauthn-adoption@w3.org
LOCATION:-1 Lower Level - Catalina 7
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:ab79ba64-2101-45cc-a5d3-18a97b09cb31
DTSTAMP:20240924T001453Z
SUMMARY:Accessibility Guidelines Working Group
DTSTART;TZID=America/Los_Angeles:20240924T090000
DTEND;TZID=America/Los_Angeles:20240924T180000
DESCRIPTION:https://www.w3.org/events/meetings/ab79ba64-2101-45cc-a5d3-18a9
7b09cb31/\n\n\n\nAgenda\n\n| Start | End | Session Title |\n| --------
| ------- |------- |\n| 9:00 | 12:30 | Conformance model discussion |\n| 1
2:30 | 13:30 | Lunch |\n| 13:30 | 16:30 | Conformance model discussion |\n
| 16:30 | 17:30 | Review next subgroups to kick off |\n\nBreaks will be in
cluded within the main sessions
STATUS:CONFIRMED
CREATED:20240614T163338Z
LAST-MODIFIED:20240924T001453Z
SEQUENCE:8
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Accessibility Guid
elines Working Group:mailto:public-ag-admin@w3.org
LOCATION:4 Concourse Level - Palos Verdes
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:9fe696a0-ddd3-461b-903f-c4494f8a5d3b
DTSTAMP:20240924T190751Z
SUMMARY:Accessible Platform Architectures Working Group
DTSTART;TZID=America/Los_Angeles:20240924T090000
DTEND;TZID=America/Los_Angeles:20240924T103000
DESCRIPTION:https://www.w3.org/events/meetings/9fe696a0-ddd3-461b-903f-c449
4f8a5d3b/\n\n\n\nAgenda\n\n* Fixed layout\n - The spec's support for read
ing order info\n - Authoring tool support\n - Title of the document\n* F
uture plans - let's start talking about what we'd like to see in EPUB 4 an
d related work (including UAs)
STATUS:CONFIRMED
CREATED:20240910T171709Z
LAST-MODIFIED:20240924T190751Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Accessible Platfor
m Architectures Working Group:mailto:public-apa@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Publishing Mainten
ance Working Group:mailto:public-pm-wg@w3.org
LOCATION:4 Concourse Level - Manhattan
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:b1f093f7-0e2a-4780-b474-96bedd198082
DTSTAMP:20240924T210855Z
SUMMARY:Accessible Rich Internet Applications Working Group
DTSTART;TZID=America/Los_Angeles:20240924T090000
DTEND;TZID=America/Los_Angeles:20240924T180000
DESCRIPTION:https://www.w3.org/events/meetings/b1f093f7-0e2a-4780-b474-96be
dd198082/\n\n\n\nAgenda: https://github.com/w3c/aria/wiki/TPAC-2024-ARIA-M
eetings
STATUS:CONFIRMED
CREATED:20240614T161712Z
LAST-MODIFIED:20240924T210855Z
SEQUENCE:5
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Accessible Rich In
ternet Applications Working Group:mailto:public-aria@w3.org
LOCATION:4 Concourse Level - Redondo
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:de6496ab-7e5a-4fe0-b49f-de6a0140ecd1
DTSTAMP:20240924T152854Z
SUMMARY:Cascading Style Sheets Working Group\, WHATWG\, OpenUI Joint Meetin
g
DTSTART;TZID=America/Los_Angeles:20240924T090000
DTEND;TZID=America/Los_Angeles:20240924T123000
DESCRIPTION:https://www.w3.org/events/meetings/de6496ab-7e5a-4fe0-b49f-de6a
0140ecd1/\n\n\n\nAgenda: https://github.com/whatwg/meta/issues/326
STATUS:CONFIRMED
CREATED:20240614T163443Z
LAST-MODIFIED:20240924T152854Z
SEQUENCE:8
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Cascading Style Sh
eets (CSS) Working Group:mailto:www-style@w3.org
LOCATION:4 Concourse Level - Laguna
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:1e564cdb-2661-415c-94a2-2d3018a5ae1e
DTSTAMP:20241011T152701Z
SUMMARY:Decentralized Identifier Working Group
DTSTART;TZID=America/Los_Angeles:20240924T090000
DTEND;TZID=America/Los_Angeles:20240924T180000
DESCRIPTION:https://www.w3.org/events/meetings/1e564cdb-2661-415c-94a2-2d30
18a5ae1e/\n\n\n\nAgenda: https://docs.google.com/presentation/d/1s6tf0VOKd
Ir3Gf_t7ROypyeg07Lk_myoOFby6AL4I7g/edit#slide=id.g2a8b040676_0_74\n\nAgend
a\n\nhttps://docs.google.com/presentation/d/1s6tf0VOKdIr3Gf_t7ROypyeg07Lk_
myoOFby6AL4I7g/edit#slide=id.g2a8b040676_0_74
STATUS:CONFIRMED
CREATED:20240614T163332Z
LAST-MODIFIED:20241011T152701Z
SEQUENCE:7
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Decentralized Iden
tifier Working Group:mailto:public-did-wg@w3.org
LOCATION:4 Concourse Level - Capistrano
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:7dfe2c59-9809-427a-9d64-724c76694cf7
DTSTAMP:20240924T190857Z
SUMMARY:Immersive Web Working Group
DTSTART;TZID=America/Los_Angeles:20240924T090000
DTEND;TZID=America/Los_Angeles:20240924T103000
DESCRIPTION:https://www.w3.org/events/meetings/7dfe2c59-9809-427a-9d64-724c
76694cf7/\n\n\n\nAgenda: https://github.com/immersive-web/administrivia/tr
ee/main/TPAC2024#agenda\n\nAgenda\n\n| | Tuesday 24/9
|\n| ------------- | -----------------------| \n| 9:00 | Introduc
tion |\n| 9:30 | Depth Sensing | \n| 10:00 | Depth
Sensing | \n| 10:30 | Break | \n| 11:00 |
[Web Apps Joint Meeting](https://www.w3.org/events/meetings/e3724be4-18f0-
4846-93c4-ddf0f0839697/)| \n| 11:30 | [Web Apps Join
t Meeting](https://www.w3.org/events/meetings/e3724be4-18f0-4846-93c4-ddf0
f0839697/)| \n| 12:00 | |
\n| 12:30 | Lunch | \n| 13:00 |
| \n| 13:30 |
| \n| 14:00 | Body Tracking | \n| 14:30
| Body Tracking |\n| 15:00 | Model | \n| 15:
30 | Model | \n| 16:00 | Break
| \n| 16:30 | Model | \n| 17:00 | Model
| \n| 17:30 | Model |
STATUS:CONFIRMED
CREATED:20240725T224946Z
LAST-MODIFIED:20240924T190857Z
SEQUENCE:4
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Immersive Web Work
ing Group:mailto:public-immersive-web-wg@w3.org
LOCATION:4 Concourse Level - San Clemente
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:fd615d85-6c27-4a8e-9e99-55a656268af1
DTSTAMP:20240924T161002Z
SUMMARY:Privacy Interest Group
DTSTART;TZID=America/Los_Angeles:20240924T090000
DTEND;TZID=America/Los_Angeles:20240924T103000
DESCRIPTION:https://www.w3.org/events/meetings/fd615d85-6c27-4a8e-9e99-55a6
56268af1/\n\n\n\nAgenda: https://github.com/w3cping/administrivia/issues/4
9
STATUS:CONFIRMED
CREATED:20240614T163326Z
LAST-MODIFIED:20240924T161002Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Privacy Interest G
roup:mailto:public-privacy@w3.org
LOCATION:-1 Lower Level - Catalina 7
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:f8a5c74c-2bd4-45d4-89e7-9f5c84c6f9e0
DTSTAMP:20241004T155156Z
SUMMARY:RDF-star Working Group
DTSTART;TZID=America/Los_Angeles:20240924T090000
DTEND;TZID=America/Los_Angeles:20240924T103000
DESCRIPTION:https://www.w3.org/events/meetings/f8a5c74c-2bd4-45d4-89e7-9f5c
84c6f9e0/\n\n\n\nAgenda\n\n1. RDF-Star: 2 Years Status [1] \n2. Un-star op
eration to support RDF Dataset Canonicalization? [2]\n3. Material about `r
df:ReificationProperty` [3]\n4. Addressing SPARQL EXISTS errata [4]\n5. Ba
cklog to add additional issues [5]\n6. Any Other Business (AOB)\, time per
mitting\n\n[1]: https://www.lassila.org/publications/2024/TPAC2024/RDF-sta
r-intro/Overview.html\n[2]: https://github.com/w3c/rdf-star-wg/issues/114\
n[3]: https://github.com/w3c/rdf-star-wg/issues/127\n[4]: https://github.c
om/w3c/sparql-query/issues/156\n[5]: https://github.com/orgs/w3c/projects/
20/views/7
STATUS:CONFIRMED
CREATED:20240614T161731Z
LAST-MODIFIED:20241004T155156Z
SEQUENCE:7
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=RDF & SPARQL Worki
ng Group:mailto:public-rdf-star-wg@w3.org
LOCATION:4 Concourse Level - La Jolla
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:c2245677-68a4-44ac-99fd-bca38333317e
DTSTAMP:20240923T054900Z
SUMMARY:Web & Networks Interest Group
DTSTART;TZID=America/Los_Angeles:20240924T090000
DTEND;TZID=America/Los_Angeles:20240924T103000
DESCRIPTION:https://www.w3.org/events/meetings/c2245677-68a4-44ac-99fd-bca3
8333317e/\n\n\n\nAgenda: https://www.w3.org/wiki/Networks/TPAC2024
STATUS:CONFIRMED
CREATED:20240614T163441Z
LAST-MODIFIED:20240923T054900Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Web & Networks Int
erest Group:mailto:public-networks-ig@w3.org
LOCATION:2 Ballroom Level - California B
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:58f67161-3138-4c48-8d35-dc5d04de8e75
DTSTAMP:20240924T162332Z
SUMMARY:Web Applications Working Group\, Devices and Sensors Working Group
Joint Meeting
DTSTART;TZID=America/Los_Angeles:20240924T090000
DTEND;TZID=America/Los_Angeles:20240924T103000
DESCRIPTION:https://www.w3.org/events/meetings/58f67161-3138-4c48-8d35-dc5d
04de8e75/\n\n\n\nAgenda: https://github.com/w3c/devicesensors-wg/issues/69
STATUS:CONFIRMED
CREATED:20240614T161709Z
LAST-MODIFIED:20240924T162332Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Devices and Sensor
s Working Group:mailto:public-device-apis@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Web Applications W
orking Group:mailto:public-webapps@w3.org
LOCATION:2 Ballroom Level - California A
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:6469898c-678d-46e7-8d8e-4c9c8b1bb7cf
DTSTAMP:20240925T000748Z
SUMMARY:Web Authentication Working Group
DTSTART;TZID=America/Los_Angeles:20240924T090000
DTEND;TZID=America/Los_Angeles:20240924T160000
DESCRIPTION:https://www.w3.org/events/meetings/6469898c-678d-46e7-8d8e-4c9c
8b1bb7cf/\n\n\n\nAgenda: https://docs.google.com/document/d/1QrFg2JP-V7Ey9
YDS2zXzUBZBg8ovhL2Ja4CD433PwFE/edit\n\nAgenda\n\n**Power back earlier\, br
idge is open**\n\n\n### L3 Target Publication Schedule discussion\n\n1. De
adline for [wide review](https://www.w3.org/Consortium/Process/#wide-revie
w) Sunday\, October 27 0024 \n2. [Group Call for Consensus (CfC)](https:/
/w3c.github.io/charter-drafts/charter-template.html#decisions) to move to
Candidate Recommendation\, [wide review](https://www.w3.org/Consortium/Pro
cess/#wide-review) is done Monday\, October 28 0024 \n3. Transition requ
est to [Candidate Recommendation](https://www.w3.org/Guide/transitions?pro
file=CR&cr=new) Thursday\, November 7 0024\n\n### L3 WD02 open pull reques
ts and open issues\n\n[Issues · w3c/webauthn (github.com)](https://github
.com/w3c/webauthn/issues?q=is%3Aopen+label%3Atype%3Atechnical+milestone%3A
L3-WD-02) (30 open technical issues on L3 to resolve or move to futures)\
n\n[Pull requests · w3c/webauthn (github.com)](https://github.com/w3c/web
authn/pulls?q=is%3Aopen+is%3Apr+label%3Atype%3Atechnical+milestone%3AL3-WD
-02) (3 technical pull requests on L3 to resolve or move to futures) \n \
n\n#### [Pull requests · w3c/webauthn (github.com)](https://github.com/w3
c/webauthn/pulls?q=is%3Aopen+is%3Apr+milestone%3AL3-WD-02)\n\n1. [Add user
Name and userDisplayName to webdriver by nsatragno · Pull Request \\#2148
· w3c/webauthn (github.com)](https://github.com/w3c/webauthn/pull/2148)
\n2. [Clarify behaviour of duplicate hints by emlun · Pull Request \\#21
45 · w3c/webauthn (github.com)](https://github.com/w3c/webauthn/pull/2145
) \n3. [Update Use Cases for L3 by timcappalli · Pull Request \\#2139 ·
w3c/webauthn (github.com)](https://github.com/w3c/webauthn/pull/2139) \n
4. [Update obsolete privacy concerns about throwing errors early by emlun
· Pull Request \\#2134 · w3c/webauthn (github.com)](https://github.com/w
3c/webauthn/pull/2134) \n5. [Clarify meaning of "unless" in UP flag valid
ation by emlun · Pull Request \\#2126 · w3c/webauthn (github.com)](https
://github.com/w3c/webauthn/pull/2126) \n6. [Cleanup: Manual References by
timcappalli · Pull Request \\#2111 · w3c/webauthn (github.com)](https:/
/github.com/w3c/webauthn/pull/2111) \n7. [https://github.com/w3c/webauthn
/pulls?q=is%3Aopen+is%3Apr+milestone%3AL3-WD-02](https://github.com/w3c/we
bauthn/pulls?q=is%3Aopen+is%3Apr+milestone%3AL3-WD-02) \n8. [Clarify TPM
attestation verification instructions by sbweeden · Pull Request \\#1926
· w3c/webauthn (github.com](https://github.com/w3c/webauthn/pull/1926)\n\
n\n#### [Pull requests · w3c/webauthn (github.com)](https://github.com/w3
c/webauthn/pulls?q=is%3Aopen+is%3Apr+no%3Amilestone)\n\n1. [Exclude all pl
atform authenticators that use self attesation from hav… by zacknewman
· Pull Request \\#2150 · w3c/webauthn (github.com)](https://github.com/w
3c/webauthn/pull/2150) \n2. [Remove bikeshed workaround by dwaite · Pull
Request \\#2149 · w3c/webauthn (github.com)](https://github.com/w3c/weba
uthn/pull/2149)\n\n#### [Issues · w3c/webauthn (github.com)](https://gith
ub.com/w3c/webauthn/issues?q=is%3Aopen+is%3Aissue+milestone%3AL3-WD-02+)\n
\n1. [Add \\`userName\\` and \\`userDisplayName\\` to WebDriver's \\`Crede
ntial Parameters\\` JSON object · Issue \\#2143 · w3c/webauthn (github.c
om)](https://github.com/w3c/webauthn/issues/2143) \n2. [Clarify behaviour
of duplicate hints · Issue \\#2135 · w3c/webauthn (github.com)](https:/
/github.com/w3c/webauthn/issues/2135) \n3. [Review privacy concerns aroun
d error conditions · Issue \\#2132 · w3c/webauthn (github.com)](https://
github.com/w3c/webauthn/issues/2132) \n4. [Remove rp.name · Issue \\#212
1 · w3c/webauthn (github.com)](https://github.com/w3c/webauthn/issues/212
1) \n5. [CollectedClientData.crossOrigin not referenced in RP ops · Issu
e \\#2113 · w3c/webauthn (github.com)](https://github.com/w3c/webauthn/is
sues/2113) \n6. [UTF-8 decode should not be required for response.clientD
ataJSON and cData · Issue \\#2100 · w3c/webauthn (github.com)](https://g
ithub.com/w3c/webauthn/issues/2100) \n7. [\\[\\[Create\\]\\] should not a
ccess the global object directly · Issue \\#2092 · w3c/webauthn (github.
com)](https://github.com/w3c/webauthn/issues/2092) \n8. [create() and get
() return an algorithm\, not a credential · Issue \\#1984 · w3c/webauthn
(github.com)](https://github.com/w3c/webauthn/issues/1984) \n9. [Ambiguo
us instructions in the Android Key Attestation Statement Format verificati
on procedure · Issue \\#1980 · w3c/webauthn (github.com)](https://github
.com/w3c/webauthn/issues/1980) \n10. [Are notes in webauthn normative or
informative? · Issue \\#1979 · w3c/webauthn (github.com)](https://github
.com/w3c/webauthn/issues/1979) \n11. [Extensions should specify partial d
ictionaries that modify AuthenticationExtensionsClient{Inputs\, Outputs}JS
ON · Issue \\#1968 · w3c/webauthn (github.com)](https://github.com/w3c/w
ebauthn/issues/1968) \n12. [\\[Superset\\] Updating credential metadata a
nd requesting deletion of stale credentials · Issue \\#1967 · w3c/webaut
hn (github.com)](https://github.com/w3c/webauthn/issues/1967) \n13. [Shou
ld credentials requested with attestation=none include an AAGUID? · Issue
\\#1962 · w3c/webauthn (github.com)](https://github.com/w3c/webauthn/iss
ues/1962) \n14. [Non-modal registration during conditional assertion · I
ssue \\#1929 · w3c/webauthn (github.com)](https://github.com/w3c/webauthn
/issues/1929) \n15. [Adding some sentences to describe credential sharing
between multiple users · Issue \\#1921 · w3c/webauthn (github.com)](htt
ps://github.com/w3c/webauthn/issues/1921) \n16. [Allow desired attestatio
n format to be an ordered list · Issue \\#1917 · w3c/webauthn (github.co
m)](https://github.com/w3c/webauthn/issues/1917) \n17. [Describe packed e
nterprise attestation · Issue \\#1916 · w3c/webauthn (github.com)](https
://github.com/w3c/webauthn/issues/1916) \n18. [Misaligned steps in Sectio
n 7.2 · Issue \\#1913 · w3c/webauthn (github.com)](https://github.com/w3
c/webauthn/issues/1913) \n19. [Prescriptive behaviours for Autofill UI ·
Issue \\#1800 · w3c/webauthn (github.com)](https://github.com/w3c/webaut
hn/issues/1800) \n20. [Should enterprise attestation support be flagged e
xplicitly? · Issue \\#1742 · w3c/webauthn · GitHub](https://github.com/
w3c/webauthn/issues/1742) \n21. [Discussing mechanisms for enterprise RP'
s to enforce bound properties of credentials · Issue \\#1739 · w3c/webau
thn · GitHub](https://github.com/w3c/webauthn/issues/1739) \n22. [Provid
e passwordless example\, or update 1.3.2. to be a passwordless example ·
Issue \\#1735 · w3c/webauthn · GitHub](https://github.com/w3c/webauthn/i
ssues/1735) \n23. [Update top level use cases to account for multi-device
credentials · Issue \\#1720 · w3c/webauthn · GitHub](https://github.co
m/w3c/webauthn/issues/1720) \n24. [Public Key Credential Source and Exten
sions · Issue \\#1719 · w3c/webauthn · GitHub](https://github.com/w3c/w
ebauthn/issues/1719) \n25. [RP operations: some extension processing may
assume that the encompassing signature is valid · Issue \\#1711 · w3c/we
bauthn · GitHub](https://github.com/w3c/webauthn/issues/1711) \n26. [Spl
it RP ops "Registering a new credential" into one with and one without att
estation · Issue \\#1710 · w3c/webauthn (github.com)](https://github.com
/w3c/webauthn/issues/1710) \n27. [Switch to permissive copyright license?
· Issue \\#1705 · w3c/webauthn (github.com)](https://github.com/w3c/web
authn/issues/1705) \n28. [Should an RP be able to provide finer grained a
uthenticator filtering in attestation options? · Issue \\#1688 · w3c/web
authn (github.com)](https://github.com/w3c/webauthn/issues/1688) \n29. [L
ookup Credential Source by Credential ID Algorithm returns sensitive data
such as the credential private key · Issue \\#1678 · w3c/webauthn · Git
Hub](https://github.com/w3c/webauthn/issues/1678) \n30. [Synced Credentia
ls · Issue \\#1665 · w3c/webauthn · GitHub](https://github.com/w3c/weba
uthn/issues/1665) \n31. [Cross-origin credential creation in iframes · I
ssue \\#1656 · w3c/webauthn (github.com)](https://github.com/w3c/webauthn
/issues/1656) \n32. [Trailing position of metadata · Issue \\#1646 · w3
c/webauthn (github.com)](https://github.com/w3c/webauthn/issues/1646) \n3
3. [\\[Editorial\\] Truncation description inaccurate · Issue \\#1645 ·
w3c/webauthn (github.com)](https://github.com/w3c/webauthn/issues/1645) \
n34. [Mechanism for encoding \\*direction\\* metadata may need more work
· Issue \\#1644 · w3c/webauthn (github.com)](https://github.com/w3c/weba
uthn/issues/1644) \n35. [Use of in-field metadata not preferred · Issue
\\#1643 · w3c/webauthn (github.com)](https://github.com/w3c/webauthn/issu
es/1643) \n36. [Unicode "tag" characters are deprecated for language tagg
ing · Issue \\#1642 · w3c/webauthn (github.com)](https://github.com/w3c/
webauthn/issues/1642) \n37. [U+ notation incorrect · Issue \\#1641 · w3
c/webauthn (github.com)](https://github.com/w3c/webauthn/issues/1641) \n3
8. [Syncing Platform Keys\, Recoverability and Security levels · Issue \\
#1640 · w3c/webauthn (github.com)](https://github.com/w3c/webauthn/issues
/1640) \n39. [Possible experiences in a future WebAuthn · Issue \\#1637
· w3c/webauthn (github.com)](https://github.com/w3c/webauthn/issues/1637)
\n40. [Missing Test Vectors · Issue \\#1633 · w3c/webauthn (github.com
)](https://github.com/w3c/webauthn/issues/1633) \n41. [CollectedClientDat
a.crossOrigin default value and whether it is required · Issue \\#1631 ·
w3c/webauthn (github.com)](https://github.com/w3c/webauthn/issues/1631)
\n42. [Support for remote desktops · Issue \\#1577 · w3c/webauthn (githu
b.com)](https://github.com/w3c/webauthn/issues/1577) \n43. [Prevent brows
ers from deleting credentials that the RP wanted to be server-side · Issu
e \\#1569 · w3c/webauthn (github.com)](https://github.com/w3c/webauthn/is
sues/1569) \n44. [Support a "create or get \\[or replace\\]" credential r
e-association operation · Issue \\#1568 · w3c/webauthn (github.com)](htt
ps://github.com/w3c/webauthn/issues/1568) \n45. [Adding info about HSTS f
or the RPID to client Data. · Issue \\#1554 · w3c/webauthn (github.com)]
(https://github.com/w3c/webauthn/issues/1554) \n46. [Making PublicKeyCred
entialDescriptor.transports mandatory · Issue \\#1522 · w3c/webauthn (gi
thub.com)](https://github.com/w3c/webauthn/issues/1522) \n47. [cleanup \\
and use \\
as appropria
te · Issue \\#1489 · w3c/webauthn (github.com)](https://github.com/w3c/w
ebauthn/issues/1489) \n48. [Regarding the issue of Credential ID exposure
(13.5.6)\, from what perspective should RP compare RK and NRK and which sh
ould be adopted? · Issue \\#1484 · w3c/webauthn (github.com)](https://gi
thub.com/w3c/webauthn/issues/1484) \n49. [Requesting properties of create
d credentials. · Issue \\#1449 · w3c/webauthn (github.com)](https://gith
ub.com/w3c/webauthn/issues/1449) \n50. [PublicKeyCredentialParameters can
't select curve (E.g. ed448) · Issue \\#1446 · w3c/webauthn (github.com)
](https://github.com/w3c/webauthn/issues/1446) \n51. [Minor cleanups from
PR 1270 review · Issue \\#1291 · w3c/webauthn (github.com)](https://git
hub.com/w3c/webauthn/issues/1291) \n52. [Clearly define the way how RP ha
ndles the extensions · Issue \\#1258 · w3c/webauthn (github.com)](https:
//github.com/w3c/webauthn/issues/1258) \n53. [export definitions? · Issu
e \\#1049 · w3c/webauthn (github.com)](https://github.com/w3c/webauthn/is
sues/1049) \n54. [undefined terms and terms we really ought to define ·
Issue \\#462 · w3c/webauthn (github.com)](https://github.com/w3c/webauthn
/issues/462)\n\n\n#### [Issues · w3c/webauthn · GitHub](https://github.c
om/w3c/webauthn/issues?q=is%3Aopen+is%3Aissue+-label%3Astat%3AOnGoing+-lab
el%3Astat%3Apr-open+no%3Amilestone)\n\n1. [Allow \\`platform\\`-based self
attestation with non-zero AAGUID when \\`AttestationConveyancePreferenceO
ption\\` \\`"none"\\` is used · Issue \\#2146 · w3c/webauthn (github.com
)](https://github.com/w3c/webauthn/issues/2146) \n2. [Cross-window \\`Vir
tual Authenticator Database\\` · Issue \\#2117 · w3c/webauthn (github.co
m)](https://github.com/w3c/webauthn/issues/2117) \n3. [Make \\`Authentica
torAttestationResponseJSON.publicKeyAlgorithm\\` optional · Issue \\#2106
· w3c/webauthn (github.com)](https://github.com/w3c/webauthn/issues/2106
) \n4. [Additional guidance/clarification on RP ID and origin validation
· Issue \\#2059 · w3c/webauthn (github.com)](https://github.com/w3c/weba
uthn/issues/2059) \n5. [excludeCredentials on Get · Issue \\#2057 · w3c
/webauthn · GitHub](https://github.com/w3c/webauthn/issues/2057) \n6. [C
ollectedClientData serialization is confusing WebIDL and/or Infra values f
or ECMAScript values · Issue \\#2056 · w3c/webauthn (github.com)](https:
//github.com/w3c/webauthn/issues/2056) \n7. [Deprecate AuthenticatorAttac
hment in favor of PublicKeyCredentialHints. · Issue \\#2053 · w3c/webaut
hn (github.com)](https://github.com/w3c/webauthn/issues/2053) \n8. [New A
uthenticator Extension: Time Since UV · Issue \\#2034 · w3c/webauthn (gi
thub.com)](https://github.com/w3c/webauthn/issues/2034) \n9. [Reflect cac
hing of user gestures in WebAuthn assertion · Issue \\#2023 · w3c/webaut
hn (github.com)](https://github.com/w3c/webauthn/issues/2023) \n10. [Revi
sed txAuthSimple extension · Issue \\#2022 · w3c/webauthn (github.com)](
https://github.com/w3c/webauthn/issues/2022) \n11. [Clarify the need for
truly randomly generated challenges (aka challenge callback issue) · Issu
e \\#1856 · w3c/webauthn (github.com)](https://github.com/w3c/webauthn/is
sues/1856) \n12. [Cross origin authentication without iframes (accommodat
ing SPC in WebAuthn) · Issue \\#1667 · w3c/webauthn · GitHub](https://g
ithub.com/w3c/webauthn/issues/1667)\n\n### Other open issues or discussio
ns \n\n### Adjourn
STATUS:CONFIRMED
CREATED:20240614T163320Z
LAST-MODIFIED:20240925T000748Z
SEQUENCE:9
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Web Authentication
Working Group:mailto:public-webauthn@w3.org
LOCATION:4 Concourse Level - Oceanside
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:ef543b12-6e19-436a-90eb-06bcad98e310
DTSTAMP:20240919T044557Z
SUMMARY:Web Fonts Working Group
DTSTART;TZID=America/Los_Angeles:20240924T090000
DTEND;TZID=America/Los_Angeles:20240924T180000
DESCRIPTION:https://www.w3.org/events/meetings/ef543b12-6e19-436a-90eb-06bc
ad98e310/\n\nHello WG\,\n\nPlease see the updated tentative agenda below.
We will discuss and finalize it at the meeting's opening.\nRemote particip
ants - please note that this particular WebFonts WG meeting held during TP
AC will be using a different Zoom Meeting ID (not one we typically use for
our regularly scheduled WG calls).\n\nAgenda\n\nThis updated version is b
ased on the [initial draft](https://lists.w3.org/Archives/Public/public-we
bfonts-wg/2024Aug/0009.html) \n0. Extras / Introductions.\n1. IFT Specific
ation overview.\n2. Detailed spec review\, in particular:\n- specification
structure\;\n- completeness / missing info\;\n- clarity / ambiguity / inc
onsistencies\;\n- missing normative requirements.\n\n3. Encod
er discussions: how to develop a high quality encoder implementation.\n4.
Review / discuss remaining [open issues](https://github.com/w3c/IFT/issues
)\n5. Conformance Test Suite planning:\n- what parts of the spec need to b
e tested (and how)\;\n- what parts (if any) would not be tested (and why).
\n6. AOB.
STATUS:CONFIRMED
CREATED:20240614T163426Z
LAST-MODIFIED:20240919T044557Z
SEQUENCE:5
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Web Fonts Working
Group:mailto:public-webfonts-wg@w3.org
LOCATION:4 Concourse Level - Coronado
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:48627a85-c65d-41f8-b513-b172d36abb12
DTSTAMP:20240924T201525Z
SUMMARY:Web Payments Working Group
DTSTART;TZID=America/Los_Angeles:20240924T090000
DTEND;TZID=America/Los_Angeles:20240924T160000
DESCRIPTION:https://www.w3.org/events/meetings/48627a85-c65d-41f8-b513-b172
d36abb12/\n\n\n\nAgenda: https://github.com/w3c/webpayments/wiki/Agenda-TP
AC2024
STATUS:CONFIRMED
CREATED:20240614T161643Z
LAST-MODIFIED:20240924T201525Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Web Payments Worki
ng Group:mailto:public-payments-wg@w3.org
LOCATION:4 Concourse Level - Huntington
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:90ce430f-02e6-4076-b468-0f0f3ae62af0
DTSTAMP:20240924T164200Z
SUMMARY:Web Performance Working Group
DTSTART;TZID=America/Los_Angeles:20240924T090000
DTEND;TZID=America/Los_Angeles:20240924T160000
DESCRIPTION:https://www.w3.org/events/meetings/90ce430f-02e6-4076-b468-0f0f
3ae62af0/\n\n\n\nAgenda: https://bit.ly/webperf-tpac24\n\nAgenda\n\n* Web
Performance APIs in Excel\n* Conditional tracing\n\n` `\n\n* Exposing
style/layout brainstorm\n* Protobuf encode/decode\n\nLunch\n\n* Scheduling
APIs\n* RUM Pain Points 2024\n\nAfter hours - RUM Archive Hacking
STATUS:CONFIRMED
CREATED:20240614T163421Z
LAST-MODIFIED:20240924T164200Z
SEQUENCE:5
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Web Performance Wo
rking Group:mailto:public-web-perf@w3.org
LOCATION:-1 Lower Level - Catalina 5
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:f9158f73-69ae-4c05-988f-5887bf4bd99b
DTSTAMP:20240927T001918Z
SUMMARY:Web Real-Time Communications Working Group
DTSTART;TZID=America/Los_Angeles:20240924T090000
DTEND;TZID=America/Los_Angeles:20240924T123000
DESCRIPTION:https://www.w3.org/events/meetings/f9158f73-69ae-4c05-988f-5887
bf4bd99b/\n\n\n\nAgenda: https://www.w3.org/2011/04/webrtc/wiki/September_
24_2024
STATUS:CONFIRMED
CREATED:20240614T161640Z
LAST-MODIFIED:20240927T001918Z
SEQUENCE:5
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Web Real-Time Comm
unications Working Group:mailto:public-webrtc@w3.org
LOCATION:-1 Lower Level - Catalina 3
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:9ded3543-e2cd-4dec-92ed-85df81ef110c
DTSTAMP:20240919T221042Z
SUMMARY:WebExtensions Community Group
DTSTART;TZID=America/Los_Angeles:20240924T090000
DTEND;TZID=America/Los_Angeles:20240924T180000
DESCRIPTION:https://www.w3.org/events/meetings/9ded3543-e2cd-4dec-92ed-85df
81ef110c/\n\n\n\nAgenda: https://github.com/w3c/webextensions/wiki/TPAC-20
24-Coordination#tuesday
STATUS:CONFIRMED
CREATED:20240704T125807Z
LAST-MODIFIED:20240919T221042Z
SEQUENCE:5
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=WebExtensions Comm
unity Group:mailto:public-webextensions@w3.org
LOCATION:-1 Lower Level - Catalina 2
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:d7c84e8e-db2f-4c8d-8047-40b69f848807
DTSTAMP:20240924T191116Z
SUMMARY:WebView Community Group
DTSTART;TZID=America/Los_Angeles:20240924T090000
DTEND;TZID=America/Los_Angeles:20240924T123000
DESCRIPTION:https://www.w3.org/events/meetings/d7c84e8e-db2f-4c8d-8047-40b6
9f848807/\n\n\n\nAgenda: https://github.com/orgs/WebView-CG/discussions/5#
discussioncomment-10336140
STATUS:CONFIRMED
CREATED:20240614T163456Z
LAST-MODIFIED:20240924T191116Z
SEQUENCE:8
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=WebView Community
Group:mailto:public-webview@w3.org
LOCATION:-1 Lower Level - Catalina 1
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:ecf72b3f-b081-499b-b50f-b9065036af65
DTSTAMP:20240924T183330Z
SUMMARY:Cancelled -- Federated Identity Working Group\, Federated Identity
Community Group Joint Meeting
DTSTART;TZID=America/Los_Angeles:20240924T110000
DTEND;TZID=America/Los_Angeles:20240924T123000
DESCRIPTION:https://www.w3.org/events/meetings/ecf72b3f-b081-499b-b50f-b906
5036af65/\n\nDue to hotel power outage\, this meeting is cancelled. Apolog
ies!\n\nAgenda: https://github.com/fedidcg/meetings/blob/main/2024/2024-09
-24-TPAC.md
STATUS:CANCELLED
CREATED:20240614T161722Z
LAST-MODIFIED:20240924T183330Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Federated Identity
Community Group:mailto:public-fed-id@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Federated Identity
Working Group:mailto:public-fedid-wg@w3.org
LOCATION:2 Ballroom Level - California B
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:1eacc897-1a39-43b1-a2ae-d9369f9966e4
DTSTAMP:20240924T043609Z
SUMMARY:Devices and Sensors Working Group
DTSTART;TZID=America/Los_Angeles:20240924T110000
DTEND;TZID=America/Los_Angeles:20240924T180000
DESCRIPTION:https://www.w3.org/events/meetings/1eacc897-1a39-43b1-a2ae-d936
9f9966e4/\n\n\n\nAgenda: https://github.com/w3c/devicesensors-wg/issues/69
STATUS:CONFIRMED
CREATED:20240614T163324Z
LAST-MODIFIED:20240924T043609Z
SEQUENCE:7
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Devices and Sensor
s Working Group:mailto:public-device-apis@w3.org
LOCATION:-1 Lower Level - Catalina 7
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:e3724be4-18f0-4846-93c4-ddf0f0839697
DTSTAMP:20240917T191602Z
SUMMARY:Immersive Web Working Group\, Web Applications Working Group Joint
Meeting
DTSTART;TZID=America/Los_Angeles:20240924T110000
DTEND;TZID=America/Los_Angeles:20240924T123000
DESCRIPTION:https://www.w3.org/events/meetings/e3724be4-18f0-4846-93c4-ddf0
f0839697/\n\nThis was cancelled due to a clash\, the topics for this discu
ssion will be discussed during the Model Element break out session.\n\nhtt
ps://www.w3.org/events/meetings/beb1a75f-bc12-42c0-9691-6d73be98632b/\n\nA
genda: https://github.com/immersive-web/administrivia/tree/main/TPAC2024#a
genda
STATUS:CANCELLED
CREATED:20240614T163409Z
LAST-MODIFIED:20240917T191602Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Immersive Web Work
ing Group:mailto:public-immersive-web-wg@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Web Applications W
orking Group:mailto:public-webapps@w3.org
LOCATION:-1 Lower Level - Catalina 4
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:46d3f649-2027-40eb-8aa1-695aa3513190
DTSTAMP:20241002T170558Z
SUMMARY:JSON-LD Working Group\, RDF-star Working Group\, JSON for Linked Da
ta Community Group Joint Meeting
DTSTART;TZID=America/Los_Angeles:20240924T110000
DTEND;TZID=America/Los_Angeles:20240924T123000
DESCRIPTION:https://www.w3.org/events/meetings/46d3f649-2027-40eb-8aa1-695a
a3513190/\n\nMeeting canceled at the last minute due to a power outage in
the conference facility.
STATUS:CANCELLED
CREATED:20240905T145921Z
LAST-MODIFIED:20241002T170558Z
SEQUENCE:5
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=JSON for Linked Da
ta Community Group:mailto:public-json-ld@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=JSON-LD Working Gr
oup:mailto:public-json-ld-wg@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=RDF & SPARQL Worki
ng Group:mailto:public-rdf-star-wg@w3.org
LOCATION:4 Concourse Level - La Jolla
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:a4bfaea7-f932-4dec-ba73-c8e78ea1fa6e
DTSTAMP:20240924T204312Z
SUMMARY:Web Platform Incubator Community Group
DTSTART;TZID=America/Los_Angeles:20240924T110000
DTEND;TZID=America/Los_Angeles:20240924T160000
DESCRIPTION:https://www.w3.org/events/meetings/a4bfaea7-f932-4dec-ba73-c8e7
8ea1fa6e/\n\n\n\nAgenda: https://github.com/WICG/admin/issues/194
STATUS:CONFIRMED
CREATED:20240614T163021Z
LAST-MODIFIED:20240924T204312Z
SEQUENCE:5
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Web Platform Incub
ator Community Group:mailto:public-wicg@w3.org
LOCATION:2 Ballroom Level - California A
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:9f5c3b5b-af36-4680-ab98-8ae7bb20659c
DTSTAMP:20240924T160049Z
SUMMARY:Accessible Platform Architectures Working Group
DTSTART;TZID=America/Los_Angeles:20240924T140000
DTEND;TZID=America/Los_Angeles:20240924T180000
DESCRIPTION:https://www.w3.org/events/meetings/9f5c3b5b-af36-4680-ab98-8ae7
bb20659c/\n\n\n\nAgenda\n\n### 1400 to 1530: Accessibility Maturity Model
(AMM) TF and Equity CG\n\n* Is the APA AMM ready for publication? Why?\n*
Is the APA AMM NOT ready for publication? Why?\n* Are our approaches suffi
ciently coordinated? How do we do better?\n* Is the Equity CG a snapshot o
f APA AMM? At what point? How maintaining synchronization?\n* Has Equity (
others) discovered an incompatability to the APA AMM that requires resolut
ion?\n\n### 1530 to 1600: TBD - APA WG working time\n\nAny WG/TF work can
be done here - if you have specific agenda to raise\, let us know.\n\nSugg
estions:\n\n* APA WG re-chartering (early 2025) - scope\, deliverables.\n*
COGA's proposed new format for the next version of ["Content Usable"](htt
ps://www.w3.org/TR/coga-usable/).\n\n### 1530 to 1600: TBD - APA WG workin
g time\n\nAny WG/TF work can be done here - if you have specific agenda to
raise\, let us know.\n\nSuggestions:\n\n* APA WG re-chartering (early 202
5) - scope\, deliverables.\n* COGA's proposed new format for the next vers
ion of ["Content Usable"](https://www.w3.org/TR/coga-usable/).
STATUS:CONFIRMED
CREATED:20240614T163339Z
LAST-MODIFIED:20240924T160049Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Accessible Platfor
m Architectures Working Group:mailto:public-apa@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Equity Community G
roup:mailto:public-equity@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Maturity Model Tas
k Force:mailto:public-maturity@w3.org
LOCATION:4 Concourse Level - Manhattan
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:c5e208d2-7b32-4e02-8edf-6bd1a0d78e21
DTSTAMP:20240922T085158Z
SUMMARY:Audio Working Group
DTSTART;TZID=America/Los_Angeles:20240924T140000
DTEND;TZID=America/Los_Angeles:20240924T180000
DESCRIPTION:https://www.w3.org/events/meetings/c5e208d2-7b32-4e02-8edf-6bd1
a0d78e21/\n\n\n\nAgenda: https://bit.ly/audiowg-tpac-2024
STATUS:CONFIRMED
CREATED:20240614T163418Z
LAST-MODIFIED:20240922T085158Z
SEQUENCE:7
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Audio Working Grou
p:mailto:public-audio@w3.org
LOCATION:4 Concourse Level - La Jolla
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:3db77274-f760-4060-80e2-cc13b616c055
DTSTAMP:20240924T210814Z
SUMMARY:Browser Testing and Tools Working Group\, Web Applications Working
Group Joint Meeting
DTSTART;TZID=America/Los_Angeles:20240924T140000
DTEND;TZID=America/Los_Angeles:20240924T160000
DESCRIPTION:https://www.w3.org/events/meetings/3db77274-f760-4060-80e2-cc13
b616c055/\n\n\n\nAgenda: https://github.com/w3c/webappswg/wiki/TPAC-2024
STATUS:CONFIRMED
CREATED:20240614T163440Z
LAST-MODIFIED:20240924T210814Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Browser Testing an
d Tools Working Group:mailto:public-browser-tools-testing@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Web Applications W
orking Group:mailto:public-webapps@w3.org
LOCATION:-1 Lower Level - Catalina 1
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:47b10aa6-3050-4714-ba22-736c4e748341
DTSTAMP:20240925T143704Z
SUMMARY:Federated Identity Working Group
DTSTART;TZID=America/Los_Angeles:20240924T140000
DTEND;TZID=America/Los_Angeles:20240924T160000
DESCRIPTION:https://www.w3.org/events/meetings/47b10aa6-3050-4714-ba22-736c
4e748341/\n\nUpdating to include WG and CG\, extending the meeting after p
ower outage earlier today. We will juggle the agenda to include items from
morning's agenda. Thanks for your patience!\n\nAgenda: https://github.com
/w3c-fedid/meetings/blob/main/2024/2024-09-24-TPAC-agenda.md
STATUS:CONFIRMED
CREATED:20240614T161718Z
LAST-MODIFIED:20240925T143704Z
SEQUENCE:7
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Federated Identity
Community Group:mailto:public-fed-id@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Federated Identity
Working Group:mailto:public-fedid-wg@w3.org
LOCATION:2 Ballroom Level - California B
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:37e4b9e4-9f2f-4fae-bb2f-e7ed767be4a8
DTSTAMP:20240925T001907Z
SUMMARY:Immersive Web Working Group
DTSTART;TZID=America/Los_Angeles:20240924T140000
DTEND;TZID=America/Los_Angeles:20240924T180000
DESCRIPTION:https://www.w3.org/events/meetings/37e4b9e4-9f2f-4fae-bb2f-e7ed
767be4a8/\n\n\n\nAgenda: https://github.com/immersive-web/administrivia/tr
ee/main/TPAC2024#agenda
STATUS:CONFIRMED
CREATED:20240614T163406Z
LAST-MODIFIED:20240925T001907Z
SEQUENCE:8
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Immersive Web Work
ing Group:mailto:public-immersive-web-wg@w3.org
LOCATION:4 Concourse Level - San Clemente
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:624ecc09-f7ed-4dac-a4bf-1b6826af680e
DTSTAMP:20240923T212707Z
SUMMARY:WebTransport Working Group
DTSTART;TZID=America/Los_Angeles:20240924T140000
DTEND;TZID=America/Los_Angeles:20240924T160000
DESCRIPTION:https://www.w3.org/events/meetings/624ecc09-f7ed-4dac-a4bf-1b68
26af680e/\n\n\n\nAgenda: https://www.w3.org/wiki/WebTransport/Meetings2023
#W3C_WebTransport_Annual_TPAC_meeting_-_Sept_24\,_2024
STATUS:CONFIRMED
CREATED:20240614T153529Z
LAST-MODIFIED:20240923T212707Z
SEQUENCE:5
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=WebTransport Worki
ng Group:mailto:public-webtransport@w3.org
LOCATION:-1 Lower Level - Catalina 3
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:bdef3142-8c25-44dc-a130-138184559d32
DTSTAMP:20240924T221618Z
SUMMARY:Internationalization Working Group\, CSS Working Group Joint Meetin
g
DTSTART;TZID=America/Los_Angeles:20240924T163000
DTEND;TZID=America/Los_Angeles:20240924T180000
DESCRIPTION:https://www.w3.org/events/meetings/bdef3142-8c25-44dc-a130-1381
84559d32/\n\n\n\nAgenda: https://lists.w3.org/Archives/Public/public-editi
ng-tf/2024Sep/0003.html
STATUS:CONFIRMED
CREATED:20240614T161654Z
LAST-MODIFIED:20240924T221618Z
SEQUENCE:7
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Cascading Style Sh
eets (CSS) Working Group:mailto:www-style@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Internationalizati
on Working Group:mailto:public-i18n-core@w3.org
LOCATION:4 Concourse Level - Laguna
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:f3553156-8aa7-41fa-9f85-1e8848b995f9
DTSTAMP:20241003T120752Z
SUMMARY:Screen Capture Community Group\, Web Real-Time Communications Worki
ng Group Joint Meeting
DTSTART;TZID=America/Los_Angeles:20240924T163000
DTEND;TZID=America/Los_Angeles:20240924T180000
DESCRIPTION:https://www.w3.org/events/meetings/f3553156-8aa7-41fa-9f85-1e88
48b995f9/\n\n\n\nAgenda: https://www.w3.org/2011/04/webrtc/wiki/September_
24b_2014
STATUS:CONFIRMED
CREATED:20240614T154328Z
LAST-MODIFIED:20241003T120752Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Screen Capture Com
munity Group:mailto:public-sccg@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Web Real-Time Comm
unications Working Group:mailto:public-webrtc@w3.org
LOCATION:-1 Lower Level - Catalina 1
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:ad4b8e60-35ce-4c2c-b52b-df4c92f148ff
DTSTAMP:20240924T234831Z
SUMMARY:Web Payments Working Group\, Web Authentication Working Group Joint
Meeting
DTSTART;TZID=America/Los_Angeles:20240924T163000
DTEND;TZID=America/Los_Angeles:20240924T180000
DESCRIPTION:https://www.w3.org/events/meetings/ad4b8e60-35ce-4c2c-b52b-df4c
92f148ff/\n\n\n\nAgenda: https://www.w3.org/2024/Talks/TPAC/wpwg-webauthn/
STATUS:CONFIRMED
CREATED:20240614T163322Z
LAST-MODIFIED:20240924T234831Z
SEQUENCE:5
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Web Authentication
Working Group:mailto:public-webauthn@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Web Payments Worki
ng Group:mailto:public-payments-wg@w3.org
LOCATION:2 Ballroom Level - California A
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:d2094f4c-5e77-4b4d-b2b7-d9ff0a1de4bb
DTSTAMP:20240924T232859Z
SUMMARY:WHATWG
DTSTART;TZID=America/Los_Angeles:20240924T163000
DTEND;TZID=America/Los_Angeles:20240924T180000
DESCRIPTION:https://www.w3.org/events/meetings/d2094f4c-5e77-4b4d-b2b7-d9ff
0a1de4bb/\n\n\n\nAgenda: https://github.com/whatwg/meta/issues/326
STATUS:CONFIRMED
CREATED:20240614T161723Z
LAST-MODIFIED:20240924T232859Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - Huntington
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:d33f09f9-a171-452e-8998-1c5130669f97
DTSTAMP:20240925T031120Z
SUMMARY:Hackathon @ TPAC 2024
DTSTART;TZID=America/Los_Angeles:20240924T203000
DTEND;TZID=America/Los_Angeles:20240924T223000
DESCRIPTION:https://www.w3.org/events/meetings/d33f09f9-a171-452e-8998-1c51
30669f97/\n\nJoin us for the TPAC Hackathon! It’s going to be a fun\, lo
w-key evening with an HTML/CSS challenge where you can show off your codin
g skills\, get creative\, and win some nerdy prizes. Snacks are included\,
and it’s a great chance to take a break\, meet new people\, and enjoy a
little friendly competition.\nAll skills and abilities welcome. We only h
ave space for 30 people\, so make sure to sign up early if you want to joi
n. This is an in-person event.\nMore information here: https://www.w3.org/
2024/09/TPAC/hackathon/
STATUS:CONFIRMED
CREATED:20240918T210744Z
LAST-MODIFIED:20240925T031120Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - Huntington
CATEGORIES:TPAC 2024
END:VEVENT
BEGIN:VEVENT
UID:3492ce36-6f12-4387-9578-162929256742
DTSTAMP:20260317T123819Z
SUMMARY:Breaking Silos: A Collaborative Discussion on Use Cases for Linked
Web Storage
DTSTART;TZID=America/Los_Angeles:20240925T083000
DTEND;TZID=America/Los_Angeles:20240925T093000
DESCRIPTION:https://www.w3.org/events/meetings/3492ce36-6f12-4387-9578-1629
29256742/\n\nThe mission of the newly created [Linked Web Storage Working
Group](https://www.w3.org/groups/wg/lws/) is to enable the development of
web applications where data storage\, entity authentication\, access contr
ol\, and application providers are all loosely coupled\, as opposed to the
web of today where these are typically all tightly coupled and changing o
ne requires changing all\, sometimes at the price of all past data.\n\nA n
umber of initiatives — such as [IndieWeb](https://indieweb.org/)\, [Unho
sted](https://www.w3.org/community/unhosted/)\, and [Solid](https://solidp
roject.org/) — have emerged to propose alternative models for web applic
ations. They are largely based on existing open web standards\, which they
extend to give priority to individual and group autonomy.\n\nThe goal of
the breakout session is to bring together current and potential participan
ts of the Linked Web Storage Working Group\, as well as members of other c
ommunities with shared interests (such as the ones cited above) to seed a
set of use-cases that the working group can later adopt to guide its work.
\n\n**Goal(s):**\nGather use cases and experiences from a wide range of pe
ople to initiate the work of the Linked Web Storage WG.\n\nAgenda\n\n**Mat
erials:**\n- [minutes (initial google doc)](https://docs.google.com/docume
nt/d/1sFZ0BozoLA3U7iROtu10tR7S05_OEOprS8Um9NZqZYw/edit)\n- [Session propos
al on GitHub](https://github.com/w3c/tpac2024-breakouts/issues/66)
STATUS:CONFIRMED
CREATED:20240916T215745Z
LAST-MODIFIED:20260317T123819Z
SEQUENCE:2
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
BEGIN:VEVENT
UID:5250e361-57a6-4b00-ab40-0ad7882116a9
DTSTAMP:20260317T122235Z
SUMMARY:Browser API for Country Data
DTSTART;TZID=America/Los_Angeles:20240925T083000
DTEND;TZID=America/Los_Angeles:20240925T093000
DESCRIPTION:https://www.w3.org/events/meetings/5250e361-57a6-4b00-ab40-0ad7
882116a9/\n\nMillions of websites rely on country and address formatting d
ata that needs to be unnecessarily downloaded on everyone of those website
s. \nFor example on a regular Shopify onlinestore this leads to 193kB unco
mpressed or 17.7kB compressed data being downloaded on every store. \nTo a
llow developers build simpler and more performant websites we want to disc
uss our [proposal for a browser API for country data](https://docs.google.
com/document/d/1tIBs9KKlTWe4qh1xWdbOk32vDqp8gKqG-KdRqBQq_30/edit).\n\n**Go
al(s):**\nDiscuss proposal\, get feedback\, and discuss next steps\n\n**Tr
ack(s):**\n- UX\n\nAgenda\n\n**Materials:**\n- [Session proposal on GitHub
](https://github.com/w3c/tpac2024-breakouts/issues/42)
STATUS:CONFIRMED
CREATED:20240916T215303Z
LAST-MODIFIED:20260317T122235Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - San Clemente
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:94791d4e-be2e-471d-8d0e-8a747bab86b7
DTSTAMP:20260317T122355Z
SUMMARY:Canvas place element
DTSTART;TZID=America/Los_Angeles:20240925T083000
DTEND;TZID=America/Los_Angeles:20240925T093000
DESCRIPTION:https://www.w3.org/events/meetings/94791d4e-be2e-471d-8d0e-8a74
7bab86b7/\n\nA fundamental capability missing from the web is the ability
to complement Canvas with HTML elements. Adding this capability enables Ca
nvas surfaces to benefit from all of the styling\, layout and behaviors of
HTML\, including interactive elements and built-in accessibility.\n\n**Go
al(s):**\nPresent high level proposal and open questions\, gather develope
r and implementor feedback\n\n**Track(s):**\n- Web Apps\n\nAgenda\n\n1. Us
e-cases targeted by this capability.\n2. Rendering model and basic syntax:
2d canvas\, WebGL\, WebGPU.\n3. Major open questions\n\n**Materials:**\n-
[minutes (initial google doc)](https://docs.google.com/document/d/1cZfeeJ
3wnPxikYJiW4P637hO6SNOeV5sQy2kEm5w0J8/edit#heading=h.xsf51u7rrtz)\n- [Sess
ion proposal on GitHub](https://github.com/w3c/tpac2024-breakouts/issues/4
3)
STATUS:CONFIRMED
CREATED:20240916T215311Z
LAST-MODIFIED:20260317T122355Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:2 Ballroom Level - California B
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
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
BEGIN:VEVENT
UID:c76163e0-bb37-444e-8129-805a7c8a2428
DTSTAMP:20260317T122550Z
SUMMARY:Discover the Italian Digital Identity Wallet
DTSTART;TZID=America/Los_Angeles:20240925T083000
DTEND;TZID=America/Los_Angeles:20240925T093000
DESCRIPTION:https://www.w3.org/events/meetings/c76163e0-bb37-444e-8129-805a
7c8a2428/\n\nAfter more than two years of work and over a year of developm
ent\, Italy has launched the first phase of the IT-Wallet pilot\, a digita
l wallet solution that balances the experience gained from existing nation
al digital identity systems with the requirements introduced by the new pa
radigm of digital wallets\, as outlined by the EUDI Wallet regulation. In
this presentation\, we will summarize how the project began\, how it conti
nues to seek harmony with the EUDI Wallet\, and the implementation choices
that make the IT-Wallet an interesting platform for a critical analysis o
f Wallet Architectures.\n\n**Goal(s):**\nThe purpose of this session is to
provide guidance on following the development of the IT-Wallet and to hig
hlight some unique aspects of the Italian model. These include the trust i
nfrastructure\, revocation control mechanisms\, and the integration model
for Authentic Sources through the national interoperability platform.\n\n*
*Track(s):**\n- Wallets\n\nAgenda: https://www.w3.org/2024/Talks/TPAC/brea
kouts/italian-wallet.pdf\n\nAgenda\n\n**Materials:**\n- [slides](https://w
ww.w3.org/2024/Talks/TPAC/breakouts/italian-wallet.pdf)\n- [Session propos
al on GitHub](https://github.com/w3c/tpac2024-breakouts/issues/93)
STATUS:CONFIRMED
CREATED:20240916T220248Z
LAST-MODIFIED:20260317T122550Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:-1 Lower Level - Catalina 5
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:6bf05e2c-56cf-4137-b918-5985080a54ed
DTSTAMP:20240925T152117Z
SUMMARY:Ecma Beyond ECMAScript—Highlights from some of the other 53 Techn
ical Committees
DTSTART;TZID=America/Los_Angeles:20240925T083000
DTEND;TZID=America/Los_Angeles:20240925T093000
DESCRIPTION:https://www.w3.org/events/meetings/6bf05e2c-56cf-4137-b918-5985
080a54ed/\n\nEcma is a standards body responsible for far more than specif
ying JavaScript™. There are currently 15 technical committees\, and hist
orically 54 total. Some of these technical committees focus on hardware\,
acoustics\, and even consumer safety. Others\, though\, include programmin
g languages (Dart\, C#\, Eiffel) and a variety of software-related topics
ranging from supply chain security to Office Open XML formats. In this bre
akout session\, we’ll explore these together and dive a little deeper on
whichever the attendees find most interesting.\n\nAgenda\n\n**Chairs:**\n
Aki Braun\n\n**Description:**\nEcma is a standards body responsible for fa
r more than specifying JavaScript™. There are currently 15 technical com
mittees\, and historically 54 total. Some of these technical committees fo
cus on hardware\, acoustics\, and even consumer safety. Others\, though\,
include programming languages (Dart\, C#\, Eiffel) and a variety of softwa
re-related topics ranging from supply chain security to Office Open XML fo
rmats. In this breakout session\, we’ll explore these together and dive
a little deeper on whichever the attendees find most interesting.\n\n**Goa
l(s):**\nDiscuss and explore the potential relationship with Ecma work are
as most relevant to W3C participants\n\n\n\n**Materials:**\n- [Session pro
posal on GitHub](https://github.com/w3c/tpac2024-breakouts/issues/86)
STATUS:CANCELLED
CREATED:20240916T220144Z
LAST-MODIFIED:20240925T152117Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - Huntington
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:76e1bb63-3f4d-43a9-b4c9-41cb403aa87c
DTSTAMP:20260317T122644Z
SUMMARY:Expanding Verifiable Credentials: Future Standards and Innovations
DTSTART;TZID=America/Los_Angeles:20240925T083000
DTEND;TZID=America/Los_Angeles:20240925T093000
DESCRIPTION:https://www.w3.org/events/meetings/76e1bb63-3f4d-43a9-b4c9-41cb
403aa87c/\n\nThis breakout session for Verifiable Credentials will explore
key areas for future development and standardization. It will cover the w
ork on renderMethod and confidenceMethod\, which provide flexibility for e
nhancing credential presentation and verifier trust. It will delve into th
e integration of the unlinkable ECDSA cryptosuite\, an advancement for pri
vacy-preserving credentials. It will cover the work on VC barcodes and the
ongoing work on the VC API\, supporting VC lifecycle management. The grou
p will explore innovative methods for VC transmission over wireless techno
logies\, including NFC and Bluetooth\, to support in-person interactions.
Finally\, there will be discussion on vocabulary development for specific
domains such as driver's licenses\, electronic ID cards (EADs)\, citizensh
ip documents\, vehicle titles\, and more\, to ensure broad applicability a
nd interoperability of Verifiable Credentials across various market vertic
als.\n\n**Goal(s):**\nInform members on upcoming Verifiable Credentials wo
rk as well as future rechartered work.\n\n**Track(s):**\n- Identity\n\nAge
nda\n\n- RenderMethod \n- ConfidenceMethod \n- Unlinkable ECDSA Cryptosuit
e\n- VC Barcodes\n- VC API \n- VC over WirelessNFC\n- Vocabulary work\n\n*
*Materials:**\n- [Session proposal on GitHub](https://github.com/w3c/tpac2
024-breakouts/issues/37)
STATUS:CONFIRMED
CREATED:20240916T215216Z
LAST-MODIFIED:20260317T122644Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - Manhattan
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:beb1a75f-bc12-42c0-9691-6d73be98632b
DTSTAMP:20260317T122752Z
SUMMARY:HTML Model Element Discussion
DTSTART;TZID=America/Los_Angeles:20240925T083000
DTEND;TZID=America/Los_Angeles:20240925T093000
DESCRIPTION:https://www.w3.org/events/meetings/beb1a75f-bc12-42c0-9691-6d73
be98632b/\n\nDiscussions about with some Wider Groups\n\n**Goal(s)
:**\nEstablish whether Model elements are Media Elements\n\nAgenda\n\nThe
HTML Model Element is an in progress proposal for a new HTML element which
can display 3D models on a Web Site\, with capabilities for displaying in
Stereo on compatible display hardware such as VR and AR devices.\n\n####
Is the element a Media Element?\n\nThe model element has many capa
bilities which overlap with Media elements\, what does it mean to be a med
ia element and is it appropriate here?\n\nFor example a model could have a
duration for it's animation but it might not be animated at all. It could
potentially have multiple independent tracks.\n\n#### Should model's allo
wed to be transparent can they always be opaque are there any always opaqu
e elements?\n\nCan lead to uncomfortable visual conflicts if the 3D model
punches through text/content which is behind it but visually in front.\n\n
#### General Q&A\n\n**Materials:**\n- [Session proposal on GitHub]
(https://github.com/w3c/tpac2024-breakouts/issues/33)
STATUS:CONFIRMED
CREATED:20240916T215121Z
LAST-MODIFIED:20260317T122752Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - Laguna
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:26d68797-a5ab-45f4-b8fa-d0b3fa5a50f5
DTSTAMP:20260317T123009Z
SUMMARY:One year update: fenced frames with local unpartitioned data access
DTSTART;TZID=America/Los_Angeles:20240925T083000
DTEND;TZID=America/Los_Angeles:20240925T093000
DESCRIPTION:https://www.w3.org/events/meetings/26d68797-a5ab-45f4-b8fa-d0b3
fa5a50f5/\n\nThis breakout session will serve as a 1 year update to the "f
enced frames with local unpartitioned data access" project. We will:\n\n-
Briefly recap the [fenced frames with local unpartitioned data access](htt
ps://github.com/WICG/fenced-frame/blob/master/explainer/fenced_frames_with
_local_unpartitioned_data_access.md) explainer.\n\n- Go over implementatio
n progress in Chrome and highlight solutions that may be valuable to other
developers.\n\n**Goal(s):**\nTo present implementation and design updates
\, and welcome feedback on any use cases that may benefit from this.\n\nAg
enda\n\n**Materials:**\n- [slides](https://www.w3.org/2024/Talks/TPAC/brea
kouts/fenced-frames.pdf)\n- [Session proposal on GitHub](https://github.co
m/w3c/tpac2024-breakouts/issues/40)
STATUS:CONFIRMED
CREATED:20240916T215247Z
LAST-MODIFIED:20260317T123009Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - Palos Verdes
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:e5cb0ff4-1696-4367-b9fe-9e74c5034dd3
DTSTAMP:20260317T123110Z
SUMMARY:One Year Update: Using LinkML in Web of Things Specifications
DTSTART;TZID=America/Los_Angeles:20240925T083000
DTEND;TZID=America/Los_Angeles:20240925T093000
DESCRIPTION:https://www.w3.org/events/meetings/e5cb0ff4-1696-4367-b9fe-9e74
c5034dd3/\n\nAs kind of a follow-up of https://github.com/w3c/breakouts-da
y-2024/issues/15 and its predecessor https://github.com/w3c/tpac2023-break
outs/issues/8 \, in this breakout\, the Thing Description Task Force of th
e Web of Things WG would like to talk about their experience using LinkML
to change how they generate various resources and specification text for t
heir technical reports.\n\n**Goal(s):**\nExperience Sharing\, Discussion\n
\nAgenda\n\n- Wrap-up of Schemata Discussions from TPAC2023 and Breakout D
ay 2024\n- Presenting LinkML Usage in WoT Thing Description Specification
Work\n- Feedback and Discussion\n\n**Materials:**\n- [slides](https://www.
w3.org/2024/Talks/TPAC/breakouts/linkml-wot.pdf)\n- [Session proposal on G
itHub](https://github.com/w3c/tpac2024-breakouts/issues/23)
STATUS:CONFIRMED
CREATED:20240916T215009Z
LAST-MODIFIED:20260317T123110Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - Capistrano
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:fe574102-b4a2-4517-8f3e-02f7b69f73b2
DTSTAMP:20260317T123211Z
SUMMARY:Sharing styles with Declarative Shadow DOM
DTSTART;TZID=America/Los_Angeles:20240925T083000
DTEND;TZID=America/Los_Angeles:20240925T093000
DESCRIPTION:https://www.w3.org/events/meetings/fe574102-b4a2-4517-8f3e-02f7
b69f73b2/\n\nScript-based Shadow DOM can share styles with AdoptedStyleshe
ets\, but Declarative Shadow DOM must either initiate network requests or
use scripting to share styles. This session will discuss various proposals
for sharing styles with Shadow DOM's declaratively. These include:\n\nhtt
ps://github.com/WICG/webcomponents/issues/909\nhttps://github.com/w3c/cssw
g-drafts/issues/10176\n\n**Goal(s):**\nCome to a consensus on which approa
ch is preferred for sharing stylesheets in Declarative Shadow DOM.\n\n**Tr
ack(s):**\n- Web Components\n\nAgenda\n\n1. Discuss requirements from deve
lopers\n a. Fully declarative (no network requests)\n b. Able to opt-in
for specific shadow roots\n c. Able to export styles *out* of shadow root
s\n2. Discuss various proposals\n a. https://github.com/WICG/webcomponent
s/issues/909\n b. https://github.com/w3c/csswg-drafts/issues/10176\n\n**M
aterials:**\n- [Session proposal on GitHub](https://github.com/w3c/tpac202
4-breakouts/issues/31)
STATUS:CONFIRMED
CREATED:20240916T215105Z
LAST-MODIFIED:20260317T123211Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:-1 Lower Level - Catalina 3
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:2da8028a-367a-4ddd-a43c-f821d04bbc0c
DTSTAMP:20260317T123307Z
SUMMARY:Trust the Origin\, Trust the Content - Originator Profile
DTSTART;TZID=America/Los_Angeles:20240925T083000
DTEND;TZID=America/Los_Angeles:20240925T093000
DESCRIPTION:https://www.w3.org/events/meetings/2da8028a-367a-4ddd-a43c-f821
d04bbc0c/\n\nThis breakout session will introduce Originator Profile\, whi
ch aims to tackle misinformation using verified originators' profiles. Dis
cussions will also explore possible collaboration with similar projects\,
such as C2PA\, that depend on the originator.\n\n**Goal(s):**\nProvides an
overview of Originator Profile Discuss potential standardization Find pot
ential collaborators.\n\nAgenda\n\n- Introduction to Originator Profile (2
0m\, includes short intro video)\n- Demonstration (5 min)\n- Discussions (
30min)\n- Wrap-up (5min)\n\n**Materials:**\n- [Session proposal on GitHub]
(https://github.com/w3c/tpac2024-breakouts/issues/90)
STATUS:CONFIRMED
CREATED:20240916T220213Z
LAST-MODIFIED:20260317T123307Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:-1 Lower Level - Catalina 2
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:a475d392-c679-4db6-95c5-2ff190a98b85
DTSTAMP:20260317T123419Z
SUMMARY:User Research on Permissions
DTSTART;TZID=America/Los_Angeles:20240925T083000
DTEND;TZID=America/Los_Angeles:20240925T093000
DESCRIPTION:https://www.w3.org/events/meetings/a475d392-c679-4db6-95c5-2ff1
90a98b85/\n\nThis breakout provides an opportunity to share results from u
ser research on permission prompts\, discuss methods and findings\, and id
eate on additional research that could help the community.\n\nPermissions
are notoriously difficult to study\, given that they happen in very brief
moments while users try to accomplish a primary task. Yet\, they are an im
portant security and privacy mechanism that can have substantial positive
or negative impact on users' experiences on the web. The Chrome team condu
cted two studies to ([1](https://dl.acm.org/doi/pdf/10.1145/3613904.364225
2)) understand the general experience of permission prompts on the web as
well as ([2](https://www.ndss-symposium.org/wp-content/uploads/2024-108-pa
per.pdf)) how users perceive a mechanism to make prompts less interruptive
. We will share a brief overview of results from the two studies and discu
ss implications.\n\nBeyond that\, this forum provides an opportunity to ex
change ideas and experiences when conducting user research on security and
privacy mechanisms in browsers as well as to identify new opportunities t
o better understand users' experiences.\n\nPlease leave comments and sugge
stions\, for example if you also have user research in the permissions spa
ce that you would like to share or other ideas that would fit well into th
e scope of this breakout.\n\n[Slide deck](https://drive.google.com/file/d/
1vEhjRx1j69fA2zDtDOJbfsMxOEC3qV-C/view)\n[Recording of conference talk for
paper 1](https://dl.acm.org/doi/full/10.1145/3613904.3642252#supplementar
y-materials)\n[Recording of conference talk for paper 2](https://www.youtu
be.com/watch?v=rbsAPw1XL5Q)\n\n#### **Notes from Q\\&A:**\n\n*Q: When acce
ssing or requesting permission websites should explain why. Any testing an
d research whether the page has made an attempt to explain to the user why
it is asking?* \nA: Permission rationale study. Tricky to draw firm con
clusions\, data is very noisy. Will follow up with a study replicating the
main flows we observed.\n\n*Q: why do websites ask for permission on arri
val? E.g. [google.com](http://google.com) asks like that without context.*
\nA: It’s tricky to get hold of non-Google website owners that would p
rovide rationale. Those that wanted to talk about it were likely to have t
hought about providing rationale anyway. \n\n*Q: if you require user inter
action to trigger the prompt what would happen? Do we care if we break pag
es because of that?* \nA: This is more a business question than a researc
h question. Browsers would need to answer that for themselves. Developers
can actually query the permission state. So there’s a way for developers
to check before prompting.\n\n*Q: Prompt fatigue: is that influencing beh
avior when dealing with the prompt?* \nA: At the median\, individuals on
Chrome see approx. 1 prompt per 2 weeks. People make fast decisions based
on habituation. Fatigue comes through qualitatively though and we do try
to avoid additional prompts. \n\n*Q: Cookie banners: users don’t differe
ntiate between actual permission prompts and cookie banners. So they add t
o fatigue. Any research related to that?* \nA: No specific research on ou
r end\, but we see study participants confuse cookie banners for permissio
n prompts.\n\n*Q: How many prompts users see is influenced by Chrome remem
bering the permission state\, this is not the same behavior for Safari. So
it feels like assumed user fatigue is more of a Chrome thing than generic
across browsers.* \nA: Agreed. We are rolling out one time permissions w
hich will change that\, but no concrete data to be shared yet.\n\n*Comment
: If we think about the people who commission websites\, they want to know
where the customers are and send them stuff. Not at all surprising that w
e have so much more notifications and location prompts.*\n\n*Q: Is there a
way for websites to know they’re getting into the quieting zone of Chro
me’s intervention?* \nA: You can look in CrUX to see your rank\, but th
ere’s not a direct way to know beyond that.\n\n*Q: Safari requires user
activation for Notifications. It’s great that Chrome and Firefox also do
this. We should start doing something about geolocation as well.* \nA:
Next session has more on notification spam and proposes some solutions.\n\
n*Q: Is there a presentation issue around users being told that the prompt
is quieted? Can we reframe it to sound more positive\, e.g. this is a new
way of doing prompting?* \n*A: That sounds interesting and worth explori
ng. We did attempt to change the string in the chip to say “Get Notifica
tions?” and that did not have substantial effects\, though.*\n\n*Q: Did
website devs complain about Chrome changing behavior?* \nA: Some\, but w
e tend to answer with “If you do the right thing you shouldn’t need to
worry about it.” But yes\, developers want predictability.\n\n**Goal(s)
:**\nShare user research findings on permissions\, discuss best practices
and ideas\n\n**Track(s):**\n- Permissions\n\nAgenda\n\n**Materials:**\n- [
slides](https://www.w3.org/2024/Talks/TPAC/breakouts/user-permissions-rese
arch.pdf)\n- [Session proposal on GitHub](https://github.com/w3c/tpac2024-
breakouts/issues/8)
STATUS:CONFIRMED
CREATED:20240916T214722Z
LAST-MODIFIED:20260317T123419Z
SEQUENCE:4
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - Oceanside
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:3fd46d95-d472-4d8a-9287-ed21ea719aa4
DTSTAMP:20260317T123541Z
SUMMARY:Web and Generative AI risks
DTSTART;TZID=America/Los_Angeles:20240925T083000
DTEND;TZID=America/Los_Angeles:20240925T093000
DESCRIPTION:https://www.w3.org/events/meetings/3fd46d95-d472-4d8a-9287-ed21
ea719aa4/\n\nGenerative Artificial Intelligence (AI) is a type of AI based
on techniques and generative models that aim to generate new content\, an
d its performance in knowledge learning\, inductive summarization\, conten
t creation\, perception and cognition is distinctly different from previou
s AI technologies. Now\, Web is fraught with AI-generated information.\nTh
ere are several new features of generative AI\, such as new contents gener
ation\, long context windows\, etc\,. At the same time\, generative AI bri
ngs new risks\, such as hallucination\, privacy leakage\, copyrights infri
ngement.\nThis session will introduce the new features and new risks broug
ht by generative AI compared with traditional AI. And the session will hav
e an open discussion about the risks related to Web and W3C can do on Web
standards to address the risks.\n\n**Goal(s):**\nDiscuss the risks of Gene
rative AI and what W3C can do to address the risks.\n\n**Track(s):**\n- AI
\n\nAgenda\n\n1. Introduction of generative AI and its potential risks \n2
. Open discussion\n\n**Materials:**\n- [slides](https://www.w3.org/2024/Ta
lks/TPAC/breakouts/generative-ai-risks.pdf)\n- [Session proposal on GitHub
](https://github.com/w3c/tpac2024-breakouts/issues/36)
STATUS:CONFIRMED
CREATED:20240916T215204Z
LAST-MODIFIED:20260317T123541Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:2 Ballroom Level - California A
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:efb8564e-dd12-4330-9f0f-029e08516f9d
DTSTAMP:20260317T123732Z
SUMMARY:Web Standards Beyond The Browser
DTSTART;TZID=America/Los_Angeles:20240925T083000
DTEND;TZID=America/Los_Angeles:20240925T093000
DESCRIPTION:https://www.w3.org/events/meetings/efb8564e-dd12-4330-9f0f-029e
08516f9d/\n\nThis breakout session aims to bring together communities and
working groups that focus on web standards beyond the traditional browser
environment. While much of the web's development has centered around brows
ers\, there are many other environments\, such as WebViews\, JavaScript ru
ntimes\, and EPUB readers\, where web standards play a critical role. This
session will explore how these different groups can collaborate to enhanc
e user perception and promote their environments in broader web standards
development.\n\n**Goal(s):**\nCollaboration between groups to discuss chal
lenges and identify areas where these environments can more effectively co
nnect with web standards development efforts.\n\n**Track(s):**\n- Feature
lifecycle\n\nAgenda\n\n* Introduction & Admin (5 min)\n* Roll call: Who is
here and what environments are we looking at? (15 min)\n* Open discussion
on discussion points (30 min)\n* Close up with minutes\, follow up items\
, results etc. (10 min)\n\n#### Session Objectives:\n\n- Foster collabora
tion between groups working on standards for non-traditional web environme
nts.\n- Discuss challenges and opportunities in promoting these environme
nts to both users and developers.\n- Explore potential synergies and shar
ed goals across different projects like WebViews\, JavaScript runtimes\, a
nd EPUB.\n- Identify areas where these environments can more effectively
align with mainstream web standards development efforts.\n\n\n#### Discuss
ion Points:\n\n- What unique challenges do environments like WebViews\, J
avaScript runtimes\, and EPUB face in relation to web standards?\n- How c
an we better communicate the role of these environments in the web ecosyst
em to users and developers?\n- What areas of collaboration between these
groups can enhance user experiences and drive further adoption of web tech
nologies?\n- How can we promote these non-traditional environments within
W3C and other standards bodies?\n\n**Materials:**\n- [Session proposal on
GitHub](https://github.com/w3c/tpac2024-breakouts/issues/69)
STATUS:CONFIRMED
CREATED:20240916T215811Z
LAST-MODIFIED:20260317T123732Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:-1 Lower Level - Catalina 1
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:6e17e78b-8cdd-4013-af65-4b98f2c905c8
DTSTAMP:20241002T122501Z
SUMMARY:Assistive Technology Interop through ARIA-AT
DTSTART;TZID=America/Los_Angeles:20240925T100000
DTEND;TZID=America/Los_Angeles:20240925T110000
DESCRIPTION:https://www.w3.org/events/meetings/6e17e78b-8cdd-4013-af65-4b98
f2c905c8/\n\nWe'll step through and demo the purpose built software we use
to collect AT output\, build consensus on verdicts\, and run those verdic
ts through automated regression tests with real ATs.\n\nAgenda\n\n**Chairs
:**\nBoaz Sender\, Chris Cuellar\n\n**Description:**\nWe'll step through a
nd demo the purpose built software we use to collect AT output\, build con
sensus on verdicts\, and run those verdicts through automated regression t
ests with real ATs.\n\n**Goal(s):**\nShare our work\, tools\, and progress
toward AT Interop\n\n\n**Agenda:**\nStill working on this.\n\n**Materials
:**\n- [minutes](https://www.w3.org/2024/09/25-aria-at-minutes.html)\n- [S
ession proposal on GitHub](https://github.com/w3c/tpac2024-breakouts/issue
s/83)
STATUS:CONFIRMED
CREATED:20240916T220117Z
LAST-MODIFIED:20241002T122501Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - Palos Verdes
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:6833d83a-78de-49e2-8ec3-2465a944f409
DTSTAMP:20241009T210448Z
SUMMARY:Community Group Program Enhancements
DTSTART;TZID=America/Los_Angeles:20240925T100000
DTEND;TZID=America/Los_Angeles:20240925T110000
DESCRIPTION:https://www.w3.org/events/meetings/6833d83a-78de-49e2-8ec3-2465
a944f409/\n\nAfter 12 years of Community Group operations and many discuss
ions about their role in Specification incubation\, the Staff are working
on greater alignment of the Community Group program with the W3C mission.
We are planning enhancements to address a small number of situations of co
ncern for those CGs that publish Specifications. (As a reminder\, CG Speci
fications are the subset of CG Reports that are subject to the CLA and FSA
.) CG Specifications that gain traction outside of the guarantees provided
by standardization processes risk weakening the W3C mission\; through the
se CG program enhancements we seek to reduce that risk.\n\nDuring this bre
akout\, we will discuss the situations of concern that are motivating this
work\, share initial ideas to address them\, and recruit early testers an
d adopters of these enhancements.\n\nAfter TPAC we will continue this work
in the [Community Council](https://github.com/w3c/cg-council).\n\nAgenda\
n\n**Chairs:**\nIan Jacobs\, Dominique Hazaël-Massieux\n\n**Description:*
*\nAfter 12 years of Community Group operations and many discussions about
their role in Specification incubation\, the Staff are working on greater
alignment of the Community Group program with the W3C mission. We are pla
nning enhancements to address a small number of situations of concern for
those CGs that publish Specifications. (As a reminder\, CG Specifications
are the subset of CG Reports that are subject to the CLA and FSA.) CG Spec
ifications that gain traction outside of the guarantees provided by standa
rdization processes risk weakening the W3C mission\; through these CG prog
ram enhancements we seek to reduce that risk.\n\nDuring this breakout\, we
will discuss the situations of concern that are motivating this work\, sh
are initial ideas to address them\, and recruit early testers and adopters
of these enhancements.\n\nAfter TPAC we will continue this work in the [C
ommunity Council](https://github.com/w3c/cg-council).\n\n**Goal(s):**\nRai
se awareness and generate interest in potential enhancements to the CG pro
gram.\n\n\n**Agenda:**\n* [Slides](https://www.w3.org/2024/Talks/TPAC/cg-b
reakout/)\n\n**Materials:**\n- [minutes](https://www.w3.org/2024/09/25-cg-
revamp-minutes.html)\n- [Session proposal on GitHub](https://github.com/w3
c/tpac2024-breakouts/issues/63)
STATUS:CONFIRMED
CREATED:20240916T215712Z
LAST-MODIFIED:20241009T210448Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - Huntington
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:6938e480-554a-4461-9b2a-ec07853a9d20
DTSTAMP:20241016T205139Z
SUMMARY:Device Bound Session Credentials
DTSTART;TZID=America/Los_Angeles:20240925T100000
DTEND;TZID=America/Los_Angeles:20240925T110000
DESCRIPTION:https://www.w3.org/events/meetings/6938e480-554a-4461-9b2a-ec07
853a9d20/\n\n[Device Bound Session Credentials (DBSC)](https://github.com/
WICG/dbsc/blob/main/README.md) aims to enhance protection against web sess
ion theft by using a secure session that is bound to the device between th
e browser and web application. This session will provide a breakdown of th
e general attack vector of cookie theft that it is aiming to disrupt\, an
overview of the proposed DBSC web standard and host an open discussion abo
ut the web standard to gather any feedback or suggestions by the community
. The session also covers an addition to the standard layered on DBSC\, ca
lled the DBSC(E). DBSC(E) aims to provide session protection from malware
for enterprise use cases against web session theft as an opt in.\n\nAgenda
\n\n**Chairs:**\nBenjamin Ackerman\, Kristian Monsen\, Arnar Birgisson\, A
leksandr Tokarev\, Sameera Gajjarapu\n\n**Description:**\n[Device Bound Se
ssion Credentials (DBSC)](https://github.com/WICG/dbsc/blob/main/README.md
) aims to enhance protection against web session theft by using a secure s
ession that is bound to the device between the browser and web application
. This session will provide a breakdown of the general attack vector of co
okie theft that it is aiming to disrupt\, an overview of the proposed DBSC
web standard and host an open discussion about the web standard to gather
any feedback or suggestions by the community. The session also covers an
addition to the standard layered on DBSC\, called the DBSC(E). DBSC(E) aim
s to provide session protection from malware for enterprise use cases agai
nst web session theft as an opt in.\n\n**Goal(s):**\nPresent the DBSC and
DBSC(E) API and protocol proposed for standardization and have an open dis
cussion about any of the various components that are of interest.\n\n\n\n*
*Materials:**\n- [dbsc breakout intro slides](https://www.w3.org/2024/Talk
s/TPAC/breakouts/dbsc-intro.pdf)\n- [dbsc slides](https://www.w3.org/2024/
Talks/TPAC/breakouts/DBSC.pdf)\n- [dbsc-e slides](https://www.w3.org/2024/
Talks/TPAC/DBSC_e_/)\n- [minutes](https://pad.w3.org/p/dbsc)\n- [Session p
roposal on GitHub](https://github.com/w3c/tpac2024-breakouts/issues/16)
STATUS:CONFIRMED
CREATED:20240916T214900Z
LAST-MODIFIED:20241016T205139Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - Capistrano
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:2385bfd8-9851-4a53-877a-9961f64a60db
DTSTAMP:20241002T122458Z
SUMMARY:DID Method Standardization
DTSTART;TZID=America/Los_Angeles:20240925T100000
DTEND;TZID=America/Los_Angeles:20240925T110000
DESCRIPTION:https://www.w3.org/events/meetings/2385bfd8-9851-4a53-877a-9961
f64a60db/\n\nStandardizing Decentralized Identifier (DID) Methods is impor
tant to progress W3C's foundational work on global identifiers that are no
t leased\, but owned by individuals. This session will discuss a proposed
W3C charter for web-based DID methods. We will also cover key categories o
f DID methods that have proven broadly useful\, including self-resolvable\
, web-based\, and decentralized methods. The goal is to standardize a few
methods that are in production within these categories\, ensuring they mee
t the needs of diverse use cases. To achieve this\, the group will establi
sh strong collaboration and liaison agreements among key organizations out
side of W3C\, minimizing barriers to participation and fostering a coopera
tive environment. Additionally\, the effort will engage the broader commun
ity of DID builders\, innovators\, and adopters\, inviting them to contrib
ute to a detailed roadmap that guides the future of DID standardization.\n
\nAgenda\n\n**Chairs:**\nMandy Venables\, Manu Sporny\, Gabe Cohen\, Kim D
uffy\n\n**Description:**\nStandardizing Decentralized Identifier (DID) Met
hods is important to progress W3C's foundational work on global identifier
s that are not leased\, but owned by individuals. This session will discus
s a proposed W3C charter for web-based DID methods. We will also cover key
categories of DID methods that have proven broadly useful\, including sel
f-resolvable\, web-based\, and decentralized methods. The goal is to stand
ardize a few methods that are in production within these categories\, ensu
ring they meet the needs of diverse use cases. To achieve this\, the group
will establish strong collaboration and liaison agreements among key orga
nizations outside of W3C\, minimizing barriers to participation and foster
ing a cooperative environment. Additionally\, the effort will engage the b
roader community of DID builders\, innovators\, and adopters\, inviting th
em to contribute to a detailed roadmap that guides the future of DID stand
ardization.\n\n**Goal(s):**\nInform members on the new DID Methods Working
Group charter.\n\n\n\n**Materials:**\n- [minutes](https://www.w3.org/2024
/09/25-did-methods-minutes.html)\n- [Session proposal on GitHub](https://g
ithub.com/w3c/tpac2024-breakouts/issues/38)\n\n**Track(s):**\n- Identity
STATUS:CONFIRMED
CREATED:20240916T215228Z
LAST-MODIFIED:20241002T122458Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - Manhattan
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:4d8d2b34-5643-461d-8ed6-bf1d53e5ed10
DTSTAMP:20240925T171135Z
SUMMARY:Lessons learned by an independent implementation of the Digital Ide
ntity Wallet in Europe
DTSTART;TZID=America/Los_Angeles:20240925T100000
DTEND;TZID=America/Los_Angeles:20240925T110000
DESCRIPTION:https://www.w3.org/events/meetings/4d8d2b34-5643-461d-8ed6-bf1d
53e5ed10/\n\nI'll introduce challenges and pitfalls emerging while impleme
nting the digital identity wallet in Europe (EUDI ARF).\n\nOur team has **
independently** implemented the EUDI ARF specification and released all co
de free open-source\, a beta demo is also available as an online applicati
on at [didroom](https://didroom.com).\n\nThis was a journey through some s
hocking revelations and frustrations shared by other large-scale pilots in
Europe\, so I'll do my best to extract critical insights that can guide o
ther digital identity initiatives and avoid similar setbacks in the future
.\n\nAgenda\n\n**Chairs:**\nDenis Roio\, Andrea D'Intino\n\n**Description:
**\nI'll introduce challenges and pitfalls emerging while implementing the
digital identity wallet in Europe (EUDI ARF).\n\nOur team has **independe
ntly** implemented the EUDI ARF specification and released all code free o
pen-source\, a beta demo is also available as an online application at [di
droom](https://didroom.com).\n\nThis was a journey through some shocking r
evelations and frustrations shared by other large-scale pilots in Europe\,
so I'll do my best to extract critical insights that can guide other digi
tal identity initiatives and avoid similar setbacks in the future.\n\n**Go
al(s):**\nShare a critical perspective on EUDI ARF based on facts\n\n\n**A
genda:**\n- Quick overview of EUDI ARF\n- critical responses\n- wrong secu
rity assumptions\n- wrong privacy assumptions\n- viable alternatives we se
e\n- Q&A\n\n**Materials:**\n- [Session proposal on GitHub](https://github.
com/w3c/tpac2024-breakouts/issues/73)\n\n**Track(s):**\n- Wallets
STATUS:CONFIRMED
CREATED:20240916T215912Z
LAST-MODIFIED:20240925T171135Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:-1 Lower Level - Catalina 5
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:2912dccd-bd4d-4671-b63f-c045c7a1703a
DTSTAMP:20241106T183245Z
SUMMARY:Page Embedded Permission Control (PEPC): Safely embedding permissio
n entry points in web content
DTSTART;TZID=America/Los_Angeles:20240925T100000
DTEND;TZID=America/Los_Angeles:20240925T110000
DESCRIPTION:https://www.w3.org/events/meetings/2912dccd-bd4d-4671-b63f-c045
c7a1703a/\n\nThis breakout will continue past discussions of the Page Embe
dded Permission Control ([PEPC](https://github.com/WICG/PEPC)). We will di
scuss safe\, consistent mechanisms for web developers to link into browser
UI surfaces\, starting with permissions. Other examples of browser contro
ls which could be embedded include content settings\, a PWA install trigge
r\, an installed app management surface\, federated login\, autofill or ot
her browser settings. To date discussion has focused on the permissions us
e case\, and while we would like to continue this discussion we believe th
e concept could be applicable to other use cases. \n\nAs web apps grow mor
e sophisticated\, rivaling native apps in capability and complexity\, user
s can become confused as to how to access important settings that affect t
heir ability to use apps. For example\, in addition to origin scoped Permi
ssions\, PWAs can have application settings scoped to the application. \n\
nWebsites can try to help users by providing guided instructions into brow
ser UI surfaces but (1) this normalizes a safety anti-pattern and should n
ot be encouraged even in legitimate sites as malicious websites are excell
ent at deceiving users into making unsafe changes to their settings\, (2)
instructions are inconvenient for the user\, difficult to maintain for dev
elopers and frequently fail to help and (3) these types of instructions pr
esent extra challenges for accessibility. \n\nThis session will continue t
he dialog on providing in page access to permission settings\, including i
mplications for the underlying browser permission model\, while expanding
the discussion to include problem spaces beyond permissions. We will prese
nt preliminary usage data and developer feedback from the PEPC prototype f
or permissions as context for conversation.\n\nAgenda: https://www.w3.org/
2024/Talks/TPAC/breakouts/pepc.pdf\n\nAgenda\n\n**Chairs:**\nPenelope McLa
chlan\, Andy Paicu\, Serena Chen\, Marian Harbach\, Balazs Engedy\n\n**Des
cription:**\nThis breakout will continue past discussions of the Page Embe
dded Permission Control ([PEPC](https://github.com/WICG/PEPC)). We will di
scuss safe\, consistent mechanisms for web developers to link into browser
UI surfaces\, starting with permissions. Other examples of browser contro
ls which could be embedded include content settings\, a PWA install trigge
r\, an installed app management surface\, federated login\, autofill or ot
her browser settings. To date discussion has focused on the permissions us
e case\, and while we would like to continue this discussion we believe th
e concept could be applicable to other use cases. \n\nAs web apps grow mor
e sophisticated\, rivaling native apps in capability and complexity\, user
s can become confused as to how to access important settings that affect t
heir ability to use apps. For example\, in addition to origin scoped Permi
ssions\, PWAs can have application settings scoped to the application. \n\
nWebsites can try to help users by providing guided instructions into brow
ser UI surfaces but (1) this normalizes a safety anti-pattern and should n
ot be encouraged even in legitimate sites as malicious websites are excell
ent at deceiving users into making unsafe changes to their settings\, (2)
instructions are inconvenient for the user\, difficult to maintain for dev
elopers and frequently fail to help and (3) these types of instructions pr
esent extra challenges for accessibility. \n\nThis session will continue t
he dialog on providing in page access to permission settings\, including i
mplications for the underlying browser permission model\, while expanding
the discussion to include problem spaces beyond permissions. We will prese
nt preliminary usage data and developer feedback from the PEPC prototype f
or permissions as context for conversation.\n\n**Goal(s):**\nGather commun
ity feedback on the use cases and requirements for a general solution to p
roviding safe entry points into browser UI surfaces from web content while
laying out an incremental roadmap. Discuss whether (1) the problem space
warrants solutions\, (2) the requirements of a solution\, (3) how the PEPC
as prototyped stacks up against requirements\, (4) alternative ways the r
equirements could be addressed.\n\n\n\n**Materials:**\n- [slides](https://
www.w3.org/2024/Talks/TPAC/breakouts/pepc.pdf)\n- [minutes](https://www.w3
.org/2024/09/breakouts/minutes-18.html)\n- [minutes (initial google doc)](
https://docs.google.com/document/d/1LR0OjpNRdZCkt6AcZZgflRJeJbGTyTPS5aTUYk
7iYk8/edit#heading=h.icqdtkv1satn)\n- [Session proposal on GitHub](https:/
/github.com/w3c/tpac2024-breakouts/issues/18)\n\n**Track(s):**\n- Permissi
ons
STATUS:CONFIRMED
CREATED:20240916T214931Z
LAST-MODIFIED:20241106T183245Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - Oceanside
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:71701032-4e1f-463a-b875-f6608345645a
DTSTAMP:20241016T223346Z
SUMMARY:RtpTransport
DTSTART;TZID=America/Los_Angeles:20240925T100000
DTEND;TZID=America/Los_Angeles:20240925T110000
DESCRIPTION:https://www.w3.org/events/meetings/71701032-4e1f-463a-b875-f660
8345645a/\n\nWhile [WebCodecs ](https://w3c.github.io/webcodecs/ )provides
low-level access to the browser's native encoders and decoders\, today th
ere is no API to transport media peer-to-peer using the Real-time Transpor
t Protocol ([RTP](https://en.wikipedia.org/wiki/Real-time_Transport_Protoc
ol))\, defined in [RFC 3550](https://www.rfc-editor.org/rfc/rfc3550).\n\nT
he goal of the [RtpTransport API](https://github.com/w3c/webrtc-rtptranspo
rt) is to enable applications to utilize peer-to-peer RTP transport\, as w
ell as to send and respond to feedback using the Real-time Control Protoco
l (RTCP).\n\nThe following use cases are being developed:\n\n- [Use case 1
: Custom Packetization](https://github.com/w3c/webrtc-rtptransport/blob/ma
in/explainer-use-case-1.md)\n- [Use case 2: Custom Congestion Control](htt
ps://github.com/w3c/webrtc-rtptransport/blob/main/explainer-use-case-2.md)
\n- [Use case 3: Custom NACK/RTX](https://github.com/w3c/webrtc-rtptransp
ort/blob/main/explainer-use-case-3.md)\n\nSee:\n- [GitHub repo](https://gi
thub.com/w3c/webrtc-rtptransport).\n- [Specification](https://w3c.github.i
o/webrtc-rtptransport/)\n\nAgenda\n\n**Chairs:**\nBernard Aboba\, Peter Th
atcher\, Erik Språng\n\n**Description:**\nWhile [WebCodecs ](https://w3c.
github.io/webcodecs/ )provides low-level access to the browser's native en
coders and decoders\, today there is no API to transport media peer-to-pee
r using the Real-time Transport Protocol ([RTP](https://en.wikipedia.org/w
iki/Real-time_Transport_Protocol))\, defined in [RFC 3550](https://www.rfc
-editor.org/rfc/rfc3550).\n\nThe goal of the [RtpTransport API](https://gi
thub.com/w3c/webrtc-rtptransport) is to enable applications to utilize pee
r-to-peer RTP transport\, as well as to send and respond to feedback using
the Real-time Control Protocol (RTCP).\n\nThe following use cases are bei
ng developed:\n\n- [Use case 1: Custom Packetization](https://github.com/w
3c/webrtc-rtptransport/blob/main/explainer-use-case-1.md)\n- [Use case 2:
Custom Congestion Control](https://github.com/w3c/webrtc-rtptransport/blob
/main/explainer-use-case-2.md) \n- [Use case 3: Custom NACK/RTX](https://g
ithub.com/w3c/webrtc-rtptransport/blob/main/explainer-use-case-3.md)\n\nSe
e:\n- [GitHub repo](https://github.com/w3c/webrtc-rtptransport).\n- [Speci
fication](https://w3c.github.io/webrtc-rtptransport/)\n\n**Goal(s):**\nTo
describe the goals of the RtpTransport API\, and to solicit feedback on de
veloper needs and use cases.\n\n\n**Agenda:**\n1. Introduction to the RtpT
ransport API.\n2. Use cases.\n3. Developer feedback.\n\n**Materials:**\n-
[slides](https://www.w3.org/2024/Talks/TPAC/breakouts/rtp-transport.pdf)\n
- [minutes](https://www.w3.org/2024/09/25-rtp-transport-minutes.html)\n- [
Session proposal on GitHub](https://github.com/w3c/tpac2024-breakouts/issu
es/13)\n\n**Track(s):**\n- Real-time Web
STATUS:CONFIRMED
CREATED:20240916T214822Z
LAST-MODIFIED:20241016T223346Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:-1 Lower Level - Catalina 2
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:581da55d-ab33-40a4-8e92-9e571e5b7950
DTSTAMP:20241002T122448Z
SUMMARY:Scoped custom element registry
DTSTART;TZID=America/Los_Angeles:20240925T100000
DTEND;TZID=America/Los_Angeles:20240925T110000
DESCRIPTION:https://www.w3.org/events/meetings/581da55d-ab33-40a4-8e92-9e57
1e5b7950/\n\nSession to discuss scoped custom element registry\n\nAgenda\n
\n**Chairs:**\nRyosuke Niwa\n\n**Description:**\nSession to discuss scoped
custom element registry\n\n**Goal(s):**\nCome up with MVP for scoped cust
om element registry\n\n\n\n**Materials:**\n- [minutes](https://www.w3.org/
2024/09/25-webcomponents-minutes.html)\n- [Session proposal on GitHub](htt
ps://github.com/w3c/tpac2024-breakouts/issues/26)\n\n**Track(s):**\n- Web
Components
STATUS:CONFIRMED
CREATED:20240916T215032Z
LAST-MODIFIED:20241002T122448Z
SEQUENCE:8
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:-1 Lower Level - Catalina 3
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:a12ba322-bd22-44aa-a649-213b51f45330
DTSTAMP:20241002T122510Z
SUMMARY:Sourcemaps\, Security\, devices\, & more: What you may have missed
from TC39 & Ecma
DTSTART;TZID=America/Los_Angeles:20240925T100000
DTEND;TZID=America/Los_Angeles:20240925T110000
DESCRIPTION:https://www.w3.org/events/meetings/a12ba322-bd22-44aa-a649-213b
51f45330/\n\nLots of people who are tuned into internet-relevant standards
know about TC39\, the technical committee within Ecma International that
specifies ECMAScript® (JavaScript™). What you may not know is that TC39
is broken up into 5 _Task Groups_\, only one of which is responsible for
the core standard\, ECMA-262. Ecma is also home to TC53\, another technica
l committee focussed on ECMAScript® in embedded systems. Join me to hear
about the rest of Ecma’s work on ECMAScript: Internationalization\, Secu
rity\, Sourcemaps\, Experiments in programming language standardization\,
and ECMAScript® modules for embedded systems.\n\nAgenda\n\n**Chairs:**\nA
ki Braun\n\n**Description:**\nLots of people who are tuned into internet-r
elevant standards know about TC39\, the technical committee within Ecma In
ternational that specifies ECMAScript® (JavaScript™). What you may not
know is that TC39 is broken up into 5 _Task Groups_\, only one of which is
responsible for the core standard\, ECMA-262. Ecma is also home to TC53\,
another technical committee focussed on ECMAScript® in embedded systems.
Join me to hear about the rest of Ecma’s work on ECMAScript: Internatio
nalization\, Security\, Sourcemaps\, Experiments in programming language s
tandardization\, and ECMAScript® modules for embedded systems.\n\n**Goal(
s):**\nSpread knowledge of JavaScript outside of the Web APIs\, identify a
reas where Ecma & W3C could be working together.\n\n\n**Agenda:**\n- [TC39
TG1](https://ecma-international.org/task-groups/tc39-tg1/) (briefly)\n- [
TC39 TG2](https://ecma-international.org/task-groups/tc39-tg2/)\n- [TC39 T
G3](https://ecma-international.org/task-groups/tc39-tg3/)\n- [TC39 TG4](ht
tps://ecma-international.org/task-groups/tc39-tg4/)\n- [TC39 TG5](https://
ecma-international.org/task-groups/tc39-tg5/)\n- [TC53](https://ecma-inter
national.org/technical-committees/tc53/)\n\n**Materials:**\n- [minutes](ht
tps://www.w3.org/2024/09/25-ecmascript-minutes.html)\n- [Session proposal
on GitHub](https://github.com/w3c/tpac2024-breakouts/issues/85)
STATUS:CONFIRMED
CREATED:20240916T220135Z
LAST-MODIFIED:20241002T122510Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - Laguna
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:c7122995-e333-461d-81a5-eb16b5a98d64
DTSTAMP:20241106T183419Z
SUMMARY:System Tray Icon Support for PWAs
DTSTART;TZID=America/Los_Angeles:20240925T100000
DTEND;TZID=America/Los_Angeles:20240925T110000
DESCRIPTION:https://www.w3.org/events/meetings/c7122995-e333-461d-81a5-eb16
b5a98d64/\n\nIn this session we want to discuss the scope of having an ins
talled PWA close to a system tray icon. What does this behavior mean in di
fferent platforms and what is the minimum functionality that needs to be s
upported to bridge the gap with platform-specific (Windows/macOS/Linux) co
unterparts.\n\nAgenda\n\n**Chairs:**\nDiego Gonzalez-Zuniga\n\n**Descripti
on:**\nIn this session we want to discuss the scope of having an installed
PWA close to a system tray icon. What does this behavior mean in differen
t platforms and what is the minimum functionality that needs to be support
ed to bridge the gap with platform-specific (Windows/macOS/Linux) counterp
arts.\n\n**Goal(s):**\nTo scope the feature based on feedback from partici
pants.\n\n\n\n**Materials:**\n- [slides](https://docs.google.com/presentat
ion/d/1H_NxBw1l-1_nORtIdn5yFOiYG59eaVVkcm8T_yLE-Zc/edit?usp=sharing)\n- [m
inutes](https://www.w3.org/2024/09/breakouts/minutes-41.html)\n- [minutes
(initial google doc)](https://docs.google.com/document/d/1AHXt83vSMmUBCbRF
s5tfHVnrSvvOy28_osm1hlSd4bM/edit?usp=sharing)\n- [Session proposal on GitH
ub](https://github.com/w3c/tpac2024-breakouts/issues/41)\n\n**Track(s):**\
n- Web Apps
STATUS:CONFIRMED
CREATED:20240916T215255Z
LAST-MODIFIED:20241106T183419Z
SEQUENCE:2
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
BEGIN:VEVENT
UID:d7345d9c-5423-42db-9b76-e0c373b5a9a1
DTSTAMP:20241106T183354Z
SUMMARY:The Future of Popups!
DTSTART;TZID=America/Los_Angeles:20240925T100000
DTEND;TZID=America/Los_Angeles:20240925T110000
DESCRIPTION:https://www.w3.org/events/meetings/d7345d9c-5423-42db-9b76-e0c3
73b5a9a1/\n\nPopups are a (mostly) desktop-only UI concept critical to man
y existing flows (e.g.\, payments and login). If popups had to be invented
today\, what would they look like? What privacy and security concerns cou
ld be addressed? What UI would exist on mobile? Consider this and other qu
estions as we examine the [Partitioned Popins](https://explainers-by-googl
ers.github.io/partitioned-popins/) proposal!\n\nAgenda\n\n**Chairs:**\nAri
Chivukula\, Johann Hofmann\n\n**Description:**\nPopups are a (mostly) des
ktop-only UI concept critical to many existing flows (e.g.\, payments and
login). If popups had to be invented today\, what would they look like? Wh
at privacy and security concerns could be addressed? What UI would exist o
n mobile? Consider this and other questions as we examine the [Partitioned
Popins](https://explainers-by-googlers.github.io/partitioned-popins/) pro
posal!\n\n**Goal(s):**\nConsider the Partitioned Popins proposal\, and re-
think popups as well know them!\n\n\n**Agenda:**\n[Slides](https://www.w3.
org/2024/Talks/TPAC/breakouts/future-of-popups.pdf)\n\n\n\n**Materials:**\n- [slides](https://www.w3.org/202
4/Talks/TPAC/breakouts/future-of-popups.pdf)\n- [minutes](https://www.w3.o
rg/2024/09/breakouts/minutes-32.html)\n- [minutes (initial google doc)](ht
tps://docs.google.com/document/d/1zN5MVAotlb2lglPtyphWcd2N6SdWbrye6Y7NhmKN
BVw/edit)\n- [Session proposal on GitHub](https://github.com/w3c/tpac2024-
breakouts/issues/32)\n\n**Track(s):**\n- UX
STATUS:CONFIRMED
CREATED:20240916T215113Z
LAST-MODIFIED:20241106T183354Z
SEQUENCE:4
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - San Clemente
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:19f87be5-b119-47dc-87a1-59514bd929fa
DTSTAMP:20241002T122510Z
SUMMARY:The Future of TAG Reviews & Other Output
DTSTART;TZID=America/Los_Angeles:20240925T100000
DTEND;TZID=America/Los_Angeles:20240925T110000
DESCRIPTION:https://www.w3.org/events/meetings/19f87be5-b119-47dc-87a1-5951
4bd929fa/\n\nSince 2013\, the TAG has been systematically reviewing new we
b features as they are being designed and specified. We’ve called this p
rocess “Design Review”. Right now\, the majority of the TAG’s time a
nd effort is spent on design reviews\, with the remainder of our time focu
sing on "other" outputs\, such as updates to the [Design Principles](https
://www.w3.org/TR/design-principles/)\, [Security & Privacy Self-Review Que
stionnaire](https://w3ctag.github.io/security-questionnaire/)\, newer docu
ments such as the [Privacy Principles](https://www.w3.org/TR/privacy-princ
iples/)\, and [BF Cache Guide](https://w3ctag.github.io/bfcache-guide/)\,
as well as [one-off "findings."](https://www.w3.org/2001/tag/doc/web-witho
ut-3p-cookies/)\n\nThe design review issue queue is what drives most of ou
r meeting agendas. Insights that come out of design reviews also inform an
d prioritize the work we do on these other documents that the TAG publishe
s. The TAG has a backlog of design reviews\, and its feedback in those rev
iews has sometimes been too late to have an effect on the development of t
he reviewed spec. This has caused some frustration both on the part of the
people filing these reviews and in the TAG. We need to find a way to focu
s and prioritize our work on the issues where it's most needed - where it
can have the greatest benefit to the web. This session is intended to gath
er community ideas on the best ways to do that.\n\nThis session is to gath
er feedback from the W3C community. Is it clear how the TAG design review
process works? Is it working for you? Have you filed TAG reviews and been
frustrated with the results? Have you filed TAG reviews and been delighted
with the results? Are we balancing correctly between design reviews and o
ther output? We’d like to “check the temperature” to ensure what we
’re doing is useful to the community and we’d also love your feedback
about what we could be doing better? Help us help you.\n\nAgenda\n\n**Chai
rs:**\nDaniel Appelquist\, Lea Verou\n\n**Description:**\nSince 2013\, the
TAG has been systematically reviewing new web features as they are being
designed and specified. We’ve called this process “Design Review”. R
ight now\, the majority of the TAG’s time and effort is spent on design
reviews\, with the remainder of our time focusing on "other" outputs\, suc
h as updates to the [Design Principles](https://www.w3.org/TR/design-princ
iples/)\, [Security & Privacy Self-Review Questionnaire](https://w3ctag.gi
thub.io/security-questionnaire/)\, newer documents such as the [Privacy Pr
inciples](https://www.w3.org/TR/privacy-principles/)\, and [BF Cache Guide
](https://w3ctag.github.io/bfcache-guide/)\, as well as [one-off "findings
."](https://www.w3.org/2001/tag/doc/web-without-3p-cookies/)\n\nThe design
review issue queue is what drives most of our meeting agendas. Insights t
hat come out of design reviews also inform and prioritize the work we do o
n these other documents that the TAG publishes. The TAG has a backlog of d
esign reviews\, and its feedback in those reviews has sometimes been too l
ate to have an effect on the development of the reviewed spec. This has ca
used some frustration both on the part of the people filing these reviews
and in the TAG. We need to find a way to focus and prioritize our work on
the issues where it's most needed - where it can have the greatest benefit
to the web. This session is intended to gather community ideas on the bes
t ways to do that.\n\nThis session is to gather feedback from the W3C comm
unity. Is it clear how the TAG design review process works? Is it working
for you? Have you filed TAG reviews and been frustrated with the results?
Have you filed TAG reviews and been delighted with the results? Are we bal
ancing correctly between design reviews and other output? We’d like to
“check the temperature” to ensure what we’re doing is useful to the
community and we’d also love your feedback about what we could be doing
better? Help us help you.\n\n**Goal(s):**\nRefine the plan in https://gith
ub.com/w3ctag/process/issues/36.\n\n\n**Agenda:**\nThe format will be a sh
ort overview of the Design Review process followed by open discussion. Ple
ase note\, we don’t want to use this as a forum to discuss the technical
details of currently open reviews.\n\n**Materials:**\n- [minutes](https:/
/www.w3.org/2024/09/25-future-tag-minutes.html)\n- [Session proposal on Gi
tHub](https://github.com/w3c/tpac2024-breakouts/issues/59)\n\n**Track(s):*
*\n- Standards
STATUS:CONFIRMED
CREATED:20240916T215613Z
LAST-MODIFIED:20241002T122510Z
SEQUENCE:1
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
BEGIN:VEVENT
UID:4dda4ee4-d1a8-4b8c-a7c5-2fc48519a013
DTSTAMP:20241016T205237Z
SUMMARY:Web API for Hybrid AI
DTSTART;TZID=America/Los_Angeles:20240925T100000
DTEND;TZID=America/Los_Angeles:20240925T110000
DESCRIPTION:https://www.w3.org/events/meetings/4dda4ee4-d1a8-4b8c-a7c5-2fc4
8519a013/\n\nWeb apps are increasingly expected to gain access to a langua
ge model. We are proposing Web APIs that allow web developers to directly
access both on-device and cloud-based language models\, and securely share
user data between multiple apps when using these models.\n\nThe following
are the APIs goals:\n\n- Provide web developers with a connection strateg
y for accessing both on-device and cloud-based models. For example\, if no
on-device models are available\, attempt to access cloud-based models. Co
nversely\, if cloud-based models are unavailable\, try accessing on-device
models.\n\n- Provide web developers with a storage strategy for sharing u
ser's private data. For example\, one web app saves users' private data in
to a local vector database. Another web app\, when accessing a on-device l
anguage model\, can leverage this data through a local RAG system.\n\nThe
following are not within our scope of concern:\n\n- Design a uniform JavaS
cript API for accessing browser-provided language models\, known as the [P
rompt API](https://github.com/explainers-by-googlers/prompt-api)\, which i
s currently being explored by Chrome's built-in AI team.\n\n- Issues faced
by hybrid AI\, such as model management\, elasticity through hybrid AI\,
and user experience\, as this topic has already been discussed in [Hybrid
AI Presentations](https://github.com/webmachinelearning/hybrid-ai/tree/mai
n/presentations) in the WebML IG\, and will be covered in the sessions on
[AI Model Management](https://github.com/w3c/tpac2024-breakouts/issues/15)
.\n\nThis session will showcase how to use our proposed API for booking fl
ights and hotels. It will also provide specific implementation details and
references for these APIs. Example source code and implementation referen
ces can be found on GitHub [web-hybrid-ai](https://github.com/kevinmoch/we
b-hybrid-ai).\n\nAgenda\n\n**Chairs:**\nChunhui Mo\, Martin Alvarez-Espina
r\n\n**Description:**\nWeb apps are increasingly expected to gain access t
o a language model. We are proposing Web APIs that allow web developers to
directly access both on-device and cloud-based language models\, and secu
rely share user data between multiple apps when using these models.\n\nThe
following are the APIs goals:\n\n- Provide web developers with a connecti
on strategy for accessing both on-device and cloud-based models. For examp
le\, if no on-device models are available\, attempt to access cloud-based
models. Conversely\, if cloud-based models are unavailable\, try accessing
on-device models.\n\n- Provide web developers with a storage strategy for
sharing user's private data. For example\, one web app saves users' priva
te data into a local vector database. Another web app\, when accessing a o
n-device language model\, can leverage this data through a local RAG syste
m.\n\nThe following are not within our scope of concern:\n\n- Design a uni
form JavaScript API for accessing browser-provided language models\, known
as the [Prompt API](https://github.com/explainers-by-googlers/prompt-api)
\, which is currently being explored by Chrome's built-in AI team.\n\n- Is
sues faced by hybrid AI\, such as model management\, elasticity through hy
brid AI\, and user experience\, as this topic has already been discussed i
n [Hybrid AI Presentations](https://github.com/webmachinelearning/hybrid-a
i/tree/main/presentations) in the WebML IG\, and will be covered in the se
ssions on [AI Model Management](https://github.com/w3c/tpac2024-breakouts/
issues/15).\n\nThis session will showcase how to use our proposed API for
booking flights and hotels. It will also provide specific implementation d
etails and references for these APIs. Example source code and implementati
on references can be found on GitHub [web-hybrid-ai](https://github.com/ke
vinmoch/web-hybrid-ai).\n\n**Goal(s):**\nExplore the potential of our prop
osed Web API for accessing hybrid AI through use case demonstrations and A
PI implementations. Additionally\, discuss concrete steps for moving forwa
rd.\n\n\n**Agenda:**\n1. Introduce the goals of the Web APIs we propose fo
r hybrid AI (2m)\n2. Introduce Connection API (5m)\n3. Introduce Storage A
PI (4m)\n4. A Showcase of Hybrid AI App (3m)\n5. Considerations for Connec
tion Strategy (2m)\n6. Considerations for Storage Strategy (2m)\n7. Consid
erations for Native OS APIs (2m)\n8. Discuss possible resolutions\, follow
up actions and collaborations (20m)\n\n#### Links\n\n* [Web API for Hybrid
AI - Slides](https://kevinmoch.github.io/web-hybrid-ai/)\n* [Web API for
Hybrid AI - Explainer](https://github.com/kevinmoch/web-hybrid-ai)\n\n**Ma
terials:**\n- [slides](https://www.w3.org/2024/Talks/TPAC/breakouts/web-hy
brid-ai/)\n- [minutes](https://www.w3.org/2024/09/25-web-hybrid-ai-minutes
.html)\n- [Session proposal on GitHub](https://github.com/w3c/tpac2024-bre
akouts/issues/44)\n\n**Track(s):**\n- AI
STATUS:CONFIRMED
CREATED:20240916T215330Z
LAST-MODIFIED:20241016T205237Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:2 Ballroom Level - California A
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:49ecab51-dbf7-4351-b2a9-314d169d0b77
DTSTAMP:20241002T122523Z
SUMMARY:Web Features: Building an index for the web platform
DTSTART;TZID=America/Los_Angeles:20240925T100000
DTEND;TZID=America/Los_Angeles:20240925T110000
DESCRIPTION:https://www.w3.org/events/meetings/49ecab51-dbf7-4351-b2a9-314d
169d0b77/\n\n[Web features](https://github.com/web-platform-dx/web-feature
s/) is an initiative of the [WebDX Community Group](https://www.w3.org/com
munity/webdx/)\, to build a list of features on the web platform\, organis
ed in a way that's useful to developers. It is currently used for providin
g "baseline" statuses\, indicating feature availability\, to be presented
on documentation sites such as [MDN](https://developer.mozilla.org/en-US/d
ocs/Glossary/Baseline/Compatibility).\n\nSo far the work has mainly been f
ocused on grouping the already-existing platform APIs into features that c
an be assigned a baseline status. However the purpose of this session is t
o understand the opportunities and requirements to use web-features earlie
r in the proposal lifecycle\, as part of the ongoing standardisation proce
ss. For example\, in a world where standards-positions and intent emails c
onsistently use well-defined feature names\, it may be possibly to build t
ooling that informs developers\, and other interested parties\, about whic
h proposals are just waiting for implementation\, or where there are more
fundamental challenges at the standards level. This data could then be use
d to inform other projects such as Interop.\n\nAgenda\n\n**Chairs:**\nJame
s Graham\n\n**Description:**\n[Web features](https://github.com/web-platfo
rm-dx/web-features/) is an initiative of the [WebDX Community Group](https
://www.w3.org/community/webdx/)\, to build a list of features on the web p
latform\, organised in a way that's useful to developers. It is currently
used for providing "baseline" statuses\, indicating feature availability\,
to be presented on documentation sites such as [MDN](https://developer.mo
zilla.org/en-US/docs/Glossary/Baseline/Compatibility).\n\nSo far the work
has mainly been focused on grouping the already-existing platform APIs int
o features that can be assigned a baseline status. However the purpose of
this session is to understand the opportunities and requirements to use we
b-features earlier in the proposal lifecycle\, as part of the ongoing stan
dardisation process. For example\, in a world where standards-positions an
d intent emails consistently use well-defined feature names\, it may be po
ssibly to build tooling that informs developers\, and other interested par
ties\, about which proposals are just waiting for implementation\, or wher
e there are more fundamental challenges at the standards level. This data
could then be used to inform other projects such as Interop.\n\n**Goal(s):
**\nUnderstand the requirements / challenges of integrating web-features e
arly into the standards development process\n\n\n\n**Materials:**\n- [minu
tes](https://www.w3.org/2024/09/25-webdx-minutes.html)\n- [Session proposa
l on GitHub](https://github.com/w3c/tpac2024-breakouts/issues/99)\n\n**Tra
ck(s):**\n- Feature lifecycle
STATUS:CONFIRMED
CREATED:20240916T220403Z
LAST-MODIFIED:20241002T122523Z
SEQUENCE:5
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:-1 Lower Level - Catalina 1
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:8e1ca708-fdbf-4264-a79b-4c953fa85248
DTSTAMP:20241002T124415Z
SUMMARY:🐞Ladybird: A new\, independent browser engine — written from
scratch
DTSTART;TZID=America/Los_Angeles:20240925T100000
DTEND;TZID=America/Los_Angeles:20240925T110000
DESCRIPTION:https://www.w3.org/events/meetings/8e1ca708-fdbf-4264-a79b-4c95
3fa85248/\n\nAn intro+Q&A for the [Ladybird](https://ladybird.org/) browse
r engine: a completely new engine written from scratch (using no code from
Blink/Chromium\, WebKit/Safari\, Gecko/Firefox\, or any other browser)\,
and backed by the non-profit [Ladybird Browser Initiative](https://ladybir
d.org/) — with a policy to never take funding from default search deal
s or any other forms of user monetization\, ever.\n\nAgenda\n\n**Chairs:**
\nMichael[tm] Smith (sideshowbarker)\, Andrew Kaster\, Jelle Raaijmakers\,
Tim Ledbetter\n\n**Description:**\nAn intro+Q&A for the [Ladybird](https:
//ladybird.org/) browser engine: a completely new engine written from scra
tch (using no code from Blink/Chromium\, WebKit/Safari\, Gecko/Firefox\, o
r any other browser)\, and backed by the non-profit [Ladybird Browser Init
iative](https://ladybird.org/) — with a policy to never take funding f
rom default search deals or any other forms of user monetization\, ever.\n
\n**Goal(s):**\nThe session goal it to give a detailed intro to Ladybird\,
and answer attendees’ questions about it.\n\n\n**Agenda:**\nSome of the
details planned to be covered include:\n\n1. What Ladybird is _not_ (just
to be clear):\n * Not a Blink/Chromium shell.\n * Not a WebKit port.\n
* Not a Firefox fork.\n\n2. What makes Ladybird/[Ladybird Browser Initiat
ive](https://ladybird.org/) different.\n * Fully independent: Written fro
m scratch\, using no code from any other browser engine.\n * Singular foc
us: Doing only one single thing: building a new browser engine and browser
.\n * No monetization: Will never take funding from default search deals
or any other forms of user monetization\, ever. \n\n3. Very short history.
\n * 2019 June: Started by [Andreas Kling](https://awesomekling.com/) wit
h [“LibHTML: Start working on a simple HTML library”](https://github.c
om/SerenityOS/serenity/commit/a67e8238389) commit for [SerenityOS](https:/
/github.com/SerenityOS/).\n * 2022 July: Renamed _Ladybird_ by Andreas in
[“Let's make a Linux GUI for the SerenityOS browser”](https://youtu.b
e/X38MTKHt3_I) live-coding video.\n * 2022 Sept: Spun off from SerenityOS
to separate project: [“A new cross-platform browser project”](https:/
/awesomekling.substack.com/p/ladybird-a-new-cross-platform-browser-project
) announcement.\n * 2024 June: [“I'm forking Ladybird and stepping down
as SerenityOS BDFL”](https://awesomekling.substack.com/p/forking-ladybi
rd-and-stepping-down-serenityos) announcement from Andreas.\n * 2024 July
: [Ladybird Browser Initiative](https://ladybird.org/posts/announcement/)
launched by Andreas and GitHub co-founder [defunkt](https://twitter.com/de
funkt) (Chris Wanstrath).\n\n4. Related early video/audio announcements an
d interviews (July–August 2024).\n * Ladybird Browser Initiative [annou
ncement video](https://www.youtube.com/watch?v=k9edTqPMX_k) from defunkt e
xplaining the project _raison d'être_ + goals (July 2024).\n * [Why we
need Ladybird](https://changelog.com/podcast/604#t=5:08): _Changelog_ podc
ast interview with Andreas and defunkt (August 2024)\; [transcript](https:
//changelog.com/podcast/604#transcript)\; [chapters](https://changelog.com
/podcast/604#chapters).\n * [Eron Wolf announcement grant of $200K](https
://youtu.be/p6k9qcRpW_k) from [FUTO](https://www.futo.org/about/what-is-fu
to/) to the project (August 2024).\n * [Eron Wolf interview with Andreas]
(https://youtu.be/4xhaAAcKLtI) (August 2024).\n \n5. Roadmap.\n * 2026:
alpha release (daily driver for developers and early adopters) for Linux a
nd macOS.\n * 2027: beta release\; downloadable app for Linux and macOS.\
n * 2028: stable release for general public.\n \n\n6. P
roject goals and culture.\n * Eventually give everybody the choice of a w
hole new browser they can use for their daily browsing.\n * Prove it is i
n fact possible to build a completely new browser\, by implementing from t
he WHATWG/W3C/etc. specs.\n * Have a lot of real fun together actually do
ing it.\n * Prove that developing an engine doesn’t take hundreds of en
gineers — and not anything close to even just a hundred.\n * Browser en
gineering: Further help de-mystify it and make it a standard thing to lear
n (hat tip: https://browser.engineering/).\n * Using project Discord serv
er for communication [discord.gg/nvfjVJ4Svh](https://discord.gg/nvfjVJ4Svh
).\n * Using [one GithHub repo](https://github.com/LadybirdBrowser/ladybi
rd) for everything: issues (no bugzilla or other)\, patch/PR submission/re
view\, CI/test automation.\n\n7. Project coding conventions and activity m
etrics.\n * Implement web-platform features exactly according to the actu
al steps in spec algorithms.\n * Abundant code comments with verbatim spe
c text copy/pasted in — showing exactly what’s being implemented.\n *
Additional _`“AD-HOC:”`_ comment convention to mark code that doesn
’t map to any spec requirements.\n * Class/file names tend to closely m
atch actual current spec terms\; e.g.\, `Navigable.h`\, `Transferable.h`.\
n * [“critically reading standards and reporting what is wrong”](http
s://matrixlogs.bakkot.com/WHATWG/2024-08-23#L10)\n\n8. Project activity me
trics.\n * Project activity data/graphs: https://git-pulse.github.io/snap
shots/LadybirdBrowser-ladybird-2024-09-12-pulse.html\n * Project activity
relative rankings: https://git-pulse.github.io/snapshots/?project=Ladybir
dBrowser_ladybird\n \n | Engine | Committers per month
| Commits per month |\n | ---------: | -----------: | -------------
------: |\n | Ladybird | `53` | `564`
|\n | Servo | `27` | `216` |\
n | WebKit | `136` | `1262` |\n |
Gecko | `417` | `3496` |\n | Chromi
um | `1297` | `13176` |\n\n9. How you can get the
code and build it\, and contribute new code/patches.\n * https://github.c
om/LadybirdBrowser/ladybird\n * https://github.com/LadybirdBrowser/ladybi
rd/blob/master/Documentation/BuildInstructionsLadybird.md\n * https://git
hub.com/LadybirdBrowser/ladybird/blob/master/CONTRIBUTING.md\n * https://
github.com/LadybirdBrowser/ladybird/blob/master/Documentation/GettingStart
edContributing.md\n * Linux\, macOS\, Windows (with WSL2)\, Android\; bui
ld uses [vcpkg](https://vcpkg.io/) to manage build dependencies.\n\n10. Co
de details and basic architecture.\n * C++ while selectively migrating pa
rts to Swift and while keeping an eye on things like Sean Baxter’s [Circ
le](https://github.com/seanbaxter/circle) & [Safe C++](https://safecpp.org
/draft.html).\n * Some use of third-party libraries (e.g.\, Harfbuzz\, Sk
ia\, [simdutf](https://github.com/simdutf/simdutf)\, libcurl).\n * Perfor
mance optimizing is not yet a super-high priority (but performance-boostin
g changes are regularly getting made).\n * [LadybirdBrowser/ladybird#feat
ures](https://github.com/LadybirdBrowser/ladybird/#features):\n * UI pr
ocess\, ImageDecoder process\, RequestServer process\, WebContent processe
s.\n * LibWeb: core web-rendering engine (HTML\, CSS\, Events\, DOM\, A
PIs).\n * LibJS: JavaScript engine written from scratch (currently JIT-
less).\n * LibWasm: WebAssembly implementation written from scratch.\n
* [AK](https://github.com/LadybirdBrowser/ladybird/tree/master/AK): Lad
ybird standard library/abstractions: asserts\, smart pointers\, strings\,
numbers (e.g.\, [fast_float](https://github.com/fastfloat/fast_float) impl
.)\, more…\n\n11. Current code size: [`cloc --vcs=git`](https://github.
com/AlDanial/cloc) details/comparison (as of 2024-09-01):\n | Engine
| C++ files | C++ lines of code |\n | ---------: | --------
---: | -------------------: |\n | Ladybird | `1695` | `31394
7` |\n | WebKit | `17189` | `4586173`
|\n | Gecko | `14187` | `5396911` |\n
| Chromium | `63826` | `14902914` |\n\n | Engine
| Rust files | Rust lines of code |\n | ---------: | -------
----: | -------------------: |\n | Servo | `1010` | `26
8796` |\n\n12. Testing.\n * Has its own test harness/runn
er and some in-tree tests.\n * Currently passing ~79% of WPT (compared to
major engines 95%–97%) — and that percentage is growing weekly.\n *
CI/regression-testing: Can’t yet practically run all WPT tests on every
PR (takes ~5.5 hours\, many timeouts).\n * So\, to have automated regres
sion testing\, we currently [add some tests in-tree](https://github.com/La
dybirdBrowser/ladybird/tree/master/Tests/LibWeb) that may be redundant wit
h WPT.\n * [wpt.fyi/results?product=ladybird](https://wpt.fyi/results/?pr
oduct=ladybird) has current test results for all WPT tests.\n\n13. Financi
al support: Funded entirely through donations and sponsorships.\n * https
://donorbox.org/ladybird – donations of any amount: $10\, $50\, $100\, e
tc.\n * https://polar.sh/LadybirdBrowser – set bounties to directly fun
d specific features/tasks\; e.g.\, [$300 legacy-encoders bounty](https://g
ithub.com/LadybirdBrowser/ladybird/issues/824).\n * [Sponsorship opportun
ities](https://ladybird.org/#sponsors): Platinum $100\,000 • Gold $50\,0
00 • Silver $10\,000 • Bronze $5\,000 • Copper $1\,000.\n * Ladybir
d Browser Initiative announced/seeded with [1 million dollar donation](htt
ps://twitter.com/defunkt/status/1807779408092234134) from defunkt and his
family.\n\n14. Where Ladybird fits in at the W3C.\n * This means we have
_six_ engines in active development: Gecko\, Servo\, WebKit\, Blink\, Flow
([88% WPT](https://wpt.fyi/results/?product=flow))\, and Ladybird.\n * F
ive _open-source_ engines in active development — and six engines in tot
al: [both things we’ve _never_ had before](https://gist.githubuserconten
t.com/sideshowbarker/8284404/raw/b4dce67abfd4dc1b6a90c8fc62960ec702df5b4f/
engines-timeline.png).\n * Imagine: Can the Ladybird project grow into a
first-class citizen in the W3C community\, along with other engines?\n *
Enlightened self-interest: Helping a new engine project helps improve our
specs\, get new editors on board\, etc.\n * You can bring your specific W
3C/professional experience to help refine/align Ladybird code in key W3C f
ocus areas:\n * Accessibility: ARIA\, AOM\, testing with AT\, more…\n
* Internationalization: CJK handling\, layout\, many other opportuniti
es…\n * Security: CSP implementation\, standards related to Spectre m
itigation\, security-related error messages\, more…\n * Privacy: Lots
of opportunities for implementing particular specs\, for privacy-related
browser/UI features\, more…\n\n15. Resources.\n * [FAQ](https://ladybir
d.org/#faq): _Independent? • When is it coming? • How many people? •
Hiring plan? • Windows? • Mobile? • C++? • Swift?_\n * Ladybird
[YouTube channel](https://www.youtube.com/@LadybirdBrowser): monthly Ladyb
ird project updates from Andreas.\n * Andreas’ [YouTube channel](https:
//www.youtube.com/@awesomekling): 1000+ videos from 6+ years\; incl. “ca
r talk” + OS/browser “hacking” (live-coding) videos.\n\n16. Tangenti
ally-related background.\n * [Understanding the role of browser engines](
https://assets.publishing.service.gov.uk/media/61b86737e90e07043c35f5be/Ap
pendix_F_-_Understanding_the_role_of_browser_engines.pdf) (UK Competition
and Markets Authority [Mobile ecosystems market study](https://www.gov.uk/
cma-cases/mobile-ecosystems-market-study#interim-report)).\n\n**Materials:
**\n- [minutes](https://www.w3.org/2024/09/25-ladybird-minutes.html)\n- [S
ession proposal on GitHub](https://github.com/w3c/tpac2024-breakouts/issue
s/56)
STATUS:CONFIRMED
CREATED:20240916T215533Z
LAST-MODIFIED:20241002T124415Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:2 Ballroom Level - California B
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:a824c2e4-312f-4bb2-90e5-3a871a24613e
DTSTAMP:20241002T132749Z
SUMMARY:Content Authenticity and the Web
DTSTART;TZID=America/Los_Angeles:20240925T111500
DTEND;TZID=America/Los_Angeles:20240925T121500
DESCRIPTION:https://www.w3.org/events/meetings/a824c2e4-312f-4bb2-90e5-3a87
1a24613e/\n\nGoal of the session: Understand user needs around provenance
and authenticity of content on the Web and their intersections with W3C wo
rk\, towards a possible W3C Workshop in 2025.\n\n\nOne of the major threat
s the Web is facing is its use as a large-scale vector or mis- and disinfo
rmation\, made even more prominent by the rise of [generative AI](https://
www.w3.org/reports/ai-web-impact/#transparency-on-ai-generated-content) wh
ich allows the production of synthetic superficially-credible content.\n\n
To understand what role W3C might play in mitigating that threat\, discuss
ions around a possible Authentic Web workshop sometime in 2025 have emerge
d in the community.\n\nThis breakout offers to discuss how we can better a
llow end users to determine the authenticity of the information they see w
hen they use the web\, as a first step towards identifying a relevant scop
e for such a workshop.\n\nThe Ethical Web Principles state: [“The web ma
kes it possible to verify information”](https://www.w3.org/TR/ethical-we
b-principles/#verify). There are technologies being developed such as [C2P
A](https://c2pa.org/specifications/specifications/2.0/index.html) or OP ([
Originator Profile](https://originator-profile.org/en-US/)) which allow fo
r stronger binding of metadata to content of various kinds. What can the w
eb do better to surface this kind of metadata to end users and ensure that
this metadata is maintained across various methods of content transfer?\n
\nThe breakout will focus on the user needs - specifically thinking of web
users (both as content creators and consumers)\, informed by current best
practice thinking in the relevant industries (for example\, journalism\,
fact checking).\n\nAgenda\n\n**Chairs:**\nDaniel Appelquist\n\n**Descripti
on:**\nGoal of the session: Understand user needs around provenance and au
thenticity of content on the Web and their intersections with W3C work\, t
owards a possible W3C Workshop in 2025.\n\n\nOne of the major threats the
Web is facing is its use as a large-scale vector or mis- and disinformatio
n\, made even more prominent by the rise of [generative AI](https://www.w3
.org/reports/ai-web-impact/#transparency-on-ai-generated-content) which al
lows the production of synthetic superficially-credible content.\n\nTo und
erstand what role W3C might play in mitigating that threat\, discussions a
round a possible Authentic Web workshop sometime in 2025 have emerged in t
he community.\n\nThis breakout offers to discuss how we can better allow e
nd users to determine the authenticity of the information they see when th
ey use the web\, as a first step towards identifying a relevant scope for
such a workshop.\n\nThe Ethical Web Principles state: [“The web makes it
possible to verify information”](https://www.w3.org/TR/ethical-web-prin
ciples/#verify). There are technologies being developed such as [C2PA](htt
ps://c2pa.org/specifications/specifications/2.0/index.html) or OP ([Origin
ator Profile](https://originator-profile.org/en-US/)) which allow for stro
nger binding of metadata to content of various kinds. What can the web do
better to surface this kind of metadata to end users and ensure that this
metadata is maintained across various methods of content transfer?\n\nThe
breakout will focus on the user needs - specifically thinking of web users
(both as content creators and consumers)\, informed by current best pract
ice thinking in the relevant industries (for example\, journalism\, fact c
hecking).\n\n**Goal(s):**\nRefine plan for a 2025 workshop on web authenti
city.\n\n\n**Agenda:**\nFormat: Short presentations followed by discussion
\n\n**Materials:**\n- [minutes](https://www.w3.org/2024/09/25-authentic-we
b-minutes.html)\n- [Session proposal on GitHub](https://github.com/w3c/tpa
c2024-breakouts/issues/70)
STATUS:CONFIRMED
CREATED:20240916T215827Z
LAST-MODIFIED:20241002T132749Z
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
BEGIN:VEVENT
UID:3652f121-6196-4606-b735-7471c2246547
DTSTAMP:20241016T205550Z
SUMMARY:Cookie Layering
DTSTART;TZID=America/Los_Angeles:20240925T111500
DTEND;TZID=America/Los_Angeles:20240925T121500
DESCRIPTION:https://www.w3.org/events/meetings/3652f121-6196-4606-b735-7471
c2246547/\n\nWe will share and discuss progress on the [Cookie Layering](h
ttps://github.com/httpwg/http-extensions/issues/2084) effort\, our new [Co
okies Internet Draft](https://github.com/johannhof/draft-annevk-johannhof-
httpbis-cookies) and how we can proceed to specify and standardize new Pri
vacy features on the web such as third-party cookie blocking\, [cookie par
titioning](https://github.com/privacycg/CHIPS)\, and the [Storage Access A
PI](https://github.com/privacycg/storage-access) in WHATWG and IETF.\n\nAg
enda\n\n**Chairs:**\nJohann Hofmann\, Anne van Kesteren\n\n**Description:*
*\nWe will share and discuss progress on the [Cookie Layering](https://git
hub.com/httpwg/http-extensions/issues/2084) effort\, our new [Cookies Inte
rnet Draft](https://github.com/johannhof/draft-annevk-johannhof-httpbis-co
okies) and how we can proceed to specify and standardize new Privacy featu
res on the web such as third-party cookie blocking\, [cookie partitioning]
(https://github.com/privacycg/CHIPS)\, and the [Storage Access API](https:
//github.com/privacycg/storage-access) in WHATWG and IETF.\n\n**Goal(s):**
\nProgress updates and planning next steps\n\n\n\n**Materials:**\n- [slide
s](https://www.w3.org/2024/Talks/TPAC/breakouts/future-of-cookies.pdf)\n-
[minutes](https://github.com/w3c/tpac2024-breakouts/issues/74#issuecomment
-2381547378)\n- [Session proposal on GitHub](https://github.com/w3c/tpac20
24-breakouts/issues/74)
STATUS:CONFIRMED
CREATED:20240916T215921Z
LAST-MODIFIED:20241016T205550Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - Capistrano
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:149479a7-9125-4287-99ba-618acacaffbb
DTSTAMP:20241002T122509Z
SUMMARY:Curating the web platform's data and documentation
DTSTART;TZID=America/Los_Angeles:20240925T111500
DTEND;TZID=America/Los_Angeles:20240925T121500
DESCRIPTION:https://www.w3.org/events/meetings/149479a7-9125-4287-99ba-618a
cacaffbb/\n\n[Open Web Docs](https://openwebdocs.org) is a nonprofit open
collective that curates web platform documentation and data for the benefi
t of web developers and the ecosystem's tooling. In this session we want t
o talk about how we work and how you (as a spec editor or implementer) can
collaborate with us.\n\nWe want to talk about how specs and web platform
features go through a "pipeline" of repositories and why that is important
for us as documentation and data curators.\n\n1. A new spec gets authored
and picked up by: https://github.com/w3c/browser-specs \n2. Spec definiti
ons and in particular IDL definitions get parsed by reffy and https://gith
ub.com/w3c/webref\n3. Web platform features get identified from webref and
continuously tested by https://github.com/openwebdocs/mdn-bcd-collector\n
4. If a browser ships an identified feature\, https://github.com/openwebdo
cs/mdn-bcd-collector signals that to https://github.com/mdn/browser-compat
-data\n5. https://github.com/mdn/browser-compat-data gets released and spr
eads the information to MDN\, caniuse\, caniwebview\, linters\, specs\, ot
her tooling and reporting.\n6. At this stage\, the feature is also marked
in need of technical documentation via https://openwebdocs.github.io/web-d
ocs-backlog/\n7. https://github.com/web-platform-dx/web-features defines a
feature id for the new feature and calculates a "baseline" status allowin
g it to be talked about in a consistent way in even more places.\n8. Web
developers start using the feature more broadly and adapt it as the featur
e hopefully transitions to "baseline high" over the course of the next few
months.\n9. (if the feature gets deprecated and we take steps to signal t
o users to move off of it again)\n\nThere is probably more to it but this
should give you an idea of our "pipeline". The above is sort of the "golde
n path". Of course\, things can go sideways in several ways and\, in the w
orst case\, that will lead to non-existing docs and compat data:\n\n- Spec
s don't make it into the browser-specs repo or don't have standing: good\n
- Browsers implement things without a spec and we have to maintain custom
IDL files and document features as non-standard\n- Features are specced bu
t never see implementation (we shy away from curating these\, "spec fictio
n").\n- Features sit behind a flag for a long time (and change drastically
\, so we don't curate docs and data until we have been promised with _some
_ stability)\n- Bugs in any of the above repositories\n- Shortage of maint
ainers\, technical writers\, developers\, curators\, in any of the reposit
ories.\n\nAgenda\n\n**Chairs:**\nFlorian Scholz\, Will Bamberg\, Estelle W
eyl\, Vinyl Da.i'gyu-Kazotetsu\n\n**Description:**\n[Open Web Docs](https:
//openwebdocs.org) is a nonprofit open collective that curates web platfor
m documentation and data for the benefit of web developers and the ecosyst
em's tooling. In this session we want to talk about how we work and how yo
u (as a spec editor or implementer) can collaborate with us.\n\nWe want to
talk about how specs and web platform features go through a "pipeline" of
repositories and why that is important for us as documentation and data c
urators.\n\n1. A new spec gets authored and picked up by: https://github.c
om/w3c/browser-specs \n2. Spec definitions and in particular IDL definitio
ns get parsed by reffy and https://github.com/w3c/webref\n3. Web platform
features get identified from webref and continuously tested by https://git
hub.com/openwebdocs/mdn-bcd-collector\n4. If a browser ships an identified
feature\, https://github.com/openwebdocs/mdn-bcd-collector signals that t
o https://github.com/mdn/browser-compat-data\n5. https://github.com/mdn/br
owser-compat-data gets released and spreads the information to MDN\, caniu
se\, caniwebview\, linters\, specs\, other tooling and reporting.\n6. At t
his stage\, the feature is also marked in need of technical documentation
via https://openwebdocs.github.io/web-docs-backlog/\n7. https://github.com
/web-platform-dx/web-features defines a feature id for the new feature and
calculates a "baseline" status allowing it to be talked about in a consis
tent way in even more places.\n8. Web developers start using the feature
more broadly and adapt it as the feature hopefully transitions to "baselin
e high" over the course of the next few months.\n9. (if the feature gets d
eprecated and we take steps to signal to users to move off of it again)\n\
nThere is probably more to it but this should give you an idea of our "pip
eline". The above is sort of the "golden path". Of course\, things can go
sideways in several ways and\, in the worst case\, that will lead to non-e
xisting docs and compat data:\n\n- Specs don't make it into the browser-sp
ecs repo or don't have standing: good\n- Browsers implement things without
a spec and we have to maintain custom IDL files and document features as
non-standard\n- Features are specced but never see implementation (we shy
away from curating these\, "spec fiction").\n- Features sit behind a flag
for a long time (and change drastically\, so we don't curate docs and data
until we have been promised with _some_ stability)\n- Bugs in any of the
above repositories\n- Shortage of maintainers\, technical writers\, develo
pers\, curators\, in any of the repositories.\n\n**Goal(s):**\nDiscussing
curation of documentation\, compatibility data. Exchanging feedback among
repo maintainers\n\n\n**Agenda:**\n1. Short presentation about OWD's web p
latform data and documentation curation pipeline\n2. Discussion\n\n**Mater
ials:**\n- [minutes](https://www.w3.org/2024/09/25-openwebdocs-minutes.htm
l)\n- [Session proposal on GitHub](https://github.com/w3c/tpac2024-breakou
ts/issues/34)\n\n**Track(s):**\n- Feature lifecycle
STATUS:CONFIRMED
CREATED:20240916T215143Z
LAST-MODIFIED:20241002T122509Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:-1 Lower Level - Catalina 1
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:e679b728-67ce-4bfb-96f3-22bc59813534
DTSTAMP:20241002T122505Z
SUMMARY:Data and Account Portability on the Social Web
DTSTART;TZID=America/Los_Angeles:20240925T111500
DTEND;TZID=America/Los_Angeles:20240925T121500
DESCRIPTION:https://www.w3.org/events/meetings/e679b728-67ce-4bfb-96f3-22bc
59813534/\n\nOne of the major pain points (and most requested feature) is
painless and automated migration\, export and import of social web profile
s and data. Join us for a discussion of the LOLA specification (Live Onlin
e Account portability)\, the Data Portability report and related specifica
tions. \nWe'll also discuss how Data Portability intersects with authentic
ation (OAuth 2 and more)\, decentralized identity\, signatures\, and so on
.\n\nAgenda\n\n**Chairs:**\nDmitri Zagidulin\n\n**Description:**\nOne of t
he major pain points (and most requested feature) is painless and automate
d migration\, export and import of social web profiles and data. Join us f
or a discussion of the LOLA specification (Live Online Account portability
)\, the Data Portability report and related specifications. \nWe'll also d
iscuss how Data Portability intersects with authentication (OAuth 2 and mo
re)\, decentralized identity\, signatures\, and so on.\n\n**Goal(s):**\nCo
mmunity Discussion of Data Portability issues\n\n\n\n**Materials:**\n- [mi
nutes](https://www.w3.org/2024/09/25-data-portability-minutes.html)\n- [Se
ssion proposal on GitHub](https://github.com/w3c/tpac2024-breakouts/issues
/88)
STATUS:CONFIRMED
CREATED:20240916T220158Z
LAST-MODIFIED:20241002T122505Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - Palos Verdes
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:366284c0-35c5-416f-9b40-b76e43c49da5
DTSTAMP:20241016T205220Z
SUMMARY:Defining views
DTSTART;TZID=America/Los_Angeles:20240925T111500
DTEND;TZID=America/Los_Angeles:20240925T121500
DESCRIPTION:https://www.w3.org/events/meetings/366284c0-35c5-416f-9b40-b76e
43c49da5/\n\nDefining what constitutes a view has been tried over the year
s. In this session\, we will re-open the discussion.\n\n[Web page in WCAG
2.2](https://www.w3.org/TR/WCAG22/#dfn-web-page-s)\n\n> a non-embedded res
ource obtained from a single URI using HTTP plus any other resources that
are used in the rendering or intended to be rendered together with it by a
user agent\n\n[Views in WCAG 3](https://www.w3.org/TR/wcag-3.0/#dfn-views
)\n\n> Views include all content visually and programmatically available w
ithout a substantive change. Conceptually\, views correspond to the defini
tion of a web page as used in WCAG 2\, but are not restricted to content m
eeting that definition. For example\, a view could be considered a “scre
en” in a mobile app or a layer of web content – such as a modal. \n\n[
Interpretation of Web Terminology in a Non-web Context](https://www.w3.org
/TR/wcag2ict-22/#interpretation-of-web-terminology-in-a-non-web-context)\n
\n> A small number of success criteria are written to apply to “a set of
web pages” or “multiple web pages” and depend upon all pages in the
set to share some characteristic or behavior. Since the unit of conforman
ce in WCAG 2 is a single web page\, the task force agreed that the equival
ent unit of conformance for non-web documents is a single document. It fol
lows that an equivalent unit of evaluation for a “set of web pages” wo
uld be a “set of documents”. **Since it isn't possible to unambiguousl
y carve up non-web software into discrete pieces**\, a single “web page
” was equated to a “software program” and a “set of web pages” w
as equated to a “set of software programs”.\n\nAgenda\n\n**Chairs:**\n
Jan Jaap de Groot\n\n**Description:**\nDefining what constitutes a view ha
s been tried over the years. In this session\, we will re-open the discuss
ion.\n\n[Web page in WCAG 2.2](https://www.w3.org/TR/WCAG22/#dfn-web-page-
s)\n\n> a non-embedded resource obtained from a single URI using HTTP plus
any other resources that are used in the rendering or intended to be rend
ered together with it by a user agent\n\n[Views in WCAG 3](https://www.w3.
org/TR/wcag-3.0/#dfn-views)\n\n> Views include all content visually and pr
ogrammatically available without a substantive change. Conceptually\, view
s correspond to the definition of a web page as used in WCAG 2\, but are n
ot restricted to content meeting that definition. For example\, a view cou
ld be considered a “screen” in a mobile app or a layer of web content
– such as a modal. \n\n[Interpretation of Web Terminology in a Non-web C
ontext](https://www.w3.org/TR/wcag2ict-22/#interpretation-of-web-terminolo
gy-in-a-non-web-context)\n\n> A small number of success criteria are writt
en to apply to “a set of web pages” or “multiple web pages” and de
pend upon all pages in the set to share some characteristic or behavior. S
ince the unit of conformance in WCAG 2 is a single web page\, the task for
ce agreed that the equivalent unit of conformance for non-web documents is
a single document. It follows that an equivalent unit of evaluation for a
“set of web pages” would be a “set of documents”. **Since it isn'
t possible to unambiguously carve up non-web software into discrete pieces
**\, a single “web page” was equated to a “software program” and a
“set of web pages” was equated to a “set of software programs”.\n
\n**Goal(s):**\nGetting closer to the definition of views\n\n\n**Agenda:**
\n1. Web page definition (WCAG 2.2)\n2. View definition (WCAG 3)\n3. Web p
age mapping (WCAG2ICT)\n4. Defining view\n\n**Materials:**\n- [slides](htt
ps://www.w3.org/2024/Talks/TPAC/breakouts/defining-views/)\n- [minutes](ht
tps://www.w3.org/2024/09/25-views-minutes.html)\n- [Session proposal on Gi
tHub](https://github.com/w3c/tpac2024-breakouts/issues/46)\n\n**Track(s):*
*\n- UX
STATUS:CONFIRMED
CREATED:20240916T215346Z
LAST-MODIFIED:20241016T205220Z
SEQUENCE:4
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - San Clemente
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:01bbf65d-aad4-4377-bacb-7eafe46f6c63
DTSTAMP:20241030T131430Z
SUMMARY:Demonstration of AI Powered Accessibility Auditing
DTSTART;TZID=America/Los_Angeles:20240925T111500
DTEND;TZID=America/Los_Angeles:20240925T121500
DESCRIPTION:https://www.w3.org/events/meetings/01bbf65d-aad4-4377-bacb-7eaf
e46f6c63/\n\nThis session will demonstrate how Artificial Intelligence can
be used for a number of accessibility analysis tasks in natural language
processing\, image understanding and design evaluation.\n\nAgenda\n\n**Cha
irs:**\nDavid Fazio\n\n**Description:**\nThis session will demonstrate how
Artificial Intelligence can be used for a number of accessibility analysi
s tasks in natural language processing\, image understanding and design ev
aluation.\n\n**Goal(s):**\nDemonstrate the power of AI-driven rule engines
to enhance accessibility auditing capabilities and reduce the need for ma
nual auditing efforts.\n\nAdditional session chairs (Optional)\n\n@nehamja
dhav\n\n\n**Agenda:**\nShare & Discuss Current Implementation:\n- Abbrevia
tions\n- Idioms and Phrases\n- Text from Images\n- Localization\n- Languag
e and Context Analysis (Link Titles)\n\nFuture Implementation\n- Screen Re
cording Analysis\n- Video/Audio File Analysis\n- Image Analysis\n- Pattern
and Relationship Recognition\n- Dynamic Content Analysis\n\n**Materials:*
*\n- [minutes](https://www.w3.org/2024/09/25-ai-powered-accessibility-minu
tes.html)\n- [recording](https://www.w3.org/2024/09/breakouts/recording-19
.html)\n- [Session proposal on GitHub](https://github.com/w3c/tpac2024-bre
akouts/issues/19)\n\n**Track(s):**\n- AI
STATUS:CONFIRMED
CREATED:20240916T214937Z
LAST-MODIFIED:20241030T131430Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:2 Ballroom Level - California A
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:f560e5d7-c36e-4b79-8b61-8f2866805f1e
DTSTAMP:20241002T130522Z
SUMMARY:Electronic Transferable Records: Implemented Using Transferable Ver
ifiable Credentials
DTSTART;TZID=America/Los_Angeles:20240925T111500
DTEND;TZID=America/Los_Angeles:20240925T121500
DESCRIPTION:https://www.w3.org/events/meetings/f560e5d7-c36e-4b79-8b61-8f28
66805f1e/\n\nThe presentation will share how Verifiable Credentials can be
coupled with other decentralised technologies to implement the transferab
ility feature of Electronic Transferable Records (ETRs). ETRs represent a
digital evolution of traditional paper-based records\, enabling instant\,
secure and easily verifiable electronic transactions. By leveraging transf
erable verifiable credentials\, ETRs ensure the authenticity\, integrity\,
and traceability of information throughout its lifecycle. Attendees will
learn how TradeTrust (a freely available digital public good) uses these t
echnologies to achieve trusted interoperability\, with examples of use cas
es and the impact on various industries.\n\nAgenda\n\n**Chairs:**\nRachel
Yager\n\n**Description:**\nThe presentation will share how Verifiable Cred
entials can be coupled with other decentralised technologies to implement
the transferability feature of Electronic Transferable Records (ETRs). ETR
s represent a digital evolution of traditional paper-based records\, enabl
ing instant\, secure and easily verifiable electronic transactions. By lev
eraging transferable verifiable credentials\, ETRs ensure the authenticity
\, integrity\, and traceability of information throughout its lifecycle. A
ttendees will learn how TradeTrust (a freely available digital public good
) uses these technologies to achieve trusted interoperability\, with examp
les of use cases and the impact on various industries.\n\n**Goal(s):**\nWe
aim to achieve: \n1. Awareness: To raise awareness among W3C members abo
ut the benefits of digitalising transferable instruments and applicability
of ETRs\; \n2. Alignment: To share latest information on related discussi
ons happening at other international forum as the global trade community m
arshals around a freely-available and neutral standardized framework for E
TRs. This would help ensure interoperability across different systems and
platforms\, making it easier for organisations to advance to digital trade
practices.\; \n3. Collaboration: To foster collaboration and discussions
among industry experts and organizations\, leading to collective efforts i
n spearheading innovation efforts. \n4. Feedback: To gather feedback from
the W3C community on the importance of the transferability feature to the
m.\n\n\n\n**Materials:**\n- [minutes](https://www.w3.org/2024/09/25-Transf
erableVC-minutes.html)\n- [Session proposal on GitHub](https://github.com/
w3c/tpac2024-breakouts/issues/50)\n\n**Track(s):**\n- Wallets
STATUS:CONFIRMED
CREATED:20240916T215418Z
LAST-MODIFIED:20241002T130522Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:-1 Lower Level - Catalina 5
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:49386363-7a65-4f4a-9580-bff867a1c6e9
DTSTAMP:20241016T205507Z
SUMMARY:Evolved Video Encoding with WebCodecs
DTSTART;TZID=America/Los_Angeles:20240925T111500
DTEND;TZID=America/Los_Angeles:20240925T121500
DESCRIPTION:https://www.w3.org/events/meetings/49386363-7a65-4f4a-9580-bff8
67a1c6e9/\n\n[WebCodecs](WebCodecs) provides a low-level API to do encodin
g and decoding of video with control over settings on a per-frame basis. A
s a relatively young API it currently lacks some more advanced features\,
such as temporal/spatial scalability that are important for real-time use
cases like video conferencing.\n\nThis session is intended to discuss a nu
mber of potential next steps\, to find which features are highest priority
\, and what benefits or problems we face with each of those. \n\nSome of t
he topics for discussion:\n\n#### Explicit reference frame control\nBy all
owing the user to specify which reference buffers to reference and which t
o update on a per-frame basis\, it is possible to implement a number of im
portant reference structures and coding features including temporal/spatia
l/quality layers\, long-term references\, low-latency 2-pass rate control\
, etc.\n\nIn short\, any of the scalability modes listed in [Scalable Vide
o Coding (SVC) Extension for WebRTC](https://www.w3.org/TR/webrtc-svc/)\,
any many more can be implemented with a small set of tools. If done right\
, this could even be done in a manner that is codec and implementation agn
ostic.\n\nThis way of modeling an encoder does also present some issues. T
he user needs to be able to determine how many reference buffers are avail
able\, how many can be referenced per frame and know which references are
allowed or disallowed based on various circumstances. How do we expose suc
h data in a way that is both user friendly\, compatible with the current A
PI\, and avoids unnecessary finger printing surfaces?\n\nThere are also tr
adeoffs when it comes to integrating with existing encoder implementations
\, a small subset of which may not fit well into this model.\n\n#### Spati
al/Quality Scalability\n\nSpatial scalability can be achieved by changing
the `encode` call to take a _sequence_ of encoding options\, instead of a
single option\, per input frame. Each option would then represent a differ
ent layer and would include a desired encoded resolution. With reference f
rame scaling\, a user may reference a buffer containing a different resolu
tion.\n\nAgain\, this comes with some challenges. Different codec types mi
ght have different bounds on the scaling factors\, and even certain implem
entations have limitations in this regard - if it is supported at all. Som
e codecs allow only reference frame scaling within the same temporal unit\
, while other support any reference at any time. How do we handle encoders
with special optimized mode such as "multi-res" or "S-mode aware" encodin
g?\n\n#### Rate Control\n\nWhen dealing with layered encoding\, rate contr
ol becomes much more involved. The easiest way is to just support CQP\, pu
tting all of the rate control control with the user. If CBR is desired\, t
he encoder needs to understand the bitrate target and expected frame rate
for each spatio-temporal layer\, this means it suddenly needs to be SVC aw
are even if the user is doing all of the reference frame control.\n\n####
Auxiliary\n\nThere are many other knobs that could potentially be added. S
peed/Quality control\, segmentation/ROI-mapping\, etc\nWhat's on the wish-
list of the community?\n\n#### Other Sessions of Interest\n\nNote that the
re will also be a first-step proposal discussed at the [joint Media/WebRTC
WG Meeting](https://www.w3.org/events/meetings/b2c200b8-7362-4330-b74c-7b
2efc05d87f/) on the 26th.\n\nFurther\, there is a proposed [breakout sessi
on](https://github.com/w3c/tpac2024-breakouts/issues/13) on [RtpTransport]
(https://github.com/w3c/webrtc-rtptransport)\, an API that allows users to
send custom-encoded frames over the RTP channel of a `PeerConnection` and
is intended to go hand-in-hand with WebCodecs.\n\nAgenda\n\n**Chairs:**\n
Erik Språng\, Eugene Zemtsov\n\n**Description:**\n[WebCodecs](WebCodecs)
provides a low-level API to do encoding and decoding of video with control
over settings on a per-frame basis. As a relatively young API it currentl
y lacks some more advanced features\, such as temporal/spatial scalability
that are important for real-time use cases like video conferencing.\n\nTh
is session is intended to discuss a number of potential next steps\, to fi
nd which features are highest priority\, and what benefits or problems we
face with each of those. \n\nSome of the topics for discussion:\n\n#### Ex
plicit reference frame control\nBy allowing the user to specify which refe
rence buffers to reference and which to update on a per-frame basis\, it i
s possible to implement a number of important reference structures and cod
ing features including temporal/spatial/quality layers\, long-term referen
ces\, low-latency 2-pass rate control\, etc.\n\nIn short\, any of the scal
ability modes listed in [Scalable Video Coding (SVC) Extension for WebRTC]
(https://www.w3.org/TR/webrtc-svc/)\, any many more can be implemented wit
h a small set of tools. If done right\, this could even be done in a manne
r that is codec and implementation agnostic.\n\nThis way of modeling an en
coder does also present some issues. The user needs to be able to determin
e how many reference buffers are available\, how many can be referenced pe
r frame and know which references are allowed or disallowed based on vario
us circumstances. How do we expose such data in a way that is both user fr
iendly\, compatible with the current API\, and avoids unnecessary finger p
rinting surfaces?\n\nThere are also tradeoffs when it comes to integrating
with existing encoder implementations\, a small subset of which may not f
it well into this model.\n\n#### Spatial/Quality Scalability\n\nSpatial sc
alability can be achieved by changing the `encode` call to take a _sequenc
e_ of encoding options\, instead of a single option\, per input frame. Eac
h option would then represent a different layer and would include a desire
d encoded resolution. With reference frame scaling\, a user may reference
a buffer containing a different resolution.\n\nAgain\, this comes with som
e challenges. Different codec types might have different bounds on the sca
ling factors\, and even certain implementations have limitations in this r
egard - if it is supported at all. Some codecs allow only reference frame
scaling within the same temporal unit\, while other support any reference
at any time. How do we handle encoders with special optimized mode such as
"multi-res" or "S-mode aware" encoding?\n\n#### Rate Control\n\nWhen deal
ing with layered encoding\, rate control becomes much more involved. The e
asiest way is to just support CQP\, putting all of the rate control contro
l with the user. If CBR is desired\, the encoder needs to understand the b
itrate target and expected frame rate for each spatio-temporal layer\, thi
s means it suddenly needs to be SVC aware even if the user is doing all of
the reference frame control.\n\n#### Auxiliary\n\nThere are many other kn
obs that could potentially be added. Speed/Quality control\, segmentation/
ROI-mapping\, etc\nWhat's on the wish-list of the community?\n\n#### Other
Sessions of Interest\n\nNote that there will also be a first-step proposa
l discussed at the [joint Media/WebRTC WG Meeting](https://www.w3.org/even
ts/meetings/b2c200b8-7362-4330-b74c-7b2efc05d87f/) on the 26th.\n\nFurther
\, there is a proposed [breakout session](https://github.com/w3c/tpac2024-
breakouts/issues/13) on [RtpTransport](https://github.com/w3c/webrtc-rtptr
ansport)\, an API that allows users to send custom-encoded frames over the
RTP channel of a `PeerConnection` and is intended to go hand-in-hand with
WebCodecs.\n\n**Goal(s):**\nFind the highest priority features in the com
munity\, and what aspects needs more consideration\n\n\n**Agenda:**\nThe a
genda is to discuss the proposal to add reference frame control to WebCode
cs\, and gather feedback and comments on the path forward. The session con
sist of a few parts:\n\n* General goals\n* Our initial proposal\, a minimu
m viable useful implementation of reference control\n* How to query what t
he encoders are capable of\n* Spatial Scalability (SVC\, Simulcast)\n* Rat
e Control \n* Miscellaneous\n\nSee also [WebCodecs spec](https://www.w3.or
g/TR/webcodecs/) and [github issue](https://github.com/w3c/webcodecs/issue
s/285) for the reference control.\n\n**Materials:**\n- [slides](https://ww
w.w3.org/2024/Talks/TPAC/breakouts/evolved-webcodecs.pdf)\n- [minutes](htt
ps://www.w3.org/2024/09/25-evolved-webcodecs-minutes.html)\n- [Session pro
posal on GitHub](https://github.com/w3c/tpac2024-breakouts/issues/71)\n\n*
*Track(s):**\n- Real-time Web
STATUS:CONFIRMED
CREATED:20240916T215856Z
LAST-MODIFIED:20241016T205507Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:-1 Lower Level - Catalina 2
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:2bc3f609-247e-4278-9c92-2bd59877b9c9
DTSTAMP:20241002T120625Z
SUMMARY:FedCM in practice
DTSTART;TZID=America/Los_Angeles:20240925T111500
DTEND;TZID=America/Los_Angeles:20240925T121500
DESCRIPTION:https://www.w3.org/events/meetings/2bc3f609-247e-4278-9c92-2bd5
9877b9c9/\n\nSmooth sign-up experiences on the web are essential for our u
sers’ experience\, and the fastest account creation experience is one wh
ere the user doesn’t have to create an account at all!!\n\nWhile such ex
periences were powered by federated identity protocols using low level pri
mitives in yesteryear’s web (e.g. third-party cookies\, iframes and redi
rects)\, today’s privacy requirements lead to a new standard proposal to
provide them with a more deliberate\, safer and private binding - Federat
ed Credential Management (or FedCM for short).\n\nIn this session we will
briefly cover FedCM and how it does its magic\, how it interacts with othe
r efforts in the identity space\, such as WebAuthn\, and demonstrate real-
life UX improvements that FedCM provides over the alternatives and discuss
what can be improved in this space.\n\nCo-hosts: @samuelgoto @gioele-anto
ci\n\nAgenda\n\n**Chairs:**\nYoav Weiss\n\n**Description:**\nSmooth sign-u
p experiences on the web are essential for our users’ experience\, and t
he fastest account creation experience is one where the user doesn’t hav
e to create an account at all!!\n\nWhile such experiences were powered by
federated identity protocols using low level primitives in yesteryear’s
web (e.g. third-party cookies\, iframes and redirects)\, today’s privacy
requirements lead to a new standard proposal to provide them with a more
deliberate\, safer and private binding - Federated Credential Management (
or FedCM for short).\n\nIn this session we will briefly cover FedCM and ho
w it does its magic\, how it interacts with other efforts in the identity
space\, such as WebAuthn\, and demonstrate real-life UX improvements that
FedCM provides over the alternatives and discuss what can be improved in t
his space.\n\nCo-hosts: @samuelgoto @gioele-antoci\n\n**Goal(s):**\nClarif
y the role of FedCM in the identity ecosystem\, demonstrate its advantages
and gather feedback on the feature and its future direction.\n\n\n\n**Mat
erials:**\n- [minutes](https://gist.github.com/yoavweiss/800cecf07ab146f18
948cf9723dc6d05)\n- [Session proposal on GitHub](https://github.com/w3c/tp
ac2024-breakouts/issues/79)\n\n**Track(s):**\n- Identity
STATUS:CONFIRMED
CREATED:20240916T220015Z
LAST-MODIFIED:20241002T120625Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - Manhattan
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:ff0db05c-72ef-468f-94db-a3dce42a3025
DTSTAMP:20241016T205850Z
SUMMARY:Mitigate Threats for Digital Credentials API
DTSTART;TZID=America/Los_Angeles:20240925T111500
DTEND;TZID=America/Los_Angeles:20240925T121500
DESCRIPTION:https://www.w3.org/events/meetings/ff0db05c-72ef-468f-94db-a3dc
e42a3025/\n\nThis is an interactive session to understand how to mitigate
a [number of specific threats](https://lists.w3.org/Archives/Public/public
-review-comments/2024Sep/0017.html) identified during the Federated Identi
ty Working Group's recharter review for the addition of the Digital Creden
tials API:\na. Perpetuates sharing of personal data by making it more avai
lable via a browser API\nb. Increased centralization through subtle tradeo
ffs\nc. Content will be moved from the deep web to the “attributed deep
web”\nd. Exchanges user agency for greater compliance and convenience\n\
nThis breakout is intended to be a collaborative\, working session. The fo
cus will be on gaining consensus on the mitigations.\n\nAgenda: https://ww
w.w3.org/2024/Talks/TPAC/breakouts/mitigating-threats-credentials.pdf\n\nA
genda\n\n**Chairs:**\nSimone Onofri\n\n**Description:**\nThis is an intera
ctive session to understand how to mitigate a [number of specific threats]
(https://lists.w3.org/Archives/Public/public-review-comments/2024Sep/0017.
html) identified during the Federated Identity Working Group's recharter r
eview for the addition of the Digital Credentials API:\na. Perpetuates sha
ring of personal data by making it more available via a browser API\nb. In
creased centralization through subtle tradeoffs\nc. Content will be moved
from the deep web to the “attributed deep web”\nd. Exchanges user agen
cy for greater compliance and convenience\n\nThis breakout is intended to
be a collaborative\, working session. The focus will be on gaining consens
us on the mitigations.\n\n**Goal(s):**\nThis breakout is intended to be a
collaborative\, working session. The focus will be on gaining consensus on
the mitigations.\n\n\n\n**Materials:**\n- [slides](https://www.w3.org/202
4/Talks/TPAC/breakouts/mitigating-threats-credentials.pdf)\n- [minutes](ht
tps://www.w3.org/2024/09/25-credential-threats-minutes.html)\n- [Session p
roposal on GitHub](https://github.com/w3c/tpac2024-breakouts/issues/98)
STATUS:CONFIRMED
CREATED:20240916T220350Z
LAST-MODIFIED:20241016T205850Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - Laguna
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:299bd998-7182-481e-8734-b7f263aff25a
DTSTAMP:20241016T222357Z
SUMMARY:New Features for the ServiceWorker Performance
DTSTART;TZID=America/Los_Angeles:20240925T111500
DTEND;TZID=America/Los_Angeles:20240925T121500
DESCRIPTION:https://www.w3.org/events/meetings/299bd998-7182-481e-8734-b7f2
63aff25a/\n\nThe session is going to be a presentation part and discussion
part.\n\n\nIn the [TPAC 2023 breakout](https://www.w3.org/events/meetings
/04625253-cec9-4c78-8c17-b1fea5c50d23/)\, the Google Chrome browser team s
hared recent efforts on [ServiceWorker](https://w3c.github.io/ServiceWorke
r/) and discussed potential opportunities for making ServiceWorker even fa
ster. This year\, we’d like to present a couple of updates from last yea
r\, including a newly shipped feature called [Static Routing API](https://
github.com/WICG/service-worker-static-routing-api)\, the new proposal exte
nding [Resource Timing API](https://github.com/WICG/service-worker-static-
routing-api/blob/main/resource-timing-api.md) for the Static Routing API\,
and some of future ideas like or [ServiceWorkerAutoPreload](https://githu
b.com/explainers-by-googlers/service-worker-auto-preload).\n\n\nFor the fi
rst half of the session\, we’re going to present performance problems ar
ound ServiceWorker and introduce new APIs and how it works. For the second
half\, we’d like to spend time on the discussion.\n\nAgenda\n\n**Chairs
:**\nShunya Shishido\, Keita Suzuki\n\n**Description:**\nThe session is go
ing to be a presentation part and discussion part.\n\n\nIn the [TPAC 2023
breakout](https://www.w3.org/events/meetings/04625253-cec9-4c78-8c17-b1fea
5c50d23/)\, the Google Chrome browser team shared recent efforts on [Servi
ceWorker](https://w3c.github.io/ServiceWorker/) and discussed potential op
portunities for making ServiceWorker even faster. This year\, we’d like
to present a couple of updates from last year\, including a newly shipped
feature called [Static Routing API](https://github.com/WICG/service-worker
-static-routing-api)\, the new proposal extending [Resource Timing API](ht
tps://github.com/WICG/service-worker-static-routing-api/blob/main/resource
-timing-api.md) for the Static Routing API\, and some of future ideas like
or [ServiceWorkerAutoPreload](https://github.com/explainers-by-googlers/s
ervice-worker-auto-preload).\n\n\nFor the first half of the session\, we
’re going to present performance problems around ServiceWorker and intro
duce new APIs and how it works. For the second half\, we’d like to spend
time on the discussion.\n\n**Goal(s):**\nThis session aims to discuss Ser
viceWorkers performance issues\, and how we can mitigate them. For the st
atic routing API (now it’s part of the ServiceWorker spec)\, we’d like
to hear browser vender status. For the other APIs that we’re proposing\
, we’d like to discuss and gather feedback from the community to make th
e standardization process forward.\n\n\n\n**Materials:**\n- [slides](https
://www.w3.org/2024/Talks/TPAC/breakouts/sw-for-performance.pdf)\n- [minute
s](https://www.w3.org/2024/09/25-serviceworkers-minutes.html)\n- [Session
proposal on GitHub](https://github.com/w3c/tpac2024-breakouts/issues/17)\n
\n**Track(s):**\n- Web Apps
STATUS:CONFIRMED
CREATED:20240916T214913Z
LAST-MODIFIED:20241016T222357Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:2 Ballroom Level - California B
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:5e346b27-9fdb-43cf-b323-0e9254b4b0ec
DTSTAMP:20241016T210023Z
SUMMARY:Purposeful Permissions - Adding data use information to permission
prompts
DTSTART;TZID=America/Los_Angeles:20240925T111500
DTEND;TZID=America/Los_Angeles:20240925T121500
DESCRIPTION:https://www.w3.org/events/meetings/5e346b27-9fdb-43cf-b323-0e92
54b4b0ec/\n\nToday’s web users often encounter permission prompts that l
ack context about why a website needs specific permissions and how the dat
a will be used. While developers strive to provide context\, the current a
pproach lacks structure and consistency across websites. This session will
explore options to add [purpose declarations](https://github.com/mikewest
/purposeful-permissions) or other trustworthy\, explainable contextual inf
ormation to a permission request to bridge this gap and bring users greate
r transparency on how their data is used.\n\nThe discussion will focus on:
\n- Use cases that might benefit or provide particular requirements for de
clarative contextual information\, including access to information from go
vernment-issued credentials.\n- The potential roles of different stakehold
ers\, including browser vendors\, developers\, and standardization bodies\
, in driving such an initiative forward.\n- Possible declaration options w
ith various granularity levels spanning from links to the privacy policy t
o a fully fledged label system for data types and purposes of use.\n- Key
challenges and opportunities in implementing purpose declarations for perm
ission-gated capabilities.\n\nAgenda\n\n**Chairs:**\nAlexandra Reimers\, N
ick Doty\, Serge Egelman\n\n**Description:**\nToday’s web users often en
counter permission prompts that lack context about why a website needs spe
cific permissions and how the data will be used. While developers strive t
o provide context\, the current approach lacks structure and consistency a
cross websites. This session will explore options to add [purpose declarat
ions](https://github.com/mikewest/purposeful-permissions) or other trustwo
rthy\, explainable contextual information to a permission request to bridg
e this gap and bring users greater transparency on how their data is used.
\n\nThe discussion will focus on:\n- Use cases that might benefit or provi
de particular requirements for declarative contextual information\, includ
ing access to information from government-issued credentials.\n- The poten
tial roles of different stakeholders\, including browser vendors\, develop
ers\, and standardization bodies\, in driving such an initiative forward.\
n- Possible declaration options with various granularity levels spanning f
rom links to the privacy policy to a fully fledged label system for data t
ypes and purposes of use.\n- Key challenges and opportunities in implement
ing purpose declarations for permission-gated capabilities.\n\n**Goal(s):*
*\n- Foster discussion and gather insights from various stakeholders on th
e development and implementation of permission purpose declarations.\n- De
scribe promising methods to provide purpose declarations and context for p
ermission requests and identify volunteers who want to explore them\, for
future incubation and research\, in credentials and other APIs.\n\n\n\n**M
aterials:**\n- [slides](https://www.w3.org/2024/Talks/TPAC/breakouts/purpo
seful-permissions.pdf)\n- [minutes](https://github.com/mikewest/purposeful
-permissions/blob/main/2024-09-25-TPAC-minutes.md)\n- [Session proposal on
GitHub](https://github.com/w3c/tpac2024-breakouts/issues/64)\n\n**Track(s
):**\n- Permissions
STATUS:CONFIRMED
CREATED:20240916T215725Z
LAST-MODIFIED:20241016T210023Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - Oceanside
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:4063788d-6e26-4d19-8898-d7ceb448fca9
DTSTAMP:20240925T180427Z
SUMMARY:Responsible Integration and New Use Cases of DNS Domain Names
DTSTART;TZID=America/Los_Angeles:20240925T111500
DTEND;TZID=America/Los_Angeles:20240925T121500
DESCRIPTION:https://www.w3.org/events/meetings/4063788d-6e26-4d19-8898-d7ce
b448fca9/\n\nDomain names have long been used as identifiers in applicatio
ns. In the early days of the Domain Name\nSystem (DNS)\, domain names were
associated with Teletype Network hosts\, File Transfer Protocol servers\,
\nand email services. Later\, they were adopted for web browsing.\n\nOver
the last several years\, many novel use cases have emerged that utilize do
main names. One such use\ncase is allowing a user to verify control of a d
omain name\, e.g.\, to show a verified badge on a profile as is\nseen with
GitHub organizations. Another use case is as a social media handle\, e.g.
\, as performed in Bluesky.\nBlockchains and other decentralized applicati
ons are yet another use case\, e.g.\, where a domain name may\nserve as a
reference to a digital wallet address as seen in the Ethereum Name Service
(ENS) or in various\nproposed Decentralized Identifiers (DID) methods.\n\
nWe propose naming the process of integrating and maintaining a domain nam
e into an application a DNS\nintegration. These integrations have benefits
\, such as allowing users to keep a consistent identifier across\ntheir we
bsite\, email\, and new application use cases. Another benefit is portabil
ity\, as users can opt into or\nout of integrations\, e.g.\, by changing w
hat DNS records are associated with their domain name.\n\nThis session wil
l raise awareness of DNS integrations\, the challenges they face\, and fac
ilitate discussions\naround how such challenges may be addressed. We will
also highlight our IETF draft for DNS integrations and\nseek feedback from
the community on additional topics to consider in this or future standard
s related work.\n\nAgenda\n\n**Chairs:**\nSwapneel Sheth\n\n**Description:
**\nDomain names have long been used as identifiers in applications. In th
e early days of the Domain Name\nSystem (DNS)\, domain names were associat
ed with Teletype Network hosts\, File Transfer Protocol servers\,\nand ema
il services. Later\, they were adopted for web browsing.\n\nOver the last
several years\, many novel use cases have emerged that utilize domain name
s. One such use\ncase is allowing a user to verify control of a domain nam
e\, e.g.\, to show a verified badge on a profile as is\nseen with GitHub o
rganizations. Another use case is as a social media handle\, e.g.\, as per
formed in Bluesky.\nBlockchains and other decentralized applications are y
et another use case\, e.g.\, where a domain name may\nserve as a reference
to a digital wallet address as seen in the Ethereum Name Service (ENS) or
in various\nproposed Decentralized Identifiers (DID) methods.\n\nWe propo
se naming the process of integrating and maintaining a domain name into an
application a DNS\nintegration. These integrations have benefits\, such a
s allowing users to keep a consistent identifier across\ntheir website\, e
mail\, and new application use cases. Another benefit is portability\, as
users can opt into or\nout of integrations\, e.g.\, by changing what DNS r
ecords are associated with their domain name.\n\nThis session will raise a
wareness of DNS integrations\, the challenges they face\, and facilitate d
iscussions\naround how such challenges may be addressed. We will also high
light our IETF draft for DNS integrations and\nseek feedback from the comm
unity on additional topics to consider in this or future standards related
work.\n\n**Goal(s):**\nRaise awareness of DNS integrations and seek feedb
ack for active standards work on providing guidance to applications that w
ant to provide a DNS integration\n\n\n**Agenda:**\nThe agenda will be two
parts.\nPart one will be a presentation to provide background context that
:\n\n- Walks through examples of DNS integrations and their use cases (soc
ial\, digital wallets\, identity\, etc.)\n- Explores why applications have
chosen to provide DNS integrations\n- Provides measurement results showin
g challenges that select DNS integrations face\n- Promotes awareness of ou
r IETF draft for DNS integrations and the topics it currently covers\n\nPa
rt two will be a discussion among participants about DNS integrations and
what additional topics or\nconcepts should be covered in the current IETF
draft or future standards work\, including at the W3C.\n\n**Materials:**\n
- [Session proposal on GitHub](https://github.com/w3c/tpac2024-breakouts/i
ssues/80)
STATUS:CONFIRMED
CREATED:20240916T220033Z
LAST-MODIFIED:20240925T180427Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - Huntington
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:17d0482c-06fa-4fab-8085-387a02dcce35
DTSTAMP:20241002T122454Z
SUMMARY:Simplifying the Updatable REC Process
DTSTART;TZID=America/Los_Angeles:20240925T111500
DTEND;TZID=America/Los_Angeles:20240925T121500
DESCRIPTION:https://www.w3.org/events/meetings/17d0482c-06fa-4fab-8085-387a
02dcce35/\n\nJoin us at the W3C TPAC 2024 Tech Plenary to address the chal
lenges and potential solutions for the updatable REC process. We'll focus
on the issues outlined in [issue #866](https://github.com/w3c/process/issu
es/866) and collaborate on making the process more efficient.\n\n**Core Ch
allenges:**\n1. **Complex Manual Markup:** The requirement for detailed ma
nual markup (e.g.\, ``\, ``\, specific classes) is time-consumin
g and prone to errors\, frustrating many editors.\n2. **Detailed Change Tr
acking:** Extensive documentation and linking for each change add unnecess
ary overhead\, often leading to mistakes and confusion.\n3. **Inflexible C
lass System:** The rigid classification system complicates the editing pro
cess and increases the potential for errors.\n\n**Proposed Alternatives:**
\n- **Enhanced Automated Tooling:** Develop tools that automatically gener
ate the necessary markup from simpler inputs\, reducing the manual burden
on editors.\n- **Streamline the Existing Process:** Simplify the current m
arkup requirements to lower the entry barrier and reduce the time spent on
updates.\n- **Educational Support:** Increase training and support for ed
itors to improve efficiency and understanding of the process.\n\n**Additio
nal Strategic Alternatives:**\n- **Discontinue the Updatable REC Process:*
* Consider phasing out the current process in favor of something that alig
ns better with the working realities of editors while maintaining necessar
y IPR protections.\n- **Discourage Use of the Current Process:** Officiall
y recommend that the current updatable REC process be used only when absol
utely necessary due to its complexity and high overhead.\n- **Introduce a
'Living Recommendation' Model:** Adopt a model similar to the WHATWG livin
g standards\, allowing for continuous updates without detailed version tra
cking and complex markup. But we do it in manner that meets W3C assurances
and requirements.\n\nAgenda\n\n**Chairs:**\nMarcos Caceres\n\n**Descripti
on:**\nJoin us at the W3C TPAC 2024 Tech Plenary to address the challenges
and potential solutions for the updatable REC process. We'll focus on the
issues outlined in [issue #866](https://github.com/w3c/process/issues/866
) and collaborate on making the process more efficient.\n\n**Core Challeng
es:**\n1. **Complex Manual Markup:** The requirement for detailed manual m
arkup (e.g.\, ``\, ``\, specific classes) is time-consuming and
prone to errors\, frustrating many editors.\n2. **Detailed Change Tracking
:** Extensive documentation and linking for each change add unnecessary ov
erhead\, often leading to mistakes and confusion.\n3. **Inflexible Class S
ystem:** The rigid classification system complicates the editing process a
nd increases the potential for errors.\n\n**Proposed Alternatives:**\n- **
Enhanced Automated Tooling:** Develop tools that automatically generate th
e necessary markup from simpler inputs\, reducing the manual burden on edi
tors.\n- **Streamline the Existing Process:** Simplify the current markup
requirements to lower the entry barrier and reduce the time spent on updat
es.\n- **Educational Support:** Increase training and support for editors
to improve efficiency and understanding of the process.\n\n**Additional St
rategic Alternatives:**\n- **Discontinue the Updatable REC Process:** Cons
ider phasing out the current process in favor of something that aligns bet
ter with the working realities of editors while maintaining necessary IPR
protections.\n- **Discourage Use of the Current Process:** Officially reco
mmend that the current updatable REC process be used only when absolutely
necessary due to its complexity and high overhead.\n- **Introduce a 'Livin
g Recommendation' Model:** Adopt a model similar to the WHATWG living stan
dards\, allowing for continuous updates without detailed version tracking
and complex markup. But we do it in manner that meets W3C assurances and r
equirements.\n\n**Goal(s):**\nImprove process and tooling\n\n\n\n**Materia
ls:**\n- [minutes](https://www.w3.org/2024/09/25-updatable-rec-minutes.htm
l)\n- [Session proposal on GitHub](https://github.com/w3c/tpac2024-breakou
ts/issues/11)\n\n**Track(s):**\n- Standards
STATUS:CONFIRMED
CREATED:20240916T214800Z
LAST-MODIFIED:20241002T122454Z
SEQUENCE:1
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
BEGIN:VEVENT
UID:b0386acd-cd59-409c-83d1-88323094dcac
DTSTAMP:20241002T123140Z
SUMMARY:Web Components & ARIA
DTSTART;TZID=America/Los_Angeles:20240925T111500
DTEND;TZID=America/Los_Angeles:20240925T121500
DESCRIPTION:https://www.w3.org/events/meetings/b0386acd-cd59-409c-83d1-8832
3094dcac/\n\nSession to discuss ARIA and web components:\nhttps://github.c
om/WICG/webcomponents/blob/gh-pages/proposals/reference-target-explainer.m
d\n\nAgenda\n\n**Chairs:**\nRyosuke Niwa\n\n**Description:**\nSession to d
iscuss ARIA and web components:\nhttps://github.com/WICG/webcomponents/blo
b/gh-pages/proposals/reference-target-explainer.md\n\n**Goal(s):**\nConcre
te proposal for ARIA across shadow trees\n\n\n\n**Materials:**\n- [minutes
](https://www.w3.org/2024/09/25-webcomponents-minutes.html#t02)\n- [Sessio
n proposal on GitHub](https://github.com/w3c/tpac2024-breakouts/issues/30)
\n\n**Track(s):**\n- Web Components
STATUS:CONFIRMED
CREATED:20240916T215056Z
LAST-MODIFIED:20241002T123140Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:-1 Lower Level - Catalina 3
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:90030c25-9d89-4e3c-82f8-ef05200d73db
DTSTAMP:20241016T223651Z
SUMMARY:AI Model Management
DTSTART;TZID=America/Los_Angeles:20240925T131500
DTEND;TZID=America/Los_Angeles:20240925T141500
DESCRIPTION:https://www.w3.org/events/meetings/90030c25-9d89-4e3c-82f8-ef05
200d73db/\n\nAI models can be executed on the client web platform and can
add significant functionality to web applications. However\, they can al
so be quite large\, requiring significant resources to download and store.
Download and compilation latencies can potentially impact the user exper
ience.\n\nThis breakout will discuss ways in which these issues can be mit
igated. Possible topics include the following. \n\n- Background model
download and compilation.\n- Caching strategies\, including potential cros
s-site caching mechanisms with privacy-preserving mitigations\n- Model nam
ing and versioning\, allowing for model substitution when useful\n- Access
to both downloadable and pre-installed models with a common interface\n-
Storage deduplication\n- Model representation independence\n- API independ
ence (e.g. sharing models between WebNN and WebGPU implementations)\n- Off
line usage\, including interaction with PWAs.\n- Common models are lower p
rivacy risks \n\nNote: this is both an AI topic and a Storage topic. Inpu
t from both communities would be useful and is encouraged!\n\nThere were s
ome [related presentations](https://github.com/webmachinelearning/hybrid-a
i/tree/main/presentations) on this topic in the WebML IG.\n\nSee:\n\n- [Re
po](https://github.com/webmachinelearning/hybrid-ai/) - Please direct foll
owup there\, and to the WebML WG\n\nAgenda\n\n**Chairs:**\nMichael McCool\
n\n**Description:**\nAI models can be executed on the client web platform
and can add significant functionality to web applications. However\, the
y can also be quite large\, requiring significant resources to download an
d store. Download and compilation latencies can potentially impact the us
er experience.\n\nThis breakout will discuss ways in which these issues ca
n be mitigated. Possible topics include the following. \n\n- Backgroun
d model download and compilation.\n- Caching strategies\, including potent
ial cross-site caching mechanisms with privacy-preserving mitigations\n- M
odel naming and versioning\, allowing for model substitution when useful\n
- Access to both downloadable and pre-installed models with a common inter
face\n- Storage deduplication\n- Model representation independence\n- API
independence (e.g. sharing models between WebNN and WebGPU implementations
)\n- Offline usage\, including interaction with PWAs.\n- Common models are
lower privacy risks \n\nNote: this is both an AI topic and a Storage topi
c. Input from both communities would be useful and is encouraged!\n\nTher
e were some [related presentations](https://github.com/webmachinelearning/
hybrid-ai/tree/main/presentations) on this topic in the WebML IG.\n\nSee:\
n\n- [Repo](https://github.com/webmachinelearning/hybrid-ai/) - Please dir
ect followup there\, and to the WebML WG\n\n**Goal(s):**\nPrioritize issue
s\, discuss highest priority issues\, define follow-up actions if possible
.\n\n\n**Agenda:**\n1. Review list of issues and add or refine any if nece
ssary (5m)\n2. Prioritize issues\, identify shortlist for discussion (10m)
\n3. Discuss potential solutions to high-priority issues (approx 15m each)
\n - Expand explanation of each issue\, identify stakeholders\n
- Discuss possible resolutions \n - Define followup actions and colla
borations\n\n**Materials:**\n- [slides](https://www.w3.org/2024/Talks/TPAC
/breakouts/ai-model-management.pdf)\n- [minutes](https://www.w3.org/2024/0
9/25-ai-model-minutes.html)\n- [Session proposal on GitHub](https://github
.com/w3c/tpac2024-breakouts/issues/15)\n\n**Track(s):**\n- AI
STATUS:CONFIRMED
CREATED:20240916T214850Z
LAST-MODIFIED:20241016T223651Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:2 Ballroom Level - California A
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:e75479d6-b578-4565-bd53-4f30a259726e
DTSTAMP:20241106T183538Z
SUMMARY:An Individual Differential Privacy Framework for Rigorous and High-
Utility Privacy Accounting in Web Measurement
DTSTART;TZID=America/Los_Angeles:20240925T131500
DTEND;TZID=America/Los_Angeles:20240925T141500
DESCRIPTION:https://www.w3.org/events/meetings/e75479d6-b578-4565-bd53-4f30
a259726e/\n\n@bmcase and I\, along with several differential privacy resea
rchers\, have developed a compelling privacy framework where each device t
racks and controls the privacy loss incurred by the user’s participation
in various measurements\, such as advertising\, engagement\, or mobility
analytics. Currently\, these measurements require collecting sensitive use
r activity traces (e.g.\, visited sites\, purchases)\, which raises privac
y concerns. Our framework proposes a privacy-preserving alternative: the d
evice tracks activity locally and generates encrypted reports\, which can
be aggregated by a trusted execution engine (TEE) or secure multi-party co
mputation system.\n\nWe formalize our framework using *individual differen
tial privacy*\, allowing each device to account for and constrain their ow
n user’s privacy loss toward each measurement party. This approach offer
s significant privacy-utility benefits over traditional models and improve
s transparency by letting users monitor their privacy on each device. Howe
ver\, it also introduces potential biases in measurement results\, which w
e are working to address\, but for whose design we require the community
’s input.\n\nAt the breakout\, we thus plan to:\n1. Present our privacy
framework\, which we developed initially for advertising measurement use c
ases.\n2. Seek community feedback on applying the framework to other domai
ns\, as we believe our framework is much more general.\n3. Discuss strateg
ies to mitigate bias introduced by individual privacy tracking.\n\nAn acad
emic paper describing our privacy framework can be found [here](https://ar
xiv.org/abs/2405.16719).\n\nAgenda\n\n**Chairs:**\nRoxana Geambasu\, Benja
min Case\n\n**Description:**\n@bmcase and I\, along with several different
ial privacy researchers\, have developed a compelling privacy framework wh
ere each device tracks and controls the privacy loss incurred by the user
’s participation in various measurements\, such as advertising\, engagem
ent\, or mobility analytics. Currently\, these measurements require collec
ting sensitive user activity traces (e.g.\, visited sites\, purchases)\, w
hich raises privacy concerns. Our framework proposes a privacy-preserving
alternative: the device tracks activity locally and generates encrypted re
ports\, which can be aggregated by a trusted execution engine (TEE) or sec
ure multi-party computation system.\n\nWe formalize our framework using *i
ndividual differential privacy*\, allowing each device to account for and
constrain their own user’s privacy loss toward each measurement party. T
his approach offers significant privacy-utility benefits over traditional
models and improves transparency by letting users monitor their privacy on
each device. However\, it also introduces potential biases in measurement
results\, which we are working to address\, but for whose design we requi
re the community’s input.\n\nAt the breakout\, we thus plan to:\n1. Pres
ent our privacy framework\, which we developed initially for advertising m
easurement use cases.\n2. Seek community feedback on applying the framewor
k to other domains\, as we believe our framework is much more general.\n3.
Discuss strategies to mitigate bias introduced by individual privacy trac
king.\n\nAn academic paper describing our privacy framework can be found [
here](https://arxiv.org/abs/2405.16719).\n\n**Goal(s):**\nTo present our i
ndividual differential privacy framework for web measurements\, gather com
munity feedback on extending its application beyond advertising\, and expl
ore strategies for addressing challenges like bias in measurement results.
\n\n\n**Agenda:**\nOutline:\n- Background on ad measurements and emerging
APIs\n- Our privacy framework: Cookie Monster\n- Discussion on broader app
lications and bias mitigation\n\n**Materials:**\n- [slides](https://www.w3
.org/2024/Talks/TPAC/breakouts/differential-privacy.pdf)\n- [minutes](http
s://www.w3.org/2024/09/breakouts/minutes-95.html)\n- [minutes (initial goo
gle doc)](https://docs.google.com/document/d/1-U3VfLRd7EtXlQvt4Z_jqIgzE82o
FrWTcnFeviXjwmM/edit#heading=h.fcwl9ktndbpo)\n- [Session proposal on GitHu
b](https://github.com/w3c/tpac2024-breakouts/issues/95)
STATUS:CONFIRMED
CREATED:20240916T220317Z
LAST-MODIFIED:20241106T183538Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - Huntington
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:d082997c-5b83-49ad-859b-eee091816964
DTSTAMP:20241106T183511Z
SUMMARY:Camera Effects Coordination
DTSTART;TZID=America/Los_Angeles:20240925T131500
DTEND;TZID=America/Los_Angeles:20240925T141500
DESCRIPTION:https://www.w3.org/events/meetings/d082997c-5b83-49ad-859b-eee0
91816964/\n\nReal-time effects applied to camera input such as background
blur\, face framing\, and lighting correction are becoming more available
to users through their operating systems\, browsers\, and other software c
omponents. These effects manipulate camera input before it reaches Web ap
plications via [`getUserMedia()`](https://developer.mozilla.org/en-US/docs
/Web/API/MediaDevices/getUserMedia). \n\nWeb applications that want to us
e camera input (and possibly apply their own effects) need know when effec
ts are applied and respond accordingly.\n \nBackground:\n- [Explainer with
alternative API shape](https://github.com/markafoltz/camera-effects) \n-
https://w3c.github.io/mediacapture-main/getusermedia.html#def-constraint-b
ackgroundBlur\n\nAgenda\n\n**Chairs:**\nMark Foltz\n\n**Description:**\nRe
al-time effects applied to camera input such as background blur\, face fra
ming\, and lighting correction are becoming more available to users throug
h their operating systems\, browsers\, and other software components. The
se effects manipulate camera input before it reaches Web applications via
[`getUserMedia()`](https://developer.mozilla.org/en-US/docs/Web/API/MediaD
evices/getUserMedia). \n\nWeb applications that want to use camera input
(and possibly apply their own effects) need know when effects are applied
and respond accordingly.\n \nBackground:\n- [Explainer with alternative AP
I shape](https://github.com/markafoltz/camera-effects) \n- https://w3c.git
hub.io/mediacapture-main/getusermedia.html#def-constraint-backgroundBlur\n
\n**Goal(s):**\nReview current work\, community discussion to gather feedb
ack\n\n\n**Agenda:**\nThis a WIP and will be updated before the session be
gins.\n\n- How should we coordinate behaviors between applications that co
nsume camera input and platforms that want to enhance camera input through
effects?\n- Review how camera effects are currently exposed to script \n-
Suggest possible improvements \n- (If time) Applicability to browser and
OS audio effects\n- Questions and discussion\n\n**Materials:**\n- [slides
- web viewer](https://docs.google.com/presentation/d/1Y2AlO7j9GhYJdUCM1-dJ
gD8EP1qXB8jDtM9HWtOJWQE/pub?start=false&loop=false&delayms=5000)\n- [slide
s - pdf](https://www.w3.org/2024/Talks/TPAC/breakouts/camera-effects.pdf)\
n- [minutes](https://www.w3.org/2024/09/breakouts/minutes-94.html)\n- [min
utes (initial google doc)](https://docs.google.com/document/d/1c7KUet5SUDp
3ZjM7T95tc-cqL77PihD9js1Dpf6Yv_4/edit?usp=sharing)\n- [Session proposal on
GitHub](https://github.com/w3c/tpac2024-breakouts/issues/94)
STATUS:CONFIRMED
CREATED:20240916T220259Z
LAST-MODIFIED:20241106T183511Z
SEQUENCE:4
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - Oceanside
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:fccf73f3-01fc-424f-9106-a005bfc21ad5
DTSTAMP:20241002T134454Z
SUMMARY:Compression: Brotli Support
DTSTART;TZID=America/Los_Angeles:20240925T131500
DTEND;TZID=America/Los_Angeles:20240925T141500
DESCRIPTION:https://www.w3.org/events/meetings/fccf73f3-01fc-424f-9106-a005
bfc21ad5/\n\nThe session is on discussing open issues with adding Brotli t
o the Compression spec.\n\nAgenda\n\n**Chairs:**\nBrandon Stewart\n\n**Des
cription:**\nThe session is on discussing open issues with adding Brotli t
o the Compression spec.\n\n**Goal(s):**\nAim to discuss open issues with B
rotli support in the Compression spec.\n\n\n\n**Materials:**\n- [minutes](
https://www.w3.org/2024/09/25-brotli-minutes.html)\n- [Session proposal on
GitHub](https://github.com/w3c/tpac2024-breakouts/issues/72)
STATUS:CONFIRMED
CREATED:20240916T215902Z
LAST-MODIFIED:20241002T134454Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - Capistrano
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:99b6da9b-7e68-45f8-bd5f-cdc0df7189bd
DTSTAMP:20240925T165959Z
SUMMARY:Context for credentials and other permissions
DTSTART;TZID=America/Los_Angeles:20240925T131500
DTEND;TZID=America/Los_Angeles:20240925T141500
DESCRIPTION:https://www.w3.org/events/meetings/99b6da9b-7e68-45f8-bd5f-cdc0
df7189bd/\n\nWill be combined with [Purposeful Permissions - Adding data u
se information to permission prompts](https://www.w3.org/events/meetings/5
e346b27-9fdb-43cf-b323-0e9254b4b0ec/)\n\nAgenda\n\n**Chairs:**\nNick Doty\
n\n**Description:**\nIn presenting government-issued credentials or making
other significant permission decisions\, users need more information abou
t how their data will be used. This session will discuss potential changes
to the Web platform to give additional info on how and why a permission w
ill be used. Everyone welcome\, especially people working on credentials\,
permissions and privacy on the Web.\n\nWe have long struggled with how th
e Web platform can design permissions requests so that users can make info
rmed decisions about granting access. Today\, users rarely have the inform
ation that they need to understand how a granted permission will be used o
r what will happen with their data\, and they often either ignore a flood
of requests or shrug and grant them to get them to go away. This is not on
ly bad for user privacy but also for site developers who want to use these
capabilities. Good practices exist but aren’t often encouraged or enabl
ed by the design of the Web platform. Permissions requests that go across
devices or between apps (like to a wallet) add further challenges.\n\nIn t
his session\, we will consider a few of the options – enums\, purpose st
rings\, well-known files\, surrounding Web context. What would be needed t
o add trustworthy\, explainable contextual information to a permission req
uest using these or other methods? The example of asking for information f
rom a government-issued credential will be a key case study\, but we can a
lso consider how other APIs could take advantage of additional context.\n\
n**Goal(s):**\nDescribing promising methods to provide context for permiss
ion requests and identifying volunteers who want to explore them\, for fut
ure incubation and experimentation\, in credentials and other APIs.\n\n\n\
n**Materials:**\n- [Session proposal on GitHub](https://github.com/w3c/tpa
c2024-breakouts/issues/77)\n\n**Track(s):**\n- Permissions
STATUS:CANCELLED
CREATED:20240916T215954Z
LAST-MODIFIED:20240925T165959Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:-1 Lower Level - Catalina 6
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:14174caa-7eee-414c-bafa-ef7053e32b39
DTSTAMP:20241002T122527Z
SUMMARY:Digital Wallet Project in Taiwan
DTSTART;TZID=America/Los_Angeles:20240925T131500
DTEND;TZID=America/Los_Angeles:20240925T141500
DESCRIPTION:https://www.w3.org/events/meetings/14174caa-7eee-414c-bafa-ef70
53e32b39/\n\nThe Ministry of Digital Affairs (moda) from Taiwan government
\, has initiated a four-year (2024-2027) project\, aiming to build a permi
ssionless infrastructure that secures digital identity.\n\nThe digital wal
let project will build digital civic infrastructure of issuer\, wallet\, a
nd verifier based on the standards of W3C Decentralized Identifiers (DID)
and Verifiable Credentials (VC). It features:\n\n1. Public Money\, Public
Code: The software parts will be licensed as open source software to the p
ublic.\n2. Open Ecosystem: To expand use cases\, we welcome everyone to be
come an issuer\, wallet\, or verifier provider to meet any market needs.\n
3. Sandbox Environment: we aim to maintain a testing playground for variou
s needs starting in 2025. If you’re interested in joining\, please send
an email to our contacts.\n\nWe will also hold a bi-monthly Technical Advi
sory Meeting for discussing related technical issues\, trusted registry an
d its trust model.\n\nAgenda\n\n**Chairs:**\nDenken Chen\n\n**Description:
**\nThe Ministry of Digital Affairs (moda) from Taiwan government\, has in
itiated a four-year (2024-2027) project\, aiming to build a permissionless
infrastructure that secures digital identity.\n\nThe digital wallet proje
ct will build digital civic infrastructure of issuer\, wallet\, and verifi
er based on the standards of W3C Decentralized Identifiers (DID) and Verif
iable Credentials (VC). It features:\n\n1. Public Money\, Public Code: The
software parts will be licensed as open source software to the public.\n2
. Open Ecosystem: To expand use cases\, we welcome everyone to become an i
ssuer\, wallet\, or verifier provider to meet any market needs.\n3. Sandbo
x Environment: we aim to maintain a testing playground for various needs s
tarting in 2025. If you’re interested in joining\, please send an email
to our contacts.\n\nWe will also hold a bi-monthly Technical Advisory Meet
ing for discussing related technical issues\, trusted registry and its tru
st model.\n\n**Goal(s):**\nFor anyone contributing in the W3C DID and VC e
cosystem\, we welcome any cooperation opportunities ranging from software
interoperability\, DID/VC use cases\, and international standards developm
ent and collaboration initiatives.\n\n\n**Agenda:**\nThe Ministry of Digit
al Affairs (moda) from Taiwan government\, has started building a permissi
onless infrastructure that secures digital identity.\n\n1. Project Overvie
w\n2. Collaboration Opportunities\n\n**Materials:**\n- [minutes](https://w
ww.w3.org/2024/09/25-digital-wallet-taiwan-minutes.html)\n- [Session propo
sal on GitHub](https://github.com/w3c/tpac2024-breakouts/issues/97)\n\n**T
rack(s):**\n- Wallets
STATUS:CONFIRMED
CREATED:20240916T220339Z
LAST-MODIFIED:20241002T122527Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:-1 Lower Level - Catalina 5
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:48bc46a0-adca-421e-86de-85cb2fde8ccb
DTSTAMP:20241002T124519Z
SUMMARY:Discuss: How to build a new feature for the web platform — and ma
ke it a success with developers
DTSTART;TZID=America/Los_Angeles:20240925T131500
DTEND;TZID=America/Los_Angeles:20240925T141500
DESCRIPTION:https://www.w3.org/events/meetings/48bc46a0-adca-421e-86de-85cb
2fde8ccb/\n\nThe goal of this session is to explore and discuss how to bes
t get new features for the platform successfully created\, implemented\, t
ested\, documented\, and adopted — likely with active participation in t
he session from some people who’ve had experience in each of those areas
and who can offer particular “lessons learned” insights and tips. Als
o:\n\n- documenting the process/advice (brainstorming\, with the goal of w
riting something up from the session notes)\n- discussing ways in which th
e existing process might be improved\n- answering questions about parts of
the process that may be especially mysterious to most people\n\nAgenda\n\
n**Chairs:**\nMichael[tm] Smith (sideshowbarker)\n\n**Description:**\nThe
goal of this session is to explore and discuss how to best get new feature
s for the platform successfully created\, implemented\, tested\, documente
d\, and adopted — likely with active participation in the session from s
ome people who’ve had experience in each of those areas and who can offe
r particular “lessons learned” insights and tips. Also:\n\n- documenti
ng the process/advice (brainstorming\, with the goal of writing something
up from the session notes)\n- discussing ways in which the existing proces
s might be improved\n- answering questions about parts of the process that
may be especially mysterious to most people\n\n**Goal(s):**\nThe session
goal is to _discuss_ and help each other understand how to successfully ge
t new features into the platform.\n\n\n**Agenda:**\nThis session aims to a
very interactive **_discussion_ session**\, along the [“How to facilita
te a breakout discussion”](https://gist.github.com/spectranaut/d000bcc29
7005c262b711c117c770b22) guidelines.\n\nSo when you come to the session\,
please be prepared to _discuss_ — with the discussion we all have togeth
er being guided by the following _“How to build a new feature for the we
b platform”_ outline:\n\n_11-step process (zero-indexed\, in hex):_\n\n0
. Describing the problem: What specific problem are you trying to solve. W
ho are you trying to solve it for?\n1. Proposing a solution\; writing a go
od explainer with a problem description + proposed solution (**optional/`T
ODO` step**)\n2. Initiating and leading a focused discussion in a spec iss
ue tracker about the problem and possible solutions.\n3. Putting together
a spec or spec PR for a problem solution (and learning spec-publishing too
ls and their quirks).\n4. Writing good WPTs and getting attention for them
from reviewers.\n5. Using browser-project bug/issue trackers to raise com
pelling implementation requests.\n6. Contributing an implementation patch
to a browser project (and learning the project’s patch-contribution proc
ess).\n7. Getting documentation written for your feature in MDN (working
with MDN writers/editors and technical reviewers).\n8. Driving web-develop
er adoption through outreach in places where web-developers pay attention.
\n9. Monitoring web-developer experience/success and identifying web-devel
oper pain points/frustrations.\n\n A. Iterating over each step as ne
eded (including\, going back to step #0 and repeating the who
le cycle)\n\n_＊ Common off-by-one error many folks make: starting at ste
p #1 (proposing solutions without first describing problems).
_\n\n**Resources**\n\n- [The history of focus-visible and inert](https://w
ww.igalia.com/chats/alice-and-rob) — success story\n- [LXJS 2013 - Domen
ic Denicola - How to win friends and influence standards bodies](https://w
ww.youtube.com/watch?v=hneN6aW-d9w)\n- [Hitchhiker's Guide to Web Standard
s // Dominic Farolino // CascadiaJS 2018](https://www.youtube.com/watch?v=
z2SbknMWtp0)\n- [Web Platform Contribution Guide](https://wpc.guide/)\n---
\n\n- [HTML Design Principles](https://www.w3.org/TR/html-design-principle
s/#toc) — the “ten commandments” of web-platform feature development
\n- [How to Win Friends and Influence People](https://archive.org/details/
bwb_KS-365-216/) — 1936 book by Dale Carnegie (pioneer “motivational s
peaker”)\n- [Tips for effective explainers](https://tag.w3.org/explainer
s/#tips-for-effective-explainers) — W3C Tag document\n- https://ian.hix
ie.ch/bible/handling-people — the secret sauce\n---\n- [`https://www.w3.
org/community/about/faq/#how-do-i-propose-a-group`](https://www.w3.org/com
munity/about/faq/#how-do-i-propose-a-group)\n- [`https://www.w3.org/commun
ity/about/faq/#how-do-we-publish-a-report`](https://www.w3.org/community/a
bout/faq/#how-do-we-publish-a-report)\n- https://www.w3.org/community/abou
t/tool/ • https://github.com/w3c-cg → `https://w3c-cg.github.io/my-
feature`\n---\n- [`https://wicg.io/#proposals`](https://wicg.io/#proposals
)\n- [`https://github.com/WICG/admin/#contributing-new-proposals`](https:/
/github.com/WICG/admin/#contributing-new-proposals)\n- https://github.com/
WICG/starter-kit\n---\n- [`https://whatwg.org/faq#adding-new-features`](ht
tps://whatwg.org/faq#adding-new-features)\n- https://whatwg.org/working-mo
de\n- https://whatwg.org/stages\n---\n- https://github.com/tc39/ecma402/bl
ob/main/CONTRIBUTING.md\n- https://tc39.es/process-document/\n---\n- https
://web-platform-tests.org/writing-tests/\n- https://github.com/tc39/test26
2/blob/main/CONTRIBUTING.md\n---\n- https://webkit.org/contributing-code/\
n- https://firefox-source-docs.mozilla.org/\n- https://chromium.googlesour
ce.com/chromium/src/+/refs/heads/main/docs/contributing.md\n---\n- https:/
/github.com/mdn/content/blob/main/CONTRIBUTING.md\n---\n\n**Materials:**\n
- [minutes](https://www.w3.org/2024/09/25-feature-success-minutes.html)\n-
[Session proposal on GitHub](https://github.com/w3c/tpac2024-breakouts/is
sues/7)\n\n**Track(s):**\n- Feature lifecycle
STATUS:CONFIRMED
CREATED:20240916T214708Z
LAST-MODIFIED:20241002T124519Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:-1 Lower Level - Catalina 1
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:2038644f-234d-4b8e-ba50-69535a4f2f7c
DTSTAMP:20240925T202234Z
SUMMARY:Harmonizing Identity-Related Web Platform APIs
DTSTART;TZID=America/Los_Angeles:20240925T131500
DTEND;TZID=America/Los_Angeles:20240925T141500
DESCRIPTION:https://www.w3.org/events/meetings/2038644f-234d-4b8e-ba50-6953
5a4f2f7c/\n\nThere are currently three active work streams for identity-re
lated Web Platform APIs in the W3C: the [Digital Credentials API (DC API)]
(https://wicg.github.io/digital-credentials/)\, [Federated Credential Mana
gement (FedCM)](https://w3c-fedid.github.io/FedCM/)\, and the [Web Authent
ication API (WebAuthn)](https://w3c.github.io/webauthn/).\n\nIn each of th
ese work streams\, there have been some common discussion items including
flexible but privacy preserving error codes\, selector experience and quer
y syntax\, conditionally mediated flows\, credential and user account iden
tifiers\, along with discussion around how these APIs should interact in t
he future (ex: requesting a VDC -or- an OIDC ID Token in one call). NOTE:
Payments will be out of scope for this discussion.\n\nThis breakout is int
ended to be a collaborative\, working session. The focus will be on gainin
g consensus on the more tactical items like errors codes and selectors\, w
ith some time at the end reserved for forward looking ideas.\n\nAgenda\n\n
**Chairs:**\nTim Cappalli\, Sam Goto\, Marcos Caceres\, Matthew Miller\n\n
**Description:**\nThere are currently three active work streams for identi
ty-related Web Platform APIs in the W3C: the [Digital Credentials API (DC
API)](https://wicg.github.io/digital-credentials/)\, [Federated Credential
Management (FedCM)](https://w3c-fedid.github.io/FedCM/)\, and the [Web Au
thentication API (WebAuthn)](https://w3c.github.io/webauthn/).\n\nIn each
of these work streams\, there have been some common discussion items inclu
ding flexible but privacy preserving error codes\, selector experience and
query syntax\, conditionally mediated flows\, credential and user account
identifiers\, along with discussion around how these APIs should interact
in the future (ex: requesting a VDC -or- an OIDC ID Token in one call). N
OTE: Payments will be out of scope for this discussion.\n\nThis breakout i
s intended to be a collaborative\, working session. The focus will be on g
aining consensus on the more tactical items like errors codes and selector
s\, with some time at the end reserved for forward looking ideas.\n\n**Goa
l(s):**\nThis breakout is intended to be a collaborative\, working session
. The focus will be on gaining consensus on the more tactical items like e
rrors codes and selectors\, with some time at the end reserved for forward
looking ideas.\n\n\n**Agenda:**\nhttps://docs.google.com/document/d/15IiQ
S0yPzWML3zRHGQ_JQ5xAO5bIgrcJE3sNdwrgSHk/\n\n**Materials:**\n- [Session pro
posal on GitHub](https://github.com/w3c/tpac2024-breakouts/issues/49)\n\n*
*Track(s):**\n- Identity
STATUS:CONFIRMED
CREATED:20240916T215406Z
LAST-MODIFIED:20240925T202234Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - Manhattan
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:09083118-ca0a-4347-9271-6adf7798c935
DTSTAMP:20241002T165501Z
SUMMARY:HTTPS for Local Networks
DTSTART;TZID=America/Los_Angeles:20240925T131500
DTEND;TZID=America/Los_Angeles:20240925T141500
DESCRIPTION:https://www.w3.org/events/meetings/09083118-ca0a-4347-9271-6adf
7798c935/\n\nIt is not possible to get a publicly trusted CA to sign a cer
tificate for a local domain (i.e. a non-publicly resolvable domain name su
ch as router.local\, printer.home\, 192.168.1.1\, etc)\, so currently rout
er configuration pages\, IoT devices\, media servers\, etc. have to either
: not use TLS\, rely on complicated workarounds\, or use self-signed certi
ficates and ask users to click through security warnings.\n\nThis session'
s goal is to explore potential solutions to this problem\, such as PAKE (P
assword-authenticated key exchange) and TOFU (trust on first use).\n\nTher
e was previously a [Community Group](https://www.w3.org/community/httpsloc
al/) dedicated to this problem\, but discussions seem to have stalled\, an
d the group was closed in 2023.\n\nAgenda\n\n**Chairs:**\nCarlos IbarraLop
ez\n\n**Description:**\nIt is not possible to get a publicly trusted CA to
sign a certificate for a local domain (i.e. a non-publicly resolvable dom
ain name such as router.local\, printer.home\, 192.168.1.1\, etc)\, so cur
rently router configuration pages\, IoT devices\, media servers\, etc. hav
e to either: not use TLS\, rely on complicated workarounds\, or use self-s
igned certificates and ask users to click through security warnings.\n\nTh
is session's goal is to explore potential solutions to this problem\, such
as PAKE (Password-authenticated key exchange) and TOFU (trust on first us
e).\n\nThere was previously a [Community Group](https://www.w3.org/communi
ty/httpslocal/) dedicated to this problem\, but discussions seem to have s
talled\, and the group was closed in 2023.\n\n**Goal(s):**\nDiscuss potent
ial ways HTTPS can be supported in local networks\n\n\n\n**Materials:**\n-
[minutes](https://www.w3.org/2024/09/HTTPSForLocalNetworks_2024-09-25.htm
l)\n- [Session proposal on GitHub](https://github.com/w3c/tpac2024-breakou
ts/issues/78)
STATUS:CONFIRMED
CREATED:20240916T220004Z
LAST-MODIFIED:20241002T165501Z
SEQUENCE:1
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
BEGIN:VEVENT
UID:cfd3443b-1348-44fc-9510-6ea5c8b25db1
DTSTAMP:20241002T122512Z
SUMMARY:Next actions for digital manga and comics
DTSTART;TZID=America/Los_Angeles:20240925T131500
DTEND;TZID=America/Los_Angeles:20240925T141500
DESCRIPTION:https://www.w3.org/events/meetings/cfd3443b-1348-44fc-9510-6ea5
c8b25db1/\n\nOver 10 years passed after EPUB based digital manga and comic
s have been delivered\, there are some issues for them.\n\nThis session ai
ms to discuss and collect issues\, such as the current situation for EPUB
based file format\, accessibility for manga contents\, format for scrolled
comics and so on.\n\nAgenda\n\n**Chairs:**\nShinya Takami\, Hadrien Garde
ur\n\n**Description:**\nOver 10 years passed after EPUB based digital mang
a and comics have been delivered\, there are some issues for them.\n\nThis
session aims to discuss and collect issues\, such as the current situatio
n for EPUB based file format\, accessibility for manga contents\, format f
or scrolled comics and so on.\n\n**Goal(s):**\nSharing the current situati
on and gathering issues\n\n\n**Agenda:**\n- Situation and issues for Manga
and Comics [25m]\n - in Japan\n - in Europe\n - in North America\n- S
tate of the art and next steps [30m]\n - Spread and Page\n - Bitmap vs H
TML/SVG\n - Accessibility\n - Scrolled Comics\n- Other topics for Manga
and Comics [5m]\n\n**Materials:**\n- [minutes](https://www.w3.org/2024/09/
25-manga-next-minutes.html)\n- [Session proposal on GitHub](https://github
.com/w3c/tpac2024-breakouts/issues/58)
STATUS:CONFIRMED
CREATED:20240916T215555Z
LAST-MODIFIED:20241002T122512Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - Laguna
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:19813be0-9902-4bad-8d50-3ad49ba792e6
DTSTAMP:20241002T122451Z
SUMMARY:Open styleable shadow tree and theming
DTSTART;TZID=America/Los_Angeles:20240925T131500
DTEND;TZID=America/Los_Angeles:20240925T141500
DESCRIPTION:https://www.w3.org/events/meetings/19813be0-9902-4bad-8d50-3ad4
9ba792e6/\n\nSession to discuss open styleable shadow tree and theming htt
ps://github.com/WICG/webcomponents/issues/909\n\nAgenda\n\n**Chairs:**\nRy
osuke Niwa\n\n**Description:**\nSession to discuss open styleable shadow t
ree and theming https://github.com/WICG/webcomponents/issues/909\n\n**Goal
(s):**\nCome up with a concrete proposal for open styleable shadow tree an
d theming\n\n\n\n**Materials:**\n- [minutes](https://www.w3.org/2024/09/25
-webcomponents-minutes.html)\n- [Session proposal on GitHub](https://githu
b.com/w3c/tpac2024-breakouts/issues/27)\n\n**Track(s):**\n- Web Components
STATUS:CONFIRMED
CREATED:20240916T215038Z
LAST-MODIFIED:20241002T122451Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:-1 Lower Level - Catalina 3
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:27699c89-3e19-40ed-9bed-9b5f137fc303
DTSTAMP:20241016T222459Z
SUMMARY:Sync on Web\, now and next of realtime media services on web
DTSTART;TZID=America/Los_Angeles:20240925T131500
DTEND;TZID=America/Los_Angeles:20240925T141500
DESCRIPTION:https://www.w3.org/events/meetings/27699c89-3e19-40ed-9bed-9b5f
137fc303/\n\nReal time Web is improving\, in this moment we have an abilit
y to build realtime media services on web w/ WebRTC\, WebCodecs\, Web Audi
o ... etc.\n\nIMO\, one interesting movement for this would be synchroniza
tion\, which means "time alignment". General case for "time alignment" wou
ld be lip-sync\, but with Media over QUIC\, mainly leveraging to WebCodes
and WebTransport\, we can develop more synchronization use cases with medi
a streaming and arbitrary time-related data. Examples would be synchroniza
tion of realtime text\, haptics\, midi events in co-watching or stream-med
ia play-out.\n\nWith this feature\, we believe that the potential of web w
ould be improving more and more\, since we can build Real/Virtual orchestr
ated services. Use cases would be meta verse\, live viewing with MIDI data
\, remote robot operation etc.\n\nFor these realtime use cases\, clock acc
uracy and frequency is quite important. And we have several questions for
this. For example\, `requestAnimationFrame()` is enough or not for the fut
ure use cases? In this breakout session\, we will discuss about these topi
c according to clock and sync on Web.\n\nAgenda\n\n**Chairs:**\nKensaku KO
MATSU\n\n**Description:**\nReal time Web is improving\, in this moment we
have an ability to build realtime media services on web w/ WebRTC\, WebCod
ecs\, Web Audio ... etc.\n\nIMO\, one interesting movement for this would
be synchronization\, which means "time alignment". General case for "time
alignment" would be lip-sync\, but with Media over QUIC\, mainly leveragin
g to WebCodes and WebTransport\, we can develop more synchronization use c
ases with media streaming and arbitrary time-related data. Examples would
be synchronization of realtime text\, haptics\, midi events in co-watching
or stream-media play-out.\n\nWith this feature\, we believe that the pote
ntial of web would be improving more and more\, since we can build Real/Vi
rtual orchestrated services. Use cases would be meta verse\, live viewing
with MIDI data\, remote robot operation etc.\n\nFor these realtime use cas
es\, clock accuracy and frequency is quite important. And we have several
questions for this. For example\, `requestAnimationFrame()` is enough or n
ot for the future use cases? In this breakout session\, we will discuss ab
out these topic according to clock and sync on Web.\n\n**Goal(s):**\nfigur
e out gap for sync on Web.\n\n\n**Agenda:**\n1. Presentations and demo\n2.
Discussion\n3. Wrap-up\n\n**Materials:**\n- [slides](https://www.w3.org/2
024/Talks/TPAC/breakouts/sync-on-web.pdf)\n- [minutes](https://www.w3.org/
2024/09/25-sync-on-web-minutes.html)\n- [Session proposal on GitHub](https
://github.com/w3c/tpac2024-breakouts/issues/54)\n\n**Track(s):**\n- Real-t
ime Web
STATUS:CONFIRMED
CREATED:20240916T215443Z
LAST-MODIFIED:20241016T222459Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:-1 Lower Level - Catalina 2
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:bf2f61ca-d86f-4fe6-b237-93466d5788b6
DTSTAMP:20241002T123501Z
SUMMARY:View transitions: a taste of the future
DTSTART;TZID=America/Los_Angeles:20240925T131500
DTEND;TZID=America/Los_Angeles:20240925T141500
DESCRIPTION:https://www.w3.org/events/meetings/bf2f61ca-d86f-4fe6-b237-9346
6d5788b6/\n\nThis is an opportunity to share the status of two future-look
ing enhancements that are in the long term pipeline for view transitions\,
and are in their early design phase:\n1. gesture-based view transitions:
using a preemptive navigation gesture (swipe) to trigger a view-transition
\n2. cross-origin view transitions: finding a secure way to allow a subset
of what's possible with view transitions to a navigation between two orig
ins that don't necessarily trust each other.\n\nAgenda\n\n**Chairs:**\nNoa
m Rosenthal\, Khushal Sagar\n\n**Description:**\nThis is an opportunity to
share the status of two future-looking enhancements that are in the long
term pipeline for view transitions\, and are in their early design phase:\
n1. gesture-based view transitions: using a preemptive navigation gesture
(swipe) to trigger a view-transition\n2. cross-origin view transitions: fi
nding a secure way to allow a subset of what's possible with view transiti
ons to a navigation between two origins that don't necessarily trust each
other.\n\n**Goal(s):**\nIntroduce the thinking behind the two future enhan
cement\, and gather early stage feedback\, pushback\, and hopefully enthus
iasm!\n\nSince these features touch on UX\, navigations\, performance and
security\, they could be of interest to people outside the CSS working gro
up.\n\n\n\n**Materials:**\n- [minutes](https://www.w3.org/2024/09/25-css-m
inutes.html#t01)\n- [Session proposal on GitHub](https://github.com/w3c/tp
ac2024-breakouts/issues/47)\n\n**Track(s):**\n- UX
STATUS:CONFIRMED
CREATED:20240916T215354Z
LAST-MODIFIED:20241002T123501Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - San Clemente
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:849a2a8e-07bc-4bca-9a8b-24995e3a15e1
DTSTAMP:20241002T122536Z
SUMMARY:W3C Sustainability meeting
DTSTART;TZID=America/Los_Angeles:20240925T131500
DTEND;TZID=America/Los_Angeles:20240925T141500
DESCRIPTION:https://www.w3.org/events/meetings/849a2a8e-07bc-4bca-9a8b-2499
5e3a15e1/\n\nThe Sustainability Community Group (CG) identified a number o
f [projects and work areas](https://www.w3.org/wiki/Sustainability#Work_Ar
eas) in its first meeting. Since then\, two things key things have happene
d: First\, the Sustainable Web Design CG has been forked off to its own [i
n-progress Interest Group charter](https://github.com/w3c/strategy/issues/
420) ([on w3c-ac-members member only link](https://lists.w3.org/Archives/M
ember/w3c-ac-members/2024JulSep/0045.html)) to focus on the Web Sustainabi
lity Guidelines. Thus this Sustainability meeting will focus on other area
s listed. Second\, the Ethical Web Principles (EWP) has been voted on by t
he W3C Advisory Committee\, and there were no objections to the [section o
n environmental sustainability](https://www.w3.org/TR/2024/NOTE-ethical-we
b-principles-20240813/#sustainable)\, which provides an excellent forward-
looking focus for a Sustainability CG meeting.\n\nAgenda\n\n**Chairs:**\nT
antek Çelik\n\n**Description:**\nThe Sustainability Community Group (CG)
identified a number of [projects and work areas](https://www.w3.org/wiki/S
ustainability#Work_Areas) in its first meeting. Since then\, two things ke
y things have happened: First\, the Sustainable Web Design CG has been for
ked off to its own [in-progress Interest Group charter](https://github.com
/w3c/strategy/issues/420) ([on w3c-ac-members member only link](https://li
sts.w3.org/Archives/Member/w3c-ac-members/2024JulSep/0045.html)) to focus
on the Web Sustainability Guidelines. Thus this Sustainability meeting wil
l focus on other areas listed. Second\, the Ethical Web Principles (EWP) h
as been voted on by the W3C Advisory Committee\, and there were no objecti
ons to the [section on environmental sustainability](https://www.w3.org/TR
/2024/NOTE-ethical-web-principles-20240813/#sustainable)\, which provides
an excellent forward-looking focus for a Sustainability CG meeting.\n\n**G
oal(s):**\nThe goal of this session is to discuss and pick a few of the Su
stainability CG work areas that are most directly and actionably aligned w
ith the EWP encouragement to “[endeavor not to do further harm to the en
vironment when we introduce new technologies to the web](https://www.w3.or
g/TR/2024/NOTE-ethical-web-principles-20240813/#sustainable)”\, and iden
tify goals and next steps towards those goals. For example\, expanding on
the Principles identified by the EWP\, and how to do a sustainability (s12
y) assessment of new and proposed technologies towards establishing a prac
tice of Sustainability Horizontal Reviews to build on W3C’s existing acc
essibility (a11y)\, internationalization (i18n)\, security\, and privacy h
orizontal reviews.\n\n**Attendance:**\nThis session is restricted to TPAC
registrants.\n\n**Agenda:**\nTo be added to https://www.w3.org/wiki/Sustai
nability if this session is approved.\n\n(Originally published at: https:/
/tantek.com/2024/260/b1/w3c-sustainability-meeting)\n\n**Materials:**\n- [
minutes](https://www.w3.org/2024/09/25-sustainability-minutes.html)\n- [Se
ssion proposal on GitHub](https://github.com/w3c/tpac2024-breakouts/issues
/100)
STATUS:CONFIRMED
CREATED:20240917T032002Z
LAST-MODIFIED:20241002T122536Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - Palos Verdes
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
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
BEGIN:VEVENT
UID:0f508bce-5002-49ba-a8e6-8c80037b9166
DTSTAMP:20241002T122508Z
SUMMARY:Why is it like this? Installed Web Apps - how they are built\, func
tion\, and struggle today.
DTSTART;TZID=America/Los_Angeles:20240925T131500
DTEND;TZID=America/Los_Angeles:20240925T141500
DESCRIPTION:https://www.w3.org/events/meetings/0f508bce-5002-49ba-a8e6-8c80
037b9166/\n\nInstalling web applications has been around for a while now\,
and common patterns\, requirements\, and problems have emerged. This pres
entation will go over these things with some case studies\, and hopes to i
nform future development of web platform functionality to provide a stable
\, non-flaky\, and functional platform for developers to create competitiv
e and rich user experiences.\n\nAgenda\n\n**Chairs:**\nDaniel Murphy\, Rei
lly Grant\n\n**Description:**\nInstalling web applications has been around
for a while now\, and common patterns\, requirements\, and problems have
emerged. This presentation will go over these things with some case studie
s\, and hopes to inform future development of web platform functionality t
o provide a stable\, non-flaky\, and functional platform for developers to
create competitive and rich user experiences.\n\n**Goal(s):**\nUnderstand
ing web app functionality\, structures\, problems\, and common gotchas tod
ay.\n\n\n**Agenda:**\nPresentation link: https://bit.ly/installed-web-app-
state-struggles-2024-presentation\nMinutes: https://www.w3.org/2024/09/25-
web-apps-struggle-minutes.html\n\n**Materials:**\n- [minutes](https://www.
w3.org/2024/09/25-web-apps-struggle-minutes.html)\n- [Session proposal on
GitHub](https://github.com/w3c/tpac2024-breakouts/issues/67)\n\n**Track(s)
:**\n- Web Apps
STATUS:CONFIRMED
CREATED:20240916T215754Z
LAST-MODIFIED:20241002T122508Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:2 Ballroom Level - California B
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:b059a6cc-ac2a-482b-a9e2-32f72c6beb60
DTSTAMP:20241016T205329Z
SUMMARY:Capture Prevention For Privacy Protection
DTSTART;TZID=America/Los_Angeles:20240925T144500
DTEND;TZID=America/Los_Angeles:20240925T154500
DESCRIPTION:https://www.w3.org/events/meetings/b059a6cc-ac2a-482b-a9e2-32f7
2c6beb60/\n\nCapturing of the screen\, window\, tab and even web elements
has made it very convenient for users to share information on the web. The
re have also been efforts to prevent or restrict capturing to reduce data
exfiltration\, e.g. in an enterprise environment\, or for content protecti
on. We'd like to review capture prevention use cases\, and discuss new per
spectives like user privacy\, e.g. to avoid accidental information leak.\n
\nAgenda\n\n**Chairs:**\nXiaohan Wang\n\n**Description:**\nCapturing of th
e screen\, window\, tab and even web elements has made it very convenient
for users to share information on the web. There have also been efforts to
prevent or restrict capturing to reduce data exfiltration\, e.g. in an en
terprise environment\, or for content protection. We'd like to review capt
ure prevention use cases\, and discuss new perspectives like user privacy\
, e.g. to avoid accidental information leak.\n\n**Goal(s):**\nCommunity di
scussion to gather interests\, ideas and feedback\n\n\n\n**Materials:**\n-
[slides](https://www.w3.org/2024/Talks/TPAC/breakouts/capture-prevention.
pdf)\n- [Session proposal on GitHub](https://github.com/w3c/tpac2024-break
outs/issues/91)
STATUS:CONFIRMED
CREATED:20240916T220221Z
LAST-MODIFIED:20241016T205329Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:-1 Lower Level - Catalina 1
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:f09dc033-201b-4806-b0a8-a2a852f2f146
DTSTAMP:20241002T122454Z
SUMMARY:Cloud Edge Client Coordination
DTSTART;TZID=America/Los_Angeles:20240925T144500
DTEND;TZID=America/Los_Angeles:20240925T154500
DESCRIPTION:https://www.w3.org/events/meetings/f09dc033-201b-4806-b0a8-a2a8
52f2f146/\n\nEnabling workload orchestration among central cloud\, edge cl
oud\, and clients has many useful use cases\, such as accelerating AI appl
ications\, streaming services\, and cloud gaming.\n\nHowever\, there is no
standardized mechanism for workload coordination and orchestration betwee
n central cloud\, edge cloud\, and clients\, which may hinder the interope
rability of the workload user\, cloud provider\, client-side OS\, and appl
ications.\n\nThis session will discuss the emerging new use cases and stan
dard gaps of cloud\, edge\, client coordination.\n\nAgenda\n\n**Chairs:**\
nDapeng(Max) Liu\, Michael McCool\n\n**Description:**\nEnabling workload o
rchestration among central cloud\, edge cloud\, and clients has many usefu
l use cases\, such as accelerating AI applications\, streaming services\,
and cloud gaming.\n\nHowever\, there is no standardized mechanism for work
load coordination and orchestration between central cloud\, edge cloud\, a
nd clients\, which may hinder the interoperability of the workload user\,
cloud provider\, client-side OS\, and applications.\n\nThis session will d
iscuss the emerging new use cases and standard gaps of cloud\, edge\, clie
nt coordination.\n\n**Goal(s):**\nGet feedback and discuss gaps in standar
ds today to realise the emerging use-cases.\n\n\n**Agenda:**\n1. Discuss e
merging use cases (AI model use case\, Home AI/IoT use case\, Cloud gaming
use case\; 10m)\n2. DEMO (EdgeRoutine\; 5m)\n3. Discuss and identify stan
dards gaps\n - list of standard gaps （25m）\n - prioritize identifi
ed standard gap (10m)\n - followup actions (10m)\n\n**Materials:**\n- [m
inutes](https://www.w3.org/2024/09/25-cloud-coordination-minutes.html)\n-
[Session proposal on GitHub](https://github.com/w3c/tpac2024-breakouts/iss
ues/39)
STATUS:CONFIRMED
CREATED:20240916T215238Z
LAST-MODIFIED:20241002T122454Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:-1 Lower Level - Catalina 2
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:4b0374bb-ddd5-40e9-ad3c-c69042883e34
DTSTAMP:20241002T130001Z
SUMMARY:CSS Modules
DTSTART;TZID=America/Los_Angeles:20240925T144500
DTEND;TZID=America/Los_Angeles:20240925T154500
DESCRIPTION:https://www.w3.org/events/meetings/4b0374bb-ddd5-40e9-ad3c-c690
42883e34/\n\nSession to discuss CSS modules and how they work with declara
tive shadow DOM:\nhttps://github.com/WICG/webcomponents/blob/gh-pages/prop
osals/css-modules-v1-explainer.md\n\nAgenda\n\n**Chairs:**\nRyosuke Niwa\n
\n**Description:**\nSession to discuss CSS modules and how they work with
declarative shadow DOM:\nhttps://github.com/WICG/webcomponents/blob/gh-pag
es/proposals/css-modules-v1-explainer.md\n\n**Goal(s):**\nConcrete proposa
l for CSS Module MVP\n\n\n\n**Materials:**\n- [minutes](https://www.w3.org
/2024/09/25-webcomponents-minutes.html)\n- [Session proposal on GitHub](ht
tps://github.com/w3c/tpac2024-breakouts/issues/29)\n\n**Track(s):**\n- Web
Components
STATUS:CONFIRMED
CREATED:20240916T215050Z
LAST-MODIFIED:20241002T130001Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:-1 Lower Level - Catalina 3
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:38e6f53c-458a-484e-b2f0-c85f7dd7d968
DTSTAMP:20241002T123548Z
SUMMARY:Enabling carousel design patterns in CSS
DTSTART;TZID=America/Los_Angeles:20240925T144500
DTEND;TZID=America/Los_Angeles:20240925T154500
DESCRIPTION:https://www.w3.org/events/meetings/38e6f53c-458a-484e-b2f0-c85f
7dd7d968/\n\nCarousels are an often used design pattern on the web. They a
re used in a variety of contexts\, from product listing pages to slideshow
like content. OpenUI has [explored a range of carousel designs](https://o
pen-ui.org/components/carousel.research/)\, showing that the specific layo
ut and appearance can vary dramatically. They are also provided by many fr
ameworks as components\, however implementing a carousel correctly is comp
licated and often results in inconsistent and sometimes inaccessible imple
mentations on the web today.\n\nThere are a [set of problems being solved
by carousels](https://css.oddbird.net/overflow/explainer/)\, which we beli
eve could be provided by a set of simple incremental CSS features\, allowi
ng developers to combine these CSS features to create the various designs
in a completely customizable fashion. CSS-only component libraries could b
e built to further simplify this process with an eventual built-in style s
imilar to customizable select.\n\nPrior discussions:\n- Carousel APIs gene
rally: https://github.com/w3c/csswg-drafts/issues/9745\n\nAgenda\n\n**Chai
rs:**\nRobert Flack\n\n**Description:**\nCarousels are an often used desig
n pattern on the web. They are used in a variety of contexts\, from produc
t listing pages to slideshow like content. OpenUI has [explored a range of
carousel designs](https://open-ui.org/components/carousel.research/)\, sh
owing that the specific layout and appearance can vary dramatically. They
are also provided by many frameworks as components\, however implementing
a carousel correctly is complicated and often results in inconsistent and
sometimes inaccessible implementations on the web today.\n\nThere are a [s
et of problems being solved by carousels](https://css.oddbird.net/overflow
/explainer/)\, which we believe could be provided by a set of simple incre
mental CSS features\, allowing developers to combine these CSS features to
create the various designs in a completely customizable fashion. CSS-only
component libraries could be built to further simplify this process with
an eventual built-in style similar to customizable select.\n\nPrior discus
sions:\n- Carousel APIs generally: https://github.com/w3c/csswg-drafts/iss
ues/9745\n\n**Goal(s):**\nShare planned feature set and demos. Discuss gap
s and plan how the related features should work.\n\n\n**Agenda:**\n1. Intr
oduction / update https://github.com/w3c/csswg-drafts/issues/9745\n2. Scro
ll markers https://github.com/w3c/csswg-drafts/issues/10720\n3. Inert http
s://github.com/w3c/csswg-drafts/issues/10711\n4. Limited fragmentainer sty
ling (e.g. columns) https://github.com/w3c/csswg-drafts/issues/10715\n5. S
croll buttons https://github.com/w3c/csswg-drafts/issues/10722\n6. Focus o
rder of the generated controls https://github.com/w3c/csswg-drafts/issues/
10912\n7. Active marker calculation https://github.com/w3c/csswg-drafts/is
sues/10917\n\n**Materials:**\n- [minutes](https://www.w3.org/2024/09/25-cs
s-minutes.html#t03)\n- [Session proposal on GitHub](https://github.com/w3c
/tpac2024-breakouts/issues/57)
STATUS:CONFIRMED
CREATED:20240916T215547Z
LAST-MODIFIED:20241002T123548Z
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
BEGIN:VEVENT
UID:98eb382b-0423-4959-a0ac-82617edcaf76
DTSTAMP:20241002T122521Z
SUMMARY:End-to-End Encryption (E2EE) on the Social Web
DTSTART;TZID=America/Los_Angeles:20240925T144500
DTEND;TZID=America/Los_Angeles:20240925T154500
DESCRIPTION:https://www.w3.org/events/meetings/98eb382b-0423-4959-a0ac-8261
7edcaf76/\n\nE2EE is useful in several key aspects of the Social Web (such
as private Direct Messages)\, as well as for backend storage in general.
Join us for a discussion of the Social Web E2EE roadmap and related specif
ications.\n\nAgenda\n\n**Chairs:**\nDmitri Zagidulin\n\n**Description:**\n
E2EE is useful in several key aspects of the Social Web (such as private D
irect Messages)\, as well as for backend storage in general. Join us for a
discussion of the Social Web E2EE roadmap and related specifications.\n\n
**Goal(s):**\nCommunity Discussion of E2EE Issues in the context of the So
cial Web\n\n\n\n**Materials:**\n- [minutes](https://www.w3.org/2024/09/25-
e2ee-minutes.html)\n- [Session proposal on GitHub](https://github.com/w3c/
tpac2024-breakouts/issues/89)
STATUS:CONFIRMED
CREATED:20240916T220205Z
LAST-MODIFIED:20241002T122521Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - Laguna
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:a9540089-cb3a-413b-966a-8c1034b31b11
DTSTAMP:20241002T114751Z
SUMMARY:Integrating UI components is too damn hard!
DTSTART;TZID=America/Los_Angeles:20240925T144500
DTEND;TZID=America/Los_Angeles:20240925T154500
DESCRIPTION:https://www.w3.org/events/meetings/a9540089-cb3a-413b-966a-8c10
34b31b11/\n\nThe vision of authors being able to drop components and UI li
braries into their pages and have things Just Work™ and look right (at l
east to a first order approximation) is still largely unrealized. Integrat
ing any UI component is incredibly laborious\, as it requires manually com
municating fine grained design tokens to every single component.\n\nThis [
Web Awesome](https://www.kickstarter.com/projects/fontawesome/web-awesome)
tutorial illustrates the problem perfectly: \n\nhttps://youtu.be/JhfYeXLf
WdI?si=vF3xRai2QrjabVFv&t=277\n\n\n\nAnd this is just for assigning a certain hue as the primary co
lor of a whole page — the effort is duplicated for every third-party UI
component that uses colors\, fonts\, measurements\, font sizes\, etc. Same
-party components can use the same naming convention to reduce effort\, bu
t that doesn't work for components from different entities.\n\nTo reduce i
ntegration effort\, we need to reduce the amount of information the host p
age needs to communicate about its design to each individual component. So
me avenues are:\n1. standardized ways to set design tokens (e.g. the page
’s primary color or serif font) in a way that can be read by other compo
nents\n2. ways to _derive_ tokens from core tokens (e.g. a light tint from
a primary color\, or the next smaller font size in a scale) to minimize h
ow many tokens need to be communicated.\n3. Ways for components to adopt a
nd repurpose page styles of existing (standard) elements\n4. ???\n\nAgenda
\n\n**Chairs:**\nLea Verou\, Keith Cirkel\n\n**Description:**\nThe vision
of authors being able to drop components and UI libraries into their pages
and have things Just Work™ and look right (at least to a first order ap
proximation) is still largely unrealized. Integrating any UI component is
incredibly laborious\, as it requires manually communicating fine grained
design tokens to every single component.\n\nThis [Web Awesome](https://www
.kickstarter.com/projects/fontawesome/web-awesome) tutorial illustrates th
e problem perfectly: \n\nhttps://youtu.be/JhfYeXLfWdI?si=vF3xRai2QrjabVFv&
t=277\n\n\n\nAnd this is
just for assigning a certain hue as the primary color of a whole page —
the effort is duplicated for every third-party UI component that uses colo
rs\, fonts\, measurements\, font sizes\, etc. Same-party components can us
e the same naming convention to reduce effort\, but that doesn't work for
components from different entities.\n\nTo reduce integration effort\, we n
eed to reduce the amount of information the host page needs to communicate
about its design to each individual component. Some avenues are:\n1. stan
dardized ways to set design tokens (e.g. the page’s primary color or ser
if font) in a way that can be read by other components\n2. ways to _derive
_ tokens from core tokens (e.g. a light tint from a primary color\, or the
next smaller font size in a scale) to minimize how many tokens need to be
communicated.\n3. Ways for components to adopt and repurpose page styles
of existing (standard) elements\n4. ???\n\n**Goal(s):**\nFlesh out ideas f
or potential directions\, see which are most viable in terms of I/E\n\n\n*
*Agenda:**\n1. Discuss requirements and potential directions\n2. Discuss r
elevant proposals:\n - https://github.com/w3c/csswg-drafts/issues/9992\n -
https://github.com/w3c/csswg-drafts/issues/9999\n - https://github.com/w3
c/csswg-drafts/issues/10452\n - https://github.com/w3c/csswg-drafts/issues
/9660\n - https://github.com/w3c/csswg-drafts/issues/10222\n - https://git
hub.com/w3c/csswg-drafts/issues/5900\n\n**Materials:**\n- [minutes](https:
//github.com/w3c/csswg-drafts/issues/10948#issuecomment-2375445066)\n- [Se
ssion proposal on GitHub](https://github.com/w3c/tpac2024-breakouts/issues
/92)\n\n**Track(s):**\n- Web Components
STATUS:CONFIRMED
CREATED:20240916T220237Z
LAST-MODIFIED:20241002T114751Z
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
BEGIN:VEVENT
UID:0b16a479-7aa3-48ec-a556-ec8b9aaac8c0
DTSTAMP:20241002T120833Z
SUMMARY:Let’s actually fix web notifications
DTSTART;TZID=America/Los_Angeles:20240925T144500
DTEND;TZID=America/Los_Angeles:20240925T154500
DESCRIPTION:https://www.w3.org/events/meetings/0b16a479-7aa3-48ec-a556-ec8b
9aaac8c0/\n\nWeb Notifications are often used as a channel for unwanted sp
am. Even when the notifications are initially wanted\, it can be difficult
for people to work out how to unsubscribe to their notification subscript
ions. The notifications permission grants never expire. It is also a commo
n observed pattern from some websites that they socially engineer people i
nto accepting the notification permission\, for example by withholding sit
e content or functionality until the permission is granted.\nIn this sessi
on we would like to propose and discuss potential alternatives for structu
rally solving the aforementioned issues. These include:\n\n#### 1: Make no
tifications not-promptable\nInstead of showing an interruptive pop-up when
websites request notification permission\, browsers could silently add a
settings row available to the user in secondary browser UI\, like so:\n\n<
img width="1303" alt="Group 2" src="https://github.com/user-attachments/as
sets/4320aafa-5fa5-4eda-ada2-65d80c967ed8">\n\nThen\, if the user wishes t
o subscribe to notifications from a website\, they can proactively navigat
e to the browser UI to turn this toggle on. The benefit of this solution i
s (even if websites socially engineer users to grant them notifications pe
rmission)\, through the act of navigating to browser UI to turn on notific
ations\, people inherently learn where to go to turn it off.\n\nThe drawba
cks here are centered on discoverability\, i.e.\, whether users will be ab
le to find how to grant notifications when they actually want them. Howeve
r\, given the current prevalence of unwanted notification prompts\, this m
ight be a tradeoff worth making.\n\n#### 2: Make default notifications beh
aviour require an open and active tab\n\nMost other permission types exist
ing today require the website to be in an open and active browser tab for
the capability to work. Notifications notably differs: it allows websites
to message people even if they close all tabs from that website. In some w
ays\, this is the point of the Web Push API.\n\nMaking the default notific
ation behaviour tied to whether tabs from that origin are open gives peopl
e an intuitive way to sample notifications from a site while it’s still
open\, and to silence these notifications if they are unwanted. For sites
that the user trusts highly\, they can “upgrade” the permission to inc
lude the ability to notify them even when tabs from that site are closed.
For installed web-apps\, the "upgraded" behaviour could be the default.\n\
n#### 3: Expire stale notification permissions\n\nCurrent decisions on not
ification permission prompts are permanent. The browser does not do any au
tomatic clean-up of stale notification subscriptions\, even if they are fr
om a site that the user has not interacted with for many years. \n\nClarif
ying the purpose of the Web Push and Web Notification APIs on a philosophi
cal level – amongst browser vendors as well as web developers – would
allow user agents to enable helpful notifications while curbing unwanted n
otifications. For example\, if we can agree that the purpose of notificati
ons is to inform users about content being changed on a site\, and in resp
onse\, users are expected to actually visit the sender origin within a rea
sonable time window (such as within a few months)\, user agents could expi
re permission grants outside that reasonable time window. It is an open qu
estion if there are legitimate in-the-wild use cases for notifications tha
t users only read\, never interact with\, nor do they ever visit the sendi
ng website again.\n\nAgenda\n\n**Chairs:**\nSerena Chen\, Balazs Engedy\n\
n**Description:**\nWeb Notifications are often used as a channel for unwan
ted spam. Even when the notifications are initially wanted\, it can be dif
ficult for people to work out how to unsubscribe to their notification sub
scriptions. The notifications permission grants never expire. It is also a
common observed pattern from some websites that they socially engineer pe
ople into accepting the notification permission\, for example by withholdi
ng site content or functionality until the permission is granted.\nIn this
session we would like to propose and discuss potential alternatives for s
tructurally solving the aforementioned issues. These include:\n\n#### 1: M
ake notifications not-promptable\nInstead of showing an interruptive pop-u
p when websites request notification permission\, browsers could silently
add a settings row available to the user in secondary browser UI\, like so
:\n\n\n\nThen\, if the user wi
shes to subscribe to notifications from a website\, they can proactively n
avigate to the browser UI to turn this toggle on. The benefit of this solu
tion is (even if websites socially engineer users to grant them notificati
ons permission)\, through the act of navigating to browser UI to turn on n
otifications\, people inherently learn where to go to turn it off.\n\nThe
drawbacks here are centered on discoverability\, i.e.\, whether users will
be able to find how to grant notifications when they actually want them.
However\, given the current prevalence of unwanted notification prompts\,
this might be a tradeoff worth making.\n\n#### 2: Make default notificatio
ns behaviour require an open and active tab\n\nMost other permission types
existing today require the website to be in an open and active browser ta
b for the capability to work. Notifications notably differs: it allows web
sites to message people even if they close all tabs from that website. In
some ways\, this is the point of the Web Push API.\n\nMaking the default n
otification behaviour tied to whether tabs from that origin are open gives
people an intuitive way to sample notifications from a site while it’s
still open\, and to silence these notifications if they are unwanted. For
sites that the user trusts highly\, they can “upgrade” the permission
to include the ability to notify them even when tabs from that site are cl
osed. For installed web-apps\, the "upgraded" behaviour could be the defau
lt.\n\n#### 3: Expire stale notification permissions\n\nCurrent decisions
on notification permission prompts are permanent. The browser does not do
any automatic clean-up of stale notification subscriptions\, even if they
are from a site that the user has not interacted with for many years. \n\n
Clarifying the purpose of the Web Push and Web Notification APIs on a phil
osophical level – amongst browser vendors as well as web developers –
would allow user agents to enable helpful notifications while curbing unwa
nted notifications. For example\, if we can agree that the purpose of noti
fications is to inform users about content being changed on a site\, and i
n response\, users are expected to actually visit the sender origin within
a reasonable time window (such as within a few months)\, user agents coul
d expire permission grants outside that reasonable time window. It is an o
pen question if there are legitimate in-the-wild use cases for notificatio
ns that users only read\, never interact with\, nor do they ever visit the
sending website again.\n\n**Goal(s):**\nShare and discuss solutions to cu
rb spammy and abusive notifications on the web\, and to help users exert b
etter control over their notifications. Identify points of consensus and p
oints of contention. Identify open questions to be answered to sort out po
ints of contention. Identify practical next steps to improve Web Notificat
ions.\n\n\n**Agenda:**\n1. Intro: Web Push Notifications problem space\n2.
Potential solutions + discussion\n i. Make notifications not-promptable\
n ii. Notifications to require open tab\n iii. Expiry for notification g
rants\n iv. Any other potential solutions from the group\n3. Identify poi
nts of consensus and points of contention\n i. What are the open question
s to answer to sort out the points of contention?\n4. Next steps\n\n**Mate
rials:**\n- [minutes](https://pad.w3.org/p/Notifications)\n- [Session prop
osal on GitHub](https://github.com/w3c/tpac2024-breakouts/issues/81)\n\n**
Track(s):**\n- Permissions
STATUS:CONFIRMED
CREATED:20240916T220103Z
LAST-MODIFIED:20241002T120833Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - Oceanside
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:028d0882-5e1e-42f7-90dd-ca524513ec57
DTSTAMP:20241106T182735Z
SUMMARY:One Year Update: Partitioning :visited links history
DTSTART;TZID=America/Los_Angeles:20240925T144500
DTEND;TZID=America/Los_Angeles:20240925T154500
DESCRIPTION:https://www.w3.org/events/meetings/028d0882-5e1e-42f7-90dd-ca52
4513ec57/\n\nThis breakout session will serve as a 1 year update to the pa
rtitioning :visited links project. We will:\n\n\n\n- Briefly recap the [Pa
rtitioning :visited links history explainer](https://github.com/kyraseever
s/Partitioning-visited-links-history). \n\n- Go over implementation progre
ss in Chrome and highlight solutions that may be valuable to other develop
ers.\n\n- Discuss public experiment results and key takeaways from our lau
nch.\n\n- Discuss how to spec this proposal and how standardization choice
s now may affect future privacy improvements to CSS\n\n- Determine what wo
rk remains towards removing the [2010 privacy mitigations](https://develop
er.mozilla.org/en-US/docs/Web/CSS/Privacy_and_the_:visited_selector).\n\nA
genda\n\n**Chairs:**\nKyra Seevers\, Artur Janc\, Mike Taylor\n\n**Descrip
tion:**\nThis breakout session will serve as a 1 year update to the partit
ioning :visited links project. We will:\n\n\n\n- Briefly recap the [Partit
ioning :visited links history explainer](https://github.com/kyraseevers/Pa
rtitioning-visited-links-history). \n\n- Go over implementation progress i
n Chrome and highlight solutions that may be valuable to other developers.
\n\n- Discuss public experiment results and key takeaways from our launch.
\n\n- Discuss how to spec this proposal and how standardization choices no
w may affect future privacy improvements to CSS\n\n- Determine what work r
emains towards removing the [2010 privacy mitigations](https://developer.m
ozilla.org/en-US/docs/Web/CSS/Privacy_and_the_:visited_selector).\n\n**Goa
l(s):**\nTo present implementation and experimentation updates\, and discu
ss concrete steps towards CSS standardization.\n\n\n\n**Materials:**\n- [s
lides](https://www.w3.org/2024/Talks/TPAC/breakouts/partitioning-visited-l
inks.pdf)\n- [minutes](https://www.w3.org/2024/09/breakouts/minutes-9.html
)\n- [minutes (initial google doc)](https://docs.google.com/document/d/1N4
TTMg90RzAWZyjWuy1j-zbYGfiiNNrzPRTDggxMX3s/edit)\n- [Session proposal on Gi
tHub](https://github.com/w3c/tpac2024-breakouts/issues/9)
STATUS:CONFIRMED
CREATED:20240916T214732Z
LAST-MODIFIED:20241106T182735Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - Capistrano
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:56c437a0-f44a-4b80-90ec-b954afb909ea
DTSTAMP:20241106T183152Z
SUMMARY:Real World Identity and the Web... Continued
DTSTART;TZID=America/Los_Angeles:20240925T144500
DTEND;TZID=America/Los_Angeles:20240925T154500
DESCRIPTION:https://www.w3.org/events/meetings/56c437a0-f44a-4b80-90ec-b954
afb909ea/\n\nAt TPAC 2023\, we introduced the topic of digital identity wa
llets and their use on the web\, and asked the community for use cases\, c
oncerns\, and asked browser engine maintainers to express interest in this
work.\n\nThis evolved into a work item in the WICG\, [the Digital Credent
ials API](https://github.com/WICG/digital-credentials)\, where folks from
multiple communities involved in the digitally verifiable credentials spac
e (including other W3C CGs and WGs\, the OpenID Foundation\, national stan
dards organizations\, privacy experts\, issuers\, verifiers\, wallet maker
s\, and more) have been working together to provide a safe\, secure\, priv
acy preserving method of sharing digital credentials on the web.\n\nThis s
ession will provide an update on the work\, the threat models being evalua
ted\, upcoming work items\, and open discussion.\n\nAgenda\n\n**Chairs:**\
nTim Cappalli\, Heather Flanagan\n\n**Description:**\nAt TPAC 2023\, we in
troduced the topic of digital identity wallets and their use on the web\,
and asked the community for use cases\, concerns\, and asked browser engin
e maintainers to express interest in this work.\n\nThis evolved into a wor
k item in the WICG\, [the Digital Credentials API](https://github.com/WICG
/digital-credentials)\, where folks from multiple communities involved in
the digitally verifiable credentials space (including other W3C CGs and WG
s\, the OpenID Foundation\, national standards organizations\, privacy exp
erts\, issuers\, verifiers\, wallet makers\, and more) have been working t
ogether to provide a safe\, secure\, privacy preserving method of sharing
digital credentials on the web.\n\nThis session will provide an update on
the work\, the threat models being evaluated\, upcoming work items\, and o
pen discussion.\n\n**Goal(s):**\nProvide an update on the work stream to t
he wider community\, hear new issues or concerns\, receive feedback on cor
e work items\n\n\n**Agenda:**\n* [Agenda](https://docs.google.com/document
/d/1k2pDac-8E3C2Ne1uJu7Fx4CGE-nn2e7YhVJbkIa106w)\n\n**Materials:**\n- [sli
des](https://www.w3.org/2024/Talks/TPAC/breakouts/real-world-identity.pdf)
\n- [minutes](https://www.w3.org/2024/09/breakouts/minutes-10.html)\n- [mi
nutes (initial google doc)](https://docs.google.com/document/d/1k2pDac-8E3
C2Ne1uJu7Fx4CGE-nn2e7YhVJbkIa106w)\n- [Session proposal on GitHub](https:/
/github.com/w3c/tpac2024-breakouts/issues/10)\n\n**Track(s):**\n- Wallets
STATUS:CONFIRMED
CREATED:20240916T214743Z
LAST-MODIFIED:20241106T183152Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:-1 Lower Level - Catalina 5
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:bf75e0c9-c534-4ccf-988e-0e720f5280ff
DTSTAMP:20241016T221511Z
SUMMARY:Registries for W3C Specifications
DTSTART;TZID=America/Los_Angeles:20240925T144500
DTEND;TZID=America/Los_Angeles:20240925T154500
DESCRIPTION:https://www.w3.org/events/meetings/bf75e0c9-c534-4ccf-988e-0e72
0f5280ff/\n\nIn [the related session](https://github.com/w3c/breakouts-day
-2024/issues/18) of the breakout day of 2024\, it was found out that the w
ide W3C community needs a place to discuss registry mechanism related topi
cs such as best practices\, experiences\, and tooling. With the Web of Thi
ngs WG advancing in defining their registry\, we want to use this session
to present the analysis that was done so far\, collect opinions from other
s.\n\nAgenda\n\n**Chairs:**\nEge Korkan\n\n**Description:**\nIn [the relat
ed session](https://github.com/w3c/breakouts-day-2024/issues/18) of the br
eakout day of 2024\, it was found out that the wide W3C community needs a
place to discuss registry mechanism related topics such as best practices\
, experiences\, and tooling. With the Web of Things WG advancing in defini
ng their registry\, we want to use this session to present the analysis th
at was done so far\, collect opinions from others.\n\n**Goal(s):**\nExperi
ence Sharing\, Discussion\n\n\n**Agenda:**\n- Wrap up of Breakout Day 2024
\, Registry Session\n- Experience from the development of the WoT Binding
Registry\n- Feedback and Discussion\n\n**Materials:**\n- [slides](https://
www.w3.org/2024/Talks/TPAC/breakouts/real-world-identity.pdf)\n- [minutes]
(https://www.w3.org/2024/09/25-registries-minutes.html)\n- [Session propos
al on GitHub](https://github.com/w3c/tpac2024-breakouts/issues/24)
STATUS:CONFIRMED
CREATED:20240916T215018Z
LAST-MODIFIED:20241016T221511Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:2 Ballroom Level - California A
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:854574de-23d7-4565-b708-a399f3f7dee8
DTSTAMP:20241002T122438Z
SUMMARY:Threat Modeling @ W3C
DTSTART;TZID=America/Los_Angeles:20240925T144500
DTEND;TZID=America/Los_Angeles:20240925T154500
DESCRIPTION:https://www.w3.org/events/meetings/854574de-23d7-4565-b708-a399
f3f7dee8/\n\nWhen a standard is written\, it's required to write Security
and Privacy Considerations and\, if the technology is particularly disrupt
ive\, to sample the human rights impact.\nOne of the processes that can be
used to get these considerations in a practical and structured way is to
use Threat Modeling\, a repeatable process with several techniques to unde
rstand best what we're doing\, what can't go wrong\, and what we can do ab
out it.\nIn this session\, we will explore how to initiate Threat Modeling
from the early stages of a specification\, using practical examples. This
approach ensures that everything is secure\, respects privacy\, and is pr
operly documented.\n\nAgenda: https://docs.google.com/presentation/d/1zauM
qnZ_e0U3JlNe3bCJacNh9h1VOkBX4_UynjqvQeg/edit#slide=id.g303b479e16d_0_15\n\
nAgenda\n\n**Chairs:**\nSimone Onofri\n\n**Description:**\nWhen a standard
is written\, it's required to write Security and Privacy Considerations a
nd\, if the technology is particularly disruptive\, to sample the human ri
ghts impact.\nOne of the processes that can be used to get these considera
tions in a practical and structured way is to use Threat Modeling\, a repe
atable process with several techniques to understand best what we're doing
\, what can't go wrong\, and what we can do about it.\nIn this session\, w
e will explore how to initiate Threat Modeling from the early stages of a
specification\, using practical examples. This approach ensures that every
thing is secure\, respects privacy\, and is properly documented.\n\n**Goal
(s):**\nSecure the standards\n\n\n\n**Materials:**\n- [minutes](https://ww
w.w3.org/2024/09/25-threat-modeling-minutes.html)\n- [Session proposal on
GitHub](https://github.com/w3c/tpac2024-breakouts/issues/12)
STATUS:CONFIRMED
CREATED:20240916T214810Z
LAST-MODIFIED:20241002T122438Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - Manhattan
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:601b0f92-e5ea-4e16-b767-2fceeb7094f9
DTSTAMP:20241002T122517Z
SUMMARY:W3C Vision — Getting To Statement
DTSTART;TZID=America/Los_Angeles:20240925T144500
DTEND;TZID=America/Los_Angeles:20240925T154500
DESCRIPTION:https://www.w3.org/events/meetings/601b0f92-e5ea-4e16-b767-2fce
eb7094f9/\n\nThe Advisory Board (AB) published the [W3C Vision as a Note](
https://www.w3.org/TR/2024/NOTE-w3c-vision-20240403/) earlier this year. T
he Vision Task Force ([VisionTF](https://www.w3.org/wiki/AB/VisionTF)) has
processed most issues and a small number of Statement Blockers remain. Th
is breakout session is an open session for working through the remaining [
Statement Blocker issues](https://github.com/w3c/AB-public/issues?q=is%3Ai
ssue+is%3Aopen+label%3A%22needed+for+Statement%22).\n\nAgenda\n\n**Chairs:
**\nTantek Çelik\, Chris Wilson\n\n**Description:**\nThe Advisory Board (
AB) published the [W3C Vision as a Note](https://www.w3.org/TR/2024/NOTE-w
3c-vision-20240403/) earlier this year. The Vision Task Force ([VisionTF](
https://www.w3.org/wiki/AB/VisionTF)) has processed most issues and a smal
l number of Statement Blockers remain. This breakout session is an open se
ssion for working through the remaining [Statement Blocker issues](https:/
/github.com/w3c/AB-public/issues?q=is%3Aissue+is%3Aopen+label%3A%22needed+
for+Statement%22).\n\n**Goal(s):**\nThe goal of this session is reach cons
ensus resolutions on the remaining Statement Blocker issues for the W3C Vi
sion\, so the Vision Task Force can prepare an updated W3C Vision Note for
publication as a proposed Statement for an Advisory Committee vote.\n\n**
Attendance:**\nThis session is restricted to TPAC registrants.\n\n**Agenda
:**\n[w3.org/wiki/AB/VisionTF/2024-09-25](https://www.w3.org/wiki/AB/Visio
nTF/2024-09-25)\n\n(Originally published at: https://tantek.com/2024/257/b
1/w3c-vision-getting-to-statement)\n\n**Materials:**\n- [minutes](https://
www.w3.org/2024/09/25-vision-minutes.html)\n- [Session proposal on GitHub]
(https://github.com/w3c/tpac2024-breakouts/issues/84)
STATUS:CONFIRMED
CREATED:20240916T220126Z
LAST-MODIFIED:20241002T122517Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - Huntington
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:cd255a8c-a18d-4e35-bb8b-2ade88af2786
DTSTAMP:20241106T183335Z
SUMMARY:Web Install API
DTSTART;TZID=America/Los_Angeles:20240925T144500
DTEND;TZID=America/Los_Angeles:20240925T154500
DESCRIPTION:https://www.w3.org/events/meetings/cd255a8c-a18d-4e35-bb8b-2ade
88af2786/\n\nThis breakout will serve as an update to the broader communit
y about the Web Install API. We will be discussing the shape of the API\,
decisions behind it\, and show the progress around the API.\n\nAs the plat
form continues to evolve with richer and more powerful capabilities\, more
developers lean on PWAs to reach their customers. Distribution is still t
ied to native app stores or proprietary protocol workarounds\, with one bi
g gap related toa application distribution.\n\nAgenda\n\n**Chairs:**\nDieg
o Gonzalez-Zuniga\, Amanda Baker\n\n**Description:**\nThis breakout will s
erve as an update to the broader community about the Web Install API. We w
ill be discussing the shape of the API\, decisions behind it\, and show th
e progress around the API.\n\nAs the platform continues to evolve with ric
her and more powerful capabilities\, more developers lean on PWAs to reach
their customers. Distribution is still tied to native app stores or propr
ietary protocol workarounds\, with one big gap related toa application dis
tribution.\n\n**Goal(s):**\nShowcase the Web Install API and give an updat
e on development. We want to gather community feedback on the API.\n\n\n**
Agenda:**\nMeeting minutes: https://docs.google.com/document/d/1ItMpSpuV1C
szg_64o4D2MJMT7KlWKBTz8jhWg3y3A5E/edit?usp=sharing\n \nand presentation as
a pdf: https://drive.google.com/file/d/1-pO4Ar5EpznGuNX-0AWp25ctIlsOCMcH/
view?usp=sharing\n\n**Materials:**\n- [slides](https://www.w3.org/2024/Tal
ks/TPAC/breakouts/web-install-api.pdf)\n- [minutes](https://www.w3.org/202
4/09/breakouts/minutes-25.html)\n- [minutes (initial google doc)](https://
docs.google.com/document/d/1ItMpSpuV1Cszg_64o4D2MJMT7KlWKBTz8jhWg3y3A5E/ed
it?usp=sharing)\n- [Session proposal on GitHub](https://github.com/w3c/tpa
c2024-breakouts/issues/25)\n\n**Track(s):**\n- Web Apps
STATUS:CONFIRMED
CREATED:20240916T215026Z
LAST-MODIFIED:20241106T183335Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:2 Ballroom Level - California B
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:80f4dd75-7ade-4761-92ee-a59abb62006d
DTSTAMP:20241002T122501Z
SUMMARY:Web on the Moon
DTSTART;TZID=America/Los_Angeles:20240925T144500
DTEND;TZID=America/Los_Angeles:20240925T154500
DESCRIPTION:https://www.w3.org/events/meetings/80f4dd75-7ade-4761-92ee-a59a
bb62006d/\n\nThe _Artemis_ plan calls for human habitation of the Moon fro
m 2028\, currently under international consideration from the perspectives
of habitation\, mineral resource collection\, food and medicine\, and is
considered the first step towards sending humans to Mars in the future. Co
mmunication with family and others is essential when people are away from
Earth for long periods. Astronauts on the ISS are already guaranteed a pri
vate conversation with their families on the ground at least once a day\,
and can even watch football games using web and remote conferencing techno
logy\, but the ISS is 400 km from the ground\, and its latency is less tha
n that of a geostationary orbit satellite (located 35\,786 km above the gr
ound) is said to be 500 ms.\n \nThe distance to the Moon is 380\,000 km\
, which theoretically translates into a latency of _2\,600 ms_.\n\nUnder t
hese conditions\, it is expected to be difficult for people living on the
Moon to explore the Web\, hold remote meetings with their families or watc
h football games\, as they do on Earth\, due to time-outs and other proble
ms with current technology.\n\nIn this breakout session\, we would like to
discuss the possibility of using web technology on the Moon in the same w
ay as on Earth\, although the speed of light cannot be exceeded.\n\nAgenda
\n\n**Chairs:**\nJay Kishigami\n\n**Description:**\nThe _Artemis_ plan cal
ls for human habitation of the Moon from 2028\, currently under internatio
nal consideration from the perspectives of habitation\, mineral resource c
ollection\, food and medicine\, and is considered the first step towards s
ending humans to Mars in the future. Communication with family and others
is essential when people are away from Earth for long periods. Astronauts
on the ISS are already guaranteed a private conversation with their famili
es on the ground at least once a day\, and can even watch football games u
sing web and remote conferencing technology\, but the ISS is 400 km from t
he ground\, and its latency is less than that of a geostationary orbit sat
ellite (located 35\,786 km above the ground) is said to be 500 ms.\n \nT
he distance to the Moon is 380\,000 km\, which theoretically translates in
to a latency of _2\,600 ms_.\n\nUnder these conditions\, it is expected to
be difficult for people living on the Moon to explore the Web\, hold remo
te meetings with their families or watch football games\, as they do on Ea
rth\, due to time-outs and other problems with current technology.\n\nIn t
his breakout session\, we would like to discuss the possibility of using w
eb technology on the Moon in the same way as on Earth\, although the speed
of light cannot be exceeded.\n\n**Goal(s):**\nParticipants will decide on
the direction of future discussions.\n\n\n**Agenda:**\n1. overview of ISS
\, Artemis\, DTN (RFC4838)\, etc.\n2. open discussion\n\n**Materials:**\n-
[minutes](https://www.w3.org/2024/09/25-web-on-the-moon-minutes.html)\n-
[Session proposal on GitHub](https://github.com/w3c/tpac2024-breakouts/iss
ues/52)
STATUS:CONFIRMED
CREATED:20240916T215431Z
LAST-MODIFIED:20241002T122501Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - Palos Verdes
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:bdefcc3d-bb14-4879-ab9d-586b863af8a5
DTSTAMP:20241002T122449Z
SUMMARY:Web Speech API Improvements
DTSTART;TZID=America/Los_Angeles:20240925T144500
DTEND;TZID=America/Los_Angeles:20240925T154500
DESCRIPTION:https://www.w3.org/events/meetings/bdefcc3d-bb14-4879-ab9d-586b
863af8a5/\n\nChrome is proposing new improvements to the Web Speech API\,
including:\n\nOffline speech recognition: Allow speech recognition without
an internet connection. [1]\nMediaStreamTrack support: Enable seamless in
tegration of speech recognition with audio and video streams. [2]\nSpoken
punctuation parameter: Add a new parameter to the speech recognition API t
hat allows developers to control how spoken punctuation marks are handled
in the transcription. [3]\n\nRelated Github issues:\n[1] [Offline/on-devic
e speech recognition #108](https://github.com/WICG/speech-api/issues/108)\
n[2] [Support SpeechRecognition on an audio MediaStreamTrack #66](https://
github.com/WICG/speech-api/issues/66)\n[3] [Speech recognition parameter f
or spoken punctuation #114](https://github.com/WICG/speech-api/issues/114)
\n\nAgenda\n\n**Chairs:**\nEvan Liu\n\n**Description:**\nChrome is proposi
ng new improvements to the Web Speech API\, including:\n\nOffline speech r
ecognition: Allow speech recognition without an internet connection. [1]\n
MediaStreamTrack support: Enable seamless integration of speech recognitio
n with audio and video streams. [2]\nSpoken punctuation parameter: Add a n
ew parameter to the speech recognition API that allows developers to contr
ol how spoken punctuation marks are handled in the transcription. [3]\n\nR
elated Github issues:\n[1] [Offline/on-device speech recognition #108](htt
ps://github.com/WICG/speech-api/issues/108)\n[2] [Support SpeechRecognitio
n on an audio MediaStreamTrack #66](https://github.com/WICG/speech-api/iss
ues/66)\n[3] [Speech recognition parameter for spoken punctuation #114](ht
tps://github.com/WICG/speech-api/issues/114)\n\n**Goal(s):**\nDiscuss and
reach a consensus on the proposed changes to the Web Speech API\n\n\n\n**M
aterials:**\n- [minutes](https://www.w3.org/2024/09/25-web-speech-minutes.
html)\n- [Session proposal on GitHub](https://github.com/w3c/tpac2024-brea
kouts/issues/21)
STATUS:CONFIRMED
CREATED:20240916T215001Z
LAST-MODIFIED:20241002T122449Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - San Clemente
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:0c09dd52-f75e-4676-bb57-43bb33f6a4eb
DTSTAMP:20241030T131535Z
SUMMARY:Blending Realities: Building An Open Web Wide World
DTSTART;TZID=America/Los_Angeles:20240925T160000
DTEND;TZID=America/Los_Angeles:20240925T164500
DESCRIPTION:https://www.w3.org/events/meetings/0c09dd52-f75e-4676-bb57-43bb
33f6a4eb/\n\nBuilding blocks for constructing a tangible virtual world has
begun to take shape. Technologies from various fields are becoming increa
singly mature\, such as gaming\, social platforms\, digital twins\, and vi
rtual reality.\nThis session aims to trigger the discussion on how each st
akeholder may collaborate to co-create a tangible virtual world that is in
terconnected\, mutually beneficial\, supportive and belongs to all. We nee
d a set of standards that enable the integration of individual efforts to
build an open platform on web\, fostering prosperity through cooperation r
ather than competition.\nThis session will delve into our recent endeavors
in crafting virtual world experiences on Tencent products. We will share
insights from our development process\, highlight the innovative solutions
we implemented\, and discuss the hurdles we encountered along the way. \n
\nThe following aspects will be addressed:\n1. Types and Corresponding Rol
es: Sites as Service Integrators and Programs as Service Providers\n2. Sco
ping: Defining the Origins of Assets and Elements\n3. Asset Deployments: P
lanning Asset URIs and Deploying according to Scoping\n4. Site Hierarchy:
Inter-Site Integration through Contracts and Administration according to S
coping\n5. Site-Program Integration: Cooperating between Programs and Site
s through Contracts\n6. Permission Controls: Managing Authorization for As
sets and Elements across Sites/Programs\n7. Version Management: Independen
t Releases by Sites/Programs with Unified Synchronization across the Virtu
al World\n8. Multi-user Interaction: Distributed across Sites and Seamless
ly Integrated through On-Demand Pub/Sub for Users\n\n\nAgenda\n\n**Chairs:**\nHarry Wang\,
Rocman Zhao\n\n**Description:**\nBuilding blocks for constructing a tangib
le virtual world has begun to take shape. Technologies from various fields
are becoming increasingly mature\, such as gaming\, social platforms\, di
gital twins\, and virtual reality.\nThis session aims to trigger the discu
ssion on how each stakeholder may collaborate to co-create a tangible virt
ual world that is interconnected\, mutually beneficial\, supportive and be
longs to all. We need a set of standards that enable the integration of in
dividual efforts to build an open platform on web\, fostering prosperity t
hrough cooperation rather than competition.\nThis session will delve into
our recent endeavors in crafting virtual world experiences on Tencent prod
ucts. We will share insights from our development process\, highlight the
innovative solutions we implemented\, and discuss the hurdles we encounter
ed along the way. \n\nThe following aspects will be addressed:\n1. Types a
nd Corresponding Roles: Sites as Service Integrators and Programs as Servi
ce Providers\n2. Scoping: Defining the Origins of Assets and Elements\n3.
Asset Deployments: Planning Asset URIs and Deploying according to Scoping\
n4. Site Hierarchy: Inter-Site Integration through Contracts and Administr
ation according to Scoping\n5. Site-Program Integration: Cooperating betwe
en Programs and Sites through Contracts\n6. Permission Controls: Managing
Authorization for Assets and Elements across Sites/Programs\n7. Version Ma
nagement: Independent Releases by Sites/Programs with Unified Synchronizat
ion across the Virtual World\n8. Multi-user Interaction: Distributed acros
s Sites and Seamlessly Integrated through On-Demand Pub/Sub for Users\n\n\n**Goal(s):**\n1
）Call for participation: co-create one tangible virtual world that is gl
obally shared\, co-constructed\, and interconnected on web. 2）Share idea
s on user experience\, economic models\, technological challenges. 3）DIs
cuss standard needs for asset\, logic\, user interaction\, UI and business
integrations.\n\n\n**Agenda:**\n1. Introduction on Web Wide World\n2. Liv
e demo\n3. Open discussion\n[Slides are available online](https://www.w3.o
rg/2024/09/Blending_Realities_breakout_20240926.pdf)\n\n**Materials:**\n-
[slides](https://www.w3.org/2024/09/Blending_Realities_breakout_20240926.p
df)\n- [minutes](https://www.w3.org/2024/09/25-co-create-web-minutes.html)
\n- [recording](https://www.w3.org/2024/09/breakouts/recording-61.html)\n-
[Session proposal on GitHub](https://github.com/w3c/tpac2024-breakouts/is
sues/61)
STATUS:CONFIRMED
CREATED:20240916T215641Z
LAST-MODIFIED:20241030T131535Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:2 Ballroom Level - California B
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:d0e47649-424b-4ffd-8424-88fb80b3ae7e
DTSTAMP:20240925T231243Z
SUMMARY:Bringing more UI utilities to specs
DTSTART;TZID=America/Los_Angeles:20240925T160000
DTEND;TZID=America/Los_Angeles:20240925T164500
DESCRIPTION:https://www.w3.org/events/meetings/d0e47649-424b-4ffd-8424-88fb
80b3ae7e/\n\nWhen used in Editor's drafts\, Respec and Bikeshed provide ve
ry powerful/useful JS controls that provide a lot o value to the community
. For example\, both Respec and Bikeshed allow clicking on variables in al
gorithms\, which get highlighted to show where they are used. ReSpec adds
a copy button to WebIDL\, letting readers copy WebIDL with a single click\
, etc. \n\nOther useful things are the definition boxes\, MDN annotations
\, etc.\n\nUnfortunately\, these are inconsistently presented across specs
/tools providing different experiences and capabilities.. as a community\,
we should look to align on the design of the above things\, and expose th
ese JS tools to all specs that need then. \n\nIt would be great to have a
session where we look the great feature both Bikeshed and Respec provide\,
and see where we have overlapping features\, and start looking at how we
can harmonize the JS libraries into a single codebase. \n\nIt would be gre
at if we could find a UI designer to help us make these tools even better.
.. and\, as a bonus\, it would be cool if we could start using `popup` and
other modern web features to achieve these things. \n\nHi @tabatkins\, @s
ideshowbarker\, @sidvishnoi\, @fantasai\, @dontcallmedom\, @tidoust\, @den
iak 👋\n\nAgenda\n\n**Chairs:**\nMarcos Caceres\n\n**Description:**\nWhe
n used in Editor's drafts\, Respec and Bikeshed provide very powerful/usef
ul JS controls that provide a lot o value to the community. For example\,
both Respec and Bikeshed allow clicking on variables in algorithms\, which
get highlighted to show where they are used. ReSpec adds a copy button to
WebIDL\, letting readers copy WebIDL with a single click\, etc. \n\nOthe
r useful things are the definition boxes\, MDN annotations\, etc.\n\nUnfor
tunately\, these are inconsistently presented across specs/tools providing
different experiences and capabilities.. as a community\, we should look
to align on the design of the above things\, and expose these JS tools to
all specs that need then. \n\nIt would be great to have a session where we
look the great feature both Bikeshed and Respec provide\, and see where w
e have overlapping features\, and start looking at how we can harmonize th
e JS libraries into a single codebase. \n\nIt would be great if we could f
ind a UI designer to help us make these tools even better... and\, as a bo
nus\, it would be cool if we could start using `popup` and other modern we
b features to achieve these things. \n\nHi @tabatkins\, @sideshowbarker\,
@sidvishnoi\, @fantasai\, @dontcallmedom\, @tidoust\, @deniak 👋\n\n**Go
al(s):**\nShared JS libraries for spec goodies\n\n\n**Agenda:**\n* Demo wh
at Bikeshed has\n* Demo what Respec has \n* Compare differences\n* Talk ab
out convergence\n* Talk about other neat things we could develop that woul
d help users\n* Talk about what we can bring to TR and maybe let TR/ desig
n handle\n\n**Materials:**\n- [Session proposal on GitHub](https://github.
com/w3c/tpac2024-breakouts/issues/14)
STATUS:CONFIRMED
CREATED:20240916T214836Z
LAST-MODIFIED:20240925T231243Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - Oceanside
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:ff83b490-7df3-4faf-89b4-6069da41c976
DTSTAMP:20241002T122452Z
SUMMARY:CBOR-LD\, YAML-LD & the JSON-LD Recharter
DTSTART;TZID=America/Los_Angeles:20240925T160000
DTEND;TZID=America/Los_Angeles:20240925T164500
DESCRIPTION:https://www.w3.org/events/meetings/ff83b490-7df3-4faf-89b4-6069
da41c976/\n\nThe upcoming JSON-LD recharter includes two new compatible fo
rmats based on the JSON-LD data model: CBOR-LD and YAML-LD. CBOR-LD provid
es a highly compressed format keeping data small enough to be represented
in QR codes\, distributed over short-lived\, low bandwidth scenarios\, or
enabling smaller device use cases when coupled with W3C Web of Thing descr
iptions. YAML-LD aims to provide simpler human-friendly formatting while s
taying fully compatible with the JSON-LD data model allowing for easy roun
d-tripping between the two formats. The WG is also exploring a handful of
other documents related to internationalization and enhanced processing mo
des.\n\nAgenda\n\n**Chairs:**\nMandy Venables\, Benjamin Young\n\n**Descri
ption:**\nThe upcoming JSON-LD recharter includes two new compatible forma
ts based on the JSON-LD data model: CBOR-LD and YAML-LD. CBOR-LD provides
a highly compressed format keeping data small enough to be represented in
QR codes\, distributed over short-lived\, low bandwidth scenarios\, or ena
bling smaller device use cases when coupled with W3C Web of Thing descript
ions. YAML-LD aims to provide simpler human-friendly formatting while stay
ing fully compatible with the JSON-LD data model allowing for easy round-t
ripping between the two formats. The WG is also exploring a handful of oth
er documents related to internationalization and enhanced processing modes
.\n\n**Goal(s):**\nInform members on the upcoming JSON-LD recharter.\n\n\n
\n**Materials:**\n- [minutes](https://www.w3.org/2024/09/25-json-ld-minute
s.html)\n- [Session proposal on GitHub](https://github.com/w3c/tpac2024-br
eakouts/issues/35)
STATUS:CONFIRMED
CREATED:20240916T215153Z
LAST-MODIFIED:20241002T122452Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:-1 Lower Level - Catalina 5
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:df616a60-8591-4f24-b305-aa0870aac1cb
DTSTAMP:20241002T140215Z
SUMMARY:Discussion for Proposal: asynchronous event listeners
DTSTART;TZID=America/Los_Angeles:20240925T160000
DTEND;TZID=America/Los_Angeles:20240925T164500
DESCRIPTION:https://www.w3.org/events/meetings/df616a60-8591-4f24-b305-aa08
70aac1cb/\n\nThere is a proposal for async event listeners: https://github
.com/whatwg/dom/issues/1308\n\nSeveral use cases identified as related (ht
tps://github.com/whatwg/dom/issues/1308#issuecomment-2312993127):\n\n- "pa
ssive" event dispatch. Observe\, but don't block\, event dispatch. Don't
need `preventDefault`.\n- lazy loading "controllers"\, aka progressive hyd
ration.\n- Tracking long running "async effects" which follow the sync eve
nt dispatch.\n- "document still loading" use cases\n- "document started un
loading" use cases\n\nAgenda\n\n**Chairs:**\nMichal Mocny\, Dominic Faroli
no\n\n**Description:**\nThere is a proposal for async event listeners: htt
ps://github.com/whatwg/dom/issues/1308\n\nSeveral use cases identified as
related (https://github.com/whatwg/dom/issues/1308#issuecomment-2312993127
):\n\n- "passive" event dispatch. Observe\, but don't block\, event dispat
ch. Don't need `preventDefault`.\n- lazy loading "controllers"\, aka prog
ressive hydration.\n- Tracking long running "async effects" which follow t
he sync event dispatch.\n- "document still loading" use cases\n- "document
started unloading" use cases\n\n**Goal(s):**\nDiscussion and sharing earl
y feedback.\n\n\n\n**Materials:**\n- [minutes](https://www.w3.org/2024/09/
25-async-event-listeners-minutes.html)\n- [Session proposal on GitHub](htt
ps://github.com/w3c/tpac2024-breakouts/issues/101)
STATUS:CONFIRMED
CREATED:20240922T193335Z
LAST-MODIFIED:20241002T140215Z
SEQUENCE:0
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:2 Ballroom Level - California A
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:8e568e2c-6e49-46e7-a1f2-49a02130aa8f
DTSTAMP:20241002T122451Z
SUMMARY:DOM Parts
DTSTART;TZID=America/Los_Angeles:20240925T160000
DTEND;TZID=America/Los_Angeles:20240925T164500
DESCRIPTION:https://www.w3.org/events/meetings/8e568e2c-6e49-46e7-a1f2-49a0
2130aa8f/\n\nSession to discuss DOM parts proposal:\nhttps://github.com/WI
CG/webcomponents/blob/gh-pages/proposals/DOM-Parts-Imperative.md\nhttps://
github.com/WICG/webcomponents/blob/gh-pages/proposals/DOM-Parts-Declarativ
e-Template.md\n\nAgenda\n\n**Chairs:**\nRyosuke Niwa\n\n**Description:**\n
Session to discuss DOM parts proposal:\nhttps://github.com/WICG/webcompone
nts/blob/gh-pages/proposals/DOM-Parts-Imperative.md\nhttps://github.com/WI
CG/webcomponents/blob/gh-pages/proposals/DOM-Parts-Declarative-Template.md
\n\n**Goal(s):**\nCome up with a concrete MVP for DOM parts\n\n\n\n**Mater
ials:**\n- [minutes](https://www.w3.org/2024/09/25-webcomponents-minutes.h
tml)\n- [Session proposal on GitHub](https://github.com/w3c/tpac2024-break
outs/issues/28)\n\n**Track(s):**\n- Web Components
STATUS:CONFIRMED
CREATED:20240916T215044Z
LAST-MODIFIED:20241002T122451Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:-1 Lower Level - Catalina 3
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:a3657654-ec52-4f63-8a6f-dcbf79030913
DTSTAMP:20241002T122510Z
SUMMARY:Horizontal reviews at W3C and beyond
DTSTART;TZID=America/Los_Angeles:20240925T160000
DTEND;TZID=America/Los_Angeles:20240925T164500
DESCRIPTION:https://www.w3.org/events/meetings/a3657654-ec52-4f63-8a6f-dcbf
79030913/\n\nThis session is meant to touch base on how horizontal reviews
are conducted at W3C and for the Web\n\nIn scope:\n* Scope of horizontal
reviews: W3C Technical Reports\, W3C Community Group reports\, Web specifi
cations from other organizations (WHATWG\, IETF\, ECMA\, etc.)\n* How to g
et [horizontal review](https://www.w3.org/Guide/documentreview/#how_to_get
_horizontal_review)\n* Horizontal review questionnaires\n* GitHub Issue re
view requests and trackers\n* Tooling improvements and needs\n\nAgenda\n\n
**Chairs:**\nPhilippe Le Hegaret\n\n**Description:**\nThis session is mean
t to touch base on how horizontal reviews are conducted at W3C and for the
Web\n\nIn scope:\n* Scope of horizontal reviews: W3C Technical Reports\,
W3C Community Group reports\, Web specifications from other organizations
(WHATWG\, IETF\, ECMA\, etc.)\n* How to get [horizontal review](https://ww
w.w3.org/Guide/documentreview/#how_to_get_horizontal_review)\n* Horizontal
review questionnaires\n* GitHub Issue review requests and trackers\n* Too
ling improvements and needs\n\n**Goal(s):**\nEvolve horizontal reviews of
Web specifications\n\n\n**Agenda:**\n1. [Slides](https://www.w3.org/2024/T
alks/TPAC/horizontal-reviews/)\n2. Discussion\n\n**Materials:**\n- [slides
](https://www.w3.org/2024/Talks/TPAC/horizontal-reviews/)\n- [minutes](htt
ps://www.w3.org/2024/09/25-horizontal-minutes.html)\n- [Session proposal o
n GitHub](https://github.com/w3c/tpac2024-breakouts/issues/65)\n\n**Track(
s):**\n- Standards
STATUS:CONFIRMED
CREATED:20240916T215733Z
LAST-MODIFIED:20241002T122510Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - Huntington
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:fe8ffb35-a841-4ec9-aa92-e9dbf5abc3bd
DTSTAMP:20240925T144155Z
SUMMARY:Open Athletics: Global Data Interoperability in Sports
DTSTART;TZID=America/Los_Angeles:20240925T160000
DTEND;TZID=America/Los_Angeles:20240925T164500
DESCRIPTION:https://www.w3.org/events/meetings/fe8ffb35-a841-4ec9-aa92-e9db
f5abc3bd/\n\nA group of sports data enthusiasts motivated by the opportuni
ties the open data promised during the rising data revolution in the publi
c sector launched the [Open Athletics CG](https://www.w3.org/community/ope
ntrack/) (officially named OpenTrack CG) in 2017. This CG aimed to motivat
e the **exchange of Athletics data** across federations\, clubs and busine
sses. \n\nInteroperability was and **still is a challenge due to the heter
ogeneity of governing bodies and systems** (i.e.\, lack of a central or a
federated system to collect results automatically at the international lev
el). Competitions are similar worldwide (i.e.\, changing distances and uni
ts\, throwing different objects\, and using different surfaces)\, and most
of the information\, like the results or the competitors\, is public\, so
global interoperability seems feasible. \n\nWe defined a [model and voc
abulary](https://w3c.github.io/opentrack-cg/spec/competition/)\, but simpl
er solutions are still in use.\n\nSince the beginning\, European Athletics
has been one of the most active interoperability advocates. Now\, World A
thletics is also in the conversations. This session aims to present our ac
tivities and current projects' status and bring more stakeholders and idea
s into the group (most of the participants are from Europe\, so we would l
ike to expand the scope).\n\nAgenda\n\n**Chairs:**\nMartin Alvarez-Espinar
\n\n**Description:**\nA group of sports data enthusiasts motivated by the
opportunities the open data promised during the rising data revolution in
the public sector launched the [Open Athletics CG](https://www.w3.org/comm
unity/opentrack/) (officially named OpenTrack CG) in 2017. This CG aimed t
o motivate the **exchange of Athletics data** across federations\, clubs a
nd businesses. \n\nInteroperability was and **still is a challenge due to
the heterogeneity of governing bodies and systems** (i.e.\, lack of a cent
ral or a federated system to collect results automatically at the internat
ional level). Competitions are similar worldwide (i.e.\, changing distance
s and units\, throwing different objects\, and using different surfaces)\,
and most of the information\, like the results or the competitors\, is pu
blic\, so global interoperability seems feasible. \n\nWe defined a [mode
l and vocabulary](https://w3c.github.io/opentrack-cg/spec/competition/)\,
but simpler solutions are still in use.\n\nSince the beginning\, European
Athletics has been one of the most active interoperability advocates. Now\
, World Athletics is also in the conversations. This session aims to prese
nt our activities and current projects' status and bring more stakeholders
and ideas into the group (most of the participants are from Europe\, so w
e would like to expand the scope).\n\n**Goal(s):**\nRedefine the strategy
of the group\, onboard new stakeholders\n\n\n**Agenda:**\n1. Introduction
Open Athletics\n2. Current and upcoming activities \n3. Open discussion\n\
n**Materials:**\n- [Session proposal on GitHub](https://github.com/w3c/tpa
c2024-breakouts/issues/60)
STATUS:CANCELLED
CREATED:20240916T215627Z
LAST-MODIFIED:20240925T144155Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:-1 Lower Level - Catalina 2
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:a5c86bfb-b4b3-4e4a-bdeb-07cd2df18085
DTSTAMP:20241016T221854Z
SUMMARY:Prompt spam and reputation attacks associated with requestStorageAc
cessFor
DTSTART;TZID=America/Los_Angeles:20240925T160000
DTEND;TZID=America/Los_Angeles:20240925T164500
DESCRIPTION:https://www.w3.org/events/meetings/a5c86bfb-b4b3-4e4a-bdeb-07cd
2df18085/\n\nDiscussion on how to expand the requestStorageAccessFor API t
o reduce the potential for it to be used as a vector for reputation attack
s and prompt spam.\n\nThese are issues because embedded sites can not cont
rol who embeds them. Which means that the top level site can prompt on beh
alf of the embedded site. This could potentially [damage](https://github.c
om/WebKit/standards-positions/issues/125#issuecomment-1422944814) the embe
dder’s reputation and/or spam the user with the generation of a large nu
mber of prompts.\n\nAgenda\n\n**Chairs:**\nAaron Selya\, Chris Fredrickson
\n\n**Description:**\nDiscussion on how to expand the requestStorageAccess
For API to reduce the potential for it to be used as a vector for reputati
on attacks and prompt spam.\n\nThese are issues because embedded sites can
not control who embeds them. Which means that the top level site can prom
pt on behalf of the embedded site. This could potentially [damage](https:/
/github.com/WebKit/standards-positions/issues/125#issuecomment-1422944814)
the embedder’s reputation and/or spam the user with the generation of a
large number of prompts.\n\n**Goal(s):**\ngather input from the community
and gain consensus on how to address the problems\n\n\n**Agenda:**\nIntro
duce the problem\nReview how the browsers have addressed it so far\nDiscus
s more potential solutions\n\n**Materials:**\n- [slides](https://www.w3.o
rg/2024/Talks/TPAC/breakouts/requestStorageAccessFor.pdf)\n- [minutes](htt
ps://www.w3.org/2024/09/rsafor-20240925.html)\n- [Session proposal on GitH
ub](https://github.com/w3c/tpac2024-breakouts/issues/75)
STATUS:CONFIRMED
CREATED:20240916T215930Z
LAST-MODIFIED:20241016T221854Z
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
BEGIN:VEVENT
UID:ac5bac79-5276-4b36-b69b-64c6ececb8da
DTSTAMP:20240925T212450Z
SUMMARY:Reconciling UIEvents and the DOM spec
DTSTART;TZID=America/Los_Angeles:20240925T160000
DTEND;TZID=America/Los_Angeles:20240925T164500
DESCRIPTION:https://www.w3.org/events/meetings/ac5bac79-5276-4b36-b69b-64c6
ececb8da/\n\nIdentify where definitions exist in the DOM spec that can be
used by UIEvents\, with the goal of removing all duplication and to enable
a proper algorithmic description of all UIEvents.\n\nAgenda\n\n**Chairs:*
*\nGary Kacmarcik\n\n**Description:**\nIdentify where definitions exist in
the DOM spec that can be used by UIEvents\, with the goal of removing all
duplication and to enable a proper algorithmic description of all UIEvent
s.\n\n**Goal(s):**\nIdentify where UIEVents needs to hook into the DOM spe
c\n\n\n**Agenda:**\n_No response_he\n\n**Materials:**\n- [Session proposal
on GitHub](https://github.com/w3c/tpac2024-breakouts/issues/82)
STATUS:CONFIRMED
CREATED:20240916T220110Z
LAST-MODIFIED:20240925T212450Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - Palos Verdes
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:e5db5bf1-154b-45db-a357-77923cf1ff5f
DTSTAMP:20241002T122515Z
SUMMARY:Social Web and Fediverse Year in Review
DTSTART;TZID=America/Los_Angeles:20240925T160000
DTEND;TZID=America/Los_Angeles:20240925T164500
DESCRIPTION:https://www.w3.org/events/meetings/e5db5bf1-154b-45db-a357-7792
3cf1ff5f/\n\nJoin us as we discuss the SocialWeb CG activities and develop
ments in the areas of Social Web\, Fediverse\, distributed social software
\, over this past year.\n\nAgenda\n\n**Chairs:**\nDmitri Zagidulin\n\n**De
scription:**\nJoin us as we discuss the SocialWeb CG activities and develo
pments in the areas of Social Web\, Fediverse\, distributed social softwar
e\, over this past year.\n\n**Goal(s):**\nAppraise the SocialWeb developer
community of relevant specs and developments\n\n\n\n**Materials:**\n- [mi
nutes](https://www.w3.org/2024/09/25-social-web-review-minutes.html)\n- [S
ession proposal on GitHub](https://github.com/w3c/tpac2024-breakouts/issue
s/87)
STATUS:CONFIRMED
CREATED:20240916T220150Z
LAST-MODIFIED:20241002T122515Z
SEQUENCE:1
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
BEGIN:VEVENT
UID:3d5ed7b5-57a3-4ea7-81df-1a2ced89b99a
DTSTAMP:20241002T120120Z
SUMMARY:Styling form controls
DTSTART;TZID=America/Los_Angeles:20240925T160000
DTEND;TZID=America/Los_Angeles:20240925T164500
DESCRIPTION:https://www.w3.org/events/meetings/3d5ed7b5-57a3-4ea7-81df-1a2c
ed89b99a/\n\nDiscussing proposals around styling form controls.\n\nAgenda\
n\n**Chairs:**\nTim Nguyen\n\n**Description:**\nDiscussing proposals aroun
d styling form controls.\n\n**Goal(s):**\nBrainstorming and refining ideas
\n\n\n**Agenda:**\n- appearance: base\n- general design principles\n- pseu
do-elements \n- layout\n- ??\n\n**Materials:**\n- [minutes](https://www.w3
.org/2024/09/25-css-minutes.html#t07)\n- [Session proposal on GitHub](http
s://github.com/w3c/tpac2024-breakouts/issues/68)
STATUS:CONFIRMED
CREATED:20240916T215800Z
LAST-MODIFIED:20241002T120120Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - Manhattan
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:df2c5c9b-b9b5-4ea2-a4d8-6cecaca81c08
DTSTAMP:20241002T115850Z
SUMMARY:Web-based Digital Twins for Smart Cities
DTSTART;TZID=America/Los_Angeles:20240925T160000
DTEND;TZID=America/Los_Angeles:20240925T164500
DESCRIPTION:https://www.w3.org/events/meetings/df2c5c9b-b9b5-4ea2-a4d8-6cec
aca81c08/\n\nBased on the discussion during the [W3C workshop on Smart Cit
ies](https://www.w3.org/2021/06/smartcities-workshop/report.html) in 2021
and then two follow-up breakout sessions with invited key stakeholders fro
m related SDOs ([one during TPAC 2022](https://www.w3.org/2022/09/14-smart
cities-minutes.html) and [another during TPAC 2023](https://www.w3.org/202
3/09/13-smartcities-minutes.html))\, we identified the stakeholders around
Smart City standardization and reasonable applications for Smart City tec
hnologies. In addition\, we got thoughtful input on how to improve the [dr
aft Charter](https://w3c.github.io/smartcities-workshop/draft-charter/inde
x.html) Charter of the proposed Web-based Digital Twins for Smart Cities I
nterest Group for further discussions.\n\nSome of the key input included:\
n* "Digital Twins" should be the key concept for Smart Cities standardizat
ion.\n* Web standards\, e.g.\, Web of Things (WoT)\, Decentralized Identif
iers (DID) and Verifiable Credentials (VC)\, should be considered as possi
ble key modules for the possible Web-based Digital Twins framework.\n* Sta
ndard vocabulary for semantic interoperability is also required for the pl
atform.\n* Collaboration by related SDOs is necessary for further discussi
on\, and W3C should become the central hub for the discussion given Web st
andards play very important roles.\n\nNow the [Web-based Digital Twins for
Smart Cities Interest Group](https://www.w3.org/2024/06/smart-cities/) ha
s been launched\, and we'd like to start actual discussion about with the
key stakeholders from related SDOs\, industries and coutries/cities to wor
k on the following deliverables of the Interest Group:\n* Survey on the ex
isting technologies and standards for Smart Cities\, e.g.\, possible build
ing blocks of Digital Twin Framework and standardized Vocabularies for Sma
rt Cities\n* Best Practices on what kind of technologies to be applied to
what kind of Smart Cities applications\, e.g.\, WoT\, Automotive\, Geospat
ial\, VR/AR\, Speech and Semantic Web to be applied to improved accessibil
ity\, visitor guidance and energy management\n* Use cases and requirements
for Smart Cities\n\nAgenda\n\n**Chairs:**\nKazuyuki Ashimura\, Michael Ko
ster\n\n**Description:**\nBased on the discussion during the [W3C workshop
on Smart Cities](https://www.w3.org/2021/06/smartcities-workshop/report.h
tml) in 2021 and then two follow-up breakout sessions with invited key sta
keholders from related SDOs ([one during TPAC 2022](https://www.w3.org/202
2/09/14-smartcities-minutes.html) and [another during TPAC 2023](https://w
ww.w3.org/2023/09/13-smartcities-minutes.html))\, we identified the stakeh
olders around Smart City standardization and reasonable applications for S
mart City technologies. In addition\, we got thoughtful input on how to im
prove the [draft Charter](https://w3c.github.io/smartcities-workshop/draft
-charter/index.html) Charter of the proposed Web-based Digital Twins for S
mart Cities Interest Group for further discussions.\n\nSome of the key inp
ut included:\n* "Digital Twins" should be the key concept for Smart Cities
standardization.\n* Web standards\, e.g.\, Web of Things (WoT)\, Decentra
lized Identifiers (DID) and Verifiable Credentials (VC)\, should be consid
ered as possible key modules for the possible Web-based Digital Twins fram
ework.\n* Standard vocabulary for semantic interoperability is also requir
ed for the platform.\n* Collaboration by related SDOs is necessary for fur
ther discussion\, and W3C should become the central hub for the discussion
given Web standards play very important roles.\n\nNow the [Web-based Digi
tal Twins for Smart Cities Interest Group](https://www.w3.org/2024/06/smar
t-cities/) has been launched\, and we'd like to start actual discussion ab
out with the key stakeholders from related SDOs\, industries and coutries/
cities to work on the following deliverables of the Interest Group:\n* Sur
vey on the existing technologies and standards for Smart Cities\, e.g.\, p
ossible building blocks of Digital Twin Framework and standardized Vocabul
aries for Smart Cities\n* Best Practices on what kind of technologies to b
e applied to what kind of Smart Cities applications\, e.g.\, WoT\, Automot
ive\, Geospatial\, VR/AR\, Speech and Semantic Web to be applied to improv
ed accessibility\, visitor guidance and energy management\n* Use cases and
requirements for Smart Cities\n\n**Goal(s):**\nFollowing the [breakout di
scussion during TPAC 2023](https://www.w3.org/2023/09/13-smartcities-minut
es.html)\, we'll summarize the discussion around Smart Cities within W3C s
o far\, share the [Charter of the Web-based Digital Twins for Smart Cities
IG](https://www.w3.org/2024/06/smart-cities/)\, and ask the key steakhold
ers to join the discussion of the IG to kick-start the group's activity.\n
\n\n**Agenda:**\n1. Review the discussion so far (Workshop and follow-up m
eetings)\n2. Review the [IG Charter](https://www.w3.org/2024/06/smart-citi
es/)\n3. Discuss next steps: high-priority issues\, clarify which existing
work to be considered\, how to proceed the discussion (monthly calls?)\n\
n**Materials:**\n- [slides](https://www.w3.org/2024/Talks/0925-smartcities
-ka/20240925-smartcities-ka.pdf)\n- [minutes](https://www.w3.org/2024/09/2
5-smartcities-minutes.html)\n- [Session proposal on GitHub](https://github
.com/w3c/tpac2024-breakouts/issues/62)
STATUS:CONFIRMED
CREATED:20240916T215701Z
LAST-MODIFIED:20241002T115850Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:-1 Lower Level - Catalina 1
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:127be7ac-91d0-4001-82b1-0958cc22ba4d
DTSTAMP:20241002T131656Z
SUMMARY:What can W3C do for members?
DTSTART;TZID=America/Los_Angeles:20240925T160000
DTEND;TZID=America/Los_Angeles:20240925T164500
DESCRIPTION:https://www.w3.org/events/meetings/127be7ac-91d0-4001-82b1-0958
cc22ba4d/\n\nW3C wants to know how to improve member engagement and member
retention. What would you like to see W3C do for you and your organizatio
n? Are you interested in regional meetups? Information about charters and
recommendations that are relevant to your organization? Creating relations
hips with other standards organizations? Tell us what you would like to se
e W3C do for you. This session will have a short introduction and then be
an open conversation.\n\nAgenda\n\n**Chairs:**\nTzviya Siegman\, Naomi Yos
hizawa\n\n**Description:**\nW3C wants to know how to improve member engage
ment and member retention. What would you like to see W3C do for you and y
our organization? Are you interested in regional meetups? Information abou
t charters and recommendations that are relevant to your organization? Cre
ating relationships with other standards organizations? Tell us what you w
ould like to see W3C do for you. This session will have a short introducti
on and then be an open conversation.\n\n**Goal(s):**\nBrainstorming for Me
mber engagement\n\n\n**Agenda:**\n* Intro to W3C Member Engagement\n* Disc
ussion\n\n**Materials:**\n- [minutes](https://www.w3.org/2024/09/25-w3c-fo
r-members-minutes.html)\n- [Session proposal on GitHub](https://github.com
/w3c/tpac2024-breakouts/issues/55)
STATUS:CONFIRMED
CREATED:20240916T215451Z
LAST-MODIFIED:20241002T131656Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - San Clemente
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:6ec14ef1-ecaa-437a-a8d7-b190a3ebbb61
DTSTAMP:20241016T222631Z
SUMMARY:WinterCG
DTSTART;TZID=America/Los_Angeles:20240925T160000
DTEND;TZID=America/Los_Angeles:20240925T164500
DESCRIPTION:https://www.w3.org/events/meetings/6ec14ef1-ecaa-437a-a8d7-b190
a3ebbb61/\n\nWeb platform APIs are typically specified having web browsers
as their main target. However\, there is a large set of JavaScript runtim
es that benefit from having a common API surface with the web platform.\n\
nWinterCG is a W3C Community Group focused on the needs of such runtimes\,
particularly in the server side. The main focus of this CG has been to wo
rk on a minimum subset of web platform APIs that all such runtimes would s
upport (the WinterCG [Minimum Common API](https://common-min-api.proposal.
wintercg.org))\, but we also work on identifying areas where such runtimes
would benefit from changes in the web platform specs.\n\nAgenda: https://
people.igalia.com/abotella/pub/TPAC-2024-WinterCG/\n\nAgenda\n\n**Chairs:*
*\nAndreu Botella\n\n**Description:**\nWeb platform APIs are typically spe
cified having web browsers as their main target. However\, there is a larg
e set of JavaScript runtimes that benefit from having a common API surface
with the web platform.\n\nWinterCG is a W3C Community Group focused on th
e needs of such runtimes\, particularly in the server side. The main focus
of this CG has been to work on a minimum subset of web platform APIs that
all such runtimes would support (the WinterCG [Minimum Common API](https:
//common-min-api.proposal.wintercg.org))\, but we also work on identifying
areas where such runtimes would benefit from changes in the web platform
specs.\n\n**Goal(s):**\nExploring the collaboration between the web platfo
rm and server-side runtimes.\n\n\n\n**Materials:**\n- [slides](hhttps://ww
w.w3.org/2024/Talks/TPAC/breakouts/wintercg.html)\n- [minutes](https://www
.w3.org/2024/09/25-wintercg-minutes.html)\n- [Session proposal on GitHub](
https://github.com/w3c/tpac2024-breakouts/issues/76)
STATUS:CONFIRMED
CREATED:20240916T215939Z
LAST-MODIFIED:20241016T222631Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - Capistrano
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:55a825e5-f1d5-4f18-990a-3d24aa18f845
DTSTAMP:20240926T000108Z
SUMMARY:W3C Plenary
DTSTART;TZID=America/Los_Angeles:20240925T170000
DTEND;TZID=America/Los_Angeles:20240925T180000
DESCRIPTION:https://www.w3.org/events/meetings/55a825e5-f1d5-4f18-990a-3d24
aa18f845/\n\nThe regular W3C Advisory Committee Meeting will be replaced t
his year by a plenary open to all TPAC2024 attendees. The plenary will cov
er W3C business and consortium updates.\n\nAgenda: https://www.w3.org/2024
/09/TPAC/ac-agenda.html
STATUS:CONFIRMED
CREATED:20240614T154208Z
LAST-MODIFIED:20240926T000108Z
SEQUENCE:9
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Advisory Committee
:mailto:w3c-ac-members@w3.org
LOCATION:2 Ballroom level - California C
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:b2d0c006-9e23-4031-b523-b21542630064
DTSTAMP:20260227T224225Z
SUMMARY:W3C@30
DTSTART;TZID=America/Los_Angeles:20240925T181000
DTEND;TZID=America/Los_Angeles:20240925T220000
DESCRIPTION:https://www.w3.org/events/meetings/b2d0c006-9e23-4031-b523-b215
42630064/\n\nWhile 1 October 2024 is the date of the 30th anniversary of t
he World Wide Web Consortium\, we will hold W3C@30 on *Wednesday 25 Septem
ber 2024*\, taking the opportunity that the web standards community will b
e gathered in Anaheim\, CA\, USA\, at our annual TPAC conference.\n\nWe wi
ll celebrate three decades of W3C and of advances in the Web\, demonstrate
the incredible impact of W3C standards on the world\, imagine the possibi
lities for the next 30 years of the Web\, and enjoy ourselves during an au
thentic evening of talks and a gala.\n\nAgenda: https://www.w3.org/2024/09
/TPAC/w3c-30.html
STATUS:CONFIRMED
CREATED:20240917T175530Z
LAST-MODIFIED:20260227T224225Z
SEQUENCE:0
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Advisory Board:mai
lto:w3c-ac-members@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Advisory Committee
:mailto:w3c-ac-members@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Board Directors:ma
ilto:board-directors@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Technical Architec
ture Group:mailto:tag@w3.org
ATTENDEE;CN=Panos Astithas:mailto:pastithas@google.com
ATTENDEE;CN=Bruce Bailey:mailto:bruce@bailey4.us
ATTENDEE;CN=Bert Bos:mailto:bert@w3.org
ATTENDEE;CN=Aykut Bulut:mailto:aykutb@google.com
ATTENDEE;CN=Pierre-Antoine Champin:mailto:pierre-antoine@w3.org
ATTENDEE;CN=Ioana Chiorean:mailto:ioana@interledger.org
ATTENDEE;CN=Matias Compiano Rielo:mailto:matias.compiano@mercadolibre.com
ATTENDEE;CN=Jan Jaap de Groot:mailto:janjaap@abra.ai
ATTENDEE;CN=Ivan Herman:mailto:ivan@w3.org
ATTENDEE;CN=Dave Hunt:mailto:dave.hunt@gmail.com
ATTENDEE;CN=Ian Jacobs:mailto:ij@w3.org
ATTENDEE;CN=Ege Korkan:mailto:ege.korkan@siemens.com
ATTENDEE;CN=Pete LePage:mailto:pete.lepage@pobox.com
ATTENDEE;CN=Michael McCool:mailto:michael.d.mccool@gmail.com
ATTENDEE;CN=Nigel Megitt:mailto:nigel.megitt@bbc.co.uk
ATTENDEE;CN=Niklas Merz:mailto:niklasmerz@apache.org
ATTENDEE;CN=Adam Page:mailto:adam.page@hilton.com
ATTENDEE;CN=Alexandra Reimers:mailto:areimers@google.com
ATTENDEE;CN=Adrian Roselli:mailto:w3c@adrianroselli.com
ATTENDEE;CN=Vincent Scheib:mailto:scheib@google.com
ATTENDEE;CN=Florian Scholz:mailto:florian@openwebdocs.org
ATTENDEE;CN=Lukas Weichselbaum:mailto:lwe@google.com
ATTENDEE;CN=Frankie Wolf:mailto:frankie@a11ybuddy.info
LOCATION:online & Hilton Anaheim: California Ballroom C\, Ballroom Level\,
Second Floor (Talks)\, Lanai Deck\, Fifth Floor (Gala)
CATEGORIES:TPAC 2024
END:VEVENT
BEGIN:VEVENT
UID:907c55ac-443a-44dc-9d34-21b1ffd6d56a
DTSTAMP:20240926T155541Z
SUMMARY:Accessible Platform Architectures Working Group\, Accessibility Gui
delines Working Group Joint Meeting
DTSTART;TZID=America/Los_Angeles:20240926T090000
DTEND;TZID=America/Los_Angeles:20240926T103000
DESCRIPTION:https://www.w3.org/events/meetings/907c55ac-443a-44dc-9d34-21b1
ffd6d56a/\n\n\n\nAgenda\n\nAG WG is going to walk us through WCAG 3 and di
scuss how to participate.
STATUS:CONFIRMED
CREATED:20240614T163345Z
LAST-MODIFIED:20240926T155541Z
SEQUENCE:8
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Accessibility Guid
elines Working Group:mailto:public-ag-admin@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Accessible Platfor
m Architectures Working Group:mailto:public-apa@w3.org
LOCATION:4 Concourse Level - Palos Verdes
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:c57d779c-befa-45f7-9fca-91ebbaa7882d
DTSTAMP:20240926T183313Z
SUMMARY:Audio Description Community Group\, Timed Text Working Group Joint
Meeting
DTSTART;TZID=America/Los_Angeles:20240926T090000
DTEND;TZID=America/Los_Angeles:20240926T103000
DESCRIPTION:https://www.w3.org/events/meetings/c57d779c-befa-45f7-9fca-91eb
baa7882d/\n\n\n\nAgenda: https://www.w3.org/wiki/TimedText/tpac2024#Agenda
_and_Schedule\n\nAgenda\n\nJust a reminder that our joint Audio Descriptio
n Community Group and Timed Text Working Group meeting will begin in about
30 minutes\, and the agenda will be mainly a run-through of DAPT\, plus a
ny other audio description-related topics anyone wishes to raise.
STATUS:CONFIRMED
CREATED:20240614T163356Z
LAST-MODIFIED:20240926T183313Z
SEQUENCE:8
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Audio Description
Community Group:mailto:public-audio-description@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Timed Text Working
Group:mailto:public-tt@w3.org
LOCATION:4 Concourse Level - San Clemente
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:f2bf3d58-2389-4e40-9e2c-34ff8fc3b749
DTSTAMP:20240926T220413Z
SUMMARY:Browser Testing and Tools Working Group
DTSTART;TZID=America/Los_Angeles:20240926T090000
DTEND;TZID=America/Los_Angeles:20240926T180000
DESCRIPTION:https://www.w3.org/events/meetings/f2bf3d58-2389-4e40-9e2c-34ff
8fc3b749/\n\n\n\nAgenda: https://www.w3.org/wiki/WebDriver/2024-09-TPAC
STATUS:CONFIRMED
CREATED:20240614T163437Z
LAST-MODIFIED:20240926T220413Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Browser Testing an
d Tools Working Group:mailto:public-browser-tools-testing@w3.org
LOCATION:-1 Lower Level - Catalina 3
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:6dcec638-d069-4b4b-bbe3-c499c0fac3e2
DTSTAMP:20240926T220230Z
SUMMARY:Cascading Style Sheets Working Group
DTSTART;TZID=America/Los_Angeles:20240926T090000
DTEND;TZID=America/Los_Angeles:20240926T180000
DESCRIPTION:https://www.w3.org/events/meetings/6dcec638-d069-4b4b-bbe3-c499
c0fac3e2/\n\nFor this CSS meeting\, the [planning page](https://wiki.csswg
.org/planning/tpac-2024#agenda)\, including [😷 Covid protocols](https:/
/wiki.csswg.org/planning/tpac-2024#covid-protocols).\n\nAgenda: https://gi
thub.com/orgs/w3c/projects/122/views/1?layout=board
STATUS:CONFIRMED
CREATED:20240614T161635Z
LAST-MODIFIED:20240926T220230Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Cascading Style Sh
eets (CSS) Working Group:mailto:www-style@w3.org
LOCATION:2 Ballroom Level - California B
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:07901330-46b8-4f87-9a7a-23e13f2bf857
DTSTAMP:20240926T160608Z
SUMMARY:MiniApps Working Group
DTSTART;TZID=America/Los_Angeles:20240926T090000
DTEND;TZID=America/Los_Angeles:20240926T110000
DESCRIPTION:https://www.w3.org/events/meetings/07901330-46b8-4f87-9a7a-23e1
3f2bf857/\n\n\n\nAgenda: https://github.com/w3c/miniapp/issues/213\n\nAgen
da\n\n1. Logistics & Administrivia\n2. Status of specifications\n3. Propos
als and next steps for the group
STATUS:CONFIRMED
CREATED:20240614T161704Z
LAST-MODIFIED:20240926T160608Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=MiniApps Working G
roup:mailto:public-miniapps-wg@w3.org
LOCATION:-1 Lower Level - Catalina 2
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:ed174942-fbc7-459b-a1d2-9277bdd022ae
DTSTAMP:20241004T155128Z
SUMMARY:RDF-star Working Group
DTSTART;TZID=America/Los_Angeles:20240926T090000
DTEND;TZID=America/Los_Angeles:20240926T123000
DESCRIPTION:https://www.w3.org/events/meetings/ed174942-fbc7-459b-a1d2-9277
bdd022ae/\n\n\n\nAgenda\n\n1. Un-star operation to support RDF Dataset Can
onicalization? [1]\n2. Shape languages and validation features [2]\n3. Mat
erial about `rdf:ReificationProperty` [3]\n4. Addressing SPARQL EXISTS err
ata [4]\n5. Define an interpretation of Triple Terms [5]\n6. Backlog to ad
d additional issues [6]\n7. Any Other Business (AOB)\, time permitting\n\n
[1]: https://github.com/w3c/rdf-star-wg/issues/114\n[2]: https://github.co
m/w3c/sparql-service-description/issues/26\n[3]: https://github.com/w3c/rd
f-star-wg/issues/127\n[4]: https://github.com/w3c/sparql-query/issues/156\
n[5]: https://github.com/w3c/rdf-semantics/issues/49\n[6]: https://github.
com/orgs/w3c/projects/20/views/7
STATUS:CONFIRMED
CREATED:20240614T161732Z
LAST-MODIFIED:20241004T155128Z
SEQUENCE:7
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=RDF & SPARQL Worki
ng Group:mailto:public-rdf-star-wg@w3.org
LOCATION:4 Concourse Level - La Jolla
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:25b6f567-2d0d-4dee-9b9b-5906fd555aba
DTSTAMP:20240927T140949Z
SUMMARY:Verifiable Credentials Working Group
DTSTART;TZID=America/Los_Angeles:20240926T090000
DTEND;TZID=America/Los_Angeles:20240926T123000
DESCRIPTION:https://www.w3.org/events/meetings/25b6f567-2d0d-4dee-9b9b-5906
fd555aba/\n\n\n\nAgenda\n\n9:00\nChairs Introduction and logistics\n9:45\n
VC Data Model 2.0\n10:30\nBreak\n11:00\nVC Data Integrity
STATUS:CONFIRMED
CREATED:20240614T161648Z
LAST-MODIFIED:20240927T140949Z
SEQUENCE:7
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Verifiable Credent
ials Working Group:mailto:public-vc-wg@w3.org
LOCATION:4 Concourse Level - Capistrano
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:5b918f03-a2a6-4b13-9391-252f61bcc09c
DTSTAMP:20240926T175750Z
SUMMARY:Web Application Security Working Group
DTSTART;TZID=America/Los_Angeles:20240926T090000
DTEND;TZID=America/Los_Angeles:20240926T123000
DESCRIPTION:https://www.w3.org/events/meetings/5b918f03-a2a6-4b13-9391-252f
61bcc09c/\n\n\n\nAgenda: https://github.com/w3c/webappsec/blob/main/meetin
gs/2024/2024-09-TPAC-agenda.md\n\nAgenda\n\n[26.09.2024\, 9:00 - 12:30](ht
tps://www.w3.org/events/meetings/5b918f03-a2a6-4b13-9391-252f61bcc09c/): [
4 Concourse Level - Laguna](https://www.w3.org/2024/09/TPAC/schedule.html#
map)\n----------------------------------------------------\n\n* **9:00 - 9
:15**: ☕ and agenda bashing.\n* **9:30 - 10:30**: Following up on breako
ut sessions\, and/or topics we didn't get to on Monday\n * [Deprecations]
(https://github.com/w3c/tpac2024-breakouts/issues/20)\, [PEPC](https://git
hub.com/WICG/PEPC/blob/main/explainer.md)\, [DBSC](https://github.com/WICG
/dbsc/) all seem like they might benefit from more conversation.\n * We c
an allocate time in this slot more clearly in the hallways on Wednesday.\n
* **10:30 - 11:00**: ☕ & 🍰 @ [Lanai Deck\, Fifth Floor](https://www.w
3.org/2024/09/TPAC/schedule.html#map)\n* **11:00 - 11:45**: Isolation\n *
(~30m) Cross-Origin Isolation\n * [Document Isolation Policy](https:
//wicg.github.io/document-isolation-policy/) (@camillelamy)\n * (~15m) [R
ealms Initialization Control](https://github.com/WICG/Realms-Initializatio
n-Control) (@weizman)\n* **11:45 - 12:20**: Cookies\n * (~10m) `sandbox="
allow-same-site-none-cookies"` (@aamuley)\n * (~10m) [Cookie Layering](ht
tps://github.com/httpwg/http-extensions/issues/2084) / [RFC6265tre](https:
//johannhof.github.io/draft-annevk-johannhof-httpbis-cookies/draft-annevk-
johannhof-httpbis-cookies.html) (@johannhof\, @annevk)\n * (~10m) [CHIPS]
(https://github.com/privacycg/CHIPS) (@johnwilander\, @dcthetall)\n* **12:
20 - 12:30**: Next steps\, followup.
STATUS:CONFIRMED
CREATED:20240614T163318Z
LAST-MODIFIED:20240926T175750Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Web Application Se
curity Working Group:mailto:public-webappsec@w3.org
LOCATION:4 Concourse Level - Laguna
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:952b3813-f07f-43fb-b3ff-f9ff8d59955f
DTSTAMP:20240925T174957Z
SUMMARY:Web Editing Working Group
DTSTART;TZID=America/Los_Angeles:20240926T090000
DTEND;TZID=America/Los_Angeles:20240926T180000
DESCRIPTION:https://www.w3.org/events/meetings/952b3813-f07f-43fb-b3ff-f9ff
8d59955f/\n\n\n\nAgenda: https://github.com/w3c/editing/issues/469\n\nAgen
da\n\nhttps://github.com/w3c/editing/issues/469
STATUS:CONFIRMED
CREATED:20240614T161646Z
LAST-MODIFIED:20240925T174957Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Web Editing Workin
g Group:mailto:public-editing-tf@w3.org
LOCATION:-1 Lower Level - Catalina 5
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:23533178-7423-4ffa-a962-896f86286453
DTSTAMP:20240926T224116Z
SUMMARY:Web Payment Security Interest Group
DTSTART;TZID=America/Los_Angeles:20240926T090000
DTEND;TZID=America/Los_Angeles:20240926T180000
DESCRIPTION:https://www.w3.org/events/meetings/23533178-7423-4ffa-a962-896f
86286453/\n\n\n\nAgenda: https://www.w3.org/securepay/wiki/Meeting/Sep2024
STATUS:CONFIRMED
CREATED:20240614T161645Z
LAST-MODIFIED:20240926T224116Z
SEQUENCE:9
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Web Payment Securi
ty Interest Group:mailto:member-wpsig@w3.org
LOCATION:4 Concourse Level - Oceanside
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:bfb7d496-d173-4aec-b566-e5ad4c1cc8f5
DTSTAMP:20240926T211653Z
SUMMARY:Web Performance Working Group
DTSTART;TZID=America/Los_Angeles:20240926T090000
DTEND;TZID=America/Los_Angeles:20240926T160000
DESCRIPTION:https://www.w3.org/events/meetings/bfb7d496-d173-4aec-b566-e5ad
4c1cc8f5/\n\n\n\nAgenda: https://bit.ly/webperf-tpac24\n\nAgenda\n\n* Serv
ice Worker TimingInfo\n* JavaScript loading\n\n` `\n\n* Soft Navigatio
ns\n\nLunch\n\n* Task Attribution: what is it\, and how it might help beyo
nd soft-navs (...RUM tooling\, LCP hover\, async event timing\, resource i
nitiators…)\n* Crash Reporting\n* Monitoring and Deployment Principles d
oc
STATUS:CONFIRMED
CREATED:20240614T163422Z
LAST-MODIFIED:20240926T211653Z
SEQUENCE:7
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Web Performance Wo
rking Group:mailto:public-web-perf@w3.org
LOCATION:4 Concourse Level - Huntington
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:1377e921-ae8f-4b47-9e81-3a800077c95c
DTSTAMP:20240926T164606Z
SUMMARY:WebDX Community Group
DTSTART;TZID=America/Los_Angeles:20240926T090000
DTEND;TZID=America/Los_Angeles:20240926T103000
DESCRIPTION:https://www.w3.org/events/meetings/1377e921-ae8f-4b47-9e81-3a80
0077c95c/\n\nWebDX CG meeting at TPAC 2024. If you're used to joining WebD
X CG meetings\, beware:\n1. This meeting is **one hour later** than usual
(9am Pacific time\, noon Boston\, 4pm UTC\, 5pm London\, 6pm Paris)\n2. We
'll meet on **Zoom** (and not on Google Meet)\n\nAgenda: https://docs.goog
le.com/document/d/1ree75ImLZjf60lTZ3BhCaLHygxgywr7SBXp-q0xPs8A/edit
STATUS:CONFIRMED
CREATED:20240614T163458Z
LAST-MODIFIED:20240926T164606Z
SEQUENCE:5
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=WebDX Community Gr
oup:mailto:public-webdx@w3.org
LOCATION:-1 Lower Level - Catalina 7
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:ec0c949e-8a42-4e27-a869-505f07c6638a
DTSTAMP:20240926T174121Z
SUMMARY:Accessible Platform Architectures Working Group\, WHATWG Joint Meet
ing
DTSTART;TZID=America/Los_Angeles:20240926T110000
DTEND;TZID=America/Los_Angeles:20240926T123000
DESCRIPTION:https://www.w3.org/events/meetings/ec0c949e-8a42-4e27-a869-505f
07c6638a/\n\n\n\nAgenda: https://github.com/whatwg/meta/issues/326\n\nAgen
da\n\nWe have two main topics to discuss\, both regarding WAI-Adapt TF's w
ork...\n\n* [Symbols](https://github.com/w3c/adapt/blob/add-explainers/exp
lainers/symbols.md) - we would like to address present technical questions
/blocks regarding authoring considerations.\n\n* [Well-known destinations]
(https://github.com/w3c/adapt/blob/add-explainers/explainers/well-known-de
stinations.md) - we would like your views on the best way to proceed with
this spec: we currently have two potential routes to implementation.
STATUS:CONFIRMED
CREATED:20240614T163349Z
LAST-MODIFIED:20240926T174121Z
SEQUENCE:5
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Accessible Platfor
m Architectures Working Group:mailto:public-apa@w3.org
LOCATION:4 Concourse Level - Redondo
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:c57f3fb1-b90c-4f08-8a9e-2b71e92f5b05
DTSTAMP:20240916T231517Z
SUMMARY:Internationalization Working Group\, Accessibility Guidelines Worki
ng Group Joint Meeting
DTSTART;TZID=America/Los_Angeles:20240926T110000
DTEND;TZID=America/Los_Angeles:20240926T123000
DESCRIPTION:https://www.w3.org/events/meetings/c57f3fb1-b90c-4f08-8a9e-2b71
e92f5b05/\n\n\n\nAgenda\n\nObjective: Discuss process for gathering input
to WCAG 3\n\n* Provide overview and get reactions\n* Focus a bit more on u
ser agent recommendations\n* Discuss QA process
STATUS:CONFIRMED
CREATED:20240614T163341Z
LAST-MODIFIED:20240916T231517Z
SEQUENCE:7
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Accessibility Guid
elines Working Group:mailto:public-ag-admin@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Internationalizati
on Working Group:mailto:public-i18n-core@w3.org
LOCATION:4 Concourse Level - Palos Verdes
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:b3cc2ea2-1663-4282-a787-19dfa2cabba3
DTSTAMP:20240926T180730Z
SUMMARY:Media Working Group
DTSTART;TZID=America/Los_Angeles:20240926T110000
DTEND;TZID=America/Los_Angeles:20240926T123000
DESCRIPTION:https://www.w3.org/events/meetings/b3cc2ea2-1663-4282-a787-19df
a2cabba3/\n\n\n\nAgenda: https://github.com/w3c/media-wg/wiki/TPAC-2024
STATUS:CONFIRMED
CREATED:20240614T163327Z
LAST-MODIFIED:20240926T180730Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Media Working Grou
p:mailto:public-media-wg@w3.org
LOCATION:4 Concourse Level - San Clemente
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:d132cf7f-a9df-4ef8-9823-87e6986441d1
DTSTAMP:20240926T190000Z
SUMMARY:Web Platform Incubator Community Group
DTSTART;TZID=America/Los_Angeles:20240926T110000
DTEND;TZID=America/Los_Angeles:20240926T160000
DESCRIPTION:https://www.w3.org/events/meetings/d132cf7f-a9df-4ef8-9823-87e6
986441d1/\n\n\n\nAgenda: https://github.com/WICG/admin/issues/194
STATUS:CONFIRMED
CREATED:20240614T163023Z
LAST-MODIFIED:20240926T190000Z
SEQUENCE:5
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Web Platform Incub
ator Community Group:mailto:public-wicg@w3.org
LOCATION:2 Ballroom Level - California A
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:3abb0d62-fb42-4d03-847f-d57393c85607
DTSTAMP:20240924T004735Z
SUMMARY:WebExtensions Community Group
DTSTART;TZID=America/Los_Angeles:20240926T110000
DTEND;TZID=America/Los_Angeles:20240926T123000
DESCRIPTION:https://www.w3.org/events/meetings/3abb0d62-fb42-4d03-847f-d573
93c85607/\n\n\n\nAgenda: https://github.com/w3c/webextensions/wiki/TPAC-20
24-Coordination#thursday
STATUS:CONFIRMED
CREATED:20240704T125808Z
LAST-MODIFIED:20240924T004735Z
SEQUENCE:4
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=WebExtensions Comm
unity Group:mailto:public-webextensions@w3.org
LOCATION:-1 Lower Level - Catalina 7
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:0cd3eeb5-6d66-45fd-bf08-e42114b1f3f9
DTSTAMP:20240926T162821Z
SUMMARY:WebView Community Group
DTSTART;TZID=America/Los_Angeles:20240926T110000
DTEND;TZID=America/Los_Angeles:20240926T123000
DESCRIPTION:https://www.w3.org/events/meetings/0cd3eeb5-6d66-45fd-bf08-e421
14b1f3f9/\n\n\n\nAgenda: https://github.com/orgs/WebView-CG/discussions/5#
discussioncomment-10336140
STATUS:CONFIRMED
CREATED:20240614T163457Z
LAST-MODIFIED:20240926T162821Z
SEQUENCE:8
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=WebView Community
Group:mailto:public-webview@w3.org
LOCATION:-1 Lower Level - Catalina 1
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:8b30448b-de20-4eb1-8cc2-df4547ed4891
DTSTAMP:20240926T205259Z
SUMMARY:Accessibility Guidelines Working Group\, Accessible Rich Internet A
pplications Working Group Joint Meeting
DTSTART;TZID=America/Los_Angeles:20240926T140000
DTEND;TZID=America/Los_Angeles:20240926T160000
DESCRIPTION:https://www.w3.org/events/meetings/8b30448b-de20-4eb1-8cc2-df45
47ed4891/\n\n\n\nAgenda\n\n* WCAG3 ARIA Techniques\n * Scope\n * Key sta
keholders involvement\n * Development process
STATUS:CONFIRMED
CREATED:20240614T163343Z
LAST-MODIFIED:20240926T205259Z
SEQUENCE:7
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Accessibility Guid
elines Working Group:mailto:public-ag-admin@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Accessible Rich In
ternet Applications Working Group:mailto:public-aria@w3.org
LOCATION:4 Concourse Level - Palos Verdes
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:362ce870-78a1-40df-96fb-4c3a7aac0399
DTSTAMP:20240926T210751Z
SUMMARY:Anti-Fraud Community Group
DTSTART;TZID=America/Los_Angeles:20240926T140000
DTEND;TZID=America/Los_Angeles:20240926T160000
DESCRIPTION:https://www.w3.org/events/meetings/362ce870-78a1-40df-96fb-4c3a
7aac0399/\n\n\n\nAgenda: https://lists.w3.org/Archives/Public/public-antif
raud/2024Sep/0000.html
STATUS:CONFIRMED
CREATED:20240614T163453Z
LAST-MODIFIED:20240926T210751Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Anti-Fraud Communi
ty Group:mailto:public-antifraud@w3.org
LOCATION:-1 Lower Level - Catalina 7
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:59c03681-a916-4f8e-a8b0-9cfaff8e5cdc
DTSTAMP:20240916T231624Z
SUMMARY:Immersive Web Working Group
DTSTART;TZID=America/Los_Angeles:20240926T140000
DTEND;TZID=America/Los_Angeles:20240926T180000
DESCRIPTION:https://www.w3.org/events/meetings/59c03681-a916-4f8e-a8b0-9cfa
ff8e5cdc/\n\nTPAC 2024 Working Group Meetings\n\nAgenda: https://github.co
m/immersive-web/administrivia/tree/main/TPAC2024#agenda\n\nAgenda\n\n## Ag
enda\n\n| | Tuesday 24/9 | Wednesday 25/9 | Thursday 26/9
|\n| ------------- | -------------- | -------------- | ------------- |\n|
9:00 | Introduction | TBD | |\n| 9:30
| Depth Sensing | | |\n| 10:00
| Depth Sensing | | |\n| 10:30 |
Break | Break | Break |\n| 11:00 | [Web
Apps Joint Meeting](https://www.w3.org/events/meetings/e3724be4-18f0-4846
-93c4-ddf0f0839697/)| | |\n| 11:30 |
[Web Apps Joint Meeting](https://www.w3.org/events/meetings/e3724be4-18f0-
4846-93c4-ddf0f0839697/)| | |\n| 12:00 |
| | |\n| 12:30 | Lunch
| Lunch | Lunch |\n| 13:00 |
| | |\n| 13:30 | |
| |\n| 14:00 | Body Tracking |
| WebXR-WebGPU |\n| 14:30 | Body Tracking |
| WebXR-WebGPU |\n| 15:00 | Model |
| WebXR-WebGPU |\n| 15:30 | Model | | Un
conference |\n| 16:00 | Break | Break | Break
|\n| 16:30 | Model | | Unconference
|\n| 17:00 | Model | | Unconference |\n
| 17:30 | Model | | Unconference |\n| 18:
00 | | W3C@30 | |
STATUS:CONFIRMED
CREATED:20240614T163407Z
LAST-MODIFIED:20240916T231624Z
SEQUENCE:7
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Immersive Web Work
ing Group:mailto:public-immersive-web-wg@w3.org
LOCATION:-1 Lower Level - Catalina 1
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:fee8eb8e-9861-4967-b011-3f54ababe841
DTSTAMP:20240926T150726Z
SUMMARY:JSON-LD Working Group\, JSON for Linked Data Community Group Joint
Meeting
DTSTART;TZID=America/Los_Angeles:20240926T140000
DTEND;TZID=America/Los_Angeles:20240926T160000
DESCRIPTION:https://www.w3.org/events/meetings/fee8eb8e-9861-4967-b011-3f54
ababe841/\n\n
STATUS:CONFIRMED
CREATED:20240909T172101Z
LAST-MODIFIED:20240926T150726Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=JSON for Linked Da
ta Community Group:mailto:public-json-ld@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=JSON-LD Working Gr
oup:mailto:public-json-ld-wg@w3.org
LOCATION:4 Concourse Level - Redondo
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:b576f610-4ed9-4e71-9709-31cb1a4d462f
DTSTAMP:20240926T210205Z
SUMMARY:Spatial Data on the Web Working Group
DTSTART;TZID=America/Los_Angeles:20240926T140000
DTEND;TZID=America/Los_Angeles:20240926T180000
DESCRIPTION:https://www.w3.org/events/meetings/b576f610-4ed9-4e71-9709-31cb
1a4d462f/\n\n
STATUS:CONFIRMED
CREATED:20240614T163427Z
LAST-MODIFIED:20240926T210205Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Spatio-temporal Da
ta on the Web Working Group:mailto:public-sdw-wg@w3.org
LOCATION:4 Concourse Level - La Jolla
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:c8d5f3d3-7564-4a60-bc1b-ef349e9b74ad
DTSTAMP:20240926T210011Z
SUMMARY:W3C Chapters
DTSTART;TZID=America/Los_Angeles:20240926T140000
DTEND;TZID=America/Los_Angeles:20240926T180000
DESCRIPTION:https://www.w3.org/events/meetings/c8d5f3d3-7564-4a60-bc1b-ef34
9e9b74ad/\n\n
STATUS:CONFIRMED
CREATED:20240625T150053Z
LAST-MODIFIED:20240926T210011Z
SEQUENCE:5
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
LOCATION:4 Concourse Level - Coronado
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:09603c14-86e3-4c4a-b66f-37d2df32def5
DTSTAMP:20240924T185144Z
SUMMARY:Web of Things Working Group\, Web of Things Interest Group Joint Me
eting
DTSTART;TZID=America/Los_Angeles:20240926T140000
DTEND;TZID=America/Los_Angeles:20240926T160000
DESCRIPTION:https://www.w3.org/events/meetings/09603c14-86e3-4c4a-b66f-37d2
df32def5/\n\n\n\nAgenda: https://www.w3.org/WoT/IG/wiki/Wiki_for_F2F_2024_
planning
STATUS:CONFIRMED
CREATED:20240614T163403Z
LAST-MODIFIED:20240924T185144Z
SEQUENCE:7
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Web of Things Inte
rest Group:mailto:public-wot-ig@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Web of Things Work
ing Group:mailto:public-wot-wg@w3.org
LOCATION:4 Concourse Level - Capistrano
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:b2c200b8-7362-4330-b74c-7b2efc05d87f
DTSTAMP:20240927T001827Z
SUMMARY:Web Real-Time Communications Working Group\, Media Working Group Jo
int Meeting
DTSTART;TZID=America/Los_Angeles:20240926T140000
DTEND;TZID=America/Los_Angeles:20240926T160000
DESCRIPTION:https://www.w3.org/events/meetings/b2c200b8-7362-4330-b74c-7b2e
fc05d87f/\n\n\n\nAgenda: https://www.w3.org/2011/04/webrtc/wiki/September_
26_2024
STATUS:CONFIRMED
CREATED:20240614T161702Z
LAST-MODIFIED:20240927T001827Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Media Working Grou
p:mailto:public-media-wg@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Web Real-Time Comm
unications Working Group:mailto:public-webrtc@w3.org
LOCATION:4 Concourse Level - San Clemente
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:7f85c868-f492-4dfb-951b-a577e7cc929e
DTSTAMP:20240916T231922Z
SUMMARY:WebAuthn Adoption Community Group
DTSTART;TZID=America/Los_Angeles:20240926T140000
DTEND;TZID=America/Los_Angeles:20240926T160000
DESCRIPTION:https://www.w3.org/events/meetings/7f85c868-f492-4dfb-951b-a577
e7cc929e/\n\n
STATUS:CONFIRMED
CREATED:20240625T155512Z
LAST-MODIFIED:20240916T231922Z
SEQUENCE:5
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=WebAuthn Adoption
Community Group:mailto:public-webauthn-adoption@w3.org
LOCATION:4 Concourse Level - Manhattan
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:63046968-03e3-4e6d-aaf3-6ffe396a2ca1
DTSTAMP:20240926T232924Z
SUMMARY:JSON-LD Working Group\, Web of Things Working Group Joint Meeting
DTSTART;TZID=America/Los_Angeles:20240926T163000
DTEND;TZID=America/Los_Angeles:20240926T180000
DESCRIPTION:https://www.w3.org/events/meetings/63046968-03e3-4e6d-aaf3-6ffe
396a2ca1/\n\n\n\nAgenda: https://www.w3.org/WoT/IG/wiki/Wiki_for_F2F_2024_
planning
STATUS:CONFIRMED
CREATED:20240614T163315Z
LAST-MODIFIED:20240926T232924Z
SEQUENCE:8
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=JSON-LD Working Gr
oup:mailto:public-json-ld-wg@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Web of Things Work
ing Group:mailto:public-wot-wg@w3.org
LOCATION:4 Concourse Level - Capistrano
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:7d0047b9-8ccc-46d1-acdb-02adf726e67e
DTSTAMP:20240926T233645Z
SUMMARY:Media Working Group
DTSTART;TZID=America/Los_Angeles:20240926T163000
DTEND;TZID=America/Los_Angeles:20240926T180000
DESCRIPTION:https://www.w3.org/events/meetings/7d0047b9-8ccc-46d1-acdb-02ad
f726e67e/\n\n\n\nAgenda: https://github.com/w3c/media-wg/wiki/TPAC-2024
STATUS:CONFIRMED
CREATED:20240614T163328Z
LAST-MODIFIED:20240926T233645Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Media Working Grou
p:mailto:public-media-wg@w3.org
LOCATION:4 Concourse Level - San Clemente
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:7e85c113-b78c-4e17-817f-21e81f424fd7
DTSTAMP:20240926T233514Z
SUMMARY:Privacy Community Group
DTSTART;TZID=America/Los_Angeles:20240926T163000
DTEND;TZID=America/Los_Angeles:20240926T180000
DESCRIPTION:https://www.w3.org/events/meetings/7e85c113-b78c-4e17-817f-21e8
1f424fd7/\n\n\n\nAgenda: https://lists.w3.org/Archives/Public/public-priva
cycg/2024Sep/0001.html
STATUS:CONFIRMED
CREATED:20240614T163649Z
LAST-MODIFIED:20240926T233514Z
SEQUENCE:5
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Privacy Community
Group:mailto:public-privacycg@w3.org
LOCATION:2 Ballroom Level - California A
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:6a6be196-75d1-4a1f-95a5-bb9d37ea93dd
DTSTAMP:20240926T233040Z
SUMMARY:WebExtensions Community Group
DTSTART;TZID=America/Los_Angeles:20240926T163000
DTEND;TZID=America/Los_Angeles:20240926T180000
DESCRIPTION:https://www.w3.org/events/meetings/6a6be196-75d1-4a1f-95a5-bb9d
37ea93dd/\n\n\n\nAgenda: https://github.com/w3c/webextensions/wiki/TPAC-20
24-Coordination#thursday
STATUS:CONFIRMED
CREATED:20240704T125809Z
LAST-MODIFIED:20240926T233040Z
SEQUENCE:4
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=WebExtensions Comm
unity Group:mailto:public-webextensions@w3.org
LOCATION:-1 Lower Level - Catalina 7
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:8f0251f6-f18e-429d-9717-ec307ccacd52
DTSTAMP:20240927T155928Z
SUMMARY:Accessible Platform Architectures Working Group
DTSTART;TZID=America/Los_Angeles:20240927T090000
DTEND;TZID=America/Los_Angeles:20240927T103000
DESCRIPTION:https://www.w3.org/events/meetings/8f0251f6-f18e-429d-9717-ec30
7ccacd52/\n\n\n\nAgenda\n\n* APA WG re-chartering (early 2025) - scope\, d
eliverables.\n* COGA's proposed new format for the next version of ["Conte
nt Usable"](https://www.w3.org/TR/coga-usable/).\n\nAny WG/TF work can be
done here - if you have specific agenda to raise\, let us know.
STATUS:CONFIRMED
CREATED:20240730T132017Z
LAST-MODIFIED:20240927T155928Z
SEQUENCE:5
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Accessible Platfor
m Architectures Working Group:mailto:public-apa@w3.org
LOCATION:4 Concourse Level - Palos Verdes
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:de0ef52d-ba9c-493b-afc5-dae04cd77ba4
DTSTAMP:20240927T142819Z
SUMMARY:Browser Testing and Tools Working Group
DTSTART;TZID=America/Los_Angeles:20240927T090000
DTEND;TZID=America/Los_Angeles:20240927T180000
DESCRIPTION:https://www.w3.org/events/meetings/de0ef52d-ba9c-493b-afc5-dae0
4cd77ba4/\n\n\n\nAgenda: https://www.w3.org/wiki/WebDriver/2024-09-TPAC
STATUS:CONFIRMED
CREATED:20240614T163438Z
LAST-MODIFIED:20240927T142819Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Browser Testing an
d Tools Working Group:mailto:public-browser-tools-testing@w3.org
LOCATION:-1 Lower Level - Catalina 3
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:3d636a8d-df83-4889-a5bc-e2074edd56ac
DTSTAMP:20240919T064411Z
SUMMARY:Cascading Style Sheets Working Group
DTSTART;TZID=America/Los_Angeles:20240927T090000
DTEND;TZID=America/Los_Angeles:20240927T180000
DESCRIPTION:https://www.w3.org/events/meetings/3d636a8d-df83-4889-a5bc-e207
4edd56ac/\n\nFor this CSS meeting\, see [planning](https://wiki.csswg.org/
planning/tpac-2024#agenda)\, including [😷 Covid protocols](https://wiki
.csswg.org/planning/tpac-2024#covid-protocols).\n\nAgenda: https://github.
com/orgs/w3c/projects/122/views/1?layout=board
STATUS:CONFIRMED
CREATED:20240614T161636Z
LAST-MODIFIED:20240919T064411Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Cascading Style Sh
eets (CSS) Working Group:mailto:www-style@w3.org
LOCATION:2 Ballroom Level - California B
CATEGORIES:TPAC 2024,Group Meetings
END:VEVENT
BEGIN:VEVENT
UID:57789807-76fd-4d76-a1f9-e434efa7a4a9
DTSTAMP:20240925T155347Z
SUMMARY:Internationalization Working Group
DTSTART;TZID=America/Los_Angeles:20240927T090000
DTEND;TZID=America/Los_Angeles:20240927T123000
DESCRIPTION:https://www.w3.org/events/meetings/57789807-76fd-4d76-a1f9-e434
efa7a4a9/\n\nThis is a Working Group meeting during TPAC 2024.\n\nAgenda\n
\n**Topic: Info Share**\n_What interesting hallway conversations were had?
What did we learn? What needs doing? Is everyone having an excellent time
?_\n\n**Topic: Glossary Publication at Note**\n_Addison discussed the stat
us of i18n-glossary and different ways to make it work better with PLH. We
need to publish it as a Note (note Draft Note) and then make changes to t
he tools warnings. Let's discuss._\n\n**Topic: Advancing LTLI**\n_Addison
would like to discuss advancing LTLI towards Note and the existing issue t
o fold its requirements to specdev._\n\n**Topic: PR and Issue Review**\n_L
et's review some outstanding PRs and merge them or discuss issues._\n* htt
ps://github.com/w3c/bp-i18n-specdev/pull/136\n* https://github.com/w3c/bp-
i18n-specdev/pull/133\n* https://github.com/w3c/i18n-glossary/pull/77\n* h
ttps://github.com/w3c/bp-i18n-specdev/issues/21\n\n\n**Topic: Preparing fo
r WHATWG**\n_Let's discuss what we want to talk about. In Monday's meeting
we talked about:_\n* Making `input` respect locale (which is quasi-in-the
-spec\, but inconsistently implemented)\n* Fixing `
\n\nAnd this is just for assigning a certain hue as the primary co lor of a whole page — the effort is duplicated for every third-party UI component that uses colors\, fonts\, measurements\, font sizes\, etc. Same -party components can use the same naming convention to reduce effort\, bu t that doesn't work for components from different entities.\n\nTo reduce i ntegration effort\, we need to reduce the amount of information the host p age needs to communicate about its design to each individual component. So me avenues are:\n1. standardized ways to set design tokens (e.g. the page ’s primary color or serif font) in a way that can be read by other compo nents\n2. ways to _derive_ tokens from core tokens (e.g. a light tint from a primary color\, or the next smaller font size in a scale) to minimize h ow many tokens need to be communicated.\n3. Ways for components to adopt a nd repurpose page styles of existing (standard) elements\n4. ???\n\nAgenda \n\n**Chairs:**\nLea Verou\, Keith Cirkel\n\n**Description:**\nThe vision of authors being able to drop components and UI libraries into their pages and have things Just Work™ and look right (at least to a first order ap proximation) is still largely unrealized. Integrating any UI component is incredibly laborious\, as it requires manually communicating fine grained design tokens to every single component.\n\nThis [Web Awesome](https://www .kickstarter.com/projects/fontawesome/web-awesome) tutorial illustrates th e problem perfectly: \n\nhttps://youtu.be/JhfYeXLfWdI?si=vF3xRai2QrjabVFv& t=277\n\n
\n\nAnd this is just for assigning a certain hue as the primary color of a whole page — the effort is duplicated for every third-party UI component that uses colo rs\, fonts\, measurements\, font sizes\, etc. Same-party components can us e the same naming convention to reduce effort\, but that doesn't work for components from different entities.\n\nTo reduce integration effort\, we n eed to reduce the amount of information the host page needs to communicate about its design to each individual component. Some avenues are:\n1. stan dardized ways to set design tokens (e.g. the page’s primary color or ser if font) in a way that can be read by other components\n2. ways to _derive _ tokens from core tokens (e.g. a light tint from a primary color\, or the next smaller font size in a scale) to minimize how many tokens need to be communicated.\n3. Ways for components to adopt and repurpose page styles of existing (standard) elements\n4. ???\n\n**Goal(s):**\nFlesh out ideas f or potential directions\, see which are most viable in terms of I/E\n\n\n* *Agenda:**\n1. Discuss requirements and potential directions\n2. Discuss r elevant proposals:\n - https://github.com/w3c/csswg-drafts/issues/9992\n - https://github.com/w3c/csswg-drafts/issues/9999\n - https://github.com/w3 c/csswg-drafts/issues/10452\n - https://github.com/w3c/csswg-drafts/issues /9660\n - https://github.com/w3c/csswg-drafts/issues/10222\n - https://git hub.com/w3c/csswg-drafts/issues/5900\n\n**Materials:**\n- [minutes](https: //github.com/w3c/csswg-drafts/issues/10948#issuecomment-2375445066)\n- [Se ssion proposal on GitHub](https://github.com/w3c/tpac2024-breakouts/issues /92)\n\n**Track(s):**\n- Web Components STATUS:CONFIRMED CREATED:20240916T220237Z LAST-MODIFIED:20241002T114751Z 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 BEGIN:VEVENT UID:0b16a479-7aa3-48ec-a556-ec8b9aaac8c0 DTSTAMP:20241002T120833Z SUMMARY:Let’s actually fix web notifications DTSTART;TZID=America/Los_Angeles:20240925T144500 DTEND;TZID=America/Los_Angeles:20240925T154500 DESCRIPTION:https://www.w3.org/events/meetings/0b16a479-7aa3-48ec-a556-ec8b 9aaac8c0/\n\nWeb Notifications are often used as a channel for unwanted sp am. Even when the notifications are initially wanted\, it can be difficult for people to work out how to unsubscribe to their notification subscript ions. The notifications permission grants never expire. It is also a commo n observed pattern from some websites that they socially engineer people i nto accepting the notification permission\, for example by withholding sit e content or functionality until the permission is granted.\nIn this sessi on we would like to propose and discuss potential alternatives for structu rally solving the aforementioned issues. These include:\n\n#### 1: Make no tifications not-promptable\nInstead of showing an interruptive pop-up when websites request notification permission\, browsers could silently add a settings row available to the user in secondary browser UI\, like so:\n\n< img width="1303" alt="Group 2" src="https://github.com/user-attachments/as sets/4320aafa-5fa5-4eda-ada2-65d80c967ed8">\n\nThen\, if the user wishes t o subscribe to notifications from a website\, they can proactively navigat e to the browser UI to turn this toggle on. The benefit of this solution i s (even if websites socially engineer users to grant them notifications pe rmission)\, through the act of navigating to browser UI to turn on notific ations\, people inherently learn where to go to turn it off.\n\nThe drawba cks here are centered on discoverability\, i.e.\, whether users will be ab le to find how to grant notifications when they actually want them. Howeve r\, given the current prevalence of unwanted notification prompts\, this m ight be a tradeoff worth making.\n\n#### 2: Make default notifications beh aviour require an open and active tab\n\nMost other permission types exist ing today require the website to be in an open and active browser tab for the capability to work. Notifications notably differs: it allows websites to message people even if they close all tabs from that website. In some w ays\, this is the point of the Web Push API.\n\nMaking the default notific ation behaviour tied to whether tabs from that origin are open gives peopl e an intuitive way to sample notifications from a site while it’s still open\, and to silence these notifications if they are unwanted. For sites that the user trusts highly\, they can “upgrade” the permission to inc lude the ability to notify them even when tabs from that site are closed. For installed web-apps\, the "upgraded" behaviour could be the default.\n\ n#### 3: Expire stale notification permissions\n\nCurrent decisions on not ification permission prompts are permanent. The browser does not do any au tomatic clean-up of stale notification subscriptions\, even if they are fr om a site that the user has not interacted with for many years. \n\nClarif ying the purpose of the Web Push and Web Notification APIs on a philosophi cal level – amongst browser vendors as well as web developers – would allow user agents to enable helpful notifications while curbing unwanted n otifications. For example\, if we can agree that the purpose of notificati ons is to inform users about content being changed on a site\, and in resp onse\, users are expected to actually visit the sender origin within a rea sonable time window (such as within a few months)\, user agents could expi re permission grants outside that reasonable time window. It is an open qu estion if there are legitimate in-the-wild use cases for notifications tha t users only read\, never interact with\, nor do they ever visit the sendi ng website again.\n\nAgenda\n\n**Chairs:**\nSerena Chen\, Balazs Engedy\n\ n**Description:**\nWeb Notifications are often used as a channel for unwan ted spam. Even when the notifications are initially wanted\, it can be dif ficult for people to work out how to unsubscribe to their notification sub scriptions. The notifications permission grants never expire. It is also a common observed pattern from some websites that they socially engineer pe ople into accepting the notification permission\, for example by withholdi ng site content or functionality until the permission is granted.\nIn this session we would like to propose and discuss potential alternatives for s tructurally solving the aforementioned issues. These include:\n\n#### 1: M ake notifications not-promptable\nInstead of showing an interruptive pop-u p when websites request notification permission\, browsers could silently add a settings row available to the user in secondary browser UI\, like so :\n\n
\n\nThen\, if the user wi shes to subscribe to notifications from a website\, they can proactively n avigate to the browser UI to turn this toggle on. The benefit of this solu tion is (even if websites socially engineer users to grant them notificati ons permission)\, through the act of navigating to browser UI to turn on n otifications\, people inherently learn where to go to turn it off.\n\nThe drawbacks here are centered on discoverability\, i.e.\, whether users will be able to find how to grant notifications when they actually want them. However\, given the current prevalence of unwanted notification prompts\, this might be a tradeoff worth making.\n\n#### 2: Make default notificatio ns behaviour require an open and active tab\n\nMost other permission types existing today require the website to be in an open and active browser ta b for the capability to work. Notifications notably differs: it allows web sites to message people even if they close all tabs from that website. In some ways\, this is the point of the Web Push API.\n\nMaking the default n otification behaviour tied to whether tabs from that origin are open gives people an intuitive way to sample notifications from a site while it’s still open\, and to silence these notifications if they are unwanted. For sites that the user trusts highly\, they can “upgrade” the permission to include the ability to notify them even when tabs from that site are cl osed. For installed web-apps\, the "upgraded" behaviour could be the defau lt.\n\n#### 3: Expire stale notification permissions\n\nCurrent decisions on notification permission prompts are permanent. The browser does not do any automatic clean-up of stale notification subscriptions\, even if they are from a site that the user has not interacted with for many years. \n\n Clarifying the purpose of the Web Push and Web Notification APIs on a phil osophical level – amongst browser vendors as well as web developers – would allow user agents to enable helpful notifications while curbing unwa nted notifications. For example\, if we can agree that the purpose of noti fications is to inform users about content being changed on a site\, and i n response\, users are expected to actually visit the sender origin within a reasonable time window (such as within a few months)\, user agents coul d expire permission grants outside that reasonable time window. It is an o pen question if there are legitimate in-the-wild use cases for notificatio ns that users only read\, never interact with\, nor do they ever visit the sending website again.\n\n**Goal(s):**\nShare and discuss solutions to cu rb spammy and abusive notifications on the web\, and to help users exert b etter control over their notifications. Identify points of consensus and p oints of contention. Identify open questions to be answered to sort out po ints of contention. Identify practical next steps to improve Web Notificat ions.\n\n\n**Agenda:**\n1. Intro: Web Push Notifications problem space\n2. Potential solutions + discussion\n i. Make notifications not-promptable\ n ii. Notifications to require open tab\n iii. Expiry for notification g rants\n iv. Any other potential solutions from the group\n3. Identify poi nts of consensus and points of contention\n i. What are the open question s to answer to sort out the points of contention?\n4. Next steps\n\n**Mate rials:**\n- [minutes](https://pad.w3.org/p/Notifications)\n- [Session prop osal on GitHub](https://github.com/w3c/tpac2024-breakouts/issues/81)\n\n** Track(s):**\n- Permissions STATUS:CONFIRMED CREATED:20240916T220103Z LAST-MODIFIED:20241002T120833Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:4 Concourse Level - Oceanside CATEGORIES:TPAC 2024,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:028d0882-5e1e-42f7-90dd-ca524513ec57 DTSTAMP:20241106T182735Z SUMMARY:One Year Update: Partitioning :visited links history DTSTART;TZID=America/Los_Angeles:20240925T144500 DTEND;TZID=America/Los_Angeles:20240925T154500 DESCRIPTION:https://www.w3.org/events/meetings/028d0882-5e1e-42f7-90dd-ca52 4513ec57/\n\nThis breakout session will serve as a 1 year update to the pa rtitioning :visited links project. We will:\n\n\n\n- Briefly recap the [Pa rtitioning :visited links history explainer](https://github.com/kyraseever s/Partitioning-visited-links-history). \n\n- Go over implementation progre ss in Chrome and highlight solutions that may be valuable to other develop ers.\n\n- Discuss public experiment results and key takeaways from our lau nch.\n\n- Discuss how to spec this proposal and how standardization choice s now may affect future privacy improvements to CSS\n\n- Determine what wo rk remains towards removing the [2010 privacy mitigations](https://develop er.mozilla.org/en-US/docs/Web/CSS/Privacy_and_the_:visited_selector).\n\nA genda\n\n**Chairs:**\nKyra Seevers\, Artur Janc\, Mike Taylor\n\n**Descrip tion:**\nThis breakout session will serve as a 1 year update to the partit ioning :visited links project. We will:\n\n\n\n- Briefly recap the [Partit ioning :visited links history explainer](https://github.com/kyraseevers/Pa rtitioning-visited-links-history). \n\n- Go over implementation progress i n Chrome and highlight solutions that may be valuable to other developers. \n\n- Discuss public experiment results and key takeaways from our launch. \n\n- Discuss how to spec this proposal and how standardization choices no w may affect future privacy improvements to CSS\n\n- Determine what work r emains towards removing the [2010 privacy mitigations](https://developer.m ozilla.org/en-US/docs/Web/CSS/Privacy_and_the_:visited_selector).\n\n**Goa l(s):**\nTo present implementation and experimentation updates\, and discu ss concrete steps towards CSS standardization.\n\n\n\n**Materials:**\n- [s lides](https://www.w3.org/2024/Talks/TPAC/breakouts/partitioning-visited-l inks.pdf)\n- [minutes](https://www.w3.org/2024/09/breakouts/minutes-9.html )\n- [minutes (initial google doc)](https://docs.google.com/document/d/1N4 TTMg90RzAWZyjWuy1j-zbYGfiiNNrzPRTDggxMX3s/edit)\n- [Session proposal on Gi tHub](https://github.com/w3c/tpac2024-breakouts/issues/9) STATUS:CONFIRMED CREATED:20240916T214732Z LAST-MODIFIED:20241106T182735Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:4 Concourse Level - Capistrano CATEGORIES:TPAC 2024,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:56c437a0-f44a-4b80-90ec-b954afb909ea DTSTAMP:20241106T183152Z SUMMARY:Real World Identity and the Web... Continued DTSTART;TZID=America/Los_Angeles:20240925T144500 DTEND;TZID=America/Los_Angeles:20240925T154500 DESCRIPTION:https://www.w3.org/events/meetings/56c437a0-f44a-4b80-90ec-b954 afb909ea/\n\nAt TPAC 2023\, we introduced the topic of digital identity wa llets and their use on the web\, and asked the community for use cases\, c oncerns\, and asked browser engine maintainers to express interest in this work.\n\nThis evolved into a work item in the WICG\, [the Digital Credent ials API](https://github.com/WICG/digital-credentials)\, where folks from multiple communities involved in the digitally verifiable credentials spac e (including other W3C CGs and WGs\, the OpenID Foundation\, national stan dards organizations\, privacy experts\, issuers\, verifiers\, wallet maker s\, and more) have been working together to provide a safe\, secure\, priv acy preserving method of sharing digital credentials on the web.\n\nThis s ession will provide an update on the work\, the threat models being evalua ted\, upcoming work items\, and open discussion.\n\nAgenda\n\n**Chairs:**\ nTim Cappalli\, Heather Flanagan\n\n**Description:**\nAt TPAC 2023\, we in troduced the topic of digital identity wallets and their use on the web\, and asked the community for use cases\, concerns\, and asked browser engin e maintainers to express interest in this work.\n\nThis evolved into a wor k item in the WICG\, [the Digital Credentials API](https://github.com/WICG /digital-credentials)\, where folks from multiple communities involved in the digitally verifiable credentials space (including other W3C CGs and WG s\, the OpenID Foundation\, national standards organizations\, privacy exp erts\, issuers\, verifiers\, wallet makers\, and more) have been working t ogether to provide a safe\, secure\, privacy preserving method of sharing digital credentials on the web.\n\nThis session will provide an update on the work\, the threat models being evaluated\, upcoming work items\, and o pen discussion.\n\n**Goal(s):**\nProvide an update on the work stream to t he wider community\, hear new issues or concerns\, receive feedback on cor e work items\n\n\n**Agenda:**\n* [Agenda](https://docs.google.com/document /d/1k2pDac-8E3C2Ne1uJu7Fx4CGE-nn2e7YhVJbkIa106w)\n\n**Materials:**\n- [sli des](https://www.w3.org/2024/Talks/TPAC/breakouts/real-world-identity.pdf) \n- [minutes](https://www.w3.org/2024/09/breakouts/minutes-10.html)\n- [mi nutes (initial google doc)](https://docs.google.com/document/d/1k2pDac-8E3 C2Ne1uJu7Fx4CGE-nn2e7YhVJbkIa106w)\n- [Session proposal on GitHub](https:/ /github.com/w3c/tpac2024-breakouts/issues/10)\n\n**Track(s):**\n- Wallets STATUS:CONFIRMED CREATED:20240916T214743Z LAST-MODIFIED:20241106T183152Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:-1 Lower Level - Catalina 5 CATEGORIES:TPAC 2024,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:bf75e0c9-c534-4ccf-988e-0e720f5280ff DTSTAMP:20241016T221511Z SUMMARY:Registries for W3C Specifications DTSTART;TZID=America/Los_Angeles:20240925T144500 DTEND;TZID=America/Los_Angeles:20240925T154500 DESCRIPTION:https://www.w3.org/events/meetings/bf75e0c9-c534-4ccf-988e-0e72 0f5280ff/\n\nIn [the related session](https://github.com/w3c/breakouts-day -2024/issues/18) of the breakout day of 2024\, it was found out that the w ide W3C community needs a place to discuss registry mechanism related topi cs such as best practices\, experiences\, and tooling. With the Web of Thi ngs WG advancing in defining their registry\, we want to use this session to present the analysis that was done so far\, collect opinions from other s.\n\nAgenda\n\n**Chairs:**\nEge Korkan\n\n**Description:**\nIn [the relat ed session](https://github.com/w3c/breakouts-day-2024/issues/18) of the br eakout day of 2024\, it was found out that the wide W3C community needs a place to discuss registry mechanism related topics such as best practices\ , experiences\, and tooling. With the Web of Things WG advancing in defini ng their registry\, we want to use this session to present the analysis th at was done so far\, collect opinions from others.\n\n**Goal(s):**\nExperi ence Sharing\, Discussion\n\n\n**Agenda:**\n- Wrap up of Breakout Day 2024 \, Registry Session\n- Experience from the development of the WoT Binding Registry\n- Feedback and Discussion\n\n**Materials:**\n- [slides](https:// www.w3.org/2024/Talks/TPAC/breakouts/real-world-identity.pdf)\n- [minutes] (https://www.w3.org/2024/09/25-registries-minutes.html)\n- [Session propos al on GitHub](https://github.com/w3c/tpac2024-breakouts/issues/24) STATUS:CONFIRMED CREATED:20240916T215018Z LAST-MODIFIED:20241016T221511Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:2 Ballroom Level - California A CATEGORIES:TPAC 2024,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:854574de-23d7-4565-b708-a399f3f7dee8 DTSTAMP:20241002T122438Z SUMMARY:Threat Modeling @ W3C DTSTART;TZID=America/Los_Angeles:20240925T144500 DTEND;TZID=America/Los_Angeles:20240925T154500 DESCRIPTION:https://www.w3.org/events/meetings/854574de-23d7-4565-b708-a399 f3f7dee8/\n\nWhen a standard is written\, it's required to write Security and Privacy Considerations and\, if the technology is particularly disrupt ive\, to sample the human rights impact.\nOne of the processes that can be used to get these considerations in a practical and structured way is to use Threat Modeling\, a repeatable process with several techniques to unde rstand best what we're doing\, what can't go wrong\, and what we can do ab out it.\nIn this session\, we will explore how to initiate Threat Modeling from the early stages of a specification\, using practical examples. This approach ensures that everything is secure\, respects privacy\, and is pr operly documented.\n\nAgenda: https://docs.google.com/presentation/d/1zauM qnZ_e0U3JlNe3bCJacNh9h1VOkBX4_UynjqvQeg/edit#slide=id.g303b479e16d_0_15\n\ nAgenda\n\n**Chairs:**\nSimone Onofri\n\n**Description:**\nWhen a standard is written\, it's required to write Security and Privacy Considerations a nd\, if the technology is particularly disruptive\, to sample the human ri ghts impact.\nOne of the processes that can be used to get these considera tions in a practical and structured way is to use Threat Modeling\, a repe atable process with several techniques to understand best what we're doing \, what can't go wrong\, and what we can do about it.\nIn this session\, w e will explore how to initiate Threat Modeling from the early stages of a specification\, using practical examples. This approach ensures that every thing is secure\, respects privacy\, and is properly documented.\n\n**Goal (s):**\nSecure the standards\n\n\n\n**Materials:**\n- [minutes](https://ww w.w3.org/2024/09/25-threat-modeling-minutes.html)\n- [Session proposal on GitHub](https://github.com/w3c/tpac2024-breakouts/issues/12) STATUS:CONFIRMED CREATED:20240916T214810Z LAST-MODIFIED:20241002T122438Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:4 Concourse Level - Manhattan CATEGORIES:TPAC 2024,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:601b0f92-e5ea-4e16-b767-2fceeb7094f9 DTSTAMP:20241002T122517Z SUMMARY:W3C Vision — Getting To Statement DTSTART;TZID=America/Los_Angeles:20240925T144500 DTEND;TZID=America/Los_Angeles:20240925T154500 DESCRIPTION:https://www.w3.org/events/meetings/601b0f92-e5ea-4e16-b767-2fce eb7094f9/\n\nThe Advisory Board (AB) published the [W3C Vision as a Note]( https://www.w3.org/TR/2024/NOTE-w3c-vision-20240403/) earlier this year. T he Vision Task Force ([VisionTF](https://www.w3.org/wiki/AB/VisionTF)) has processed most issues and a small number of Statement Blockers remain. Th is breakout session is an open session for working through the remaining [ Statement Blocker issues](https://github.com/w3c/AB-public/issues?q=is%3Ai ssue+is%3Aopen+label%3A%22needed+for+Statement%22).\n\nAgenda\n\n**Chairs: **\nTantek Çelik\, Chris Wilson\n\n**Description:**\nThe Advisory Board ( AB) published the [W3C Vision as a Note](https://www.w3.org/TR/2024/NOTE-w 3c-vision-20240403/) earlier this year. The Vision Task Force ([VisionTF]( https://www.w3.org/wiki/AB/VisionTF)) has processed most issues and a smal l number of Statement Blockers remain. This breakout session is an open se ssion for working through the remaining [Statement Blocker issues](https:/ /github.com/w3c/AB-public/issues?q=is%3Aissue+is%3Aopen+label%3A%22needed+ for+Statement%22).\n\n**Goal(s):**\nThe goal of this session is reach cons ensus resolutions on the remaining Statement Blocker issues for the W3C Vi sion\, so the Vision Task Force can prepare an updated W3C Vision Note for publication as a proposed Statement for an Advisory Committee vote.\n\n** Attendance:**\nThis session is restricted to TPAC registrants.\n\n**Agenda :**\n[w3.org/wiki/AB/VisionTF/2024-09-25](https://www.w3.org/wiki/AB/Visio nTF/2024-09-25)\n\n(Originally published at: https://tantek.com/2024/257/b 1/w3c-vision-getting-to-statement)\n\n**Materials:**\n- [minutes](https:// www.w3.org/2024/09/25-vision-minutes.html)\n- [Session proposal on GitHub] (https://github.com/w3c/tpac2024-breakouts/issues/84) STATUS:CONFIRMED CREATED:20240916T220126Z LAST-MODIFIED:20241002T122517Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:4 Concourse Level - Huntington CATEGORIES:TPAC 2024,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:cd255a8c-a18d-4e35-bb8b-2ade88af2786 DTSTAMP:20241106T183335Z SUMMARY:Web Install API DTSTART;TZID=America/Los_Angeles:20240925T144500 DTEND;TZID=America/Los_Angeles:20240925T154500 DESCRIPTION:https://www.w3.org/events/meetings/cd255a8c-a18d-4e35-bb8b-2ade 88af2786/\n\nThis breakout will serve as an update to the broader communit y about the Web Install API. We will be discussing the shape of the API\, decisions behind it\, and show the progress around the API.\n\nAs the plat form continues to evolve with richer and more powerful capabilities\, more developers lean on PWAs to reach their customers. Distribution is still t ied to native app stores or proprietary protocol workarounds\, with one bi g gap related toa application distribution.\n\nAgenda\n\n**Chairs:**\nDieg o Gonzalez-Zuniga\, Amanda Baker\n\n**Description:**\nThis breakout will s erve as an update to the broader community about the Web Install API. We w ill be discussing the shape of the API\, decisions behind it\, and show th e progress around the API.\n\nAs the platform continues to evolve with ric her and more powerful capabilities\, more developers lean on PWAs to reach their customers. Distribution is still tied to native app stores or propr ietary protocol workarounds\, with one big gap related toa application dis tribution.\n\n**Goal(s):**\nShowcase the Web Install API and give an updat e on development. We want to gather community feedback on the API.\n\n\n** Agenda:**\nMeeting minutes: https://docs.google.com/document/d/1ItMpSpuV1C szg_64o4D2MJMT7KlWKBTz8jhWg3y3A5E/edit?usp=sharing\n \nand presentation as a pdf: https://drive.google.com/file/d/1-pO4Ar5EpznGuNX-0AWp25ctIlsOCMcH/ view?usp=sharing\n\n**Materials:**\n- [slides](https://www.w3.org/2024/Tal ks/TPAC/breakouts/web-install-api.pdf)\n- [minutes](https://www.w3.org/202 4/09/breakouts/minutes-25.html)\n- [minutes (initial google doc)](https:// docs.google.com/document/d/1ItMpSpuV1Cszg_64o4D2MJMT7KlWKBTz8jhWg3y3A5E/ed it?usp=sharing)\n- [Session proposal on GitHub](https://github.com/w3c/tpa c2024-breakouts/issues/25)\n\n**Track(s):**\n- Web Apps STATUS:CONFIRMED CREATED:20240916T215026Z LAST-MODIFIED:20241106T183335Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:2 Ballroom Level - California B CATEGORIES:TPAC 2024,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:80f4dd75-7ade-4761-92ee-a59abb62006d DTSTAMP:20241002T122501Z SUMMARY:Web on the Moon DTSTART;TZID=America/Los_Angeles:20240925T144500 DTEND;TZID=America/Los_Angeles:20240925T154500 DESCRIPTION:https://www.w3.org/events/meetings/80f4dd75-7ade-4761-92ee-a59a bb62006d/\n\nThe _Artemis_ plan calls for human habitation of the Moon fro m 2028\, currently under international consideration from the perspectives of habitation\, mineral resource collection\, food and medicine\, and is considered the first step towards sending humans to Mars in the future. Co mmunication with family and others is essential when people are away from Earth for long periods. Astronauts on the ISS are already guaranteed a pri vate conversation with their families on the ground at least once a day\, and can even watch football games using web and remote conferencing techno logy\, but the ISS is 400 km from the ground\, and its latency is less tha n that of a geostationary orbit satellite (located 35\,786 km above the gr ound) is said to be 500 ms.\n \nThe distance to the Moon is 380\,000 km\ , which theoretically translates into a latency of _2\,600 ms_.\n\nUnder t hese conditions\, it is expected to be difficult for people living on the Moon to explore the Web\, hold remote meetings with their families or watc h football games\, as they do on Earth\, due to time-outs and other proble ms with current technology.\n\nIn this breakout session\, we would like to discuss the possibility of using web technology on the Moon in the same w ay as on Earth\, although the speed of light cannot be exceeded.\n\nAgenda \n\n**Chairs:**\nJay Kishigami\n\n**Description:**\nThe _Artemis_ plan cal ls for human habitation of the Moon from 2028\, currently under internatio nal consideration from the perspectives of habitation\, mineral resource c ollection\, food and medicine\, and is considered the first step towards s ending humans to Mars in the future. Communication with family and others is essential when people are away from Earth for long periods. Astronauts on the ISS are already guaranteed a private conversation with their famili es on the ground at least once a day\, and can even watch football games u sing web and remote conferencing technology\, but the ISS is 400 km from t he ground\, and its latency is less than that of a geostationary orbit sat ellite (located 35\,786 km above the ground) is said to be 500 ms.\n \nT he distance to the Moon is 380\,000 km\, which theoretically translates in to a latency of _2\,600 ms_.\n\nUnder these conditions\, it is expected to be difficult for people living on the Moon to explore the Web\, hold remo te meetings with their families or watch football games\, as they do on Ea rth\, due to time-outs and other problems with current technology.\n\nIn t his breakout session\, we would like to discuss the possibility of using w eb technology on the Moon in the same way as on Earth\, although the speed of light cannot be exceeded.\n\n**Goal(s):**\nParticipants will decide on the direction of future discussions.\n\n\n**Agenda:**\n1. overview of ISS \, Artemis\, DTN (RFC4838)\, etc.\n2. open discussion\n\n**Materials:**\n- [minutes](https://www.w3.org/2024/09/25-web-on-the-moon-minutes.html)\n- [Session proposal on GitHub](https://github.com/w3c/tpac2024-breakouts/iss ues/52) STATUS:CONFIRMED CREATED:20240916T215431Z LAST-MODIFIED:20241002T122501Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:4 Concourse Level - Palos Verdes CATEGORIES:TPAC 2024,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:bdefcc3d-bb14-4879-ab9d-586b863af8a5 DTSTAMP:20241002T122449Z SUMMARY:Web Speech API Improvements DTSTART;TZID=America/Los_Angeles:20240925T144500 DTEND;TZID=America/Los_Angeles:20240925T154500 DESCRIPTION:https://www.w3.org/events/meetings/bdefcc3d-bb14-4879-ab9d-586b 863af8a5/\n\nChrome is proposing new improvements to the Web Speech API\, including:\n\nOffline speech recognition: Allow speech recognition without an internet connection. [1]\nMediaStreamTrack support: Enable seamless in tegration of speech recognition with audio and video streams. [2]\nSpoken punctuation parameter: Add a new parameter to the speech recognition API t hat allows developers to control how spoken punctuation marks are handled in the transcription. [3]\n\nRelated Github issues:\n[1] [Offline/on-devic e speech recognition #108](https://github.com/WICG/speech-api/issues/108)\ n[2] [Support SpeechRecognition on an audio MediaStreamTrack #66](https:// github.com/WICG/speech-api/issues/66)\n[3] [Speech recognition parameter f or spoken punctuation #114](https://github.com/WICG/speech-api/issues/114) \n\nAgenda\n\n**Chairs:**\nEvan Liu\n\n**Description:**\nChrome is proposi ng new improvements to the Web Speech API\, including:\n\nOffline speech r ecognition: Allow speech recognition without an internet connection. [1]\n MediaStreamTrack support: Enable seamless integration of speech recognitio n with audio and video streams. [2]\nSpoken punctuation parameter: Add a n ew parameter to the speech recognition API that allows developers to contr ol how spoken punctuation marks are handled in the transcription. [3]\n\nR elated Github issues:\n[1] [Offline/on-device speech recognition #108](htt ps://github.com/WICG/speech-api/issues/108)\n[2] [Support SpeechRecognitio n on an audio MediaStreamTrack #66](https://github.com/WICG/speech-api/iss ues/66)\n[3] [Speech recognition parameter for spoken punctuation #114](ht tps://github.com/WICG/speech-api/issues/114)\n\n**Goal(s):**\nDiscuss and reach a consensus on the proposed changes to the Web Speech API\n\n\n\n**M aterials:**\n- [minutes](https://www.w3.org/2024/09/25-web-speech-minutes. html)\n- [Session proposal on GitHub](https://github.com/w3c/tpac2024-brea kouts/issues/21) STATUS:CONFIRMED CREATED:20240916T215001Z LAST-MODIFIED:20241002T122449Z SEQUENCE:2 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:4 Concourse Level - San Clemente CATEGORIES:TPAC 2024,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:0c09dd52-f75e-4676-bb57-43bb33f6a4eb DTSTAMP:20241030T131535Z SUMMARY:Blending Realities: Building An Open Web Wide World DTSTART;TZID=America/Los_Angeles:20240925T160000 DTEND;TZID=America/Los_Angeles:20240925T164500 DESCRIPTION:https://www.w3.org/events/meetings/0c09dd52-f75e-4676-bb57-43bb 33f6a4eb/\n\nBuilding blocks for constructing a tangible virtual world has begun to take shape. Technologies from various fields are becoming increa singly mature\, such as gaming\, social platforms\, digital twins\, and vi rtual reality.\nThis session aims to trigger the discussion on how each st akeholder may collaborate to co-create a tangible virtual world that is in terconnected\, mutually beneficial\, supportive and belongs to all. We nee d a set of standards that enable the integration of individual efforts to build an open platform on web\, fostering prosperity through cooperation r ather than competition.\nThis session will delve into our recent endeavors in crafting virtual world experiences on Tencent products. We will share insights from our development process\, highlight the innovative solutions we implemented\, and discuss the hurdles we encountered along the way. \n \nThe following aspects will be addressed:\n1. Types and Corresponding Rol es: Sites as Service Integrators and Programs as Service Providers\n2. Sco ping: Defining the Origins of Assets and Elements\n3. Asset Deployments: P lanning Asset URIs and Deploying according to Scoping\n4. Site Hierarchy: Inter-Site Integration through Contracts and Administration according to S coping\n5. Site-Program Integration: Cooperating between Programs and Site s through Contracts\n6. Permission Controls: Managing Authorization for As sets and Elements across Sites/Programs\n7. Version Management: Independen t Releases by Sites/Programs with Unified Synchronization across the Virtu al World\n8. Multi-user Interaction: Distributed across Sites and Seamless ly Integrated through On-Demand Pub/Sub for Users\n
\n\nAgenda\n\n**Chairs:**\nHarry Wang\, Rocman Zhao\n\n**Description:**\nBuilding blocks for constructing a tangib le virtual world has begun to take shape. Technologies from various fields are becoming increasingly mature\, such as gaming\, social platforms\, di gital twins\, and virtual reality.\nThis session aims to trigger the discu ssion on how each stakeholder may collaborate to co-create a tangible virt ual world that is interconnected\, mutually beneficial\, supportive and be longs to all. We need a set of standards that enable the integration of in dividual efforts to build an open platform on web\, fostering prosperity t hrough cooperation rather than competition.\nThis session will delve into our recent endeavors in crafting virtual world experiences on Tencent prod ucts. We will share insights from our development process\, highlight the innovative solutions we implemented\, and discuss the hurdles we encounter ed along the way. \n\nThe following aspects will be addressed:\n1. Types a nd Corresponding Roles: Sites as Service Integrators and Programs as Servi ce Providers\n2. Scoping: Defining the Origins of Assets and Elements\n3. Asset Deployments: Planning Asset URIs and Deploying according to Scoping\ n4. Site Hierarchy: Inter-Site Integration through Contracts and Administr ation according to Scoping\n5. Site-Program Integration: Cooperating betwe en Programs and Sites through Contracts\n6. Permission Controls: Managing Authorization for Assets and Elements across Sites/Programs\n7. Version Ma nagement: Independent Releases by Sites/Programs with Unified Synchronizat ion across the Virtual World\n8. Multi-user Interaction: Distributed acros s Sites and Seamlessly Integrated through On-Demand Pub/Sub for Users\n