BEGIN:VCALENDAR VERSION:2.0 PRODID:-//Sabre//Sabre VObject 4.5.8//EN CALSCALE:GREGORIAN NAME:TPAC 2025 Calendar X-WR-CALNAME:TPAC 2025 Calendar LAST-MODIFIED:20260227T232844Z BEGIN:VTIMEZONE TZID:Etc/UTC BEGIN:STANDARD DTSTART:20241103T140000 TZOFFSETFROM:+0000 TZOFFSETTO:+0000 TZNAME:UTC END:STANDARD END:VTIMEZONE BEGIN:VTIMEZONE TZID:Asia/Tokyo X-MICROSOFT-CDO-TZID:20 BEGIN:STANDARD DTSTART:20241115T000000 TZOFFSETFROM:+0900 TZOFFSETTO:+0900 TZNAME:JST END:STANDARD END:VTIMEZONE BEGIN:VEVENT UID:0c23056d-c03e-432c-9691-b8c65ca9c2e1 DTSTAMP:20251027T112604Z SUMMARY:Get ready for TPAC: A guide for TPAC newbies DTSTART;TZID=Etc/UTC:20251029T140000 DTEND;TZID=Etc/UTC:20251029T150000 DESCRIPTION:https://www.w3.org/events/meetings/0c23056d-c03e-432c-9691-b8c6 5ca9c2e1/\n\nIf you are attending TPAC for the first time\, join us for a warm welcome and general introduction to W3C.\n\nAgenda\n\n- Welcome from Seth Dobbs\, CEO of W3C\n- Introduction to W3C\n- TPAC Agenda walk through \n- Get to know TPAC breakouts\n- Mentor system\n- How to ask for help\n- Q&A\n\nSee the [slides](https://www.w3.org/2025/Talks/TPAC/get-ready/). STATUS:CONFIRMED CREATED:20250820T031447Z LAST-MODIFIED:20251027T112604Z 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=Advisory Committee :mailto:w3c-ac-members@w3.org LOCATION:Virtual CATEGORIES:TPAC 2025 END:VEVENT BEGIN:VEVENT UID:5ba02c76-d748-4db0-9e2a-c73e4238ec48 DTSTAMP:20251107T151715Z SUMMARY:Accessibility Guidelines Working Group DTSTART;TZID=Asia/Tokyo:20251110T090000 DTEND;TZID=Asia/Tokyo:20251110T164500 DESCRIPTION:https://www.w3.org/events/meetings/5ba02c76-d748-4db0-9e2a-c73e 4238ec48/\n\n\n\nAgenda\n\n* Retrospective (2 hours\, Chuck)\n* Forward wo rk (scoping / project plan\, Rachael)\n * Do we want to suggest an access ibility testing working group? (ARIA\, ACT\, WCAG-EM\, etc.)\n * What key areas do we want to cover in addition to WCAG 3? (aka\, what task forces do we want to stand up for the next charter period?)\n * Usability Test ing and Assertions (WCAG3)\n * COGA\n * WCAG 2\n * WCAG2ICT\n * Policy (WCAG3)\n * Low Vision (Color Contrast Algorithm)\n * ACT \n * Mobile (WCAG3/WCAG2) STATUS:CONFIRMED CREATED:20250725T162702Z LAST-MODIFIED:20251107T151715Z 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=Accessibility Guid elines Working Group:mailto:public-ag-admin@w3.org LOCATION:Floor 4 - 402 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:827ca43f-43bf-438c-9e89-4045e301eae3 DTSTAMP:20251107T181330Z SUMMARY:Accessible Rich Internet Applications Working Group DTSTART;TZID=Asia/Tokyo:20251110T090000 DTEND;TZID=Asia/Tokyo:20251110T164500 DESCRIPTION:https://www.w3.org/events/meetings/827ca43f-43bf-438c-9e89-4045 e301eae3/\n\n\n\nAgenda: https://github.com/w3c/aria/wiki/TPAC-2025-Kobe\, -Japan-Agenda#monday-nov-10-2025 STATUS:CONFIRMED CREATED:20251106T161014Z LAST-MODIFIED:20251107T181330Z 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=Accessible Rich In ternet Applications Working Group:mailto:public-aria@w3.org LOCATION:Floor 5 - 504 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:f59d41da-06cf-44d9-9723-2a8abf2db6a9 DTSTAMP:20251106T155446Z SUMMARY:Accessible Rich Internet Applications Working Group DTSTART;TZID=Asia/Tokyo:20251110T090000 DTEND;TZID=Asia/Tokyo:20251110T164500 DESCRIPTION:https://www.w3.org/events/meetings/f59d41da-06cf-44d9-9723-2a8a bf2db6a9/\n\n STATUS:CANCELLED CREATED:20250716T142351Z LAST-MODIFIED:20251106T155446Z SEQUENCE:10 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:Floor 5 - 504 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:e75c7109-c997-467b-911a-b1b5b388da3a DTSTAMP:20260227T232826Z SUMMARY:Advisory Board DTSTART;TZID=Asia/Tokyo:20251110T090000 DTEND;TZID=Asia/Tokyo:20251110T123000 DESCRIPTION:https://www.w3.org/events/meetings/e75c7109-c997-467b-911a-b1b5 b388da3a/\n\nAB meeting 9am-12:30pm Monday 10 November at TPAC 2025 STATUS:CONFIRMED CREATED:20250818T145638Z LAST-MODIFIED:20260227T232826Z 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 Board:mai lto:w3c-ac-members@w3.org LOCATION:Floor 5 - 503 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:b57b269a-291a-41dd-878d-c546374246f6 DTSTAMP:20251109T082727Z SUMMARY:Anti-Fraud CG DTSTART;TZID=Asia/Tokyo:20251110T090000 DTEND;TZID=Asia/Tokyo:20251110T103000 DESCRIPTION:https://www.w3.org/events/meetings/b57b269a-291a-41dd-878d-c546 374246f6/\n\n\n\nAgenda: https://github.com/antifraudcg/meetings/blob/main /tpac/tpac-2025.md\n\nAgenda\n\n# TPAC Anti-Fraud Agenda\n\n## Anti Fraud CG Meeting\n\n### Logistics\n\n10 November 2025\, 9:00-10:30AM JST\n\n### Resources\n\n* [Minutes](https://tinyurl.com/tpac-2025-afcg)\n* [Chair Sli des](https://docs.google.com/presentation/d/1Kanv7M_2pqfF0lHPXEbOzuJsi4SQX 8J5AmCcdS3N54Q/edit?slide=id.p#slide=id.p)\n\n### Agenda\n\n* AFCG Focus A reas into 2026\n* Unconference\n* Next Steps STATUS:CONFIRMED CREATED:20250716T142332Z LAST-MODIFIED:20251109T082727Z 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=Anti-Fraud Communi ty Group:mailto:public-antifraud@w3.org LOCATION:Floor 4 - 405 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:86ea031d-776b-426e-aa2a-bdf6ba6d50af DTSTAMP:20251110T012237Z SUMMARY:Internationalization Working Group DTSTART;TZID=Asia/Tokyo:20251110T090000 DTEND;TZID=Asia/Tokyo:20251110T164500 DESCRIPTION:https://www.w3.org/events/meetings/86ea031d-776b-426e-aa2a-bdf6 ba6d50af/\n\n\n\nAgenda\n\nThis is the I18N WG meeting at TPAC\n\n\n\n\n\n ---\n\n### Agenda Parking Lot\n\n_Items that might become part of the agen da._\n\n- DOM Localization\n- IRI vulnerability\, IRI status in general (c f. RFC3987\, WHATWG URL)\n- Ruby status\n\n- APA. Chris Wilson contact. Ma tthew Atkinson contact. August 12.\n- I18N+CSS. Our shared calls have fall en away and there's been little progress recently.\n- CSS topics: https:// github.com/w3c/i18n-activity/issues?q=is%3Aissue%20state%3Aopen%20label%3A wg%3Acss\n- PEWG/I18N/CSS. Patrick H. Lauke contact. Level 4 concerns? Jun e 4.\n- XML Errata. PLH contact.\n- Plan for the 2025-11-14 meeting with W HATWG (review open issues\, discussion topics)\n\n- Glossary and the norma tive approach\n- Pending issues: https://github.com/w3c/i18n-activity/labe ls/pending STATUS:CONFIRMED CREATED:20250716T142309Z LAST-MODIFIED:20251110T012237Z 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=Internationalizati on Working Group:mailto:public-i18n-core@w3.org LOCATION:Floor 3 - 305 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:373019a8-a511-4cca-8ba9-7618447f1152 DTSTAMP:20251103T174617Z SUMMARY:Media and Entertainment Interest Group DTSTART;TZID=Asia/Tokyo:20251110T090000 DTEND;TZID=Asia/Tokyo:20251110T123000 DESCRIPTION:https://www.w3.org/events/meetings/373019a8-a511-4cca-8ba9-7618 447f1152/\n\n\n\nAgenda: https://github.com/w3c/media-and-entertainment/is sues/110 STATUS:CONFIRMED CREATED:20250716T142456Z LAST-MODIFIED:20251103T174617Z 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=Media and Entertai nment Interest Group:mailto:public-web-and-tv@w3.org LOCATION:Floor 4 - 404 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:fcbb3292-4982-4a65-89e0-6eda0c6b217a DTSTAMP:20251104T161327Z SUMMARY:Publishing Maintenance WG DTSTART;TZID=Asia/Tokyo:20251110T090000 DTEND;TZID=Asia/Tokyo:20251110T164500 DESCRIPTION:https://www.w3.org/events/meetings/fcbb3292-4982-4a65-89e0-6eda 0c6b217a/\n\n\n\nAgenda: https://github.com/w3c/epub-specs/discussions/281 5#discussioncomment-14751130\n\nAgenda\n\n| Time (JST) | Topic | CET | ET |\n| -------- ------- | -------------------------------------------- | ----------- | --- -------- |\n| 9:00-9:45 | Update on Annotations | 01:00-01:45 | 19:00-19:45 |\n| 9:45-10:30 | Technical Direction for Annotations | 01:45-02:30 | 19:45-20:30 |\n| 10:30- 11:00 | Break | 02:30-03:00 | 2 0:30-21:00 |\n| 11:00-12:30 | ISO Update + Liaising with ISO/IEC JTC1/ SC34 | 03:00-04:30 | 21:00-22:30 |\n| 12:30-13:30 | Lunch | 04:30-05:30 | 22:30-23:30 |\n| 13:30-14:15 | Update on Digital Comics | 05:30-06:15 | 23:30-00:15 |\n| 14: 15-15:00 | Images in Spine/FXL Changes | 06:15-07:00 | 00:15-01:00 |\n| 15:00-15:30 | Break | 07:00-07:30 | 01:00-01:30 |\n| 15:30-16:30 | FXL Changes (co ntinued) | 07:30-08:30 | 01:30-02:30 |\n| 16:30-16:45 | Buffer/Wrap up | 08:30-08:45 | 02:30- 02:45 | STATUS:CONFIRMED CREATED:20250716T142256Z LAST-MODIFIED:20251104T161327Z 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=Publishing Mainten ance Working Group:mailto:public-pm-wg@w3.org LOCATION:Floor 3 - 302 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:6449c85b-7e05-4ecf-a6cb-438e3bbfda47 DTSTAMP:20251109T191529Z SUMMARY:Technical Architecture Group DTSTART;TZID=Asia/Tokyo:20251110T090000 DTEND;TZID=Asia/Tokyo:20251110T103000 DESCRIPTION:https://www.w3.org/events/meetings/6449c85b-7e05-4ecf-a6cb-438e 3bbfda47/\n\n**This is a _closed_ session. Only TAG members and TAG Associ ates may attend.** It's unlikely to be very interesting for others anyway: we're just assigning people to attend various meetings. If you want us to send someone to your meeting\, file an issue in https://w3ctag.github.io/ tpac-meetings/.\n\nAgenda\n\n1. Go through the week's sessions\, in https: //github.com/w3ctag/tpac-meetings/issues and https://w3ctag.github.io/tpac -meetings/.\n2. Figure out which ones actually need a TAG attendee.\n3. Vo lunteer at least 1 TAG member to go to each of those. STATUS:CONFIRMED CREATED:20250716T142344Z LAST-MODIFIED:20251109T191529Z 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=Technical Architec ture Group:mailto:tag@w3.org LOCATION:Floor 3 - 304 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:ab234e0d-6bf5-4f76-9c76-f557b5b385cb DTSTAMP:20251103T174831Z SUMMARY:Web Application Security Working Group DTSTART;TZID=Asia/Tokyo:20251110T090000 DTEND;TZID=Asia/Tokyo:20251110T164500 DESCRIPTION:https://www.w3.org/events/meetings/ab234e0d-6bf5-4f76-9c76-f557 b5b385cb/\n\n STATUS:CONFIRMED CREATED:20250716T142717Z LAST-MODIFIED:20251103T174831Z 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 Application Se curity Working Group:mailto:public-webappsec@w3.org LOCATION:Floor 5 - 501 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:d079bef8-3db1-47a4-a876-2bad6b9c683f DTSTAMP:20251109T141009Z SUMMARY:Web Applications Working Group DTSTART;TZID=Asia/Tokyo:20251110T090000 DTEND;TZID=Asia/Tokyo:20251110T164500 DESCRIPTION:https://www.w3.org/events/meetings/d079bef8-3db1-47a4-a876-2bad 6b9c683f/\n\n\n\nAgenda: https://github.com/w3c/webappswg/wiki/TPAC-2025 STATUS:CONFIRMED CREATED:20250716T142601Z LAST-MODIFIED:20251109T141009Z 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 Applications W orking Group:mailto:public-webapps@w3.org LOCATION:Floor 4 - 401 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:3d545adf-8de1-4f6d-abb5-be2030e66cf6 DTSTAMP:20251110T000126Z SUMMARY:Web Components CG DTSTART;TZID=Asia/Tokyo:20251110T090000 DTEND;TZID=Asia/Tokyo:20251110T123000 DESCRIPTION:https://www.w3.org/events/meetings/3d545adf-8de1-4f6d-abb5-be20 30e66cf6/\n\n\n\nAgenda: https://docs.google.com/document/d/1KeqMzuPHzHXTG R2zXmOHQydMUgVm2Y8onZHVmygAQFc/edit?tab=t.0#heading=h.gaqncq7xkj STATUS:CONFIRMED CREATED:20250716T142607Z LAST-MODIFIED:20251110T000126Z 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 Components Com munity Group:mailto:public-webcomponents@w3.org LOCATION:Floor 3 - 306 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:be187f25-8a30-4093-a0cb-e0489c1e59ad DTSTAMP:20251107T041303Z SUMMARY:Web Fonts WG DTSTART;TZID=Asia/Tokyo:20251110T090000 DTEND;TZID=Asia/Tokyo:20251110T164500 DESCRIPTION:https://www.w3.org/events/meetings/be187f25-8a30-4093-a0cb-e048 9c1e59ad/\n\n\n\nAgenda\n\n0. Extras (agenda\, topics+\, etc.)\n1. Review [recent IFT spec updates](https://pr-preview.s3.amazonaws.com/w3c/IFT/302/ b871826...3acd670.html)\n2. Discuss existing [normative requirements and c onformance classes](https://pr-preview.s3.amazonaws.com/w3c/IFT/pull/302.h tml)\n3. Review [CTS plan](https://github.com/w3c/ift-client-tests/pull/2) and discuss approaches for each conformance test.\n4. Review recent [test generation updates](https://github.com/w3c/ift-client-tests/pull/3/files) \n5. Discussion: encoder updates - current approaches to [glyph segmentati on](https://github.com/w3c/ift-encoder/blob/main/docs/experimental/closure _glyph_segmentation.md) & [merging process](https://github.com/w3c/ift-enc oder/blob/main/docs/experimental/closure_glyph_segmentation_merging.md)\n6 . AOB STATUS:CONFIRMED CREATED:20250716T142522Z LAST-MODIFIED:20251107T041303Z 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 Fonts Working Group:mailto:public-webfonts-wg@w3.org LOCATION:Floor 3 - 303 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:f63193ec-259b-4ab8-ad65-a5a6e0adf556 DTSTAMP:20251113T235012Z SUMMARY:Web Machine Learning Working Group DTSTART;TZID=Asia/Tokyo:20251110T090000 DTEND;TZID=Asia/Tokyo:20251110T164500 DESCRIPTION:https://www.w3.org/events/meetings/f63193ec-259b-4ab8-ad65-a5a6 e0adf556/\n\n\n\nAgenda: https://github.com/webmachinelearning/meetings/is sues/35 STATUS:CONFIRMED CREATED:20250716T142406Z LAST-MODIFIED:20251113T235012Z 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:Floor 4 - 403 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:43b38ab3-f525-40d8-b1b4-ea8675a74d91 DTSTAMP:20251103T162449Z SUMMARY:Web of Things Plugfest DTSTART;TZID=Asia/Tokyo:20251110T090000 DTEND;TZID=Asia/Tokyo:20251110T164500 DESCRIPTION:https://www.w3.org/events/meetings/43b38ab3-f525-40d8-b1b4-ea86 75a74d91/\n\n STATUS:CONFIRMED CREATED:20250812T142134Z LAST-MODIFIED:20251103T162449Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 3 - 307 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:145277e4-38e8-4454-b065-836171473b42 DTSTAMP:20251103T174224Z SUMMARY:Web Payments Working Group DTSTART;TZID=Asia/Tokyo:20251110T090000 DTEND;TZID=Asia/Tokyo:20251110T164500 DESCRIPTION:https://www.w3.org/events/meetings/145277e4-38e8-4454-b065-8361 71473b42/\n\n\n\nAgenda: https://github.com/w3c/webpayments/wiki/Agenda%E2 %80%90TPAC2025 STATUS:CONFIRMED CREATED:20250716T141907Z LAST-MODIFIED:20251103T174224Z 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 Payments Worki ng Group:mailto:public-payments-wg@w3.org LOCATION:Floor 5 - 502 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:cd42cdf2-39f0-4d02-a95c-fec219889098 DTSTAMP:20251108T191137Z SUMMARY:Web Performance Working Group DTSTART;TZID=Asia/Tokyo:20251110T090000 DTEND;TZID=Asia/Tokyo:20251110T164500 DESCRIPTION:https://www.w3.org/events/meetings/cd42cdf2-39f0-4d02-a95c-fec2 19889098/\n\nAgenda: https://docs.google.com/document/d/1EbG3VL27YlzQj8bnW VRI-OUHm6WcUowYoxjYOu4RlXM/edit?tab=t.0\n\nAgenda: https://docs.google.com /document/d/1EbG3VL27YlzQj8bnWVRI-OUHm6WcUowYoxjYOu4RlXM/edit?tab=t.0 STATUS:CONFIRMED CREATED:20250716T142649Z LAST-MODIFIED:20251108T191137Z 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 Performance Wo rking Group:mailto:public-web-perf@w3.org LOCATION:Floor 5 - 505 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:99da5248-3b8c-4e5e-a06e-ff1430c7ac84 DTSTAMP:20251103T174746Z SUMMARY:Audio Working Group DTSTART;TZID=Asia/Tokyo:20251110T110000 DTEND;TZID=Asia/Tokyo:20251110T164500 DESCRIPTION:https://www.w3.org/events/meetings/99da5248-3b8c-4e5e-a06e-ff14 30c7ac84/\n\n STATUS:CONFIRMED CREATED:20250716T142631Z LAST-MODIFIED:20251103T174746Z 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 Working Grou p:mailto:public-audio@w3.org LOCATION:Floor 3 - 304 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:46fa22d3-d716-4e61-b1bd-53b4212f2f06 DTSTAMP:20251103T174445Z SUMMARY:DID Methods WG Charter Discussion DTSTART;TZID=Asia/Tokyo:20251110T110000 DTEND;TZID=Asia/Tokyo:20251110T123000 DESCRIPTION:https://www.w3.org/events/meetings/46fa22d3-d716-4e61-b1bd-53b4 212f2f06/\n\nDiscuss DID Methods WG Charter scope and concerns. STATUS:CONFIRMED CREATED:20250716T142319Z LAST-MODIFIED:20251103T174445Z SEQUENCE:9 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 4 - 406 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:bdd0ac94-40e3-4a3f-9f0f-a7b595590657 DTSTAMP:20251103T174517Z SUMMARY:WebExtensions Community Group DTSTART;TZID=Asia/Tokyo:20251110T110000 DTEND;TZID=Asia/Tokyo:20251110T164500 DESCRIPTION:https://www.w3.org/events/meetings/bdd0ac94-40e3-4a3f-9f0f-a7b5 95590657/\n\n\n\nAgenda: https://github.com/w3c/webextensions/issues/843 STATUS:CONFIRMED CREATED:20250716T142357Z LAST-MODIFIED:20251103T174517Z 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=WebExtensions Comm unity Group:mailto:public-webextensions@w3.org LOCATION:Floor 4 - 405 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:31046de8-90b7-40f2-9b52-93d2fe0450b5 DTSTAMP:20251107T170934Z SUMMARY:Accessible Platform Architectures Working Group DTSTART;TZID=Asia/Tokyo:20251110T134500 DTEND;TZID=Asia/Tokyo:20251110T150000 DESCRIPTION:https://www.w3.org/events/meetings/31046de8-90b7-40f2-9b52-93d2 fe0450b5/\n\n\n\nAgenda: https://github.com/w3c/apa/issues/356 STATUS:CONFIRMED CREATED:20250716T142436Z LAST-MODIFIED:20251107T170934Z SEQUENCE:10 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:Floor 5 - 503 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:d45c8d74-9273-40eb-949e-a070a4c2be79 DTSTAMP:20251103T174651Z SUMMARY:Media and Entertainment Interest Group\, Timed Text Working Group j oint meeting DTSTART;TZID=Asia/Tokyo:20251110T134500 DTEND;TZID=Asia/Tokyo:20251110T150000 DESCRIPTION:https://www.w3.org/events/meetings/d45c8d74-9273-40eb-949e-a070 a4c2be79/\n\n\n\nAgenda: https://github.com/w3c/media-and-entertainment/is sues/110 STATUS:CONFIRMED CREATED:20250716T142531Z LAST-MODIFIED:20251103T174651Z 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=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:Floor 4 - 404 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:0bf6ca9c-9bd3-4043-854c-5dd1280fafee DTSTAMP:20251110T004346Z SUMMARY:Audio Description Community Group DTSTART;TZID=Asia/Tokyo:20251110T153000 DTEND;TZID=Asia/Tokyo:20251110T164500 DESCRIPTION:https://www.w3.org/events/meetings/0bf6ca9c-9bd3-4043-854c-5dd1 280fafee/\n\nReview of current status of DAPT and its implementations.\n\n Agenda\n\n* Review of DAPT specification\n* Implementations and status STATUS:CONFIRMED CREATED:20250716T142554Z LAST-MODIFIED:20251110T004346Z 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=Audio Description Community Group:mailto:public-audio-description@w3.org LOCATION:Floor 4 - 404 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:cf8f76b2-8756-44f5-9299-fb39cf5ee66a DTSTAMP:20251105T231558Z SUMMARY:Autonomous Agents on the Web CG DTSTART;TZID=Asia/Tokyo:20251110T153000 DTEND;TZID=Asia/Tokyo:20251110T164500 DESCRIPTION:https://www.w3.org/events/meetings/cf8f76b2-8756-44f5-9299-fb39 cf5ee66a/\n\nThe meeting will begin with an overview of the WebAgents CG — including its history\, goals\, and scope.\n\nWe will then continue wi th a discussion of Hypermedia Multi-Agent Systems\, starting from early vi sions of agents on the Web\, a brief history of Web-based agents and multi -agent systems (MAS)\, and focusing on the CG's current work on defining a rchitectural patterns for Web-based MAS.\n\nAgenda: https://github.com/w3c -cg/webagents/tree/main/Meetings/2025-11-10-TPAC STATUS:CONFIRMED CREATED:20250716T142815Z LAST-MODIFIED:20251105T231558Z 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=Autonomous Agents on the Web Community Group:mailto:public-webagents@w3.org LOCATION:Floor 3 - 306 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:cb1431ba-d0d5-461c-9e5e-aab4c2da403f DTSTAMP:20251103T174753Z SUMMARY:Documentation CG DTSTART;TZID=Asia/Tokyo:20251110T153000 DTEND;TZID=Asia/Tokyo:20251110T164500 DESCRIPTION:https://www.w3.org/events/meetings/cb1431ba-d0d5-461c-9e5e-aab4 c2da403f/\n\nDocumentation CG session: Explainer workshop (with TAG member s)\n\nAgenda: https://github.com/w3c-cg/webdocs/issues/24 STATUS:CONFIRMED CREATED:20250716T142637Z LAST-MODIFIED:20251103T174753Z 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=Documentation Comm unity Group:mailto:public-docs-cg@w3.org LOCATION:Floor 5 - 503 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:af242c02-5463-4aea-9203-7b2616111a6e DTSTAMP:20260219T073445Z SUMMARY:Building it in vs. Bolting it on - Making Accessible Specs\, and Up dates to the accessibility horizontal review process DTSTART;TZID=Asia/Tokyo:20251110T170000 DTEND;TZID=Asia/Tokyo:20251110T180000 DESCRIPTION:https://www.w3.org/events/meetings/af242c02-5463-4aea-9203-7b26 16111a6e/\n\nWe want to make it easy for you to add features that enhance and deepen the accessibility of the platform on a document level. There ar e a number of existing and forthcoming to support you in this.\n\nIn this session\, we’ll share with you some recent updates to several of these r esources\, as well as details on further enhancements we’re working on. Most importantly\, we want to get your feedback\, to ensure that the work will help you out.\n\nA full agenda is given separately\, but at the highe st level\, we’ll cover the following\, before having a group discussion\ , so we can answer your questions and get your feedback:\n\n* Recent and p lanned ease-of-use improvements to the horizontal review process for acces sibility - including the need for early help and support\, and how we’re making it easier for you to request that.\n\n* What exactly the Accessibl e Platform Architectures (APA) WG can provide you with in reviews\; where that advice comes from\; and how you and the review process might contribu te to it.\n\n* A new\, more concrete\, direction for the Framework for Acc essibility in the Specification of Technologies (FAST)\, which aims to red uce the amount of things that come up in review\, by supporting you in wri ting specs that consider\, promote\, and enhance accessibility from the ou tset.\n\nCredit to Peter Korn for the ‘building it in vs. bolting it on ’ concept.\n\n**Goal(s):**\nTo update people on improvements to accessib ility horizontal review that have been made\, and are planned\, and to get feedback on them.\n\nAgenda\n\n* Short presentation\n\n - Myths around t he horizontal review process.\n - Getting review earlier\, and making the process easier.\n - How the pieces fit together: TAG\, FAST\, APA\, othe rs\, and where our guidance comes from.\n - Speeding up: How FAST is bein g retooled.\n\n* Group discussion. Suggested topics:\n\n - Answering ques tions about the current process\, and recent changes.\n - What you need f rom resources like the FAST.\n - Collecting your feedback\, and giving yo u options for providing more.\n - How we could use your help\, and your o rganization’s help.\n\n**Materials:**\n- [recording](https://www.w3.org/ 2025/11/breakouts/recording-60.html)\n- [Session proposal on GitHub](https ://github.com/w3c/tpac2025-breakouts/issues/60) STATUS:CONFIRMED CREATED:20251028T131458Z LAST-MODIFIED:20260219T073445Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 4 - 405 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:1a19962f-cbe5-42b9-8070-80d4209fd779 DTSTAMP:20260219T073537Z SUMMARY:Declarative capability access DTSTART;TZID=Asia/Tokyo:20251110T170000 DTEND;TZID=Asia/Tokyo:20251110T180000 DESCRIPTION:https://www.w3.org/events/meetings/1a19962f-cbe5-42b9-8070-80d4 209fd779/\n\nhttps://github.com/WICG/PEPC/ (along with specific instantiat ions of the pattern in proposals like [``](https://github.com /WICG/PEPC/blob/main/geolocation_explainer.md) and [``](https://g ithub.com/mikewest/pepc-install/)) suggests a declarative model for capabi lity access\, pushing away from a status quo in which developers trigger p rompts at will\, towards one in which users are more firmly in the drivers ' seat.\n\n**Goal(s):**\nIt would be lovely to discuss the capability mode l these proposals embody\, and how we might align on its application acros s a broader swath of the web's API surface.\n\nAgenda\n\n**Materials:**\n- [Session proposal on GitHub](https://github.com/w3c/tpac2025-breakouts/is sues/81) STATUS:CONFIRMED CREATED:20251028T131755Z LAST-MODIFIED:20260219T073537Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 5 - 504 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:f5bc8948-a0d0-4d95-9f89-b29dfbff62fa DTSTAMP:20260219T073616Z SUMMARY:Find deterministic sizing rules for free-form documents DTSTART;TZID=Asia/Tokyo:20251110T170000 DTEND;TZID=Asia/Tokyo:20251110T180000 DESCRIPTION:https://www.w3.org/events/meetings/f5bc8948-a0d0-4d95-9f89-b29d fbff62fa/\n\nHistorically\, the viewport of html documents has always been determined by the browsers frame\, being the browser window\, browser tab \, or browser popup size. The author of the html document can then base th eir own styling and dimensions based on this size with units like vw and v h which in these situations are deterministic and non-ambiguous.\n\nWith t he introduction of web extensions\, a new type of situation is born in whi ch the author of the html document can\, with certain restraints and many issues (which you can read about below) determine and change the size of t he viewport by changing the height/width of the html/body elements. Exampl es are the extension popup and the options page if defined with options_ui .open_in_tab=false.\n\nIn an ideal world the document would communicate (i n any form\, declarative in css for example) its preferred min/ideal/max h eight/width if in auto size. In which the ideal height/width could also me an "match" the browsers ideal sizing if it sits in between the min/max ran ge. This preference is then incorporated by the browser and either fully o r partially respected to render the auto-sized content.\n\nThere is some p rior art in the CSSWG which discusses the auto-sizing of iframe elements o n their parent document. See:\nhttps://github.com/w3c/csswg-drafts/issues/ 1771 and https://github.com/domenic/cooperatively-sized-iframes\nand in th e WECG:\nhttps://github.com/w3c/webextensions/issues/692 and https://githu b.com/w3c/webextensions/issues/436\n\nSome of the techniques currently in use for the auto sizing and some of the proposals to accompany them can be reused/shared for auto-sizing of iframes.\n\nWith iframes\, security is a concern so the auto-sizing can not be opt-in by default for both host and iframe. A potential way to address this would be adding a "autosize" keyw ord to the and an autosize attribute on the iframe. \n\n**Goal(s):**\nBrainstorm about potential solutions and reduce the scop e of solutions to determine next steps.\n\nAgenda\n\n**Materials:**\n- [Se ssion proposal on GitHub](https://github.com/w3c/tpac2025-breakouts/issues /58) STATUS:CONFIRMED CREATED:20251028T131432Z LAST-MODIFIED:20260219T073616Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 4 - 406 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:c40ecf9f-be75-47ae-a387-6d1101566f0f DTSTAMP:20260219T073712Z SUMMARY:Harm and Threat Modeling for National Digital Identities DTSTART;TZID=Asia/Tokyo:20251110T170000 DTEND;TZID=Asia/Tokyo:20251110T180000 DESCRIPTION:https://www.w3.org/events/meetings/c40ecf9f-be75-47ae-a387-6d11 01566f0f/\n\nIn line with ongoing efforts to address the harms and threats associated with the deployment of national digital identities\, W3C and F BK’s Center for Cybersecurity are collaborating to develop an innovative \, high-level threat modeling framework. This model is based on a card dec k (similar to the STRIDE Elevation of Privilege game) and integrates the t ransformative principles of the LEGO® SERIOUS PLAY® methodology to enabl e comprehensive and participatory threat modeling.\n\nIn this breakout ses sion\, we will explore how using LEGO® SERIOUS PLAY® for threat modeling can help uncover security\, privacy\, and human rights risks in digital i dentity systems\, and share insights from the initial validation of our ca rd game.\n\nWe will then introduce the card deck itself by showcasing a se lection of example cards\, built on our previous research and inspired by both the STRIDE Elevation of Privilege game and the LIDDUN-GO deck.\n\nFin ally\, we will outline our future plans to advance this line of work in th e name of safe\, human-centric technologies and web standards.\n\n**Goal(s ):**\nIntroduce our work on Harm and Threat Modeling using LSP in the cont ext of Digital Identities\n\nAgenda\n\n**Materials:**\n- [Session proposal on GitHub](https://github.com/w3c/tpac2025-breakouts/issues/56) STATUS:CONFIRMED CREATED:20251028T131409Z LAST-MODIFIED:20260219T073712Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 5 - 505 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:ef18fde3-f3f0-498a-addf-d47f33716014 DTSTAMP:20260219T074106Z SUMMARY:LinkID – Toward a Persistent Identifier Standard for Hyperlinks DTSTART;TZID=Asia/Tokyo:20251110T170000 DTEND;TZID=Asia/Tokyo:20251110T180000 DESCRIPTION:https://www.w3.org/events/meetings/ef18fde3-f3f0-498a-addf-d47f 33716014/\n\nBroken links threaten the long-term integrity and trustworthi ness of the Web. \nThe [Link Genetic initiative](https://github.com/Link-G enetic-GmbH/lid/) introduces “LinkID”\, a persistent\, bidirectional i dentifier scheme designed to ensure link resilience\, metadata preservatio n\, and semantic interoperability across domains and over time.\n\nThis se ssion invites W3C members to discuss the feasibility of a new `linkid:` UR I scheme\, alignment with existing identifier systems (DOI\, ARK\, UUID)\, and next steps toward standardisation.\n\nWe plan to:\n\n- Identify poten tial Working Groups or Community Groups interested in hosting a LinkID pro posal. \n- Discuss governance\, persistence\, and interoperability model s for resilient linking. \n- Outline a roadmap for open-source reference implementation and metadata framework.\n\n**Goal(s):**\n- Introduce LinkI D as a general-purpose persistent identifier for hyperlinks. \n- Present a rchitecture\, components\, privacy & interoperability model. \n- Validate the need for a W3C Community Group. \n- Collect feedback from browser vend ors\, archives\, PID ecosystem and W3C participants.\n\nAgenda\n\n- Welcom e & logistics (remote chair + in-room support) \n- Link decay problem (mo tivation) \n- Challenges of link fragility \n- What is LinkID \n- Archi tecture components \n- Security & privacy \n- Interoperability with DOI/ ARK/UUID/archives \n- Why W3C & standardization path \n- Open discussion \n- Next steps & follow-up channels\n\n**Materials:** \n- [Slides](https ://github.com/Link-Genetic-GmbH/lid/blob/main/TPAC%202025/Link%20Genetic%2 0-%20TPAC%202025%20Breakout%20session.pdf) \n- GitHub Repo: https://githu b.com/Link-Genetic-GmbH/lid/ \n- [Session proposal on GitHub](https://git hub.com/w3c/tpac2025-breakouts/issues/83) STATUS:CONFIRMED CREATED:20251103T200239Z LAST-MODIFIED:20260219T074106Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 3 - 303 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:b35bbc5a-bf2b-49fe-bd05-e04164fb4560 DTSTAMP:20260219T074223Z SUMMARY:Payment Authentication on the Web: an Issuer’s Perspective DTSTART;TZID=Asia/Tokyo:20251110T170000 DTEND;TZID=Asia/Tokyo:20251110T180000 DESCRIPTION:https://www.w3.org/events/meetings/b35bbc5a-bf2b-49fe-bd05-e041 64fb4560/\n\nDigital payment authentication is nearly ubiquitous in all re gions\, yet payment security continues to collide with customer friction. With advancements in webAuthn extensions\, digital credentials\, and biome tric authenticators\, it’s clear that antiquated authentication methods like OTP are part of a fading past. \n\nIn this session\, I’ll walk thro ugh Capital One’s digital payment authentication approach. Topics will i nclude our thoughts towards Passkeys\, challenges with our novel AirKey au thentication method\, and our journey to disintegrate a reliance on OTP.\n \n**Goal(s):**\nProvide an issuer perspective on digital payment authentic ation. Drive discussion & brainstorm potential advancements in payment sec urity.\n\nAgenda\n\n**Materials:**\n- [Session proposal on GitHub](https:/ /github.com/w3c/tpac2025-breakouts/issues/78) STATUS:CONFIRMED CREATED:20251028T131732Z LAST-MODIFIED:20260219T074223Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 4 - 403 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:5c2a1848-9508-4948-a9f8-74757796d6b7 DTSTAMP:20260219T074350Z SUMMARY:Publication tooling DTSTART;TZID=Asia/Tokyo:20251110T170000 DTEND;TZID=Asia/Tokyo:20251110T180000 DESCRIPTION:https://www.w3.org/events/meetings/5c2a1848-9508-4948-a9f8-7475 7796d6b7/\n\nThis breakout will be divided into two parts:\n* Part 1: Exte rnal Metadata Integration — How ReSpec and Bikeshed could leverage share d metadata files (e.g. JSON files) to provide more details on the future o f the specification. We'll discuss practical approaches to linking externa l data sources and improving maintainability. The use case mainly comes fr om the [revamp of the CG program](https://github.com/w3c/tpac2025-breakout s/issues/41) but there may be other needs.\n* Part 2: Bikeshed support in spec-generator — We are looking at adding bikeshed support to [spec-gene rator](https://labs.w3.org/spec-generator/). We will present a demo and di scuss what we are missing to replace [the service from csswg.org](https:// api.csswg.org/bikeshed/).\n\n@tabatkins\, @marcoscaceres\, @sidvishnoi\, @ kfranqueiro\, @dontcallmedom\, @tidoust\, @vivienlacourba 👋\n\n**Goal( s):**\nThis breakout is intended to be a collaborative session and gather feedback.\n\nAgenda\n\n**Materials:**\n- [slides](https://www.w3.org/Talks /2025/dak-publication-tools/)\n- [Session proposal on GitHub](https://gith ub.com/w3c/tpac2025-breakouts/issues/85) STATUS:CONFIRMED CREATED:20251104T144834Z LAST-MODIFIED:20260219T074350Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 4 - 404 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:a19681fa-101f-4a78-8efb-54314172dd42 DTSTAMP:20260219T074459Z SUMMARY:Stronger Together: Super-charging Agentic AI with Accessibility Des tinations DTSTART;TZID=Asia/Tokyo:20251110T170000 DTEND;TZID=Asia/Tokyo:20251110T180000 DESCRIPTION:https://www.w3.org/events/meetings/a19681fa-101f-4a78-8efb-5431 4172dd42/\n\nAgentic AI aims to function with minimal user interaction.\n\ nAPA's Discoverable Destinations\nenables predictable programmatic access to common\nweb content components (such as login\, contact data\, store ho urs\,\nand more). Currently\, such content is discovered by\nbrittle web s craping techniques that are unreliable and cumbersome to code.\n\nTogether they can super-charge classic piping and I/O redirection.\n\n**Goal(s):** \nExplore potential synergies of WAI-Adapt Discoverable Destinations and A gentic AI.\n\nAgenda\n\n**Materials:**\n- [recording](https://www.w3.org/2 025/11/breakouts/recording-62.html)\n- [Session proposal on GitHub](https: //github.com/w3c/tpac2025-breakouts/issues/62) STATUS:CONFIRMED CREATED:20251028T131521Z LAST-MODIFIED:20260219T074459Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 3 - 302 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:006632e7-fb94-44e9-8b12-a22f43556788 DTSTAMP:20260219T074626Z SUMMARY:Why W3C? Motivational Drivers for Participation DTSTART;TZID=Asia/Tokyo:20251110T170000 DTEND;TZID=Asia/Tokyo:20251110T180000 DESCRIPTION:https://www.w3.org/events/meetings/006632e7-fb94-44e9-8b12-a22f 43556788/\n\nThis breakout examines why people participate in W3C based on new research\, [Investigating Motivational Drivers of Participation in W3 C’s Web Standards Development Process](https://dspace.mit.edu/handle/172 1.1/162519). I’ll share findings from a literature review and 13 semi‑ structured interviews about W3C. Economic\, philosophical\, and moral driv ers are revealed through the frameworks of game theory\, design persons\, and early Web philosophy. Also examined are the influence of structural dy namics like consensus requirements\, proof‑of‑implementation norms\, a nd the role of power players. After a concise briefing on the research's f indings\, I’ll open the floor for participants to share perspectives\, c hallenge assumptions\, and explore ideas for how these dynamics can or sho uld shape the future of W3C standards work.\n\n**Goal(s):**\nBuild a share d understanding of motivational drivers and influence patterns within W3C and how these themes could inform future thinking.\n\nAgenda\n\n- Welcome & context\n- Research findings briefing (20 min)\n- Open discussion: refle ctions\, challenges\, and ideas\n\n**Materials:**\n- [Session proposal on GitHub](https://github.com/w3c/tpac2025-breakouts/issues/86) STATUS:CONFIRMED CREATED:20251105T142327Z LAST-MODIFIED:20260219T074626Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 4 - 402 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:7a9ce9b0-23ff-45e3-a9fa-0426ce803cee DTSTAMP:20260219T072043Z SUMMARY:Annotating WPT to Surface the Status of the Platform DTSTART;TZID=Asia/Tokyo:20251111T083000 DTEND;TZID=Asia/Tokyo:20251111T093000 DESCRIPTION:https://www.w3.org/events/meetings/7a9ce9b0-23ff-45e3-a9fa-0426 ce803cee/\n\nIn this breakout\, you'll become acquainted with [the Web Dev eloper Experience (WebDX) Community Group](https://www.w3.org/community/we bdx/) and its efforts to formally classify the platform's capabilities int o a set of "features" as understood by web developers. You will see how th is information is integrated into WPT and the practical value of that inte gration. You'll also learn how you can support the process as a specificat ion editor and/or test author. Finally\, you'll brainstorm opportunities t o refine the process in service of fostering more nuanced insights into th e state of the platform.\n\n**Goal(s):**\nInspire participation in an ongo ing effort to improve visibility into implementation status\n\nAgenda\n\n* *Materials:**\n- [Session proposal on GitHub](https://github.com/w3c/tpac2 025-breakouts/issues/16) STATUS:CONFIRMED CREATED:20251028T073458Z LAST-MODIFIED:20260219T072043Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 5 - 505 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:758666a3-cb69-443b-a93d-934fe9c17f7f DTSTAMP:20260219T072223Z SUMMARY:DOM Localization DTSTART;TZID=Asia/Tokyo:20251111T083000 DTEND;TZID=Asia/Tokyo:20251111T093000 DESCRIPTION:https://www.w3.org/events/meetings/758666a3-cb69-443b-a93d-934f e9c17f7f/\n\nUsers of the web are best served by being able to experience it in their native languages. Currently\, localization of web content is a chieved with a multitude of custom solutions\, most of which are unable to express the full depth and breadth of human expressions in all languages. Introducing an easy-to-use but powerful standard localization solution wo uld improve the experience of all users\, in particular the vast majority who do not speak English natively.\n\nThis session is a continuation of th e [2023 breakout session](https://www.w3.org/events/meetings/4fd28161-058b -4daa-9618-d1893be9c39c/). Since then\, the Unicode MessageFormat standard has been published as a [part of Unicode Technical Standard #35](https:// unicode.org/reports/tr35/tr35-messageFormat.html) and the [DOM Localizatio n explainer](https://github.com/mozilla/explainers/blob/main/dom-localizat ion.md) has been updated. It has also become clear that a web-compatible f ile format for localization resources needs to be identified as a part of the work towards DOM localization\, or a new file format needs to be speci fied.\n\n**Goal(s):**\nCollect comments on the proposal and recruit intere sts to work on the standard.\n\nAgenda\n\n**Big Questions:**\n1. Should we work on introducing localization as a capability of the web platform?\n2. Is the Internationalization WG an appropriate forum for standardizing the message resource file format?\n3. How specific to localization should the HTML capabilities be?\n\n**Materials:**\n- [Introductory slides](https:// docs.google.com/presentation/d/1ON2yeocyDSVr8r0cg8ZlhgpFfsvloznq1pJqYSADJs 8/edit?usp=sharing)\n- [Session proposal on GitHub](https://github.com/w3c /tpac2025-breakouts/issues/67) STATUS:CONFIRMED CREATED:20251028T131556Z LAST-MODIFIED:20260219T072223Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 3 - 303 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:e9d8c4dc-b34a-4e43-bef9-b7a0c041f407 DTSTAMP:20260219T072417Z SUMMARY:Media Content Metadata: Practical Approaches for Cross-Industry Col laboration DTSTART;TZID=Asia/Tokyo:20251111T083000 DTEND;TZID=Asia/Tokyo:20251111T093000 DESCRIPTION:https://www.w3.org/events/meetings/e9d8c4dc-b34a-4e43-bef9-b7a0 c041f407/\n\nMedia content metadata is a key enabler for cross-industry se rvice deployment and value creation.\n\nThis session will explore practica l approaches to improve media metadata interoperability\, focusing on indu stry use cases.\n\nAt TPAC 2023\, the breakout session titled [Facilitatin g media content distribution across industries](https://www.w3.org/2023/09 /13-cross-industry-media-content-minutes.html) discussed the potential and challenges of media interoperability across sectors such as broadcasting and publishing.\n\nFollowing that discussion\, the [Media Content Metadata Japanese Community Group](https://github.com/w3c-cg/mcm-jp/blob/main/READ ME_en.md) (MCM-JP CG) was established. The group gathered case studies\, r eviewed existing specifications\, and verified feasibility using operation al metadata.\n\nWe will present the outcomes of MCM-JP CG activities with live demonstrations and invite feedback from participants. The session wil l also identify next steps to expand collaboration and promote practical i mplementation across industries.\n\n**Goal(s):**\nTo report on metadata in teroperability efforts across media sectors and gather feedback for future collaboration.\n\nAgenda\n\n- Introduction and background\n- Presentation of MCM-JP CG activities and findings (including live demos)\n- Feedback a nd discussion on interoperability challenges and opportunities\n- Identify ing next steps for collaboration and implementation\n\n**Materials:**\n- [ Session proposal on GitHub](https://github.com/w3c/tpac2025-breakouts/issu es/51) STATUS:CONFIRMED CREATED:20251028T131326Z LAST-MODIFIED:20260219T072417Z SEQUENCE:4 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 3 - 302 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:918534a2-ae5e-4559-b28e-9f0c5a92a1d1 DTSTAMP:20260219T072510Z SUMMARY:Mobile student ID implementation into Japanese society. DTSTART;TZID=Asia/Tokyo:20251111T083000 DTEND;TZID=Asia/Tokyo:20251111T093000 DESCRIPTION:https://www.w3.org/events/meetings/918534a2-ae5e-4559-b28e-9f0c 5a92a1d1/\n\nCurrently\, it is technically possible to apply various legac y credentials to new web standards such as W3C VC\, IETF SD-JWT\, and ISO mdoc. However\, there are no established rules for using these standards i n an interoperable or universal manner\, not only for National IDs but als o for private sector IDs such as Student IDs and Corporate IDs.\n\nWe are collaborating with the National Institute of Informatics (NII) to establis h standards for Student IDs in Japan based on the ISO/IEC 18013 standard. They are set to create rules regarding how to issue credentials\, how to c onstruct the data model\, and how to assure and validate the data. We atte nded a use case demonstration event held by Osaka University this October\ , where several use cases were accepted by participants from various unive rsities in Japan.\n\nOur goal is to make Student ID interoperable and easy to use\, not just in Japan but globally. Therefore\, we would like to dis cuss the following points:\n\n- What are the most common use cases for Stu dent IDs in your country?\n- What capabilities would be enabled if Global Student ID Interoperability is achieved?\n- What is needed to achieve this \, including the prospects for Digital Credentials API?\n\n**Goal(s):**\nL et's Ideate and identify key use cases regarding Student ID interoperabili ty.\n\nAgenda\n\n**Materials:**\n- [Session proposal on GitHub](https://gi thub.com/w3c/tpac2025-breakouts/issues/26) STATUS:CONFIRMED CREATED:20251028T073655Z LAST-MODIFIED:20260219T072510Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 4 - 401 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:8b1b3b2d-132e-4ce5-a00a-dff9d7bb70a4 DTSTAMP:20260219T072559Z SUMMARY:Privacy Pass for digital ads verification DTSTART;TZID=Asia/Tokyo:20251111T083000 DTEND;TZID=Asia/Tokyo:20251111T093000 DESCRIPTION:https://www.w3.org/events/meetings/8b1b3b2d-132e-4ce5-a00a-dff9 d7bb70a4/\n\nDevice spoofing is a pervasive problem in digital ads\, with bots masquerading as user devices\, and bad actors spoofing high-value Con nected TV inventory. This results in wasted ad spend for advertisers and r educed ad revenue for legitimate publishers. The Privacy Pass protocol\, w hich enables devices to assert their authenticity in a privacy-preserving manner\, has been adopted for a digital ads verification use case. This im plementation is being standardized within the IAB Tech Lab's Open Measurem ent SDK to simplify broad adoption by publishers. Using this mechanism\, V erifiers (Origins in Privacy Pass)\, which are typically Traffic Quality / ad verification vendors\, will be able to uncover sellers of spoofed inve ntory and take enforcement actions on them.\n\nWe will present the mechani sm and how a "positive" and anonymous signal that does not have 100% cover age can be used for fraud detection.\n\n**Goal(s):**\nTo create awareness of a new fraud detection use case implemented with Privacy Pass and to sol icit feedback on potential improvements.\n\nAgenda\n\n**Materials:**\n- [S ession proposal on GitHub](https://github.com/w3c/tpac2025-breakouts/issue s/4) STATUS:CONFIRMED CREATED:20251028T073324Z LAST-MODIFIED:20260219T072559Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 4 - 404 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:f14a2789-e642-4208-a9a3-c49e72978f41 DTSTAMP:20260219T072646Z SUMMARY:Restarting W3C QA - Quality Assurance DTSTART;TZID=Asia/Tokyo:20251111T083000 DTEND;TZID=Asia/Tokyo:20251111T093000 DESCRIPTION:https://www.w3.org/events/meetings/f14a2789-e642-4208-a9a3-c49e 72978f41/\n\nTo make better specifications/standards\, QA work needs to ad vance.\n\nRelated work:\n\n* [W3C QA](https://www.w3.org/QA/WG/) - core wo rk\n* [EARL](https://www.w3.org/TR/EARL10-Schema/) - to facilitate the exc hange of test results between Web accessibility evaluation tools in a vend or-neutral and platform-independent format.\n* [WPT](https://github.com/we b-platform-tests/wpt) - test suites for some web platform specs.\n* [Spec Terms](http://www.w3.org/ns/spec) - provides classes and properties that c an be used to describe any significant unit of information in technical re ports.\n* [Solid QA](https://solidproject.org/ED/qa) - connects a bunch of the core QA work (but not actually tied to Solid).\n* ...\n\n**Goal(s):** \nQA as CG or WG or Horizontal Group\n\nAgenda\n\n**Materials:**\n- [Sessi on proposal on GitHub](https://github.com/w3c/tpac2025-breakouts/issues/36 ) STATUS:CONFIRMED CREATED:20251028T073817Z LAST-MODIFIED:20260219T072646Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 5 - 504 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:ca0be7c4-0d4a-4d67-b815-05accd660bec DTSTAMP:20260219T072734Z SUMMARY:Security guidance for web developers DTSTART;TZID=Asia/Tokyo:20251111T083000 DTEND;TZID=Asia/Tokyo:20251111T093000 DESCRIPTION:https://www.w3.org/events/meetings/ca0be7c4-0d4a-4d67-b815-05ac cd660bec/\n\nIn the [Security Web Application Guidelines Community Group]( https://github.com/w3c-cg/swag/) (SWAG CG) we're trying to understand what web platform security best practices exist and which guidance we can give web developers to secure web applications.\n\nThe Open Web Docs (OWD) col lective has been awarded an investment to write documentation and to condu ct research on this matter by the Sovereign Tech Agency. The work OWD is p lanning to do over the next months is described in this blog post: https:/ /openwebdocs.org/content/posts/stf-investment-2025/\n\nThis is an open-end ed session proposed to discuss the efforts of SWAG and OWD for security do cumentation and guidelines for web developers.\n\n**Goal(s):**\nExchange a bout web security guidelines in the context of SWAG and the OWD project\n\ nAgenda\n\n**Materials:**\n- [Session proposal on GitHub](https://github.c om/w3c/tpac2025-breakouts/issues/52) STATUS:CONFIRMED CREATED:20251028T131334Z LAST-MODIFIED:20260219T072734Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 4 - 403 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:f4b8985a-2604-4cb0-a37a-1e189ac6fe19 DTSTAMP:20260219T072812Z SUMMARY:WCAG 2.2 and non-Latin languages DTSTART;TZID=Asia/Tokyo:20251111T083000 DTEND;TZID=Asia/Tokyo:20251111T093000 DESCRIPTION:https://www.w3.org/events/meetings/f4b8985a-2604-4cb0-a37a-1e18 9ac6fe19/\n\nWCAG 2.2 includes success criteria related to the visual pres entation of text including how text spacing can be used to benefit people with reading disabilities or low vision. In particular:\n\n* [1.4.8 Visual presentation](https://www.w3.org/TR/WCAG22/#visual-presentation)\n* [1.4. 12 Text spacing](https://www.w3.org/TR/WCAG22/#text-spacing)\n\nThis sessi on will introduce the topic and issues. Specifically:\n\n* What changes ar e necessary to 1.4.8 and 1.4.12 to accommodate non-Latin scripts?\n* What research is available to support changes?\n* What other success criteria m ight include issues related to non-Latin scripts\n\n**Goal(s):**\nTo devel op a plan of action to address gap in provision\n\nAgenda\n\n* Introductio n and outline of issue\n* Identify key issues\n* Explore possible solution s\n* Develop initial plan of action\n\n**Materials:**\n- [Session proposal on GitHub](https://github.com/w3c/tpac2025-breakouts/issues/38) STATUS:CONFIRMED CREATED:20251028T073843Z LAST-MODIFIED:20260219T072812Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 4 - 402 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:757dc9dc-d7a4-4041-908b-ea1daf5589e2 DTSTAMP:20260219T073233Z SUMMARY:WebSpatial API for Spatialized HTML/CSS and Spatialized PWAs on spa tial and multimodal AI devices DTSTART;TZID=Asia/Tokyo:20251111T083000 DTEND;TZID=Asia/Tokyo:20251111T093000 DESCRIPTION:https://www.w3.org/events/meetings/757dc9dc-d7a4-4041-908b-ea1d af5589e2/\n\nThe strong demand for multimodal interaction capabilities in client-side AI is driving the evolution of next-generation general computi ng platforms from screen-based and handheld devices to hands-free wearable devices\, such as augmented reality glasses and mixed reality visors (hea d-mounted displays).\n\nApps (include Web) on such next-gen platforms must be able to:\n\n1. Fully leverage 3D space surrounding the user\, moving b eyond the limitations of 2D planes\, breaking free from window borders.\n\ n2. Work with a new OS architecture based on [Unified Rendering](https://d eveloper.picoxr.com/news/multi-app-rendering/) and Shared Space\, in which apps no longer render themselves independently\, they can blend in with o ther apps in the same shared space\, and use OS-managed spatial containers instead of old-style windows or browser tabs.\n\n3. Integrate seamlessly with the real-world environment\, for example\, Apple's recently proposed liquid/frosted glass UI. Instead of using a fixed solid background color o r just switching between light and dark modes\, the UI dynamically renders a blended material background based on what's behind each part of the int erface from the user's perspective\, making it clear and readable no matte r the lighting or colors in the environment.\n\n4. In addition to conventi onal 2D panel-based and 3D canvas-based GUIs\, apps should be able to incl ude real volumetric 3D content that can be viewed from all angles and meas ured in real-world units.\n\n5. Whether 2D or 3D\, elements must be capabl e of positioning and transformation along the spatial Z-axis\, supporting spatial interaction events to acquire positional and motion data within 3D space\, thereby enabling interactions such as dragging\, rotation\, and s caling.\n\n6. Don't break away from mainstream GUI development ecosystems\ , keep using the established view components\, layout systems\, and stylin g systems from 2D GUI development (for the web\, that means HTML/CSS). In most application scenarios\, limited 3D development requirements should be embedded within the overarching 2D development approach. For example\, 3 D container elements should be able to join the X/Y layout system just lik e 2D elements\, while supporting full 3D-engine-style development inside. That means in HTML code you can use different Entities (different geometri c Entities\, Entities capable of loading 3D model assets\, or Entities cap able of hosting 2D HTML or particle effects)\, declare\, load and configur e materials and textures\, and work with EntityTransform and physics engin e properties.\n\nWithin the existing Immersive Web WG\, the WebXR standard \, analogous to OpenXR\, always take over the binocular display and the en tire spatial environment\, perform self-contained rendering\, and build in teractions from scratch\, thereby failing to satisfy the aforementioned re quirements.\n\nThere are some scattered Spatial Web features right now\, l ike Model Element\, Immersive Media (Fullscreen API)\, and Interactive Reg ions (Hover Effects for Eye-Hand Interactions). They can't systematically meet the needs above\, and they still lag far behind native spatial apps.\ n\nA systematic solution can only be achieved by equipping existing HTML/C SS and PWA technologies with spatial capabilities\, extending the current 2D web standards with a minimal set of new APIs (let's call them the WebSp atial API). \n\nSuch an approach would enable the open web to gain entry i nto the paradigm shift of general computing platforms\, and potentially em erge as the optimal application solution for these platforms. This is beca use both AI OS and MR OS inherently demand vast numbers of apps that are i nstallation-free\, on-demand\, and disposable - characteristics naturally aligned with the web.\n\n**Goal(s):**\nInitiate the discussion and draftin g of the WebSpatial API's requirements and standardization.\n\nAgenda\n\n* *Materials:**\n- [recording](https://www.w3.org/2025/11/breakouts/recordin g-22.html)\n- [Session proposal on GitHub](https://github.com/w3c/tpac2025 -breakouts/issues/22) STATUS:CONFIRMED CREATED:20251028T073614Z LAST-MODIFIED:20260219T073233Z SEQUENCE:4 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 4 - 406 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:344a5851-3cea-4905-b920-996ee476bb10 DTSTAMP:20260219T072932Z SUMMARY:WebView quirks and testing DTSTART;TZID=Asia/Tokyo:20251111T083000 DTEND;TZID=Asia/Tokyo:20251111T093000 DESCRIPTION:https://www.w3.org/events/meetings/344a5851-3cea-4905-b920-996e e476bb10/\n\nThis is a session for everyone to tell stories about weird bu gs and behaviors in WebViews. You can also learn how to test your web cont ent in WebViews. We would like to present a few reasons and resources for testing your web content inside WebViews. Then it’s time to share some c omplex or weird issues you had with WebViews over the years and present so me hacky workarounds.\n\n**Please bring your stories and issues and share them with us!** We maintain the site [caniwebview.com](http://caniwebview. com/) and would like to add some examples of when WebViews are doing stran ge things and provide developers with help to deal with them.\n\n**Goal(s) :**\n* Collect WebViews bugs workarounds\n* Spread the word on testing Web Views\n\nAgenda: https://github.com/WebView-CG/tpac/blob/main/TPAC-2025/Br eakout/WebViewQuirksAndTestingAgenda.md\n\nAgenda\n\n**Materials:**\n- [sl ides](https://webview-cg.github.io/tpac/TPAC-2025/Breakout/WebViewQuirksan dTesting.html)\n- [Session proposal on GitHub](https://github.com/w3c/tpac 2025-breakouts/issues/20) STATUS:CONFIRMED CREATED:20251028T073531Z LAST-MODIFIED:20260219T072932Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 4 - 405 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:7c7e68a1-2d98-4b85-b812-a9c3d2f6f50c DTSTAMP:20251107T152834Z SUMMARY:Accessibility Guidelines Working Group DTSTART;TZID=Asia/Tokyo:20251111T094500 DTEND;TZID=Asia/Tokyo:20251111T180000 DESCRIPTION:https://www.w3.org/events/meetings/7c7e68a1-2d98-4b85-b812-a9c3 d2f6f50c/\n\n\n\nAgenda\n\nMorning: WCAG 2 updates\n* Proposal\;\n * Clea n up of existing content\n * Internationalization \n * Possible algorith m updates\n * Normative errata\n * Deduplication?\n * Fixing audio desc ription\n * Timing adjustable\n * NOT: Adding new requirements\n* Discus sion Questions\n * Which of the changes above raise risks of breaking bac kwards compatibility?\n * Can we address items above WITHOUT breaking bac kwards compatibility?\n* What do we call it?\n * WCAG 2.3\n * WCAG 2026\ n * WCAG 2.final\n * WCAG 2.3 (Not backwards compatible)\n\nAfternoon: W hat would a policy document with WCAG 3 look like?\n* Input of [info from editors week](https://docs.google.com/presentation/d/1DlDxp8MCYXj3RWnFCCz1 3zsmM2fV4Wf8NbECKogdul8/edit?slide=id.g39fd5db5083_2_5#slide=id.g39fd5db50 83_2_5)\n* Desired outcome: Resolution to do such a document (in charter) \, and desired outline (not in charter) STATUS:CONFIRMED CREATED:20250716T142447Z LAST-MODIFIED:20251107T152834Z 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:Floor 4 - 402 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:3f0f2064-dc0b-4388-a6d2-80c8aea62758 DTSTAMP:20251107T171113Z SUMMARY:Accessible Platform Architectures Working Group DTSTART;TZID=Asia/Tokyo:20251111T094500 DTEND;TZID=Asia/Tokyo:20251111T110000 DESCRIPTION:https://www.w3.org/events/meetings/3f0f2064-dc0b-4388-a6d2-80c8 aea62758/\n\n\n\nAgenda: https://github.com/w3c/apa/issues/357 STATUS:CONFIRMED CREATED:20250716T142438Z LAST-MODIFIED:20251107T171113Z 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=Accessible Platfor m Architectures Working Group:mailto:public-apa@w3.org LOCATION:Floor 5 - 503 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:a4b0e300-9879-4438-aada-e25608803f21 DTSTAMP:20251107T181634Z SUMMARY:Accessible Rich Internet Applications Working Group DTSTART;TZID=Asia/Tokyo:20251111T094500 DTEND;TZID=Asia/Tokyo:20251111T180000 DESCRIPTION:https://www.w3.org/events/meetings/a4b0e300-9879-4438-aada-e256 08803f21/\n\n\n\nAgenda: https://github.com/w3c/aria/wiki/TPAC-2025-Kobe\, -Japan-Agenda#tuesday-nov-11-2025 STATUS:CONFIRMED CREATED:20251106T161017Z LAST-MODIFIED:20251107T181634Z 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=Accessible Rich In ternet Applications Working Group:mailto:public-aria@w3.org LOCATION:Floor 5 - 504 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:a5b5a614-83da-4906-8a35-1b913c6293c1 DTSTAMP:20251106T155447Z SUMMARY:Accessible Rich Internet Applications Working Group DTSTART;TZID=Asia/Tokyo:20251111T094500 DTEND;TZID=Asia/Tokyo:20251111T180000 DESCRIPTION:https://www.w3.org/events/meetings/a5b5a614-83da-4906-8a35-1b91 3c6293c1/\n\n STATUS:CANCELLED CREATED:20250716T142352Z LAST-MODIFIED:20251106T155447Z 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=Accessible Rich In ternet Applications Working Group:mailto:public-aria@w3.org LOCATION:Floor 5 - 504 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:5918a72d-0c77-4257-88c2-fa2ce51e382e DTSTAMP:20251201T161700Z SUMMARY:Decentralized Identifier Working Group DTSTART;TZID=Asia/Tokyo:20251111T094500 DTEND;TZID=Asia/Tokyo:20251111T180000 DESCRIPTION:https://www.w3.org/events/meetings/5918a72d-0c77-4257-88c2-fa2c e51e382e/\n\n\n\nAgenda\n\n|Start|End | Topic |\n|-------|------|--------- |\n|9:45 | 10:00 | Welcome\, Introductions\, and Logistics |\n|10:00 | 10: 30 | Introduction to DIDs and DID Resolution |\n|10:30 | 11:00 | Getting t o Recommendation (timeline) |\n|11:00 | 11:30 | Break |\n|11:30 | 12:00 | DID Resolution vs DID URL Dereferencing |\n|12:00 | 12:30 | DID Resolution Issue Processing |\n|12:30 | 13:00 | DID Resolution Issue Processing |\n| 13:00 | 14:15 | Lunch |\n|14:15 | 14:45 | DID Resolution PR Processing |\n |14:45 | 15:30 | DID Resolution Issue Processing |\n|15:30 | 16:00 | DIDWG Charter extension |\n|16:00 | 16:30 | Break |\n|16:30 | 17:30 | Test Suit e (Testability of normative statements) |\n|17:30 | 18:30 | Next Steps | STATUS:CONFIRMED CREATED:20250716T142315Z LAST-MODIFIED:20251201T161700Z 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=Decentralized Iden tifier Working Group:mailto:public-did-wg@w3.org LOCATION:Floor 4 - 406 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:775981da-ea46-4db2-840d-8995414c29e0 DTSTAMP:20251103T174438Z SUMMARY:Internationalization Working Group DTSTART;TZID=Asia/Tokyo:20251111T094500 DTEND;TZID=Asia/Tokyo:20251111T180000 DESCRIPTION:https://www.w3.org/events/meetings/775981da-ea46-4db2-840d-8995 414c29e0/\n\n STATUS:CONFIRMED CREATED:20250716T142311Z LAST-MODIFIED:20251103T174438Z 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=Internationalizati on Working Group:mailto:public-i18n-core@w3.org LOCATION:Floor 3 - 305 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:73fd84aa-6e01-4ffe-96a3-d1463bcbded9 DTSTAMP:20251103T174554Z SUMMARY:Publishing Business Group DTSTART;TZID=Asia/Tokyo:20251111T094500 DTEND;TZID=Asia/Tokyo:20251111T110000 DESCRIPTION:https://www.w3.org/events/meetings/73fd84aa-6e01-4ffe-96a3-d146 3bcbded9/\n\n STATUS:CONFIRMED CREATED:20250716T142432Z LAST-MODIFIED:20251103T174554Z 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=Publishing Busines s Group:mailto:public-publishingbg@w3.org LOCATION:Floor 3 - 302 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:95b183fd-41bb-4f92-b013-b69121090498 DTSTAMP:20251111T005311Z SUMMARY:RDF & SPARQL Working Group DTSTART;TZID=Asia/Tokyo:20251111T094500 DTEND;TZID=Asia/Tokyo:20251111T130000 DESCRIPTION:https://www.w3.org/events/meetings/95b183fd-41bb-4f92-b013-b691 21090498/\n\n STATUS:CONFIRMED CREATED:20250716T142741Z LAST-MODIFIED:20251111T005311Z 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:Floor 4 - 404 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:f2344829-8d2f-4152-9498-c31d21d66fee DTSTAMP:20251016T203722Z SUMMARY:Second Screen Working Group DTSTART;TZID=Asia/Tokyo:20251111T094500 DTEND;TZID=Asia/Tokyo:20251111T110000 DESCRIPTION:https://www.w3.org/events/meetings/f2344829-8d2f-4152-9498-c31d 21d66fee/\n\n STATUS:CANCELLED CREATED:20250716T142452Z LAST-MODIFIED:20251016T203722Z 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=Second Screen Work ing Group:mailto:public-secondscreen@w3.org LOCATION:R12 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:72fcd843-c3ea-400d-80b5-115202deb224 DTSTAMP:20251112T094309Z SUMMARY:Timed Text WG DTSTART;TZID=Asia/Tokyo:20251111T094500 DTEND;TZID=Asia/Tokyo:20251111T180000 DESCRIPTION:https://www.w3.org/events/meetings/72fcd843-c3ea-400d-80b5-1152 02deb224/\n\n\n\nAgenda: https://github.com/w3c/ttwg/issues/323\n\nAgenda\ n\n(subject to change on the day!)\n\n09:45-10:00 - Introductions and Agen da bash\n10:00-10:30 - IMSC 1.3\n10:30-11:00 - Regulatory changes and new API proposal (Apple)\n\n11:00-11:30 - Break\n\n11:30-12:00 - DAPT issues a nd pull requests\n12:00-12:30 - WebVTT interop testing\n12:30-13:00 - Subt itle purpose field in TV-Anytime\n\n13:00-14:15 - Lunch\n\n14:15-14:45 - T TML Profile registry - make it into a proper modern-style Registry?\n14:45 -15:15 - Joint meeting follow-ups and planning\n\n16:00-16:30 - Break\n\n1 6:30-18:00 - Wrap up and next steps\, AOB STATUS:CONFIRMED CREATED:20250716T142340Z LAST-MODIFIED:20251112T094309Z 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=Timed Text Working Group:mailto:public-tt@w3.org LOCATION:Floor 3 - 306 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:f979d4dd-2934-45c5-bf39-23386f756b0b DTSTAMP:20251103T174833Z SUMMARY:Web Application Security Working Group DTSTART;TZID=Asia/Tokyo:20251111T094500 DTEND;TZID=Asia/Tokyo:20251111T130000 DESCRIPTION:https://www.w3.org/events/meetings/f979d4dd-2934-45c5-bf39-2338 6f756b0b/\n\n STATUS:CONFIRMED CREATED:20250716T142719Z LAST-MODIFIED:20251103T174833Z 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 Application Se curity Working Group:mailto:public-webappsec@w3.org LOCATION:Floor 4 - 403 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:58f360f0-e2dc-4e4c-bccf-16dadaa918ac DTSTAMP:20251124T152030Z SUMMARY:Web Applications Working Group DTSTART;TZID=Asia/Tokyo:20251111T094500 DTEND;TZID=Asia/Tokyo:20251111T180000 DESCRIPTION:https://www.w3.org/events/meetings/58f360f0-e2dc-4e4c-bccf-16da daa918ac/\n\n\n\nAgenda: https://github.com/w3c/webappswg/wiki/TPAC-2025 STATUS:CONFIRMED CREATED:20250716T142603Z LAST-MODIFIED:20251124T152030Z 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 Applications W orking Group:mailto:public-webapps@w3.org LOCATION:Floor 4 - 401 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:091a2581-034b-4afa-8ddc-91155bd4d710 DTSTAMP:20251106T105539Z SUMMARY:Web Machine Learning Community Group DTSTART;TZID=Asia/Tokyo:20251111T094500 DTEND;TZID=Asia/Tokyo:20251111T180000 DESCRIPTION:https://www.w3.org/events/meetings/091a2581-034b-4afa-8ddc-9115 5bd4d710/\n\n\n\nAgenda: https://github.com/webmachinelearning/meetings/is sues/35 STATUS:CONFIRMED CREATED:20250716T142443Z LAST-MODIFIED:20251106T105539Z 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 Machine Learni ng Community Group:mailto:public-webmachinelearning@w3.org LOCATION:Floor 4 - 405 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:3766296e-5858-40b1-92a2-2cf13206addb DTSTAMP:20251103T162450Z SUMMARY:Web of Things Plugfest DTSTART;TZID=Asia/Tokyo:20251111T094500 DTEND;TZID=Asia/Tokyo:20251111T180000 DESCRIPTION:https://www.w3.org/events/meetings/3766296e-5858-40b1-92a2-2cf1 3206addb/\n\n STATUS:CONFIRMED CREATED:20250812T142136Z LAST-MODIFIED:20251103T162450Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 3 - 307 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:23cc79d9-d1d2-4cab-9f54-2b3d7bc13633 DTSTAMP:20251103T174227Z SUMMARY:Web Payments Working Group DTSTART;TZID=Asia/Tokyo:20251111T094500 DTEND;TZID=Asia/Tokyo:20251111T160000 DESCRIPTION:https://www.w3.org/events/meetings/23cc79d9-d1d2-4cab-9f54-2b3d 7bc13633/\n\n\n\nAgenda: https://github.com/w3c/webpayments/wiki/Agenda%E2 %80%90TPAC2025 STATUS:CONFIRMED CREATED:20250716T141909Z LAST-MODIFIED:20251103T174227Z 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 Payments Worki ng Group:mailto:public-payments-wg@w3.org LOCATION:Floor 5 - 502 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:08e11ef8-c4b4-42d0-9c49-219fc5dbdded DTSTAMP:20251108T191039Z SUMMARY:Web Performance Working Group DTSTART;TZID=Asia/Tokyo:20251111T094500 DTEND;TZID=Asia/Tokyo:20251111T180000 DESCRIPTION:https://www.w3.org/events/meetings/08e11ef8-c4b4-42d0-9c49-219f c5dbdded/\n\nAgenda: https://docs.google.com/document/d/1EbG3VL27YlzQj8bnW VRI-OUHm6WcUowYoxjYOu4RlXM/edit?tab=t.0\n\nAgenda: https://docs.google.com /document/d/1EbG3VL27YlzQj8bnWVRI-OUHm6WcUowYoxjYOu4RlXM/edit?tab=t.0 STATUS:CONFIRMED CREATED:20250716T142650Z LAST-MODIFIED:20251108T191039Z 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 Performance Wo rking Group:mailto:public-web-perf@w3.org LOCATION:Floor 5 - 505 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:c33b890d-56a9-429b-ac81-aca8c5447772 DTSTAMP:20251111T004632Z SUMMARY:WHATWG DTSTART;TZID=Asia/Tokyo:20251111T094500 DTEND;TZID=Asia/Tokyo:20251111T180000 DESCRIPTION:https://www.w3.org/events/meetings/c33b890d-56a9-429b-ac81-aca8 c5447772/\n\n\n\nAgenda: https://github.com/whatwg/html/issues/11711#issue comment-3499143498 STATUS:CONFIRMED CREATED:20250716T142419Z LAST-MODIFIED:20251111T004632Z SEQUENCE:7 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 5 - 501 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:f0b973af-8de9-4c12-be03-2e89fac9b6c4 DTSTAMP:20251104T161407Z SUMMARY:Publishing Maintenance WG DTSTART;TZID=Asia/Tokyo:20251111T113000 DTEND;TZID=Asia/Tokyo:20251111T180000 DESCRIPTION:https://www.w3.org/events/meetings/f0b973af-8de9-4c12-be03-2e89 fac9b6c4/\n\n\n\nAgenda: https://github.com/w3c/epub-specs/discussions/281 5#discussioncomment-14751130\n\nAgenda\n\n| Time (JST) | Topic | CET | ET |\n| ----------- | ----- -------------------------------- | ----------- | ----------- |\n| 9:45-11: 00 | Publishing Business Group Meeting | 01:45-03:00 | 19:45-21:00 |\ n| 11:00-11:30 | Break | 03:00-03:30 | 21: 00-21:30 |\n| 11:30-12:15 | Summary of Day 1 | 03:30-04:15 | 21:30-22:15 | \n| 12:15-13:00 | Japanese Publishing Guidelines Update | 04:15-05:00 | 22 :15-23:00 |\n| 13:00-14:00 | Lunch | 05:00 -06:00 | 23:00-24:00 |\n| 14:00-15:00 | Updating Publication Manifest | 06:00-07:00 | 24:00-01:00 |\n| 15:00-16:00 | HTML in EPUB | 07:00-08:00 | 01:00-02:00 |\n| 16:00-16:30 | Break | 08:00-08:30 | 02:00-02:30 |\n| 16:30-17:15 | Issue Clean-up | 08:30-09:15 | 02:30-03:15 |\n| 17:15 -18:00 | Buffer/Wrap up | 09:15-10:00 | 03:15-04:00 | STATUS:CONFIRMED CREATED:20250905T164659Z LAST-MODIFIED:20251104T161407Z 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=Publishing Mainten ance Working Group:mailto:public-pm-wg@w3.org LOCATION:Floor 3 - 302 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:e7776945-8f20-4fd9-9935-7ec3d213b58d DTSTAMP:20251107T170953Z SUMMARY:Accessible Platform Architectures Working Group DTSTART;TZID=Asia/Tokyo:20251111T141500 DTEND;TZID=Asia/Tokyo:20251111T180000 DESCRIPTION:https://www.w3.org/events/meetings/e7776945-8f20-4fd9-9935-7ec3 d213b58d/\n\n\n\nAgenda: https://github.com/w3c/apa/issues/358 STATUS:CONFIRMED CREATED:20250716T142439Z LAST-MODIFIED:20251107T170953Z 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=Accessible Platfor m Architectures Working Group:mailto:public-apa@w3.org LOCATION:Floor 5 - 503 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:b9cb82aa-5175-4be5-bd2c-ac6c879a1100 DTSTAMP:20251103T174937Z SUMMARY:AI Agent Protocol CG DTSTART;TZID=Asia/Tokyo:20251111T141500 DTEND;TZID=Asia/Tokyo:20251111T160000 DESCRIPTION:https://www.w3.org/events/meetings/b9cb82aa-5175-4be5-bd2c-ac6c 879a1100/\n\n STATUS:CONFIRMED CREATED:20250812T142143Z LAST-MODIFIED:20251103T174937Z 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=AI Agent Protocol Community Group:mailto:public-agentprotocol@w3.org LOCATION:Floor 4 - 404 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:322c6ef9-6541-404f-9159-ad45f9339614 DTSTAMP:20251103T174748Z SUMMARY:Audio Working Group DTSTART;TZID=Asia/Tokyo:20251111T141500 DTEND;TZID=Asia/Tokyo:20251111T180000 DESCRIPTION:https://www.w3.org/events/meetings/322c6ef9-6541-404f-9159-ad45 f9339614/\n\n STATUS:CONFIRMED CREATED:20250716T142633Z LAST-MODIFIED:20251103T174748Z 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 Working Grou p:mailto:public-audio@w3.org LOCATION:Floor 3 - 304 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:6860f8d9-9ec2-46ee-9e49-e9dc4dfbc824 DTSTAMP:20251007T220805Z SUMMARY:JSON-LD WG DTSTART;TZID=Asia/Tokyo:20251111T141500 DTEND;TZID=Asia/Tokyo:20251111T160000 DESCRIPTION:https://www.w3.org/events/meetings/6860f8d9-9ec2-46ee-9e49-e9dc 4dfbc824/\n\n STATUS:CANCELLED CREATED:20250716T142557Z LAST-MODIFIED:20251007T220805Z 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=JSON-LD Working Gr oup:mailto:public-json-ld-wg@w3.org LOCATION:R12 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:5d607525-a09d-463d-b5c1-7fb5ef50a721 DTSTAMP:20251021T162106Z SUMMARY:Publishing Maintenance WG DTSTART;TZID=Asia/Tokyo:20251111T141500 DTEND;TZID=Asia/Tokyo:20251111T180000 DESCRIPTION:https://www.w3.org/events/meetings/5d607525-a09d-463d-b5c1-7fb5 ef50a721/\n\n STATUS:CANCELLED CREATED:20250716T142258Z LAST-MODIFIED:20251021T162106Z 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=Publishing Mainten ance Working Group:mailto:public-pm-wg@w3.org LOCATION:R02 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:0a775c6d-67c0-4680-9925-0a5d50513187 DTSTAMP:20251103T174754Z SUMMARY:Documentation CG DTSTART;TZID=Asia/Tokyo:20251111T163000 DTEND;TZID=Asia/Tokyo:20251111T180000 DESCRIPTION:https://www.w3.org/events/meetings/0a775c6d-67c0-4680-9925-0a5d 50513187/\n\nGeneral Documentation CG session to talk about our charter\, reviewing 2025 work\, and planning 2026.\n\nAgenda: https://github.com/w3c -cg/webdocs/issues/25 STATUS:CONFIRMED CREATED:20250716T142638Z LAST-MODIFIED:20251103T174754Z 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=Documentation Comm unity Group:mailto:public-docs-cg@w3.org LOCATION:Floor 4 - 403 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:ca2eef4b-fe56-4339-b194-d035a7070a60 DTSTAMP:20251103T174913Z SUMMARY:Web Payments WG\, Web Authentication WG joint meeting DTSTART;TZID=Asia/Tokyo:20251111T163000 DTEND;TZID=Asia/Tokyo:20251111T180000 DESCRIPTION:https://www.w3.org/events/meetings/ca2eef4b-fe56-4339-b194-d035 a7070a60/\n\n STATUS:CONFIRMED CREATED:20250716T142807Z LAST-MODIFIED:20251103T174913Z 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 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:Floor 5 - 502 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:7960bff7-981c-470d-b9b6-b36992d6d490 DTSTAMP:20251113T081020Z SUMMARY:Web Real-Time Communications WG DTSTART;TZID=Asia/Tokyo:20251111T163000 DTEND;TZID=Asia/Tokyo:20251111T180000 DESCRIPTION:https://www.w3.org/events/meetings/7960bff7-981c-470d-b9b6-b369 92d6d490/\n\n[Slides](https://docs.google.com/presentation/d/1sd5zEnvlXO5S k3ENQorUUIQiRz65sv0KZKxDMMYHM3I)\n\n### 16:35 - 16:55 State of the WG (Har ald)\n\n### 16:55 - 17:20 \n\nRTCTransport API - 10 minutes (Tony Herre) \nWebTransport over WebRTC ICE? - 5 minutes (Jan-Ivar)\nDiscussion - 10 m inutes\n\n### 17:20 - 17:35 Encoder Complexity API (Erik)\n### 17:35 - 17: 55 PEPC (Marian Harbach)\n### 17:55 - 18:00 Wrap-up and Next Steps (Chairs ) STATUS:CONFIRMED CREATED:20250716T142246Z LAST-MODIFIED:20251113T081020Z 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 Real-Time Comm unications Working Group:mailto:public-webrtc@w3.org LOCATION:Floor 4 - 404 CATEGORIES:TPAC 2025,Group Meetings END:VEVENT BEGIN:VEVENT UID:a1128bb9-d32d-49b4-9f84-a6378800d73b DTSTAMP:20251103T170828Z SUMMARY:TPAC 2025 Hackathon DTSTART;TZID=Asia/Tokyo:20251111T190000 DTEND;TZID=Asia/Tokyo:20251111T223000 DESCRIPTION:https://www.w3.org/events/meetings/a1128bb9-d32d-49b4-9f84-a637 8800d73b/\n\nJoin fellow W3C TPAC attendees for fun and fast-paced challen ges! Test your coding skills\, and compete for nerdy prizes.\nThis hackath on is open to everyone attending TPAC in person. Enjoy snacks\, meet new p eople\, and show off your creativity in this competitive evening event in a relaxed setting.\n\nRegister for this event: https://www.w3.org/register /tpac2025-hackathon\nLimited to 50 participants\n\nAgenda: https://www.w3. org/2025/11/TPAC/hackathon/ STATUS:CONFIRMED CREATED:20250820T035204Z LAST-MODIFIED:20251103T170828Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 5 - 501 CATEGORIES:TPAC 2025 END:VEVENT BEGIN:VEVENT UID:95b89f3d-1494-4f0e-9968-53fdf15945dc DTSTAMP:20260219T070840Z SUMMARY:Accelerating the adoption of modern web features\, and migrating aw ay from outdated approaches DTSTART;TZID=Asia/Tokyo:20251112T083000 DTEND;TZID=Asia/Tokyo:20251112T093000 DESCRIPTION:https://www.w3.org/events/meetings/95b89f3d-1494-4f0e-9968-53fd f15945dc/\n\nThe web platform's evolution is often faster than developer p ractices. This lag creates a two-part problem that slows the adoption of m odern APIs and leaves unnecessary bloat on the web:\n\n1. **The "sticky po lyfill" problem**: A feature (e.g.\, `IntersectionObserver`) becomes Basel ine\, but developers continue to ship unnecessary polyfills and fallbacks for it\, sometimes for years. The `IntersectionObserver` polyfill\, for ex ample\, still gets over 2.1 million weekly downloads despite the feature b eing Baseline for over 6.5 years.\n\n2. **The "reluctant adoption" problem **: A new\, powerful feature (e.g.\, the `Scheduler` API) is available\, b ut because it is not yet Baseline\, developers may be reluctant to use it\ , even when robust polyfills and fallback strategies exist. Those strategi es should be easily discoverable to developers and integrated with their t ools.\n\nBoth problems hold back the web and share a common root: the lack of a structured\, machine-readable data source that maps "old ways" (spec ific polyfill packages\, legacy patterns) to their "new way" modern API co unterparts.\n\nThis session proposes we create one.\n\nIf tooling (IDEs\, linters\, framework CLIs\, browser DevTools) had a "Rosetta Stone" dataset \, it could\, for example:\n\n- Detect the `IntersectionObserver` polyfill \, query this dataset\, see the native API is Baseline\, and confidently r ecommend removing the polyfill.\n- See a use case for the `Scheduler` API\ , query the dataset\, and suggest a progressive enhancement strategy that safely encourages immediate adoption.\n\n**Goal(s):**\nThis session is a w orking discussion to brainstorm this dataset: what it should contain\, whe re it could live\, and how we can collaborate to build and maintain it to accelerate the entire web forward.\n\nAgenda\n\n**Materials:**\n- [Session proposal on GitHub](https://github.com/w3c/tpac2025-breakouts/issues/76) STATUS:CONFIRMED CREATED:20251028T131711Z LAST-MODIFIED:20260219T070840Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 5 - 505 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:54f3b095-120d-4d22-ba9d-b67631c29ef0 DTSTAMP:20260219T070929Z SUMMARY:Customizable select and combobox DTSTART;TZID=Asia/Tokyo:20251112T083000 DTEND;TZID=Asia/Tokyo:20251112T093000 DESCRIPTION:https://www.w3.org/events/meetings/54f3b095-120d-4d22-ba9d-b676 31c29ef0/\n\nThere are a number of followups for customizable select that I'd like to gauge interest in and get feedback on:\n- https://github.com/w hatwg/html/issues/8189\n- https://github.com/whatwg/html/issues/11477\n- h ttps://github.com/whatwg/html/issues/11535\n\nThere are also other proposa ls related to having a text filter for a select element\, as well as makin g `` more customizable:\n- https://github.c om/whatwg/html/issues/11288\n- https://github.com/openui/open-ui/issues/84 7\n- https://open-ui.org/components/combobox.explainer/\n- https://github. com/openui/open-ui/issues/1273\n\n**Goal(s):**\nCollect feedback on propos als\, gauge interest in proposals\, and collect additional use cases for c ustomizable select and combobox\n\nAgenda\n\nI don't have a detailed agend a besides the github issues I linked above\, and I think this could be an open-ended discussion.\n\n**Materials:**\n- [Session proposal on GitHub](h ttps://github.com/w3c/tpac2025-breakouts/issues/10) STATUS:CONFIRMED CREATED:20251028T073401Z LAST-MODIFIED:20260219T070929Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 4 - 406 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:d2246ce0-6843-4b18-9268-efb0134c939b DTSTAMP:20260219T071024Z SUMMARY:Digital Identity Wallet Project in Taiwan: Entering the Second Year DTSTART;TZID=Asia/Tokyo:20251112T083000 DTEND;TZID=Asia/Tokyo:20251112T093000 DESCRIPTION:https://www.w3.org/events/meetings/d2246ce0-6843-4b18-9268-efb0 134c939b/\n\nThe Ministry of Digital Affairs (moda) of Taiwan has develope d a Digital Identity Wallet infrastructure based on W3C standards for Dece ntralized Identifiers (DID) and Verifiable Credentials (VC)\, enabling an open and interoperable ecosystem: https://wallet.gov.tw/\n\nThis session w ill share our key achievements and learnings from the past year\, and high light related regional collaboration efforts.\n\n**Goal(s):**\nFor anyone contributing in the W3C DID and VC ecosystem\, we welcome any cooperation opportunities ranging from software interoperability\, DID/VC use cases\, and international standards development and collaboration initiatives.\n\n Agenda\n\n1. Achievements and Learnings\n2. Regional Efforts\n\n**Material s:**\n- [Session proposal on GitHub](https://github.com/w3c/tpac2025-break outs/issues/33) STATUS:CONFIRMED CREATED:20251028T073751Z LAST-MODIFIED:20260219T071024Z SEQUENCE:4 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 4 - 403 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:d0ca9f6b-12e1-4c8b-9ae1-4ba24c8cee10 DTSTAMP:20260219T071110Z SUMMARY:Ecma Beyond ECMAScript—Highlights from some of the other 55 Techn ical Committees (take two) DTSTART;TZID=Asia/Tokyo:20251112T083000 DTEND;TZID=Asia/Tokyo:20251112T093000 DESCRIPTION:https://www.w3.org/events/meetings/d0ca9f6b-12e1-4c8b-9ae1-4ba2 4c8cee10/\n\nEcma is a standards body responsible for far more than specif ying JavaScript™. There are currently 17⅔ active technical committees †\, and historically 56 total. Some of these technical committees focus on hardware\, acoustics\, the environment\, and even consumer safety. Clos er to W3C home\, work areas include programming languages (Dart\, C#\, Eif fel) and a variety of software-related topics ranging from supply chain se curity to Office Open XML formats. In this breakout session\, we’ll expl ore these together and dive a little deeper on whichever the attendees fin d most interesting.\n\nI proposed this breakout session last year but wasn 't able to gather the information I wanted to provide. This year I'll be a ble to show up with a deeper knowledge of history and\, after an introduct ion\, prompt participants for which topics they wish to further discuss.\n \n† The ⅔ will absolutely make sense\n\n**Goal(s):**\nProvide an overv iew of the breadth of Ecma work areas\, then discuss in depth the most rel evant to TPAC participants\n\nAgenda\n\nNo agenda\, I'll breeze through [t he slides](https://hosted.akiro.se/2025/tpac/Ecma-everything-else.pdf)\, a nswering questions as I go\, and then we'll talk about how Ecma can suppor t W3C\n\n**Materials:**\n- [Session proposal on GitHub](https://github.com /w3c/tpac2025-breakouts/issues/82) STATUS:CONFIRMED CREATED:20251028T131803Z LAST-MODIFIED:20260219T071110Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 4 - 405 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:9d36f30a-3f6f-4e82-b7b2-1c88546e57e5 DTSTAMP:20260219T071154Z SUMMARY:Email Verification Protocol DTSTART;TZID=Asia/Tokyo:20251112T083000 DTEND;TZID=Asia/Tokyo:20251112T093000 DESCRIPTION:https://www.w3.org/events/meetings/9d36f30a-3f6f-4e82-b7b2-1c88 546e57e5/\n\nVerifying control of an email address is a frequent activity on the web today and is used both to prove the user has provided a valid e mail address\, and as a means of authenticating the user when returning to an application.\n\nVerification is performed by either:\n\n- Sending the user a link they click on or a verification code. This requires the user t o switch from the application they are using to their email address and ha ving to wait for the email arrive\, and then perform the verification acti on. This friction often causes drop off in users completing the task. Ther e are privacy implications as the email transmission informs the mail serv ice the applications the user is using and when they used them.\n- The use r logs in with a social login provider such as Apple or Google that provid e a verified email address. This requires the application to have set up a relationship with each social provider\, and the user to be using one of those services and wanting to share the additional profile information tha t is also provided in the OpenID Connect flow.\n\nThe Email Verification P rotocol enables a web application to obtain a verified email address witho ut sending an email\, and without the user leaving the web page they are o n. To enable the functionality\, the mail domain delegates email verificat ion to an issuer that has authentication cookies for the user. When the us er provides an email to the HTML form field\, the browser calls the issuer passing authentication cookies\, the issuer returns a token\, which the b rowser verifies and updates and provides to the web application. The web a pplication then verifies the token and has a verified email address for th e user.\n\nUser privacy is enhanced as the issuer does not learn which web application is making the request as the request is mediated by the brows er.\n\nhttps://github.com/WICG/email-verification-protocol\n\n**Goal(s):** \nShare an early exploration and make an invitation to developers and brow ser engines to participate\n\nAgenda\n\n- Introduction to the Problem\n- I ntroduction to the Proposal\n- Open Discussion\n\n**Materials:**\n- [Sessi on proposal on GitHub](https://github.com/w3c/tpac2025-breakouts/issues/77 ) STATUS:CONFIRMED CREATED:20251028T131725Z LAST-MODIFIED:20260219T071154Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 5 - 504 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:2107ef50-86f2-47b9-9b4e-a36cf0e3015a DTSTAMP:20260219T071259Z SUMMARY:For Everyone: Towards a Sustainable Future for Independent Standard s Work DTSTART;TZID=Asia/Tokyo:20251112T083000 DTEND;TZID=Asia/Tokyo:20251112T093000 DESCRIPTION:https://www.w3.org/events/meetings/2107ef50-86f2-47b9-9b4e-a36c f0e3015a/\n\nThe bulk of today’s web platform design is done in-house at major browser vendors. This deprives the Web of vital **diversity of pers pective** and naturally favors work with visible short-term impact over th e **exploratory\, bigger picture R&D** needed to tackle deeper architectur al issues.\n\nFor most other web stakeholders\, the standards process rema ins an intimidating black box — so rife with misconceptions and barriers to entry that **spending millions on workarounds** can seem easier than f ixing shortcomings at the source.\n\nAnd for most other web standards desi gners\, it is a labor of love\, disincentivized by employers or as an unpa id side project.\nThe web platform is one of the most impactful products i n the world. \nShaping its evolution requires a rare combination of **deep \, broad\, and interdisciplinary expertise**. When the few who can do it w ell are driven away from it in order to make ends meet\, **the entire Web loses**.\n\nThese issues are intertwined. To make independent standards wo rk sustainable\, we need to **expand the pool of available funding** — a nd the only lasting way to do that is by helping more organizations see we b platform design as a path to solving their own problems.\n\n**Goal(s):** \nThis session aims to explore potential structures\, governance models\, and outreach strategies for a _new\, independent entity_ with the mission of addressing both issues. The goal of this new entity is **not to compet e with any existing organization**\, but to strengthen the entire ecosyste m by increasing awareness and abstracting the complexity of the standards process.\n\nAgenda\n\n**Materials:**\n- [Session proposal on GitHub](https ://github.com/w3c/tpac2025-breakouts/issues/63) STATUS:CONFIRMED CREATED:20251028T131532Z LAST-MODIFIED:20260219T071259Z SEQUENCE:4 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 4 - 402 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:96fd35c2-219d-4986-ba08-cc0de0871744 DTSTAMP:20260219T071438Z SUMMARY:Private Cross-Origin/Site Prefetch DTSTART;TZID=Asia/Tokyo:20251112T083000 DTEND;TZID=Asia/Tokyo:20251112T093000 DESCRIPTION:https://www.w3.org/events/meetings/96fd35c2-219d-4986-ba08-cc0d e0871744/\n\nPrefetching can significantly improve web performance by load ing resources before a user navigates to them\, but doing so across differ ent origins or sites can harm user privacy. Directly prefetching from a th ird-party server can leak a user's IP address and browsing context. \n\nTh e Prefetch spec states a need for IP anonymization and handwaves over how it’s achieved\, leaving it implementation-defined [[1](https://wicg.gith ub.io/nav-speculation/prefetch.html#create-navigation-params-by-fetching)] . Let’s look at a couple proposals of how this works in the browser\, wi th a browser-provided proxy [[2](https://developer.chrome.com/blog/private -prefetch-proxy)] and a proposal for website-provided proxies [[3](https:/ /github.com/WICG/nav-speculation/issues/368)].\n\nFinally\, we will discus s the path to enable private cross-origin/site prefetch across browsers. O pen discussion of privacy and security goals\, threat models\, and future work in implementation and standardization.\n\n**Goal(s):**\nDiscussion\n\ nAgenda\n\n1. Introduction\n2. Cross-origin/site prefetch\n3. Privacy-pres erving prefetch\n4. Future directions\n5. Discussion\n\n**Materials:**\n\n - [Slides](https://docs.google.com/presentation/d/1fBEJXtRe7qoJA5ISNYzAEE6 gRYiJ9lOhDu9hdRYlCxM/edit?usp=sharing)\n- [Session proposal on GitHub](htt ps://github.com/w3c/tpac2025-breakouts/issues/42) STATUS:CONFIRMED CREATED:20251028T073921Z LAST-MODIFIED:20260219T071438Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 4 - 404 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:f4cc8f18-a362-4f41-adaf-5088e5f38364 DTSTAMP:20260219T071554Z SUMMARY:Semantics for the Agentic Web DTSTART;TZID=Asia/Tokyo:20251112T083000 DTEND;TZID=Asia/Tokyo:20251112T093000 DESCRIPTION:https://www.w3.org/events/meetings/f4cc8f18-a362-4f41-adaf-5088 e5f38364/\n\nThe concept of an "agentic web\," where AI agents act on a us er's behalf\, is a growing topic of discussion. Currently\, these agents o ften rely on brittle inference\, parsing visual labels or class names to u nderstand a website's functionality. This model is fragile\; simple A/B te sts or site redesigns can break an agent\, leading to high task failure ra tes. Keeping in mind that for many tasks the acceptable failure rate is 0. This model can also be compute-expensive\, as many implementations resolv e ambiguities using a combination of DOM Tree and pixel scraping\, greatly limiting the performance of agents who might have resource constrained (i .e. on-device) models.\n\nFor human-facing assistive technologies\, ARIA c losed gaps in semantic HTML\, creating a more robust experience for users of AT. Now\, we face a similar question for machines.\n\nThis session is a general discussion to explore whether our existing semantic toolkit is su fficient for this potential use case.\n\n- Is ARIA\, which is designed for human accessibility\, the right tool to serve machine agents? An interes ting point of reference is [this FAQ from ChatGPT](https://help.openai.com /en/articles/12627856-publishers-and-developers-faq#h_30e9aae450) which st ates "ChatGPT Atlas uses ARIA tags—the same labels and roles that suppor t screen readers—to interpret page structure and interactive elements." \n- What happens when we conflate these two distinct purposes?\n- More imp ortantly\, are there semantic needs for agents that have no human-facing e quivalent?\n\nConsider hints that could improve agent reliability and safe ty\, such as:\n\n- Explicitly flagging a button as a destructive action (e .g.\, distinguishing "Archive" from "Delete Permanently").\n- Identifying page content as User-Generated Content (UGC) to allow agents to apply extr a safeguards.\n- Signaling transient states\, like logged-in vs. logged-ou t status\, to help an agent plan a task.\n\nThis session is not about a sp ecific proposal. It's about the core problem. Does ARIA already solve for all the hints a machine might need\, or should we be considering an additi onal semantic layer for machines at all?\n\nLet's come together to discuss the problem\, the risks of both action and inaction\, and the potential p aths forwards.\n\n**Goal(s):**\nTo collectively explore whether semantic H TML and ARIA is sufficient for AI agents or if a new\, machine-facing sema ntic layer is needed for a reliable agentic web.\n\nAgenda\n\n**Materials: **\n- [deck](https://docs.google.com/presentation/d/1GnFVx8J3j3ZYGGR-zd5P_ 3yP1DBvn5AyH4i4SgxMAoE/edit?slide=id.g3207132d5c2_0_70#slide=id.g3207132d5 c2_0_70)\n- [Session proposal on GitHub](https://github.com/w3c/tpac2025-b reakouts/issues/48) STATUS:CONFIRMED CREATED:20251028T131245Z LAST-MODIFIED:20260219T071554Z SEQUENCE:4 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 4 - 401 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:f7fcc7e0-49fc-4636-bd06-9f31babc0352 DTSTAMP:20260219T071654Z SUMMARY:Sustainable Web IG Update for the Web Sustainability Guidelines DTSTART;TZID=Asia/Tokyo:20251112T083000 DTEND;TZID=Asia/Tokyo:20251112T093000 DESCRIPTION:https://www.w3.org/events/meetings/f7fcc7e0-49fc-4636-bd06-9f31 babc0352/\n\nThe web is critical infrastructure\, but its environmental an d social impacts are growing: energy use\, e-waste\, and inefficiency at g lobal scale. W3C has championed accessibility and privacy as pillars of a trustworthy web—sustainability needs the same attention.\n\nThe Web Sust ainability Guidelines (WSG) Community Group initially drafted guidelines\, modeled on WCAG\, that offers practical\, testable steps for reducing the footprint of web technologies. Since then\, the Industry group has substa ntially revised this. We are now seeking a wide review. This breakout will share updates and solicit feedback about implementability\, organizationa l structure\, and adoption.\n\nKey discussion points:\n- How to incorporat e sustainability alongside accessibility and privacy\, performance\n- How to ensure testability / measure-ability and avoid greenwashing\n- Opportun ities to highlight integrations with other standards\n- Next steps: pilots \, adoption paths\, and potential W3C involvement\n\n[Slack](https://w3cco mmunity.slack.com/archives/C02JETQAQG4)\n\n**Goal(s):**\nSolicit feedback about implementability\, organizational structure\, and adoption of the WS G\n\nAgenda\n\n- Introductions\n- Review of recent updates in the WSG\n- A lignment with accessibility\, privacy\, and performance\n- Measure-ability \n- Next steps: pilots\, adoption paths\, and potential W3C involvement\n\ n**Materials:**\n- [Session proposal on GitHub](https://github.com/w3c/tpa c2025-breakouts/issues/17) STATUS:CONFIRMED CREATED:20251028T073508Z LAST-MODIFIED:20260219T071654Z SEQUENCE:4 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 3 - 302 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:ac6c0300-8b35-45a2-a7fc-0b361e6c0260 DTSTAMP:20260219T071852Z SUMMARY:WCAG2Mobile: presentation\, explanation\, feedback DTSTART;TZID=Asia/Tokyo:20251112T083000 DTEND;TZID=Asia/Tokyo:20251112T093000 DESCRIPTION:https://www.w3.org/events/meetings/ac6c0300-8b35-45a2-a7fc-0b36 1e6c0260/\n\nThe Mobile Accessibility Task Force (MATF) produces resources for how to apply the Web Content Accessibility Guidelines (WCAG) to mobil e\, and makes sure mobile apps are considered in new accessibility guideli nes.\n\nThe MATF has published its first [Group Draft Note of WCAG2Mobile] (https://www.w3.org/TR/wcag2mobile-22/) on 6 May 2025\, and is currently w orking towards an update of this draft.\n\nIn this TPAC session we want to present the document\, explain the challenges\, and gather feedback.\n\nL ink to presentation: [janjaap.com/tpac2025](https://janjaap.com/tpac2025)\ n\n**Goal(s):**\nGather feedback on applying WCAG to Mobile\n\nAgenda\n\n- Presentation\n- Explanation\n- Feedback\n\n**Materials:**\n- [Slides](htt ps://janjaap.com/tpac2025)\n- [Session proposal on GitHub](https://github. com/w3c/tpac2025-breakouts/issues/32) STATUS:CONFIRMED CREATED:20251028T073744Z LAST-MODIFIED:20260219T071852Z SEQUENCE:4 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 3 - 303 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:422ec06e-a24f-4471-810b-1bddd5911cec DTSTAMP:20260219T064347Z SUMMARY:A Foundation for a Decentralized User-centric Web Mapping : The Hyp er-Layering Architecture DTSTART;TZID=Asia/Tokyo:20251112T100000 DTEND;TZID=Asia/Tokyo:20251112T110000 DESCRIPTION:https://www.w3.org/events/meetings/422ec06e-a24f-4471-810b-1bdd d5911cec/\n\nThe World Wide Web is at a critical juncture\, facing increas ing centralization and the loss of its original decentralized philosophy. This breakout session will propose a new approach to web mapping that not only addresses the need for a modern\, interoperable map standard\, but al so serves as a model for shifting the entire Web's paradigm from centraliz ation back to a self-organizing\, user-centric model.\n\nWe will introduce the **[Hyper-Layering Architecture (HLA)](https://svgmap.org/movie/AC2024 /)**\, a philosophy that has been under development since 1996 and [submit ted to SVGWG in 2011](https://www.w3.org/submissions/2011/04/). Unlike tra ditional approaches that rely on a single\, centralized service or data fo rmat\, HLA leverages existing Web principles to enable a decentralized\, f lexible\, and powerful web mapping system. This session is in scope for a breakout as it addresses core web architectural principles (decentralizati on\, user control) described in the W3C's [Ethical Web Principles](https:/ /www.w3.org/TR/ethical-web-principles/) and [Vision for W3C](https://www.w 3.org/TR/w3c-vision/)\, and their application to a new\, native content ty pe (maps).\n\nWe understand and respect the work of the [Maps in HTML Comm unity Group](https://www.w3.org/community/maps4html/)\, with whom we have been in discussion for many years. However\, we also believe there remains a non-negligible philosophical gap between our two approaches.\n\n**Goal( s):**\nThe goal is to present the **Hyper-Layering Architecture (HLA)** as a philosophical foundation for a decentralized\, user-centric web. We aim to initiate a constructive dialogue on how we can align future web mappin g standards with the **W3C's Ethical Web Principles** and **Vision for W3C **. We also seek to explore potential collaboration points with the Maps i n HTML Community Group and other stakeholders to pave the way for a unifie d proposal that leverages existing web standards to their fullest potentia l.\n\nAgenda\n\n- Introduction to the Hyper-Layering Architecture (HLA) an d its philosophy.\n- Layers as Web Apps (LaWA): How can we integrate diver se data sources using existing Web technologies?\n- Leveraging and Extendi ng Existing Browser Standards: The Roles of svg and the map Tag\n- The phi losophical case for decentralization in web mapping and the broader Web.\n - Q&A and discussion on next steps.\n\n**Materials:**\n- [Slides](https:// svgmap.org/movie/TPAC2025/index_HLA_breakout.html)\n- [Session proposal on GitHub](https://github.com/w3c/tpac2025-breakouts/issues/14) STATUS:CONFIRMED CREATED:20251028T073441Z LAST-MODIFIED:20260219T064347Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 4 - 406 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:d5045a79-b5a2-4200-8eda-8465bd1d3863 DTSTAMP:20260219T070027Z SUMMARY:Accessibility Maturity Model Group Note Update DTSTART;TZID=Asia/Tokyo:20251112T100000 DTEND;TZID=Asia/Tokyo:20251112T110000 DESCRIPTION:https://www.w3.org/events/meetings/d5045a79-b5a2-4200-8eda-8465 bd1d3863/\n\nBrief overview of the Accessible Platform Architectures Acces sibility Maturity Model Group Note. We will give of condensed history of i ts inception\, what it means to you\, why it’s important\, how to use it \, and what our future plans are for further development.\n\n**Goal(s):**\ nUpdate the public on the accessibility Maturity Model Group Note\n\nAgend a\n\nDemystifying the Accessibility Maturity Model (what it is\, and what it does)\n\nWhy the Accessibility Maturity Model is important/needed (a br ief history of its inception)\n\nHow to use the Accessibility Maturity Mod el\n\nOutlining the future of the Accessibility Maturity Model (what are n ext steps are\, and what future versions may look like)\n\n**Materials:**\ n- [recording](https://www.w3.org/2025/11/breakouts/recording-88.html)\n- [Session proposal on GitHub](https://github.com/w3c/tpac2025-breakouts/iss ues/88) STATUS:CONFIRMED CREATED:20251106T144753Z LAST-MODIFIED:20260219T070027Z SEQUENCE:2 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 5 - 504 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:fb95b528-abb3-44cd-a0b5-7e67c084fced DTSTAMP:20260219T070113Z SUMMARY:Agentic Browsing and the Web's Security Model DTSTART;TZID=Asia/Tokyo:20251112T100000 DTEND;TZID=Asia/Tokyo:20251112T110000 DESCRIPTION:https://www.w3.org/events/meetings/fb95b528-abb3-44cd-a0b5-7e67 c084fced/\n\nVarious browser implementers have announced plans to ship age ntic browsing experiences\, i.e. AI-powered features that take action on w ebsites on the user's behalf. ([1](https://www.perplexity.ai/comet)\, [2]( https://brave.com/blog/leo-roadmap-2025-update/)\, [3](https://www.operane on.com/)\, [4](https://www.microsoft.com/en-us/edge/ai-powered/copilot-mod e)\, [5](https://blog.google/products/chrome/new-ai-features-for-chrome/)\ , [6](https://www.anthropic.com/news/claude-for-chrome)\, [7](https://deep mind.google/models/project-mariner/)\, etc.)\n\nThese exciting new capabil ities also come with new security challenges through the exposure of LLMs to untrusted web content and their ability to access the user's private in formation and take action on their behalf (a case of [lethal trifecta](htt ps://simonwillison.net/2025/Jun/16/the-lethal-trifecta/)).\n\nWe'll examin e how the new possibility of [prompt injected](https://en.wikipedia.org/wi ki/Prompt_injection) user agents impacts the Web's security model and disc uss how browser and agent implementers\, web developers and other ecosyste m participants can design a safe agentic browsing experience for the Web P latform.\n\n**Goal(s):**\nBrainstorming and knowledge sharing\n\nAgenda\n\ n**Materials:**\n- [Session proposal on GitHub](https://github.com/w3c/tpa c2025-breakouts/issues/25) STATUS:CONFIRMED CREATED:20251028T073644Z LAST-MODIFIED:20260219T070113Z SEQUENCE:5 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 4 - 401 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:aa294586-f779-466f-9066-7d73e4ea6c92 DTSTAMP:20260219T070203Z SUMMARY:CG Specification Communication Enhancements DTSTART;TZID=Asia/Tokyo:20251112T100000 DTEND;TZID=Asia/Tokyo:20251112T110000 DESCRIPTION:https://www.w3.org/events/meetings/aa294586-f779-466f-9066-7d73 e4ea6c92/\n\nOur [project to revamp the Community Group program](https://g ithub.com/w3c/cg-program?tab=readme-ov-file#revamp-started-in-2024) includ es improvements to communications about CG specifications. In this breakou t session we will discuss our current thinking about the [CG specification lifecycle](https://github.com/w3c/cg-program/blob/main/proposals/spec-lif ecycle.md).\n\nAn important part of improved communication includes cleare r representation of status information and greater stylistics distinctions between CG specifications and Rec-track deliverables. We will share mocku ps and invite feedback. \n\nWe will also demo tooling for helping editors gather data that will be used to convey status information in specificatio ns\, and discuss ideas for maintenance of that data.\n\n**Goal(s):**\nBuil d support for enhanced CG specification lifecycle and gather feedback on m ockups\n\nAgenda\n\n* Updates on CG spec lifecycle\n* Seek feedback on moc kups for CG specification changes\n* Anticipated approach for gathering da ta used to communicate specification circumstances\n* Planning for beta te st of new styles (implemented in bikeshed and respec).\n\nSee our [slides] (https://docs.google.com/presentation/d/1-96YXga4LLRDmWITdUnjjFtnRnftkS0Dk _yJKBeHBgA/edit?slide=id.p#slide=id.p)\n\n**Materials:**\n- [Session propo sal on GitHub](https://github.com/w3c/tpac2025-breakouts/issues/41) STATUS:CONFIRMED CREATED:20251028T073912Z LAST-MODIFIED:20260219T070203Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 4 - 404 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:c986882c-0da9-48d9-8eab-6313cde178ea DTSTAMP:20260219T070252Z SUMMARY:Dynamic Accessibility Remediation: A report from the Accessibility at the Edge Community Group DTSTART;TZID=Asia/Tokyo:20251112T100000 DTEND;TZID=Asia/Tokyo:20251112T110000 DESCRIPTION:https://www.w3.org/events/meetings/c986882c-0da9-48d9-8eab-6313 cde178ea/\n\nThe W3C Accessibility at the Edge Community Group is finalizi ng for imminent\nrelease it's final report addressing the trade-offs and b enefits of applying\ndynamic accessibility\nremediations to web content. T oday's typical web page is a complex blend\nof multiple original sources\, yielding experiences that work well for some\nusers but fail for others\, leaving many websites and online applications\ninaccessible to people wit h disabilities. In development since early 2023\, the\nreport titled: [Acc essibility Capabilities: Post-Source Code and Content](https://a11yedge.gi thub.io/capabilities/) features cross-references to WCAG throughout\, beca use WCAG remains the valid yardstick whether applied in-source or post-sou rce.\n\n**Goal(s):**\nBroaden understanding of when and how post-source ac cessibility remediations can be effective.\n\nAgenda\n\n**Materials:**\n- [recording](https://www.w3.org/2025/11/breakouts/recording-47.html)\n- [Se ssion proposal on GitHub](https://github.com/w3c/tpac2025-breakouts/issues /47) STATUS:CONFIRMED CREATED:20251028T131227Z LAST-MODIFIED:20260219T070252Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 4 - 402 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:f3f84f84-e1a0-49a6-97d8-6db2736ccd74 DTSTAMP:20260219T070423Z SUMMARY:Enabling Effective AC Participation DTSTART;TZID=Asia/Tokyo:20251112T100000 DTEND;TZID=Asia/Tokyo:20251112T110000 DESCRIPTION:https://www.w3.org/events/meetings/f3f84f84-e1a0-49a6-97d8-6db2 736ccd74/\n\nBrainstorm ways to improve the effectiveness of the AC\, as a community and in its role advising and overseeing W3C activities.\n\nThis session will target AC Reps in particular.\n\n**Goal(s):**\nCome up with concrete implementable ideas to improve the experience and effectiveness o f the AC.\n\nAgenda\n\n* Collect ideas for problems and solutions.\n* Disc uss which ones are most likely to help.\n* Come up with an implementation plan that we can execute.\n\n**Materials:**\n- [Session proposal on GitHub ](https://github.com/w3c/tpac2025-breakouts/issues/80) STATUS:CONFIRMED CREATED:20251028T131748Z LAST-MODIFIED:20260219T070423Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 5 - 505 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:bb7b1db2-920a-4ccd-844b-0805e4074b8c DTSTAMP:20260219T070514Z SUMMARY:Human Rights & Web Standards? DTSTART;TZID=Asia/Tokyo:20251112T100000 DTEND;TZID=Asia/Tokyo:20251112T110000 DESCRIPTION:https://www.w3.org/events/meetings/bb7b1db2-920a-4ccd-844b-0805 e4074b8c/\n\nAt the W3C’s Advisory Committee meeting in Hiroshima\, Japa n\, last year\, Mitsuo Ochi\, the president of Hiroshima University\, [cha llenged W3C](https://www.w3.org/2024/04/AC/talk/welcome-mitsuo-ochi.html#t alk) to “take proactive actions towards realizing a peaceful future.” \n\nTim Engelhardt from the UN Office of the High Commissioner of Human Ri ghts\, while acknowledging the reference to human rights in the Ethical We b Principles\, likewise [challenged W3C](https://www.w3.org/2024/04/AC/tal k/human-rights#talk) to put people and their rights at the center of proce sses\, saying “standard setting organizations and their participants\, s hould commit to the application of human rights\, using human rights metho dologies”.\n\nMore recently\, the UN OHCHR has run a series of workshops involving standards bodies\, one of which I did a write-up of here: https ://lists.w3.org/Archives/Member/w3c-archive/2025Jul/att-0280/Workshop_Repo rt__Advancing_Human_Rights-Aligned_Standard-Setting.pdf. \n\nWe have also discussed this topic in the Advisory Board.\n\n**Goal(s):**\nhave an open discussion\n\nAgenda\n\n**Materials:**\n- [Session proposal on GitHub](htt ps://github.com/w3c/tpac2025-breakouts/issues/43) STATUS:CONFIRMED CREATED:20251028T073931Z LAST-MODIFIED:20260219T070514Z SEQUENCE:4 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 4 - 403 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:dd3db797-f465-4cd7-9cd3-b045dde91c10 DTSTAMP:20260219T070618Z SUMMARY:Lighter weight standards processes by using a cross-translating PL to craft reference implementations DTSTART;TZID=Asia/Tokyo:20251112T100000 DTEND;TZID=Asia/Tokyo:20251112T110000 DESCRIPTION:https://www.w3.org/events/meetings/dd3db797-f465-4cd7-9cd3-b045 dde91c10/\n\nTemper is a programming language that translates to all the o ther languages and which aims to simplify standards development.\nThe goal of the tool is to make it easier for different language communities (data scientists/pythonistas\, web devs/javascripters\, backenders) to identify common problems and share solutions.\n\n[Slides](https://temperlang.githu b.io/tpac2025/Templates/Overview.html)\n\nWith it\, you can write a librar y once and get libraries in all the languages widely used in OSS software. (Traditional compiler methods based\, not AI)\n\nSome standards efforts have significant components that are not dependent on the stack:\n\n- L10N /I18N standards are about human languages and cultures\, not the tech stac k that is composing strings to present. Having ubiquitously available libr aries like ICU & grapheme clustering would be good.\n- Representations of currencies\n- How to derive "safe" HTML from untrusted HTML is not about t he tech stack.\n- Arithmetic about color\n- Parsing and unparsing URLs\n- How to encode and decode records received over the web\, validate\, and fi ll in missing info.\n\nPerhaps these or similar standards would benefit fr om providing a partial reference implementation\, data files\, and/or test suites to developers\, tool authors\, and horizontally to other W3C group s.\n\nFor standards driven mostly by non-software-engineer domain experts\ , the hope is that a tool like this might allow building reference impleme ntations for many programming language communities with a single engineeri ng point of contact lowering coordination overhead when changes to a stand ard are needed.\n\n**Goal(s):**\nExplore how to make the results of standa rds efforts easier to achieve and available to more developer communities via an emerging technology\, and gather requirements from attendees before they require breaking changes in the language\n\nAgenda\n\n- Demo the lan guage showing how a well-understood standard could have been developed alo ngside a reference implementation that cross-compiles to many languages\n- Open discussion on language changes that might make the tool fit well int o standards workers' workflow\n- Open discussion to identify legalese that would need to be addressed before the proposed tool could be relied upon\ n- Ideally\, identify one or more pilot project partners who are willing t o trial the project in their work\, or who might form an interest group ar ound guiding language development to be awesome for standards work\n\n**Ma terials:**\n- [Session proposal on GitHub](https://github.com/w3c/tpac2025 -breakouts/issues/6) STATUS:CONFIRMED CREATED:20251028T073346Z LAST-MODIFIED:20260219T070618Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 4 - 405 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:9363fa89-64f3-447c-80a7-c04409d60377 DTSTAMP:20260219T070721Z SUMMARY:Modular Web Engines DTSTART;TZID=Asia/Tokyo:20251112T100000 DTEND;TZID=Asia/Tokyo:20251112T110000 DESCRIPTION:https://www.w3.org/events/meetings/9363fa89-64f3-447c-80a7-c044 09d60377/\n\nBeyond pure web apps\, **WebViews** are essential for **cross -platform development**. Frameworks like Cordova\, React Native\, Electron \, Tauri\, and many others prove that. Other relevant use cases are: **Min iApps**\, whose SuperApps implement dedicated embedded web engines for con tent rendering\; EPUB readers\; and infotainment systems. These domain-spe cific use cases sometimes do not require a full-fledged WebView with a ful l implementation of Web standards. Indeed\, these platforms use hybrid tec hnologies that are inspired by Web standards (e.g.\, restricted CSS module s\, [HTML subsets](https://github.com/w3c/miniapp-components/blob/main/doc s/gap-analysis-elements.md)\, and JavaScript [APIs](https://github.com/w3c /miniapp-components/blob/main/docs/gap-analysis-api.md)). Occasionally non standard features are added and can create fragmentation.\n\nThis breakou t session aims to discuss the design and use of modular web engines\, cons idering the concrete constraints of the application scenario and the benef its for potential new use cases\, including the homogeneous implementation of cross-platform MiniApps\, **WoT** apps\, and **AI agents**. These hybr id platforms could benefit from these modular standards-based application profiles (i.e.\, subsets of current specifications) to reduce the size of engines\, thereby increasing efficiency while maintaining compatibility wi th existing standards. \n\nSome questions to be addressed during the sessi on:\n- How these modular Web engines support the growth of the Web without bringing fragmentation?\n- How do new web engines define their roadmap a nd development priorities?\n- Could the existing Web DevX tools (e.g.\, WP T\, CanIUse\, [CanIWebView](https://github.com/WebView-CG/Compatibility-Da ta-Project)\, Web-Features\, …) support the development of new engines f or these purposes?\n\n**Goal(s):**\nDiscussion on new requirements and W3C activities for the web ecosystem\n\nAgenda\n\n- Intro and background on t he challenge (Chairs)\n- Design of a new embedded engine (Bai Haili & Shen Jing\, Huawei)\n- Open questions and discussion\n\n**Materials:**\n- [sli des](https://espinr.github.io/talks/2025/1112-Modular-Web-Engines-TPAC/)\n - [Session proposal on GitHub](https://github.com/w3c/tpac2025-breakouts/i ssues/50) STATUS:CONFIRMED CREATED:20251028T131315Z LAST-MODIFIED:20260219T070721Z SEQUENCE:4 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 3 - 302 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:23cd1b88-624c-424f-adbf-355e41981015 DTSTAMP:20260219T063146Z SUMMARY:Convertible Devices Brainstorming DTSTART;TZID=Asia/Tokyo:20251112T111500 DTEND;TZID=Asia/Tokyo:20251112T121500 DESCRIPTION:https://www.w3.org/events/meetings/23cd1b88-624c-424f-adbf-355e 41981015/\n\nConvertible devices (Chromebooks\, Surfaces\, and tablets\, t o name a few) are devices that can switch from a touch-first mode into a m ore traditional desktop mode. Today\, they're not well represented in web standards: the [Form Factor client hint](https://developer.mozilla.org/en- US/docs/Web/HTTP/Reference/Headers/Sec-CH-UA-Form-Factors) neither include s it nor is there another way to query for it\, there's no listener event for form factor changes\, and key user experience flows that can change de pending on the form factor (like how `window.open` works) can't be queried for.\n\nI'd like for this to be a brainstorming session on the different items\, like mentioned above\, a developer may need to know and react to f or a convertible device to provide users a better experience on those devi ces.\n\n**Goal(s):**\nCreate a list of proposed feature gaps\, and potenti al solutions\, for convertible devices to bring back to relevant working a nd community groups.\n\nAgenda\n\n* Introduction to the Problem Space (wha t are convertibles\, what unique challenges do they face)\n* Currently ide ntified problems (`window.open` differences\, lack of clear Form Factor c lient hint?) with discussion\n* Open forum for problems identified by part icipants\, with initial brainstorming for fixes to bring back to other com mittees.\n\n**Materials:**\n- [Session proposal on GitHub](https://github. com/w3c/tpac2025-breakouts/issues/39) STATUS:CONFIRMED CREATED:20251028T073852Z LAST-MODIFIED:20260219T063146Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 5 - 504 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:aaf35157-20e5-47f8-91a7-2db38aeb3cfc DTSTAMP:20260219T063242Z SUMMARY:Design and Implementation of the Agent Network Protocol (ANP) DTSTART;TZID=Asia/Tokyo:20251112T111500 DTEND;TZID=Asia/Tokyo:20251112T121500 DESCRIPTION:https://www.w3.org/events/meetings/aaf35157-20e5-47f8-91a7-2db3 8aeb3cfc/\n\nThe Agent Network Protocol (ANP) is an open-source communicat ion protocol for AI Agents\, aiming to become the “HTTP of the Agentic W eb era.” Its ultimate vision is to build an efficient\, secure\, and ope n network for agent collaboration. ANP seeks to break down data and agent silos by adopting open\, interoperable standards that enable cross-platfor m identity authentication\, discovery\, and interaction between agents.\n\ nBuilt upon W3C standards such as DID (Decentralized Identifiers)\, Verifi able Credentials\, and JSON-LD\, ANP defines how agents publish their iden tities\, describe their capabilities\, and establish secure communication channels for data exchange and task collaboration.\n\nThis session will in troduce the core design principles of ANP and explain how it differs from emerging protocols such as A2A (Google) and MCP (Anthropic).\n\nANP Open S ource Repository:\nhttps://github.com/agent-network-protocol/AgentNetworkP rotocol\n\n**Goal(s):**\nIntroduction to the Design and Implementation of the ANP Protocol\n\nAgenda\n\n* Introduce our perspective on the Agentic W eb and explain why protocols are essential to its development.\n* Present the architecture\, design\, and implementation of the ANP.\n* Explain the differences between ANP\, MCP\, and A2A.\n* Introduce the agent network we are building — a developing network of interconnected agents.\n\n**Mate rials:**\n- [Session proposal on GitHub](https://github.com/w3c/tpac2025-b reakouts/issues/34) STATUS:CONFIRMED CREATED:20251028T073802Z LAST-MODIFIED:20260219T063242Z SEQUENCE:4 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 4 - 403 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:679c6e5a-f288-4a9b-8887-9d9af4d8b8ad DTSTAMP:20260219T063406Z SUMMARY:Future of the Open Web DTSTART;TZID=Asia/Tokyo:20251112T111500 DTEND;TZID=Asia/Tokyo:20251112T121500 DESCRIPTION:https://www.w3.org/events/meetings/679c6e5a-f288-4a9b-8887-9d9a f4d8b8ad/\n\nThe phrase “Open Web” has served as a rallying cry for th ose who champion the benefits of the Web as we know it to humanity. Howeve r\, there are subtle (and not-so-subtle) distinctions in what it means dep ending on who you talk to: some believe it to be a Web where all content i s available no matter the purpose\; others focus on “Open Web” in rela tion to the advertising market\; yet others distinguish between open to hu mans-using-browsers vs. other clients.\n\nAt the same time\, large parts o f the Web have always been behind logins and paywalls: the so-called “de ep Web”. Furthermore\, it’s important to acknowledge that the reason t hat many parts of the Web have been free to access because they are advert ising-supported – along with all of the concurrent privacy harms.\n\nWhi le there may not be strong agreement on what the Open Web is\, it’s wide ly held that it is under more threat than ever\, thanks to the emergence o f AI. Content authors\, publishers\, and hosters may have been accepting o f the bargain they got from search crawlers: let us access your content an d you will get traffic from search results. They are much more reticent ab out exposing their content when it has no such quid pro quo.\n\nAs a resul t\, blocking unknown or unwanted crawlers has become more common\, and the Web Bot Auth effort is in the process of being chartered to enable known bots to cryptographically authenticate themselves – with the implication that those clients that don’t may be blocked. There are also proposals emerging for payment protocols specifically targeted at not only crawlers\ , but also bots and agents – and maybe even for browser micropayments.\n \nThere are also emerging concerns that AI will put gatekeeper platforms i n the position to drive further concentration: to pressure publishers to s ubmit content to them directly rather than taking on the cost of hosting c ontent themselves\, thereby further foreclosing what was previously open c ontent. \n\nThese changes have led to questions about the future of the O pen Web – whether we’ll have one\, and what it will look like. A less open Web is one where it is more difficult to introduce new non-browser ag ents or run services that don’t have immediate financial advantage for s ites. One where more data is locked up indiscriminately.\n\nThis session w ill explore questions in this area\, such as:\n\n* Is there a useful defin ition for the “Open Web”? Or is it better to have more specific goals? \n* Are there useful metrics for the Open Web that can be tracked?\n* What purposes do sites have for not being open?\n* Is there more than one econ omic model that promotes the Open Web?\n* How is privileged access for sea rch engine crawlers changing?\n* What impacts on the Open Web do we see fr om AI and “agentic” clients?\n* Are there best practices for sites and services that could help mitigate those impacts?\n* Are there standards a ctivities that could help mitigate those impacts?\n\nFor notes from both m eetings\, see:\n https://docs.google.com/document/d/1WaXDfwPP6olY-UVQxDZK NkUyqvmHt-u4kREJW4ys6ms/edit?usp=sharing\n\n**Goal(s):**\nDiscussion and p lanning\n\nAgenda\n\n**Materials:**\n- [Session proposal on GitHub](https: //github.com/w3c/tpac2025-breakouts/issues/37) STATUS:CONFIRMED CREATED:20251028T073835Z LAST-MODIFIED:20260219T063406Z SEQUENCE:4 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 4 - 401 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:22b75ecd-a861-4818-8eb5-1c40cba52c13 DTSTAMP:20260219T063508Z SUMMARY:Geolocation and Privacy DTSTART;TZID=Asia/Tokyo:20251112T111500 DTEND;TZID=Asia/Tokyo:20251112T121500 DESCRIPTION:https://www.w3.org/events/meetings/22b75ecd-a861-4818-8eb5-1c40 cba52c13/\n\nA discussion on geolocation and privacy.\n\n[Approximate Geol ocation](https://github.com/explainers-by-googlers/approximate-geolocation /blob/main/README.md) proposes to give sites the ability to request obfusc ated position estimates. Obfuscation protects user privacy by making it mo re difficult for sites to recover the user's true location. We'll review I ETF GEOPRIV recommendations for location obfuscation and discuss how obfus cation was implemented for Mozilla's Geode add-on.\n\nWe'll recap the hist ory of geolocation on the web platform. What were the influences that resu lted in Geolocation API's privacy model? How did the Geofencing and Geoloc ation Sensor proposals approach location privacy? How do current proposals address privacy concerns?\n\nOpen discussion on the future of location pr ivacy on the web.\n\n**Goal(s):**\nReview geolocation privacy consideratio ns\, feedback on current proposals\n\nAgenda\n\n**Materials:**\n- [Session proposal on GitHub](https://github.com/w3c/tpac2025-breakouts/issues/29) STATUS:CONFIRMED CREATED:20251028T073721Z LAST-MODIFIED:20260219T063508Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 5 - 505 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:eb45163d-e184-4ace-b7e3-900816a75c36 DTSTAMP:20260219T063600Z SUMMARY:Introducing the Cybernetic Avatar Community Group: Extending Human Presence through the Internet DTSTART;TZID=Asia/Tokyo:20251112T111500 DTEND;TZID=Asia/Tokyo:20251112T121500 DESCRIPTION:https://www.w3.org/events/meetings/eb45163d-e184-4ace-b7e3-9008 16a75c36/\n\nThe Cybernetic Avatar is a concept of a networked embodiment that digitally extends and transmits human physical\, perceptual\, and cog nitive capabilities through the Internet.\n\nIt envisions a world where pe ople can project their presence\, perception\, and action beyond the limit s of body\, space\, and time by connecting to digital or robotic embodimen ts.\nThis breakout session will share the current vision and motivation be hind the emerging Cybernetic Avatar Community Group (currently in formatio n).\n\nWe aim to discuss how the concept of the Cybernetic Avatar could re late to existing or future Web standards\, and how the W3C community might help define its role within the broader Internet ecosystem.\nTogether\, w e will consider how human embodiment\, communication\, and agency may evol ve through connected systems\, and how open\, ethical\, and inclusive fram eworks could support this transformation.\n\nWe are currently in the proce ss of forming the Cybernetic Avatar Community Group\, and this session ser ves as an open discussion for anyone interested — please join us!\n(The introductory video for the Cybernetic Avatar initiative is available here. - https://www.youtube.com/watch?v=u0NjMfUod10)\n\n**Goal(s):**\nIntroduct ion and discussion\n\nAgenda\n\n- Introduction to the Cybernetic Avatar co ncept and vision\n- Sharing background and current initiatives\n- Open dis cussion on potential relevance to the Web and Internet ecosystems\n\n**Mat erials:**\n- [Session proposal on GitHub](https://github.com/w3c/tpac2025- breakouts/issues/49) STATUS:CONFIRMED CREATED:20251028T131300Z LAST-MODIFIED:20260219T063600Z SEQUENCE:4 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 3 - 302 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:560c3a5b-494c-4364-b65e-d92e5805e70c DTSTAMP:20260219T063711Z SUMMARY:Low-level RTC Transport API DTSTART;TZID=Asia/Tokyo:20251112T111500 DTEND;TZID=Asia/Tokyo:20251112T121500 DESCRIPTION:https://www.w3.org/events/meetings/560c3a5b-494c-4364-b65e-d92e 5805e70c/\n\nThe [WebRTC APIs](https://www.w3.org/TR/webrtc/) have long en abled sending and receiving realtime media peer-to-peer with a streamlined control interface\, but with limited ability to tune how media is encoded and interacts with the network. While APIs such as [WebCodecs](https://w3 c.github.io/webcodecs/) have begun to allow users low-level access to the browser's built-in encoders and decoders\, there is still no API to allow similar levels of access to the low-latency peer-to-peer network transport s like those used within an RTCPeerConnection.\n\nThe RtcTransport API aim s to enable applications to directly utilize peer-to-peer datagram based t ransport for realtime media\, controlling the details of congestion contro l and allowing arbitrary media encodings and formats. The current proposal is an evolution of the RTP-focussed transport discussed in a breakout ses sion at TPAC 2024.\n\n**Goal(s):**\nTo describe the goals of the RtcTransp ort API\, and to solicit feedback on developer needs and use cases.\n\nAge nda\n\n1. Introduction to the RtcTransport API\n2. Use cases\n3. Developer feedback\n\n**Materials:**\n- [Session proposal on GitHub](https://github .com/w3c/tpac2025-breakouts/issues/15) STATUS:CONFIRMED CREATED:20251028T073450Z LAST-MODIFIED:20260219T063711Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 4 - 404 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:202a8c77-ba79-42d9-8c60-33b10544a227 DTSTAMP:20260219T063932Z SUMMARY:Mitigate Threats for Digital Credentials API: Episode III - Revenge of the Wallet DTSTART;TZID=Asia/Tokyo:20251112T111500 DTEND;TZID=Asia/Tokyo:20251112T121500 DESCRIPTION:https://www.w3.org/events/meetings/202a8c77-ba79-42d9-8c60-33b1 0544a227/\n\nIn the [first episode](https://github.com/w3c/tpac2024-breako uts/issues/98) we focused on high-level threats related to the [Formal Obj ection received for the addition of the Digital Credentials API](https://l ists.w3.org/Archives/Public/public-review-comments/2024Sep/0017.html).\n\n In the [second episode](https://github.com/w3c/breakouts-day-2025/issues/1 7)\, we discussed the presentation side\, in particular how Digital Creden tials API can differentiate between different presentation approaches (e.g .\, custom schemes and QR Codes).\n\nIn this third episode\, we will discu ss the new layered heart model in the presentation\, and on how to derive the security consideration sections\, then we'll prioritize threats - e.g. \, of [Malicious Wallets during issuance](https://github.com/w3c-fedid/dig ital-credentials/issues/382) or others - to propose mitigations.\n\n**Goal (s):**\nDC API Security Consideration Section / Mitigation\n\nAgenda\n\n** Materials:**\n- [Session proposal on GitHub](https://github.com/w3c/tpac20 25-breakouts/issues/45) STATUS:CONFIRMED CREATED:20251028T131206Z LAST-MODIFIED:20260219T063932Z SEQUENCE:4 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 3 - 303 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:140f2455-7351-4ea9-a71d-023ad26dccfc DTSTAMP:20260219T063046Z SUMMARY:WCAG 3 update DTSTART;TZID=Asia/Tokyo:20251112T111500 DTEND;TZID=Asia/Tokyo:20251112T121500 DESCRIPTION:https://www.w3.org/events/meetings/140f2455-7351-4ea9-a71d-023a d26dccfc/\n\nThis session will provide an update on the approach and progr ess for the W3C Accessibility Guidelines (WCAG) 3.\n\nW3C Accessibility Gu idelines (WCAG) 3.0 is a successor to [Web Content Accessibility Guideline s 2.2](https://www.w3.org/TR/wcag-3.0-explainer/#bib-wcag22) and previous versions. Changing technology and changing needs of people with disabiliti es require a new model to address content accessibility more comprehensive ly.\n\nWCAG 3.0 will use a model that allows it to:\n\n* address more disa bility needs than WCAG 2\,\n* incorporate publishing requirements and emer ging technologies such as web XR (augmented\, virtual\, and mixed reality) and voice input\,\n* facilitate maintenance\, so that the new model will be more enduring over time as technologies evolve\, and\n* include additio nal information about the ways web technologies need to work with authorin g tools\, user agents\, and assistive technologies.\n\n**Goal(s):**\nUpdat e attendees on the progress of the work on WCAG 3\n\nAgenda\n\n**Materials :**\n- [Session proposal on GitHub](https://github.com/w3c/tpac2025-breako uts/issues/54) STATUS:CONFIRMED CREATED:20251028T131351Z LAST-MODIFIED:20260219T063046Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 4 - 402 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:44573c5b-3bdd-488f-9c61-5c0d240da1b6 DTSTAMP:20260219T064128Z SUMMARY:WinterTC DTSTART;TZID=Asia/Tokyo:20251112T111500 DTEND;TZID=Asia/Tokyo:20251112T121500 DESCRIPTION:https://www.w3.org/events/meetings/44573c5b-3bdd-488f-9c61-5c0d 240da1b6/\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\ nWinterTC is a new Ecma Technical Committee focused on the needs of such r untimes\, particularly in the server side. This TC is an evolution of the previous WinterCG W3C Community Group\, to focus on standardizing a minimu m subset of the web platform APIs that all such runtimes would support (th e WinterTC [Minimum Common API](https://min-common-api.proposal.wintertc.o rg)).\n\nAside from publishing its own standards\, however\, WinterTC also aims to propose changes to existing W3C and WHATWG standards to better su pport the needs of server-side runtimes. For example\, in browsers\, origi ns are a fundamental security primitive\, and it makes sense that\, for ex ample\, the `fetch()` API has cross-origin restrictions. But since server- side runtimes don't have this security primitive\, these restrictions are unnecessary in such environments\, which is why they all willingly violate the spec. WinterTC aims to fix this in the web standards by adding confor mance modes for server-side runtimes.\n\n**Goal(s):**\nExplore the collabo ration between W3C/WHATWG and WinterTC\, including adding support in W3C/W HATWG specs for the needs of server-side runtimes.\n\nAgenda: https://peop le.igalia.com/abotella/pub/TPAC-2025-WinterTC/\n\nAgenda\n\n**Materials:** \n- [recording](https://www.w3.org/2025/11/breakouts/recording-72.html)\n- [Session proposal on GitHub](https://github.com/w3c/tpac2025-breakouts/is sues/72) STATUS:CONFIRMED CREATED:20251028T131631Z LAST-MODIFIED:20260219T064128Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 4 - 406 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:eb2ae838-ab05-41ca-9c41-58e60b07c3cd DTSTAMP:20251126T130642Z SUMMARY:Advisory Committee & Community Session DTSTART;TZID=Asia/Tokyo:20251112T133000 DTEND;TZID=Asia/Tokyo:20251112T143000 DESCRIPTION:https://www.w3.org/events/meetings/eb2ae838-ab05-41ca-9c41-58e6 0b07c3cd/\n\n\n\nAgenda\n\n* 13:30: Introduction\, remembering Gregg Kello gg - Seth Dobbs ([slide](https://docs.google.com/presentation/d/e/2PACX-1v Tpvd8aIctzZfjhtHKCUTtZjEiQBrRkphqpOKrDMrhvCLOwhH_b8vVSxXk1fanMRGUqQmCysINi ghR1/pub?start=false&loop=false&delayms=3000#slide=id.g39ba4d8a8af_0_1))\n * 13:30 - 13:35: Process 2025 - François Daoust\, Director\, Project & Pr ocess W3C ([slides](https://www.w3.org/2025/Talks/TPAC/fd-ac-process/)\, [ video](https://www.w3.org/2025/11/TPAC/ac-session/fd-ac-process))\n* 13:35 - 13:45: Technical Strategy Initiative Task force - Philippe Le Hégaret\ , VP\, Technical Strategy ([slides](https://www.w3.org/2025/Talks/TPAC/tec hnology-strategy/)\, [video](https://www.w3.org/2025/11/TPAC/ac-session/te chnology-strategy#intro))\n* 13:45 - 13:55: Update from October Age-restri ction Workshop - Tara Whalen\, Principal Privacy Specialist ([slides](http s://www.w3.org/2025/Talks/TPAC/tw-age-workshop/)\, [video](https://www.w3. org/2025/11/TPAC/ac-session/tw-age-workshop#intro))\n* 13:55 - 14:05: Acce ssibility Updates - Shawn Lawton Henry\, Director\, Web Accessibility Init iative (WAI) ([slides](https://www.w3.org/2025/Talks/TPAC/ac-wai-update/)\ , [video](https://www.w3.org/2025/11/TPAC/ac-session/ac-wai-update#intro)) & Kevin White\, Senior Principal Accessibility Specialist ([slides](https ://www.w3.org/2025/Talks/TPAC/ac-wai-update/)\, [video](https://www.w3.org /2025/11/TPAC/ac-session/ac-wai-update-kevin#intro))\n* 14:05 - 14:15: Int ernationalization - Fuqiao Xue\, Senior Principal Internationlization Spec ialist ([slides](https://www.w3.org/2025/Talks/TPAC/xfq-i18n/)\, [video](h ttps://www.w3.org/2025/11/TPAC/ac-session/xfq-i18n#intro))\n* 14:15 - 14:2 5: Web & AI in W3C - Roy Ran\, Principal Accessibility Specialist ([slides ](https://www.w3.org/People/Roy/Talks/TPAC-2025/Web-AI/)\, [video](https:/ /www.w3.org/2025/11/TPAC/ac-session/ran-ai#intro))\n* 14:25 - 14:30: Q&A ( [video](https://www.w3.org/2025/11/TPAC/ac-session/dobbs-closing#intro)) STATUS:CONFIRMED CREATED:20250902T151335Z LAST-MODIFIED:20251126T130642Z 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=Advisory Committee :mailto:w3c-ac-members@w3.org LOCATION:301 International Conference Room CATEGORIES:TPAC 2025 END:VEVENT BEGIN:VEVENT UID:60052a7f-8289-4018-845c-9b752187ac23 DTSTAMP:20260219T061658Z SUMMARY:Age-Based Restrictions Have Come for the Web DTSTART;TZID=Asia/Tokyo:20251112T144500 DTEND;TZID=Asia/Tokyo:20251112T154500 DESCRIPTION:https://www.w3.org/events/meetings/60052a7f-8289-4018-845c-9b75 2187ac23/\n\nMany jurisdictions have enacted (or are currently enacting) r egulations on age-based restrictions to online content. These regulations\ , and their requirements\, can have significant effects on technical archi tectures and end users. This is a complicated technopolicy issue that is m oving fast–although the policy debates indicate a lack of understanding about available technologies\, their capabilities and their limitations. T his breakout seeks to bring together people with interest and insights abo ut this problem\, in the hopes of advancing the discussion in a positive d irection. The recent [IAB/W3C workshop](https://datatracker.ietf.org/group /agews/about/) provides a starting point\, and will be used to shape the d iscussion. However\, it is clear that more work needs to be done to develo p\, explore\, and analyze different technical approaches to this problem s pace. Please join us to learn and help identify better solutions in this s pace.\n\n**Goal(s):**\nDevelop a shared understanding of age-based content restriction considerations\; Deepen insights into technological solutions (e.g.\, zero-knowledge proofs\, device-enforcement): their capabilities\, limitations\, deployment considerations\, etc\; Identify standards work –if any–for addressing these issues\n\nAgenda\n\n* Debrief from IAB/W3 C workshop (5 min)\n* Brainstorming (45 min)\n* Next steps (5 min)\n\n**Ma terials:**\n- [Session proposal on GitHub](https://github.com/w3c/tpac2025 -breakouts/issues/75) STATUS:CONFIRMED CREATED:20251028T131659Z LAST-MODIFIED:20260219T061658Z SEQUENCE:4 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 4 - 402 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:b85c36d0-322f-440d-bed5-061a413fc189 DTSTAMP:20260219T061600Z SUMMARY:AI Agents and The Web DTSTART;TZID=Asia/Tokyo:20251112T144500 DTEND;TZID=Asia/Tokyo:20251112T154500 DESCRIPTION:https://www.w3.org/events/meetings/b85c36d0-322f-440d-bed5-061a 413fc189/\n\nThis breakout session will explore the intersection of Artifi cial Intelligence (AI) Agents and Web in W3C\, focusing on whether and how browsers should evolve to support AI-driven applications\, computation\, and agent interactions.\nThe discussion will cover the ongoing work within the WebML WG/CG\, emerging AI-related APIs\, and the potential role of br owsers as intelligent execution and interaction platforms in the age of la rge language models (LLMs) and AI agents.\n\n**Goal(s):**\nThe goal is to identify gaps\, opportunities\, and potential areas for coordination acros s W3C groups\, including whether this work could be explored in the future Web & AI Interest Group from related Community Groups\, Working Groups.\n \nThis session also seeks community input to inform the scope and focus a reas of the forthcoming [AI Agents & the Web workshop](https://github.com/ w3c/strategy/issues/507).\n\nAgenda\n\n1. AI Agents Impact on the Web\n2. Web ML WG/CG work in W3C \n3. Browser as AI Agent hosts\n4. Open discussio n and Q&A\n\n**Materials:**\n- [Session proposal on GitHub](https://github .com/w3c/tpac2025-breakouts/issues/68) STATUS:CONFIRMED CREATED:20251028T131604Z LAST-MODIFIED:20260219T061600Z SEQUENCE:4 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 4 - 401 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:b6079f86-83e0-4889-a180-c78ecd696457 DTSTAMP:20260219T061741Z SUMMARY:Declarative Partial Updates - Customizing navigation experience DTSTART;TZID=Asia/Tokyo:20251112T144500 DTEND;TZID=Asia/Tokyo:20251112T154500 DESCRIPTION:https://www.w3.org/events/meetings/b6079f86-83e0-4889-a180-c78e cd696457/\n\nCustomizing the navigation experience\, whether same-document or cross-document\, is a theme that is associated with many web features\ , especially newer ones like view transitions.\n\nSeveral new features tha t are being worked on address this theme directly\, by making more parts o f the navigation experience declarative. \n \n- Declaratively streaming HT ML\n- Respond to document URL changes & navigations directly in CSS\n- Bet ter support for navigational gestures\n- Two-phase view transitions\n\nPar ticipants will receive an overview of the use cases\, motivations\, plans and challenges behind working on this theme\, some shallow dive into each of the features\, and opportunities for follow up.\n\n**Goal(s):**\nRaise awareness for the different features and their motivation\n\nAgenda\n\n**M aterials:**\n- [recording](https://www.w3.org/2025/11/breakouts/recording- 66.html)\n- [Session proposal on GitHub](https://github.com/w3c/tpac2025-b reakouts/issues/66) STATUS:CONFIRMED CREATED:20251028T131546Z LAST-MODIFIED:20260219T061741Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 5 - 504 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:4313e40c-2ac1-4bfd-869d-16ac4e003e01 DTSTAMP:20260219T062005Z SUMMARY:Effective and trustworthy conformance evaluation for WCAG and beyon d DTSTART;TZID=Asia/Tokyo:20251112T144500 DTEND;TZID=Asia/Tokyo:20251112T154500 DESCRIPTION:https://www.w3.org/events/meetings/4313e40c-2ac1-4bfd-869d-16ac 4e003e01/\n\n[WCAG-EM](https://www.w3.org/TR/WCAG-EM/) is a process for de ciding whether a website conform to [WCAG](https://www.w3.org/TR/WCAG22/)\ , the Web Content Accessibility Guidelines\, even if that website is very large. It is currently being updated (to [WCAG-EM 2](https://w3c.github.io /wai-wcag-em/). In this breakout\, I'd like to:\n\n- give an overview of w hat we're updating and solicit feedback \n- get input on making evaluation more effective\n- get input on making evaluation more trustworthy\n\n**Go al(s):**\nShare what's happening\, solicit feedback\n\nAgenda\n\n- give an overview of what we're updating and solicit feedback \n- how can we make evaluation more effective\n- how can we make evaluation more trustworthy\n \n**Materials:**\n- [Slides](https://hidde.github.io/b6-logius/20251111-tp ac-wcag-em/)\n- [Slack: agwg-wcag-em](https://w3ccommunity.slack.com/archi ves/C08LDGQ16CD)\n- [Session proposal on GitHub](https://github.com/w3c/tp ac2025-breakouts/issues/28) STATUS:CONFIRMED CREATED:20251028T073712Z LAST-MODIFIED:20260219T062005Z SEQUENCE:4 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 5 - 505 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:95dfd03b-88fc-4e5d-9afa-24ec28ba02cd DTSTAMP:20260219T062121Z SUMMARY:Originator Profile Overview and further discussions DTSTART;TZID=Asia/Tokyo:20251112T144500 DTEND;TZID=Asia/Tokyo:20251112T154500 DESCRIPTION:https://www.w3.org/events/meetings/95dfd03b-88fc-4e5d-9afa-24ec 28ba02cd/\n\nOriginator Profile (OP) has published its technical specifica tions\, architecture overview\, and Originator Profile Blueprints series d ocuments. Join us to see how the current version works and discuss how we manage and operate this framework to combat the flood of malicious informa tion on the internet. Please come and provide feedback or discuss with us. \nWe would also like to introduce the progress of implementing the framewo rk to the Japanese media industry and local governments.\n\n**Goal(s):**\n Provides an overview of the Originator Profile framework and gets feedback from the community.\n\nAgenda\n\n1. Originator Profile overview\n2. OP do cuments + α\n - Specifications: Architectural Overview\, OP blueprints ( GitHub access now available)\n - PoC Code via GitHub\n - CA Server for e xperimental use\n3. OP’s latest progress\n - Heated discussion over inf ormation uncertainty\n - PoC – Implement OP to content management syste ms of news media\n - PoC – Confirm that ad creatives with OP can be dis tributed in actual advertising auction systems.\n - Implement on Tottori local government’s website\n4. Next step\n5. Q & A\n\n[Originator Profil e Overview and further discussions_GH (2).pdf](https://github.com/user-att achments/files/23492500/Originator.Profile.Overview.and.further.discussion s_GH.2.pdf)\n\n**Materials:**\n- [recording](https://www.w3.org/2025/11/br eakouts/recording-31.html)\n- [Session proposal on GitHub](https://github. com/w3c/tpac2025-breakouts/issues/31) STATUS:CONFIRMED CREATED:20251028T073736Z LAST-MODIFIED:20260219T062121Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 4 - 405 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:73116de7-09aa-4396-b4c0-4f7b73895abc DTSTAMP:20260219T062215Z SUMMARY:Tell Us What's Wrong with the Process DTSTART;TZID=Asia/Tokyo:20251112T144500 DTEND;TZID=Asia/Tokyo:20251112T154500 DESCRIPTION:https://www.w3.org/events/meetings/73116de7-09aa-4396-b4c0-4f7b 73895abc/\n\nThis session is an opportunity to engage with the AB to discu ss frictions and difficulties that may exist within the current Process d ocument and engage in a conversation about potential changes.\n\n**Goal(s) :**\nFeedback on the W3C Process\n\nAgenda\n\nThis is a feedback session f or the AB to hear from the W3C Membership. \n\nIn addition to frank feedba ck about the Process\, we will focus conversation on the following questio ns:\n - "How would you improve the W3C standards process?”\n - “What are your priorities for improving the W3C Process?”\n - “Are there s tandardization processes of other orgs W3C could learn from?”\n\n**Mater ials:**\n- [Session proposal on GitHub](https://github.com/w3c/tpac2025-br eakouts/issues/13) STATUS:CONFIRMED CREATED:20251028T073428Z LAST-MODIFIED:20260219T062215Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 3 - 303 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:17df0a07-99d8-4d4d-be2b-3e94c90c3ddf DTSTAMP:20260219T062305Z SUMMARY:W3C Threat Modeling Guide and the Threat Model for the Web DTSTART;TZID=Asia/Tokyo:20251112T144500 DTEND;TZID=Asia/Tokyo:20251112T154500 DESCRIPTION:https://www.w3.org/events/meetings/17df0a07-99d8-4d4d-be2b-3e94 c90c3ddf/\n\nAs required by the Security and Privacy Questionnaire for the Horizontal Review\, when writing security consideration sections that ref erence RFC 3552\, a threat model must be created and the specific elements exported to the Security Consideration sections (but this also applies to privacy\, and in general to harms as well).\nBut how can threat modeling be done in a structured way in practice?\n\nThe Threat Modeling Guide answ ers this question in a practical way and includes a Threat Model for the W eb to speed up the work.\n\n**Goal(s):**\nThe idea is to present the guide and gather feedback.\n\nAgenda\n\n**Materials:**\n- [Session proposal on GitHub](https://github.com/w3c/tpac2025-breakouts/issues/64) STATUS:CONFIRMED CREATED:20251028T131539Z LAST-MODIFIED:20260219T062305Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 4 - 403 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:4dd94c3f-8527-477f-aa73-36db966efce9 DTSTAMP:20260219T062402Z SUMMARY:Web Engines Hackfest / TPAC 2 DTSTART;TZID=Asia/Tokyo:20251112T144500 DTEND;TZID=Asia/Tokyo:20251112T154500 DESCRIPTION:https://www.w3.org/events/meetings/4dd94c3f-8527-477f-aa73-36db 966efce9/\n\nSeveral times over the years\, ACs have discussed whether the re would be value in "another TPAC" but this is challenging for a whole lo t of practical reasons. But what if it were simpler? What if it basically already existed?\n\nThe [Web Engines Hackfest](https://webengineshackfest .org/) has been held annually since 2009\, hosted by Igalia in A Coruña\, Galicia\, Spain. For several years now we have hosted it at [palexco](ht tps://www.palexco.com/en/) a large conference venue. It is "shaped" simil arly to TPAC in many ways\, with talks and breakout sessions on all things web\, and attendees from all of the major browser vendors (and numerous s maller ones!).\n\nIt would be interesting to discuss partnership/promotion and collaboration on the Hackfest's ability to play this role.\n\n**Goal( s):**\nTo discuss interest from wider W3C in exploring something like a se cond TPAC by way of the Hackfest\n\nAgenda\n\n**Materials:**\n- [Session p roposal on GitHub](https://github.com/w3c/tpac2025-breakouts/issues/12) STATUS:CONFIRMED CREATED:20251028T073421Z LAST-MODIFIED:20260219T062402Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 4 - 406 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:421e0e1f-bade-4b6d-8cc6-8d01fbc7f7e9 DTSTAMP:20260219T062508Z SUMMARY:Web platform features to enable biometric liveness detection DTSTART;TZID=Asia/Tokyo:20251112T144500 DTEND;TZID=Asia/Tokyo:20251112T154500 DESCRIPTION:https://www.w3.org/events/meetings/421e0e1f-bade-4b6d-8cc6-8d01 fbc7f7e9/\n\nThe advent of Passkeys and Face ID on the web has been a huge boost to security and simplicity for verifying returning users.\n\nHoweve r\, there remain the questions of:\n1. How can an institution can confirm the authentic identity of an end user when registering these credentials?\ n2. What would happen if a user lost their passkey-bearing device?\n3. How could a web-based\, shared user device handle multiple identities without requiring those people to hold devices.\n\nThe established answer is biom etric ID verification where a facial comparison of an identity document an d selfie image are made\, in addition to liveness checks to prevent presen tation and deepfake injection attacks. Many offerings exist today\, includ ing from established tech firms such as Amazon and Microsoft.\n\nThe Web p latform is well-positioned to perform these sorts of ID check ceremonies s ince it doesn't require heavy apps to be downloaded for what is usually a one-time task\, and key tenets of the platform are to provide an accessibl e\, democratised and powerful way to interact with digital services - impo rtant to avoid "digital deserts" and to enable people in all geographies\, of any demographic\, to interact with civic services\, financial institut ions and so on.\n\nToday\, the best experience is afforded to users of nat ive apps due to the availability of several features that the Web platform doesn't have any\, or uniform API support for.\n\nHere are some examples we could improve on:\n\n1. Reading the current lighting environment via am bient light or EXIF data - useful for guiding users to submit good quality imagery for checking.\n2. Boosting screen brightness\, if needed\, for th e duration of the image capture.\n3. Detecting the presence of and accessi ng any infrared cameras.\n\n**Goal(s):**\nGauge interest in reviving exist ing proposals such as ambient light sensor\, screen brightness. Detecting types of camera via MediaDevices API.\n\nAgenda\n\n1. Liveness 101: what i s it\, how does it fit in with Passkeys et al?\n2. Why supporting liveness and biometrics on the web is essential.\n3. Standards proposals and techn ologies\, past present and future:\n 1. AmbientLightSensor\n 2. Scre en brightness control\n 3. Infrared device selection\n 4. Face detec tion\n4. Invitation to collaborate with vendors and other interested parti es with adjacent or similar use cases\n\n**Materials:**\n- [Session propos al on GitHub](https://github.com/w3c/tpac2025-breakouts/issues/21) STATUS:CONFIRMED CREATED:20251028T073545Z LAST-MODIFIED:20260219T062508Z SEQUENCE:4 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 3 - 302 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:eec3d0a2-86ed-453d-a2ee-e5e5595e4f73 DTSTAMP:20260219T062608Z SUMMARY:Web-based Digital Twins for Smart Cities DTSTART;TZID=Asia/Tokyo:20251112T144500 DTEND;TZID=Asia/Tokyo:20251112T154500 DESCRIPTION:https://www.w3.org/events/meetings/eec3d0a2-86ed-453d-a2ee-e5e5 595e4f73/\n\nThe mission of the Web-based Digital Twins for Smart Cities I nterest Group\n(SCIG) is working on the following:\n* identify and documen t use cases and requirements that W3C specifications need to meet to suppo rt various services within Smart Cities\,\n* obtain feedback from all stak eholders on the usage of Web technologies for those services\,\n* gather e xpert input on important features for those services based on the Web tech nology\,\n* and provide a forum for technical and business discussions rel ated to those services.\n\nYou will learn the current best practices of cu tting-edge standards for smart\ncities around possible framework and vocab ulary ontologies\, and then see how Web standards could possibly counter t he fragmentation of existing smart city\napproaches.\n\n**Goal(s):**\nBase d on the [group's Charter](https://www.w3.org/2024/06/smart-cities/)\, we' ll summarize the SCIG's discussion so far\, and ask the key stakeholders f rom related SDOs about their pain points and current best practices. Then we'd like to discuss what is still missing and what Web standards possibly could improve the fragmented situation.\n\nAgenda\n\n1. Review the discus sion so far\n2. Get input from stakeholders about their pain points and cu rrent practices\n3. Discuss what's still missing and what/how Web standard s could help\n\n**Materials:**\n- [Session proposal on GitHub](https://git hub.com/w3c/tpac2025-breakouts/issues/23) STATUS:CONFIRMED CREATED:20251028T073624Z LAST-MODIFIED:20260219T062608Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 4 - 404 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:0c0af714-032a-419c-885a-97b9921e3a50 DTSTAMP:20260219T060547Z SUMMARY:A Lean4-Verified Protocol for Smart Cities Addressing the Three Cor e Challenges of DIDs and VCs DTSTART;TZID=Asia/Tokyo:20251112T161500 DTEND;TZID=Asia/Tokyo:20251112T171500 DESCRIPTION:https://www.w3.org/events/meetings/0c0af714-032a-419c-885a-97b9 921e3a50/\n\nWe propose the international standardization of the AMT Proto col (Japanese name: AMATELUS) — a Lean4-verified protocol designed to so lve the three critical challenges encountered when introducing DIDs and VC s into Japanese municipal systems.\nThese challenges are not unique to Jap an\; municipalities and enterprises around the world likely face the same issues.\n\nThree Core Challenges in Implementing DIDs and VCs for Smart Ci ties\n1. Traceability Problem – Resolving DID Documents on blockchains o r IPFS makes DIDs inherently traceable.\n2. Over-Disclosure Problem – Se lective disclosure in VCs still requires revealing excessive personal info rmation and enables cross-linking of identities.\n3. Auditability Problem – Using ZKPs can conceal DIDs and personal data but makes legitimate gov ernmental audits impossible.\n\nTo move beyond proof-of-concept and enable real-world deployment of decentralized identity systems\,\nwe present the AMT Protocol\, a concrete and verifiable solution integrating decentraliz ed identity\, privacy preservation\, and public accountability.\nA detaile d Blueprint and formal verification in Lean4 are already publicly availabl e.\n\nWeb site: https://amatelus.com\nDID method PR: https://github.com/w3 c/did-extensions/pull/639\nLean4 code (Japanese): https://github.com/amate lus/amatelus\n\n**Goal(s):**\nThis session aims to gather and discuss the challenges faced by municipalities around the world in adopting DIDs and V Cs for smart city development\, and to explore how the AMT Protocol approa ch can help address these issues.\n\nAgenda\n\n1. Share the technical and political challenges of building smart cities using DIDs and VCs.\n2. Pres ent the AMT Protocol’s solutions and provide a brief overview of the Lea n4 formal verification results.\n3. Disclose the constraints observed in J apanese municipalities and discuss the limitations that exist in other cou ntries.\n4. Review coexistence and distinctions between the AMT Protocol a nd related international standards and technologies.\n\n**Materials:**\n- [Session proposal on GitHub](https://github.com/w3c/tpac2025-breakouts/iss ues/73) STATUS:CONFIRMED CREATED:20251028T131643Z LAST-MODIFIED:20260219T060547Z SEQUENCE:4 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 3 - 302 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:76eeff8c-9750-4d3e-874b-a32293d6af9c DTSTAMP:20260219T060628Z SUMMARY:Accessibility Roles and Responsibilities Mapping (ARRM) DTSTART;TZID=Asia/Tokyo:20251112T161500 DTEND;TZID=Asia/Tokyo:20251112T171500 DESCRIPTION:https://www.w3.org/events/meetings/76eeff8c-9750-4d3e-874b-a322 93d6af9c/\n\nA discussion about Accessibility Roles and Responsibilities M apping (ARRM) and its role in helping accessibility evaluation.\n\n[Slack] (https://w3ccommunity.slack.com/archives/C07CN8EGAPQ)\n\n**Goal(s):**\nRev iew progress thus far and look to opportunities ahead\n\nAgenda\n\n- Revie w ARRM & its history\n- Look at the roadmap for a teams based approach\n- Consider the Web Sustainability Guidelines approach to highlight roles\n- Consider implications for future WCAG releases\n\n**Materials:**\n- [Sessi on proposal on GitHub](https://github.com/w3c/tpac2025-breakouts/issues/2) STATUS:CONFIRMED CREATED:20251028T073304Z LAST-MODIFIED:20260219T060628Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 4 - 402 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:ac1c9702-429c-4d69-b59b-7153358bce6e DTSTAMP:20260219T060730Z SUMMARY:Converged Use Cases for the Credential Management API DTSTART;TZID=Asia/Tokyo:20251112T161500 DTEND;TZID=Asia/Tokyo:20251112T171500 DESCRIPTION:https://www.w3.org/events/meetings/ac1c9702-429c-4d69-b59b-7153 358bce6e/\n\nThe Credential Management API has rapidly evolved into a crit ical component of identity on the web. From enabling seamless passkey expe riences via WebAuthn to integrating federated identity flows through FedCM \, facilitating SMS OTPs with WebOTP\, and now facilitating the exchange o f verifiable digital credentials via the Digital Credentials API\, its sco pe continues to expand. This proliferation of capabilities sparks a critic al discussion: how can these individual strengths be synergized for richer \, more secure\, and user-friendly identity experiences? \n\nThis session aims to explore three key scenarios: first\, the concept of multi-type cre dential for sign-in requests\, for example allowing a single API call to s olicit a passkey\, a password or a federated identity\, second\, a multi-t ype credential for identity attributes\, for example allowing a single API call to solicit either a federated assertion or a digital credential base d on the application's needs\; and third\, the potential for a method that combines identity claim acquisition (e.g.\, name and verified email via f ederation) with simultaneous passkey creation\, streamlining initial sign- up and subsequent passwordless authentication.\n\n**Goal(s):**\nIdeation a nd requirements gathering\n\nAgenda\n\n**Materials:**\n- [Session proposal on GitHub](https://github.com/w3c/tpac2025-breakouts/issues/3) STATUS:CONFIRMED CREATED:20251028T073315Z LAST-MODIFIED:20260219T060730Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 5 - 505 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:a556e2f0-107a-43a7-bd11-dd75d8dbe953 DTSTAMP:20260219T060825Z SUMMARY:Cryptography Usage Guideline in Web Standards DTSTART;TZID=Asia/Tokyo:20251112T161500 DTEND;TZID=Asia/Tokyo:20251112T171500 DESCRIPTION:https://www.w3.org/events/meetings/a556e2f0-107a-43a7-bd11-dd75 d8dbe953/\n\nSeveral Web standards rely on cryptographic algorithms to ens ure security and privacy properties.\nHowever\, choosing the right algorit hm and configuring it correctly is often challenging for developers who ar e not cryptography experts. The number of available algorithms\, evolving standards\, and frequent deprecations make it difficult to identify secure and interoperable solutions.\n\nSING Interest Group proposes a session on the use of cryptography to present an ongoing draft addressing this topic .\nThis draft document aims to provide a clear and practical overview of s tandardized cryptographic algorithms and their recommended usage in variou s contexts. It offers guidelines on when and how to use specific algorithm s\, parameter choices\, and common pitfalls to avoid — promoting a consi stent\, standards-based\, and secure use of cryptography across web techno logies.\n\nYou can find the most recent editor's draft at [https://w3c.gi thub.io/security-guidelines-cryptography/](https://w3c.github.io/security- guidelines-cryptography//).\n\nThe purpose of this session is to present t he current version of the document and discuss its content\, by collecting feedback from participants and discussing some open points that require f urther analysis or decisions.\n\n**Goal(s):**\nCollect feedback on the dra ft document and discuss open points\n\nAgenda\n\n**Materials:**\n- [Sessio n proposal on GitHub](https://github.com/w3c/tpac2025-breakouts/issues/40) STATUS:CONFIRMED CREATED:20251028T073903Z LAST-MODIFIED:20260219T060825Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Floor 5 - 504 CATEGORIES:TPAC 2025,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:e3553cb1-34f7-47f5-81e8-eea4da37aa73 DTSTAMP:20260219T060920Z SUMMARY:Custom attributes for all elements DTSTART;TZID=Asia/Tokyo:20251112T161500 DTEND;TZID=Asia/Tokyo:20251112T171500 DESCRIPTION:https://www.w3.org/events/meetings/e3553cb1-34f7-47f5-81e8-eea4 da37aa73/\n\n2023's breakouts had a [discussion on alternatives to customi zed built-ins](https://github.com/w3c/tpac2023-breakouts/issues/44).\n\nA sketch of a proposal came out around this time: customised attributes. htt ps://github.com/WICG/webcomponents/issues/1029\n\nI'd like to set some tim e to discuss this idea\, the merits\, complexities\, and discuss whether o r not this solves problems for developers without too much complexity for the platform.\n\n**Goal(s):**\nDecide if a model for Custom Attributes is viable in the platform\, and what a design might look like.\n\nAgenda\n\n1 . Can we reasonably enforce that HTML will only standardise attribute name s without dashes\, and developers can use dashes (modulo `data-*` and `ari a-*`)\; see https://github.com/whatwg/html/issues/2271\n2. Can we agree th at pursuing a series of lifecycle callbacks for when an attribute node is connected\, disconnected\, and changed would be a useful feature for devel opers\, and something that the major browser vendors would be happy pursui ng.\n3. Do we agree that `class CustomAttr extends Attr {}` is a good desi gn choice? This means giving Attr() a constructor\, and would be `getAttri buteNode()` etc could now return subclasses of `Attr`. It would also mean `setAttribute`/`removeAttribute`/`toggleAttribute` would run these lifecyc les\, including: looking up the attribute name in some form of registry\, & calling into script. Is this okay?\n4. Can Attrs leverage `CEReactions` or would we need some kind of new `CAReactions`?\n5. Reflection is useful for attributes\, could we design a way to bake reflection into custom attr ibute nodes? E.g. `static reflectedAs = "long"` which would change the beh aviour of `Attr.prototype.value` for such custom attributes.\n6. Default v alues for attributes is useful\, can we design something like `static defa ultValue = ...`?\n7. We would likely need some kind of attribute registry (much like `window.customElements`). Does `window.customAttributes` make s ense? Perhaps we wish to define attributes only for specific elements\, su ch as `