BEGIN:VCALENDAR VERSION:2.0 PRODID:-//Sabre//Sabre VObject 4.5.8//EN CALSCALE:GREGORIAN NAME:TPAC 2023 Calendar X-WR-CALNAME:TPAC 2023 Calendar LAST-MODIFIED:20240301T194013Z BEGIN:VTIMEZONE TZID:Europe/Madrid BEGIN:STANDARD DTSTART:20221030T010000 TZOFFSETFROM:+0200 TZOFFSETTO:+0100 TZNAME:CET END:STANDARD BEGIN:STANDARD DTSTART:20231029T010000 TZOFFSETFROM:+0200 TZOFFSETTO:+0100 TZNAME:CET END:STANDARD BEGIN:DAYLIGHT DTSTART:20230326T010000 TZOFFSETFROM:+0100 TZOFFSETTO:+0200 TZNAME:CEST END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT UID:1a5b66fb-e618-45d0-9896-6d187b23fd89 DTSTAMP:20230921T103204Z SUMMARY:Accelerating the Web performance by compiling Javascript code to WA SM DTSTART;TZID=Europe/Madrid:20230913T093000 DTEND;TZID=Europe/Madrid:20230913T103000 DESCRIPTION:https://www.w3.org/events/meetings/1a5b66fb-e618-45d0-9896-6d18 7b23fd89/\n\nWASM is the technology bringing more development languages\, additional security and better performance to the Web. Javascript is the d ominant language in developing Web applications\, front frameworks and lib raries. How to enhance the cooperation between the two technnologies for a more efficient Web?\n\n\n\n\n\n\n\nThis session intends to open up a dis cussion on an innovative proposal to compile and run Javascript code on WA SM for better Web performance\, and related standards work.\n\nAgenda: htt ps://docs.google.com/document/d/1skQFGhxvK9F-o9jIkQOAKUziuvPzUigGlRE6InwC3 sQ/edit#heading=h.2zye3qyc2qk\n\nAgenda\n\n**Chairs:**\nWei Ding\, Shi Lin g\n\n**Description:**\nWASM is the technology bringing more development la nguages\, additional security and better performance to the Web. Javascrip t is the dominant language in developing Web applications\, front framewor ks and libraries. How to enhance the cooperation between the two technnolo gies for a more efficient Web?\n\n\n\n\n\n\n\nThis session intends to ope n up a discussion on an innovative proposal to compile and run Javascript code on WASM for better Web performance\, and related standards work.\n\n* *Goal(s):**\n1. Collect comments on the proposal regarding the Javascript code to WASM compiling program. \n\n\n\n2. Recruit interests to work on th e standards development. \n\n\n\n3. Discuss the maturity going to the W3C strategy incubation pipeline.\n\n\n**Materials:**\n- [minutes](https://www .w3.org/2023/09/13-js2wasm-minutes.html)\n- [slides web for apps](https:// lists.w3.org/Archives/Public/www-archive/2023Sep/att-0021/TPCA_2023_-_Web_ for_Apps_v1.pdf)\n- [slides jwst](https://lists.w3.org/Archives/Public/www -archive/2023Sep/att-0021/W3C-TPAC-JWST-Beihang-ShiXiaohua-final.pdf)\n- [ recording](https://www.w3.org/2023/09/breakouts/recording-22.html)\n- [Ses sion proposal on GitHub](https://github.com/w3c/tpac2023-breakouts/issues/ 22)\n\n**Track(s):**\n- performance STATUS:CONFIRMED CREATED:20230905T053718Z LAST-MODIFIED:20230921T103204Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Nervion I - Level -1 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:ed5925cb-c1de-43ff-b7d3-7411ce8d0d84 DTSTAMP:20230921T103544Z SUMMARY:Accessibility at the Edge\, One Year On DTSTART;TZID=Europe/Madrid:20230913T093000 DTEND;TZID=Europe/Madrid:20230913T103000 DESCRIPTION:https://www.w3.org/events/meetings/ed5925cb-c1de-43ff-b7d3-7411 ce8d0d84/\n\n#### Annual Review: Community Group's Work on Accessibility i n Overlay Technology\n\n\n\n##### Agenda:\n\n\n\n1. **Year-in-Review**: Ou r Achievements\n\n2. **Deep Dive**: Guided Reading of the Capabilities Dra ft Report\n\n3. **Getting on the Same Page**: Terminology Discussion\n\n4. **Looking Forward**: Next Steps\n\n\n\n##### Details:\n\n\n\n- **Year-in- Review**:\n\n - We'll discuss the major milestones and progress we've mad e in the past year.\n\n- **Deep Dive**:\n\n - **Highlighting Key Capabili ties**: Understand the capabilities present in COTS (commercial off the sh elf) products. These are essential in evaluating and contrasting current t echnologies.\n\n - **Future Potential**: We'll discuss aspirational capab ilities that hold promise for advancing accessibility\, especially when im plemented as edge technology.\n\n- **Getting on the Same Page**:\n\n - Le t's dive deep into the vocabulary we've come across. We'll carefully explo re terms like "overlay"\, "user agent"\, "assistive technology"\, "browser extensions"\, and other edge-located add-ons to ensure a shared understan ding.\n\n\n\n[Link to the Capabilities Draft Report](https://a11yedge.gith ub.io/capabilities/)\n\n\n\nLooking forward to an insightful session. See you there!\n\nAgenda\n\n**Chairs:**\nJanina Sajka\, Lionel Wolberger\n\n** Description:**\n#### Annual Review: Community Group's Work on Accessibilit y in Overlay Technology\n\n\n\n##### Agenda:\n\n\n\n1. **Year-in-Review**: Our Achievements\n\n2. **Deep Dive**: Guided Reading of the Capabilities Draft Report\n\n3. **Getting on the Same Page**: Terminology Discussion\n\ n4. **Looking Forward**: Next Steps\n\n\n\n##### Details:\n\n\n\n- **Year- in-Review**:\n\n - We'll discuss the major milestones and progress we've made in the past year.\n\n- **Deep Dive**:\n\n - **Highlighting Key Capab ilities**: Understand the capabilities present in COTS (commercial off the shelf) products. These are essential in evaluating and contrasting curren t technologies.\n\n - **Future Potential**: We'll discuss aspirational ca pabilities that hold promise for advancing accessibility\, especially when implemented as edge technology.\n\n- **Getting on the Same Page**:\n\n - Let's dive deep into the vocabulary we've come across. We'll carefully ex plore terms like "overlay"\, "user agent"\, "assistive technology"\, "brow ser extensions"\, and other edge-located add-ons to ensure a shared unders tanding.\n\n\n\n[Link to the Capabilities Draft Report](https://a11yedge.g ithub.io/capabilities/)\n\n\n\nLooking forward to an insightful session. S ee you there!\n\n**Goal(s):**\nProvide an update and transparency.\n\n\n** Materials:**\n- [minutes](https://www.w3.org/2023/09/13-a11yedge-minutes.h tml)\n- [recording](https://www.w3.org/2023/09/breakouts/recording-51.html )\n- [Session proposal on GitHub](https://github.com/w3c/tpac2023-breakout s/issues/51)\n\n**Track(s):**\n- accessibility STATUS:CONFIRMED CREATED:20230905T053953Z LAST-MODIFIED:20230921T103544Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Prado - Level -1 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:cef9b5d1-2b24-4c04-aec9-61066556590b DTSTAMP:20230919T113504Z SUMMARY:Chartering at W3C DTSTART;TZID=Europe/Madrid:20230913T093000 DTEND;TZID=Europe/Madrid:20230913T103000 DESCRIPTION:https://www.w3.org/events/meetings/cef9b5d1-2b24-4c04-aec9-6106 6556590b/\n\nReviewing and possibly improving chartering of Working Groups and Interest Groups is an AB priority for this year.\n\n\n\n\n\n\n\nThe g oal of this session is to review the landscape\, and have people share wha t they like and dislike about how it currently works\, and share their exp erience.\n\n\n\n\n\n\n\nWe don't expect to resolve on anything in particul ar during this session\, but it can be a good time to surface and socializ e potential improvements.\n\nAgenda\n\n**Chairs:**\nFlorian Rivoal\, Elika Etemad\, Philippe Le Hegaret\n\n**Description:**\nReviewing and possibly improving chartering of Working Groups and Interest Groups is an AB priori ty for this year.\n\n\n\n\n\n\n\nThe goal of this session is to review the landscape\, and have people share what they like and dislike about how it currently works\, and share their experience.\n\n\n\n\n\n\n\nWe don't exp ect to resolve on anything in particular during this session\, but it can be a good time to surface and socialize potential improvements.\n\n**Goal( s):**\nGet feedback on the W3C chartering Process\, to be used as input fo r the AB\n\n\n**Materials:**\n- [minutes](https://www.w3.org/2023/09/13-w3 process-minutes.html)\n- [Session proposal on GitHub](https://github.com/w 3c/tpac2023-breakouts/issues/43)\n\n**Track(s):**\n- getting work done STATUS:CONFIRMED CREATED:20230905T053915Z LAST-MODIFIED:20230919T113504Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Magnolia - Low Level CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:4fd28161-058b-4daa-9618-d1893be9c39c DTSTAMP:20230919T113604Z SUMMARY:DOM Localization DTSTART;TZID=Europe/Madrid:20230913T093000 DTEND;TZID=Europe/Madrid:20230913T103000 DESCRIPTION:https://www.w3.org/events/meetings/4fd28161-058b-4daa-9618-d189 3be9c39c/\n\nThe base requirements for message formatting and localization are experiencing some significant advancements as the [MessageFormat 2 sp ec](https://github.com/unicode-org/message-format-wg/tree/main/spec) is be ing defined in the Unicode Consortium\, and the [Intl.MessageFormat](https ://github.com/tc39/proposal-intl-messageformat) API is being defined in TC -39 for JavaScript.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nBuilding on these\, wor k should start on defining a localization system for HTML that's _reactive _ rather than _imperative_\, and which allows for localization without any JS dependency. At Mozilla\, we've been using a similar system based on [F luent](https://projectfluent.org/) to localize Firefox and our other proje cts\, and have learned much about what works and what doesn't. Some of our ideas have been [collected as a draft](https://nordzilla.github.io/dom-l1 0n-draft-spec/) of what this could look like in practice.\n\nAgenda\n\n**C hairs:**\nEemeli Aro\n\n**Description:**\nThe base requirements for messag e formatting and localization are experiencing some significant advancemen ts as the [MessageFormat 2 spec](https://github.com/unicode-org/message-fo rmat-wg/tree/main/spec) is being defined in the Unicode Consortium\, and t he [Intl.MessageFormat](https://github.com/tc39/proposal-intl-messageforma t) API is being defined in TC-39 for JavaScript.\n\n\n\n\n\n\n\n\n\n\n\n\n \n\n\nBuilding on these\, work should start on defining a localization sys tem for HTML that's _reactive_ rather than _imperative_\, and which allows for localization without any JS dependency. At Mozilla\, we've been using a similar system based on [Fluent](https://projectfluent.org/) to localiz e Firefox and our other projects\, and have learned much about what works and what doesn't. Some of our ideas have been [collected as a draft](https ://nordzilla.github.io/dom-l10n-draft-spec/) of what this could look like in practice.\n\n**Goal(s):**\n1. Collect comments on the proposal.\n\n\n\n 2. Recruit interests to work on the standards development.\n\n\n\n3. Discu ss the most appropriate forum for further work.\n\n\n**Materials:**\n- [sl ides](https://docs.google.com/presentation/d/1cvvNcC2jMKztYKFIAg1Q5JPWrMCd 0q8Ac2m7P1RYhOc/edit?usp=sharing)\n- [minutes](https://www.w3.org/2023/09/ 13-dom-localization-minutes.html)\n- [Session proposal on GitHub](https:// github.com/w3c/tpac2023-breakouts/issues/52) STATUS:CONFIRMED CREATED:20230905T053959Z LAST-MODIFIED:20230919T113604Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Triana - Level -1 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:d4dc1937-2707-4d29-b54b-0096522bc8fb DTSTAMP:20230923T163237Z SUMMARY:Evolving anti-fingerprinting protections DTSTART;TZID=Europe/Madrid:20230913T093000 DTEND;TZID=Europe/Madrid:20230913T103000 DESCRIPTION:https://www.w3.org/events/meetings/d4dc1937-2707-4d29-b54b-0096 522bc8fb/\n\n[Link to slides](https://docs.google.com/presentation/d/1QBCl J9HKqUh2k81eMGPGMeHuGeIC8Tnmywd1PUN-kss/edit#slide=id.p)\n\n\n\n[Link to m inutes](https://docs.google.com/document/d/1BlFZYfqCEgSqnev1jo2SYKRNlIq-SX Tn-92YpgAL8OQ/edit)\n\n\n\nAs third party cookies become less available\, tracking will shift further towards fingerprinting and other forms of cove rt cross-site tracking.\n\n\n\n\n\n\n\nWhile it is infeasible to fundament ally remove or change usage of IP addresses or web APIs which could be use d for fingerprinting\, it is possible to curtail access to these surfaces in scenarios that are sensitive for cross-site tracking. \n\n\n\nBrowsers have been developing and shipping mitigations using tracker lists as a pra gmatic path forward -- spanning IP proxying and active fingerprinting miti gations. There are some common challenges and potential opportunities acro ss browsers.\n\nAgenda\n\n**Chairs:**\nShubhie Panicker\n\n**Description:* *\n[Link to slides](https://docs.google.com/presentation/d/1QBClJ9HKqUh2k8 1eMGPGMeHuGeIC8Tnmywd1PUN-kss/edit#slide=id.p)\n\n\n\n[Link to minutes](ht tps://docs.google.com/document/d/1BlFZYfqCEgSqnev1jo2SYKRNlIq-SXTn-92YpgAL 8OQ/edit)\n\n\n\nAs third party cookies become less available\, tracking w ill shift further towards fingerprinting and other forms of covert cross-s ite tracking.\n\n\n\n\n\n\n\nWhile it is infeasible to fundamentally remov e or change usage of IP addresses or web APIs which could be used for fing erprinting\, it is possible to curtail access to these surfaces in scenari os that are sensitive for cross-site tracking. \n\n\n\nBrowsers have been developing and shipping mitigations using tracker lists as a pragmatic pat h forward -- spanning IP proxying and active fingerprinting mitigations. T here are some common challenges and potential opportunities across browser s.\n\n**Goal(s):**\nDiscuss challenges & evolving mitigations\, identify c ollaboration opportunities\n\n**Attendance:**\nThis session is restricted to TPAC registrants.\n\n**Materials:**\n- [slides](https://docs.google.com /presentation/d/1QBClJ9HKqUh2k81eMGPGMeHuGeIC8Tnmywd1PUN-kss/edit#slide=id .p)\n- [minutes](http://www.w3.org/2023/09/tpac-breakouts/46-minutes.pdf)\ n- [live google doc minutes](https://docs.google.com/document/d/1BlFZYfqCE gSqnev1jo2SYKRNlIq-SXTn-92YpgAL8OQ/edit)\n- [Session proposal on GitHub](h ttps://github.com/w3c/tpac2023-breakouts/issues/46)\n\n**Track(s):**\n- pr ivacy STATUS:CONFIRMED CREATED:20230905T053929Z LAST-MODIFIED:20230923T163237Z SEQUENCE:2 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Giralda III - Level -2 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:7c94f300-08ee-4906-b932-6dfc1d8a4f06 DTSTAMP:20230919T113346Z SUMMARY:Interop Project DTSTART;TZID=Europe/Madrid:20230913T093000 DTEND;TZID=Europe/Madrid:20230913T103000 DESCRIPTION:https://www.w3.org/events/meetings/7c94f300-08ee-4906-b932-6dfc 1d8a4f06/\n\nThe [Interop Project](https://github.com/web-platform-tests/i nterop/) is designed to improve the real world interoperability of web bro wser implementations by producing shared public metrics that show the test pass rates of important features\, based on a curated selection of web-pl atform-tests.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nIn this session we will descr ibe the current state of Interop 2023 and describe the process for submitt ing proposals for Interop 2024\, and how the proposal selection process wo rks. We will also be looking for discussion and feedback on the process\, to gauge how well Interop is working for working groups and their particip ants\, and for any opportunities to make improvements going forward\, or n ew ways to improve the interoperability of web implementations in the futu re.\n\nAgenda\n\n**Chairs:**\nJames Graham\n\n**Description:**\nThe [Inter op Project](https://github.com/web-platform-tests/interop/) is designed to improve the real world interoperability of web browser implementations by producing shared public metrics that show the test pass rates of importan t features\, based on a curated selection of web-platform-tests.\n\n\n\n\n \n\n\n\n\n\n\n\n\n\n\nIn this session we will describe the current state o f Interop 2023 and describe the process for submitting proposals for Inter op 2024\, and how the proposal selection process works. We will also be lo oking for discussion and feedback on the process\, to gauge how well Inter op is working for working groups and their participants\, and for any oppo rtunities to make improvements going forward\, or new ways to improve the interoperability of web implementations in the future.\n\n**Goal(s):**\nEn sure the Interop process is well understood by W3C members\, so they are a ble to submit proposals\, and gather input to make the process better goin g forward.\n\n\n**Materials:**\n- [minutes](https://www.w3.org/2023/09/13- interop-minutes.html)\n- [Session proposal on GitHub](https://github.com/w 3c/tpac2023-breakouts/issues/33)\n\n**Track(s):**\n- developer experience STATUS:CONFIRMED CREATED:20230905T053820Z LAST-MODIFIED:20230919T113346Z SEQUENCE:2 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Nervion-Arenal II - Level -1 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:acd0702a-85fc-4f79-8c22-200080dd7aad DTSTAMP:20230928T055850Z SUMMARY:Meeting Facilitation Training (Pt 2) DTSTART;TZID=Europe/Madrid:20230913T093000 DTEND;TZID=Europe/Madrid:20230913T103000 DESCRIPTION:https://www.w3.org/events/meetings/acd0702a-85fc-4f79-8c22-2000 80dd7aad/\n\nAs a follow-up to the first part of Meeting Facilitation Trai ning (video is online at [link here])\, this session will be an in-person and remote discussion covering the second part of the training. Participan ts in this session will be expected to have watched the first part of this training in advance of the session. \n\n\n\n\n\n\n\nThis session is open to all meeting facilitators (chairs\, taskforce leads\, or aspiring to be) \, and will be a collaborative session covering tip and tricks participant s use to make running meetings easier\, and discussion on how to handle di fficult discussions or situations as a chair or meeting facilitator. \n\n\ n\nDue to the nature of topics that might come up during the meeting\, we will not be minuting the part of the session on difficult conversations\, but will minute the tips and tricks discussion.\n\n\n\n_Post-TPAC note: No minutes were taken at this session._\n\nAgenda\n\n**Chairs:**\nWendy Reid \n\n**Description:**\nAs a follow-up to the first part of Meeting Facilita tion Training (video is online at [link here])\, this session will be an i n-person and remote discussion covering the second part of the training. P articipants in this session will be expected to have watched the first par t of this training in advance of the session. \n\n\n\n\n\n\n\nThis session is open to all meeting facilitators (chairs\, taskforce leads\, or aspiri ng to be)\, and will be a collaborative session covering tip and tricks pa rticipants use to make running meetings easier\, and discussion on how to handle difficult discussions or situations as a chair or meeting facilitat or. \n\n\n\nDue to the nature of topics that might come up during the meet ing\, we will not be minuting the part of the session on difficult convers ations\, but will minute the tips and tricks discussion.\n\n\n\n_Post-TPAC note: No minutes were taken at this session._\n\n**Goal(s):**\nMeeting Fa cilitator Training\n\n**Attendance:**\nThis session is restricted to TPAC registrants.\n\n**Materials:**\n- [Session proposal on GitHub](https://git hub.com/w3c/tpac2023-breakouts/issues/11) STATUS:CONFIRMED CREATED:20230905T053615Z LAST-MODIFIED:20230928T055850Z SEQUENCE:2 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Giralda V - Level -2 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:762bb84d-ef4a-42db-8c0c-4563e1b2ff37 DTSTAMP:20231012T082320Z SUMMARY:Notifications - Sharing current problems & issues DTSTART;TZID=Europe/Madrid:20230913T093000 DTEND;TZID=Europe/Madrid:20230913T103000 DESCRIPTION:https://www.w3.org/events/meetings/762bb84d-ef4a-42db-8c0c-4563 e1b2ff37/\n\nWe have a number of rough areas\, and while we might not be r eady to figure out a solution yet\, we would love to chat about the curren t issues we are seeting. @b1tr0t and @beverloo have most of the context he re (although @beverloo won't be at TPAC this year)\n\n\n\n\n\n\n\n\n\n\n\n \n\n\n\n* Abuse / spam / requiring install for notifications \n\n * Chrom ium is seeing a large quantity of abuse across the ecosystem. We don’t b elieve gating notifications to installed use is the answer for reasons. \n \n * We are considering rate limiting and other countermeasures \n\n * A re there opportunities for standards revisions that might help? \n\n\n\n\n \n\n\n* "important" notifications (VOIP). @beverloo notes:\n\n * MSFT alr eady working on this:\n\n * [Intent to Prototype on blink-dev](https://gr oups.google.com/a/chromium.org/g/blink-dev/c/PtHemJah2Qc/m/EkXmztgzCgAJ?ut m_medium=email&utm_source=footer)\, [explainer](https://github.com/Microso ftEdge/MSEdgeExplainers/blob/main/Notifications/notifications_actions_cust omization.md)\, [initial implementation](https://chromium-review.googlesou rce.com/c/chromium/src/+/4088048)\n\n * Example hero use-case - empower S kype on the Web.\n\n * On Android this would require a permission (FOREGR OUND_SERVICE_PHONE_CALL) that we probably don’t want to issue to Chrome itself. Limiting this functionality to installed experiences seems good in either case\, as otherwise there would be complicated incentives.\n\n\n\n * Notification sounds (ringing?)\n\n * Related to important notifications \, some apps might want a ringing sound\n\n * Somewhat limited by OS supp ort of custom notification sounds\, however\, may be possible to create a “Safe” set of standard notification sounds for developer to choose fro m e.g. “Chime” “Ringing” “Alarm”\, and perhaps others\n\n * @ beverloo notes: This was part of a Microsoft proposal that we provided fee dback on\n\n * [Explainer](https://github.com/MicrosoftEdge/MSEdgeExpla iners/blob/main/Notifications/notifications_actions_customization.md#play- ringtone-from-inside-the-tab)\n\n * Long story short\, a (admittedly br ief) joint investigation showed that very few sounds would actually be con sistent across operating systems\, which is hard to explain to developers. It’s important that these are OS-consistent: ideally an e-mail in Apple Mail and one in Gmail alert Apple users in exactly the same way.\n\n * For Chromium to support arbitrary sounds\, the media team advised that th e best way to achieve that would be to load a (background) tab with a element in which we play the developer-provided URL. That’s a signif icant system health cost.\n\n * On Android such sounds are tied to the notification channel as opposed to individual notifications\, and actually cannot be set for individual notifications anymore.\n\n\n\n\n\n\n\n* Noti fication channels.\n\n * Allow sites to register and send to specific cha nnels\, similar to capabilities offered on Android and iOS platforms\n\n * Can be a useful way for users to reduce unwanted notification volume\, for example on a messaging app like IG the user could choose to allow DMs but not receive notifications about new posts in the feed\n\n * beverloo @ note:\n\n * ChromeOS is also very interested in this\, would like to see something like this supported. We might be able to mimic support in Wi ndows through grouping.\n\n * Nuances to consider on Android: channel s are declared once and are then permanent\, i.e. updating the importance\ , sound\, vibration etc. of a channel **should not happen** after it’s b een created\, even when the channel’s name changes.\n\n\n\n* Reducing no tification energy use (currently need to spin up JS)\n\n * The current we b notifications spec was designed with maximum flexibility as the objectiv e. With the current spec\, notifications require a Service Worker and when a notification is received\, the ServiceWorker wakes and can then take so me action. \n\n * The solution is an amendment to the notification specif ication that optimizes for the most common notification usage pattern of s imply displaying a notification on the user’s device. This change will i mprove performance and energy usage of notification delivery.\n\n * @beve rloo note: We’ve always been supportive of receiving push messages and s howing notifications w/o involving the service worker\, this would bring m ajor system health benefits.\n\n * There has been some resistance from partners to support this as they need the SW / analytics logic to run for monetization.\n\n * Android would be able to support high priority noti fications in a declarative path. This is important because the framework d eprioritises notifications for an entire app (i.e. the browser) based on s how and interaction rates\, which means that currently a single misbehavin g site can negatively impact the holistic browser notification experience. \n\n * Big +1 to doing this if we can get broader ecosystem adoption.\n \nAgenda\n\n**Chairs:**\nDaniel Murphy\n\n**Description:**\nWe have a numb er of rough areas\, and while we might not be ready to figure out a soluti on yet\, we would love to chat about the current issues we are seeting. @b 1tr0t and @beverloo have most of the context here (although @beverloo won' t be at TPAC this year)\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n* Abuse / spam / re quiring install for notifications \n\n * Chromium is seeing a large quant ity of abuse across the ecosystem. We don’t believe gating notifications to installed use is the answer for reasons. \n\n * We are considering ra te limiting and other countermeasures \n\n * Are there opportunities for standards revisions that might help? \n\n\n\n\n\n\n\n* "important" notific ations (VOIP). @beverloo notes:\n\n * MSFT already working on this:\n\n * [Intent to Prototype on blink-dev](https://groups.google.com/a/chromium. org/g/blink-dev/c/PtHemJah2Qc/m/EkXmztgzCgAJ?utm_medium=email&utm_source=f ooter)\, [explainer](https://github.com/MicrosoftEdge/MSEdgeExplainers/blo b/main/Notifications/notifications_actions_customization.md)\, [initial im plementation](https://chromium-review.googlesource.com/c/chromium/src/+/40 88048)\n\n * Example hero use-case - empower Skype on the Web.\n\n * On Android this would require a permission (FOREGROUND_SERVICE_PHONE_CALL) th at we probably don’t want to issue to Chrome itself. Limiting this funct ionality to installed experiences seems good in either case\, as otherwise there would be complicated incentives.\n\n\n\n* Notification sounds (ring ing?)\n\n * Related to important notifications\, some apps might want a r inging sound\n\n * Somewhat limited by OS support of custom notification sounds\, however\, may be possible to create a “Safe” set of standard notification sounds for developer to choose from e.g. “Chime” “Ringi ng” “Alarm”\, and perhaps others\n\n * @beverloo notes: This was pa rt of a Microsoft proposal that we provided feedback on\n\n * [Explaine r](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/Notificatio ns/notifications_actions_customization.md#play-ringtone-from-inside-the-ta b)\n\n * Long story short\, a (admittedly brief) joint investigation sh owed that very few sounds would actually be consistent across operating sy stems\, which is hard to explain to developers. It’s important that thes e are OS-consistent: ideally an e-mail in Apple Mail and one in Gmail aler t Apple users in exactly the same way.\n\n * For Chromium to support ar bitrary sounds\, the media team advised that the best way to achieve that would be to load a (background) tab with a element in which we pla y the developer-provided URL. That’s a significant system health cost.\n \n * On Android such sounds are tied to the notification channel as opp osed to individual notifications\, and actually cannot be set for individu al notifications anymore.\n\n\n\n\n\n\n\n* Notification channels.\n\n * A llow sites to register and send to specific channels\, similar to capabili ties offered on Android and iOS platforms\n\n * Can be a useful way for users to reduce unwanted notification volume\, for example on a messaging app like IG the user could choose to allow DMs but not receive notificati ons about new posts in the feed\n\n * beverloo@ note:\n\n * ChromeOS i s also very interested in this\, would like to see something like this sup ported. We might be able to mimic support in Windows through grouping.\n\n * Nuances to consider on Android: channels are declared once and are then permanent\, i.e. updating the importance\, sound\, vibration etc. of a channel **should not happen** after it’s been created\, even when the channel’s name changes.\n\n\n\n* Reducing notification energy use (curr ently need to spin up JS)\n\n * The current web notifications spec was de signed with maximum flexibility as the objective. With the current spec\, notifications require a Service Worker and when a notification is received \, the ServiceWorker wakes and can then take some action. \n\n * The solu tion is an amendment to the notification specification that optimizes for the most common notification usage pattern of simply displaying a notifica tion on the user’s device. This change will improve performance and ener gy usage of notification delivery.\n\n * @beverloo note: We’ve always b een supportive of receiving push messages and showing notifications w/o in volving the service worker\, this would bring major system health benefits .\n\n * There has been some resistance from partners to support this as they need the SW / analytics logic to run for monetization.\n\n * Andr oid would be able to support high priority notifications in a declarative path. This is important because the framework deprioritises notifications for an entire app (i.e. the browser) based on show and interaction rates\, which means that currently a single misbehaving site can negatively impac t the holistic browser notification experience.\n\n * Big +1 to doing t his if we can get broader ecosystem adoption.\n\n**Goal(s):**\nShare issue s with current notification spec & ecosystem\, possibly connect to problem solve in the future.\n\n\n**Materials:**\n- [slides](https://lists.w3.org /Archives/Public/www-archive/2023Oct/att-0001/Notifications_discussion_-_T PAC_2023.pdf)\n- [minutes](http://www.w3.org/2023/09/tpac-breakouts/18-min utes.pdf)\n- [live google doc minutes](https://docs.google.com/document/d/ 1QJ-zs7B9EHIolG_8RwwxwsUyr1FHRKe7bYscP9zOLus/edit)\n- [Session proposal on GitHub](https://github.com/w3c/tpac2023-breakouts/issues/18) STATUS:CONFIRMED CREATED:20230905T053655Z LAST-MODIFIED:20231012T082320Z SEQUENCE:2 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Lebrija - 1st floor CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:395680d5-1ed7-4127-91e2-48a855549965 DTSTAMP:20230923T163521Z SUMMARY:Sustainability in the digital world DTSTART;TZID=Europe/Madrid:20230913T093000 DTEND;TZID=Europe/Madrid:20230913T103000 DESCRIPTION:https://www.w3.org/events/meetings/395680d5-1ed7-4127-91e2-48a8 55549965/\n\nWhen we speak about sustainability and climate change\, we th ink about long-haul flights and solar panels. We do not realize that our d ay-to-day digital behavior\, like mindless scrolling\, dark vs bright back grounds\, and the online advertisements we see\, also contributes to our c arbon footprint. This open discussion is about how we\, the people on the web\, can build products and technologies that are sustainable and positiv ely impact the user behavior in a way that contributes to a greener enviro nment.\n\nAgenda: https://docs.google.com/document/d/1YlOjHoBQOvTIAN-rLTzR W4B7qbGEzOEXpgqzXQKeLQI/edit?usp=sharing\n\nAgenda\n\n**Chairs:**\nChristo s Bacharakis\, Dr. Humera Noor Minhas\, Cornelius Witt\n\n**Description:** \nWhen we speak about sustainability and climate change\, we think about l ong-haul flights and solar panels. We do not realize that our day-to-day d igital behavior\, like mindless scrolling\, dark vs bright backgrounds\, a nd the online advertisements we see\, also contributes to our carbon footp rint. This open discussion is about how we\, the people on the web\, can b uild products and technologies that are sustainable and positively impact the user behavior in a way that contributes to a greener environment.\n\n* *Goal(s):**\nUnderstand how we can build technologies and products that co ntribute to our fight against carbon emissions\n\n\n**Materials:**\n- [sli des](https://docs.google.com/presentation/d/1IlDWssKyJ8bUk3iOePgNeVXtTQCtj ru5N46lb-KK-WU/edit#slide=id.p1)\n- [minutes](http://www.w3.org/2023/09/tp ac-breakouts/73-minutes.pdf)\n- [live google doc minutes](https://docs.goo gle.com/document/d/1YlOjHoBQOvTIAN-rLTzRW4B7qbGEzOEXpgqzXQKeLQI/edit#headi ng=h.nlctw1ms1t7y)\n- [recording](https://www.w3.org/2023/09/breakouts/rec ording-73.html)\n- [Session proposal on GitHub](https://github.com/w3c/tpa c2023-breakouts/issues/73) STATUS:CONFIRMED CREATED:20230905T054151Z LAST-MODIFIED:20230923T163521Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Azalea - Low Level CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:ab0de26f-c84d-40b6-80a7-79f3020da3aa DTSTAMP:20230919T113237Z SUMMARY:Unleashing the Power of Computational Intelligence on the Web DTSTART;TZID=Europe/Madrid:20230913T093000 DTEND;TZID=Europe/Madrid:20230913T103000 DESCRIPTION:https://www.w3.org/events/meetings/ab0de26f-c84d-40b6-80a7-79f3 020da3aa/\n\nIn this session\, we will explore how the deployment of Compu tational Intelligence as a Service (CIaaS) is reshaping web technologies a nd impacting the global digital community. We will discuss essential web t echnologies underpinning CIaaS\, including cloud computing infrastructure\ , data analytics tools\, and advanced machine learning algorithms. Partici pants will gain insights into how these technologies drive computational i ntelligence capabilities on the web\, enhance user experiences\, and facil itate data-driven decision-making. The session will also provide a platfor m to foster dialogue\, exchange ideas\, and build a community centered aro und advancing the application of CIaaS on the web. Whether you are an indu stry practitioner\, a researcher\, or a tech enthusiast\, this session pro mises to enrich your understanding of the transformative power of computat ional intelligence on the web.\n\nAgenda\n\n**Chairs:**\nRachel Yager\, Ga briella Pasi\n\n**Description:**\nIn this session\, we will explore how th e deployment of Computational Intelligence as a Service (CIaaS) is reshapi ng web technologies and impacting the global digital community. We will di scuss essential web technologies underpinning CIaaS\, including cloud comp uting infrastructure\, data analytics tools\, and advanced machine learnin g algorithms. Participants will gain insights into how these technologies drive computational intelligence capabilities on the web\, enhance user ex periences\, and facilitate data-driven decision-making. The session will a lso provide a platform to foster dialogue\, exchange ideas\, and build a c ommunity centered around advancing the application of CIaaS on the web. Wh ether you are an industry practitioner\, a researcher\, or a tech enthusia st\, this session promises to enrich your understanding of the transformat ive power of computational intelligence on the web.\n\n**Goal(s):**\nThe o bjective of this session is to facilitate an open community discussion abo ut the challenges and impact of Computational Intelligence on the Web.\n\n \n**Materials:**\n- [minutes](https://www.w3.org/2023/09/13-computationali ntelligence-minutes.html)\n- [Session proposal on GitHub](https://github.c om/w3c/tpac2023-breakouts/issues/24)\n\n**Track(s):**\n- AI STATUS:CONFIRMED CREATED:20230905T053730Z LAST-MODIFIED:20230919T113237Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Ecija - 1st floor CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:4ade6562-701f-431a-a149-efec4e97cdc5 DTSTAMP:20231010T101732Z SUMMARY:Verifiable Credentials and Decentralized Identifiers in action DTSTART;TZID=Europe/Madrid:20230913T093000 DTEND;TZID=Europe/Madrid:20230913T103000 DESCRIPTION:https://www.w3.org/events/meetings/4ade6562-701f-431a-a149-efec 4e97cdc5/\n\n[Verifiable Credentials](https://www.w3.org/TR/vc-data-model/ ) and [Decentralized Identifiers](https://www.w3.org/TR/did-core/) have ga ined significant momentum since their publication as W3C recommendations. The goal of this breakout session is to provide a quick introduction to th ese technologies\, and showcase a number of their deployments.\n\n\n\n_Pos t-TPAC note: No minutes were taken at this session._\n\nAgenda\n\n**Chairs :**\nPierre-Antoine Champin\, Brent Zundel\n\n**Description:**\n[Verifiabl e Credentials](https://www.w3.org/TR/vc-data-model/) and [Decentralized Id entifiers](https://www.w3.org/TR/did-core/) have gained significant moment um since their publication as W3C recommendations. The goal of this breako ut session is to provide a quick introduction to these technologies\, and showcase a number of their deployments.\n\n\n\n_Post-TPAC note: No minutes were taken at this session._\n\n**Goal(s):**\nDemonstrate and discuss dep loyments of VCs and DIDs\n\n\n**Materials:**\n- [Session proposal on GitHu b](https://github.com/w3c/tpac2023-breakouts/issues/28)\n\n**Track(s):**\n - trust STATUS:CONFIRMED CREATED:20230905T053751Z LAST-MODIFIED:20231010T101732Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Santa Cruz - Level -1 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:e7043fa0-fb32-4470-8069-780ba0fadbc4 DTSTAMP:20230919T113124Z SUMMARY:Web Components API/Specs Report and Alignment DTSTART;TZID=Europe/Madrid:20230913T093000 DTEND;TZID=Europe/Madrid:20230913T103000 DESCRIPTION:https://www.w3.org/events/meetings/e7043fa0-fb32-4470-8069-780b a0fadbc4/\n\nThe [Web Components Community Group](https://github.com/w3c/w ebcomponents-cg) will share their 2023 report on the APIs and specs that a re deserving of prioritization across implementors in 2023 going into 2023 . This follows up on previous reports in [2021](https://w3c.github.io/webc omponents-cg/2021.html) and [2022](https://w3c.github.io/webcomponents-cg/ 2022.html). From there\, we will have an open discussion on how the commun ity group can support implementors in shipping\, coming to consensus\, or altering various specs in order to get them into the hands of developers a nd their site/application visitors in as prompt a manner as possible.\n\n\ n\n\n\n\n\nLast years discussion focused on [browser parity](https://w3c.g ithub.io/webcomponents-cg/2022.html#browser-parity) and [spec alignment](h ttps://w3c.github.io/webcomponents-cg/2022.html#spec-alignment). Implement or partnerships lead to x-browser support for Imperative Slotting and Cons tructible Stylesheets\, expanded support for Form Associated Custom Elemen ts\, and progress on CSS module scripts\, as well as the triumphant return of the Web Components Spring Face to Face (albiet virtual) to further flu sh out features like Cross-root Aria\, Scoped Registries\, and Declarative Shadow DOM. We look forward to what we can do in the next year as we cont inue to develop the relationship between implementors and web developers.\ n\nAgenda: https://w3c.github.io/webcomponents-cg/2023.html\n\nAgenda\n\n* *Chairs:**\nWestbrook Johnson\, Keith Cirkel\n\n**Description:**\nThe [Web Components Community Group](https://github.com/w3c/webcomponents-cg) will share their 2023 report on the APIs and specs that are deserving of prior itization across implementors in 2023 going into 2023. This follows up on previous reports in [2021](https://w3c.github.io/webcomponents-cg/2021.htm l) and [2022](https://w3c.github.io/webcomponents-cg/2022.html). From ther e\, we will have an open discussion on how the community group can support implementors in shipping\, coming to consensus\, or altering various spec s in order to get them into the hands of developers and their site/applica tion visitors in as prompt a manner as possible.\n\n\n\n\n\n\n\nLast years discussion focused on [browser parity](https://w3c.github.io/webcomponent s-cg/2022.html#browser-parity) and [spec alignment](https://w3c.github.io/ webcomponents-cg/2022.html#spec-alignment). Implementor partnerships lead to x-browser support for Imperative Slotting and Constructible Stylesheets \, expanded support for Form Associated Custom Elements\, and progress on CSS module scripts\, as well as the triumphant return of the Web Component s Spring Face to Face (albiet virtual) to further flush out features like Cross-root Aria\, Scoped Registries\, and Declarative Shadow DOM. We look forward to what we can do in the next year as we continue to develop the r elationship between implementors and web developers.\n\n**Goal(s):**\nAlig n implementors on high priority web component APIs for shipping in 2024\n\ n\n**Materials:**\n- [slides](https://webcomponents-cg.github.io/TPAC-2023 /WCCG/Overview.html?full)\n- [minutes](https://www.w3.org/2023/09/13-webco mponents-minutes.html)\n- [Session proposal on GitHub](https://github.com/ w3c/tpac2023-breakouts/issues/17)\n\n**Track(s):**\n- web components STATUS:CONFIRMED CREATED:20230905T053650Z LAST-MODIFIED:20230919T113124Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Estepa - 1st floor CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:25ca79ec-c756-4771-b61b-5c47fb0202b8 DTSTAMP:20230919T113113Z SUMMARY:After 50 years\, GS1 is replacing the barcode with QR codes. That m atters for devs\, for consumers\, for brands\, for retailers\, for trust o n the Web. DTSTART;TZID=Europe/Madrid:20230913T110000 DTEND;TZID=Europe/Madrid:20230913T120000 DESCRIPTION:https://www.w3.org/events/meetings/25ca79ec-c756-4771-b61b-5c47 fb0202b8/\n\nThe [first barcode went beep](https://americanhistory.si.edu/ collections/search/object/nmah_892778) at a checkout in Ohio almost 50 yea rs ago (1974-06-26T08:01:00+05:00). [GS1](https://www.gs1.org/)\, the glob al organization behind the numbering system embedded in billions of barcod es around the world\, is [working with industry to replace it](https://www .gs1.org/industries/retail/2D-barcodes) with higher-capacity\, more functi onal alternatives. You won't be surprised to learn that in many cases this will be a QR code that contains a URI. But the URI has additional structu re that encodes not just the basic product identifier but things like batc h numbers\, serial numbers\, expiry dates and more. The ambition is that b y the end of 2027\, the original 1970s barcode can begin to retire.\n\n\n\ n\n\n\n\nThis presents substantial opportunities for the Web. Some claim i t also presents opportunities for bad actors. This breakout session is abo ut:\n\n\n\n1. How do I recognize a "GS1 Digital Link URI" when I see it? ( example: https://example.com/01/09506000134352/10/ABC)\n\n\n\n2. What can I do with it? Linked Data? HATEOS? (try https://id.gs1.org/01/095060001343 52/10/ABC?linkType=all)\n\n\n\n3. Whaddyamean the domain name isn't part o f the identifier?? That's nuts! (it's also true)\n\n\n\n4. How does this t ie in with product conformance certificates\, trade digitization\, the for thcoming EU Digital Product Passport regulation\, traceability\, sustainab ility and generally 'selling more stuff'\n\n\n\n5. Ah\, forget it\, it's a URL so I can do what I like... (true)\n\nAgenda: https://github.com/w3c/t pac2023-breakouts/issues/16#issuecomment-1716035374\n\nAgenda\n\n**Chairs: **\nPhil Archer\n\n**Description:**\nThe [first barcode went beep](https:/ /americanhistory.si.edu/collections/search/object/nmah_892778) at a checko ut in Ohio almost 50 years ago (1974-06-26T08:01:00+05:00). [GS1](https:// www.gs1.org/)\, the global organization behind the numbering system embedd ed in billions of barcodes around the world\, is [working with industry to replace it](https://www.gs1.org/industries/retail/2D-barcodes) with highe r-capacity\, more functional alternatives. You won't be surprised to learn that in many cases this will be a QR code that contains a URI. But the UR I has additional structure that encodes not just the basic product identif ier but things like batch numbers\, serial numbers\, expiry dates and more . The ambition is that by the end of 2027\, the original 1970s barcode can begin to retire.\n\n\n\n\n\n\n\nThis presents substantial opportunities f or the Web. Some claim it also presents opportunities for bad actors. This breakout session is about:\n\n\n\n1. How do I recognize a "GS1 Digital Li nk URI" when I see it? (example: https://example.com/01/09506000134352/10/ ABC)\n\n\n\n2. What can I do with it? Linked Data? HATEOS? (try https://id .gs1.org/01/09506000134352/10/ABC?linkType=all)\n\n\n\n3. Whaddyamean the domain name isn't part of the identifier?? That's nuts! (it's also true)\n \n\n\n4. How does this tie in with product conformance certificates\, trad e digitization\, the forthcoming EU Digital Product Passport regulation\, traceability\, sustainability and generally 'selling more stuff'\n\n\n\n5. Ah\, forget it\, it's a URL so I can do what I like... (true)\n\n**Goal(s ):**\nTo discuss the future possibilities - good and bad - that the change to Web-enabled barcodes offer. How it ties in with DIDs and VCs\, and how it can be used to improve consumer experiences online.\n\n\n\n\n\n\n\nOne specific question: does putting URIs with additional structure into QR co des on millions of products create a massive security headache?\n\n\n**Mat erials:**\n- [slides](https://philarcher.org/gs1/files/2023/09/qr-gs1.pdf) \n- [minutes](https://www.w3.org/2023/09/13-qr-minutes.html)\n- [Session p roposal on GitHub](https://github.com/w3c/tpac2023-breakouts/issues/16) STATUS:CONFIRMED CREATED:20230905T053643Z LAST-MODIFIED:20230919T113113Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Giralda V - Level -2 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:c2342b95-4d80-47c3-893c-25f07f2d8eb2 DTSTAMP:20230919T113651Z SUMMARY:Beyond Interop: Baseline and more DTSTART;TZID=Europe/Madrid:20230913T110000 DTEND;TZID=Europe/Madrid:20230913T120000 DESCRIPTION:https://www.w3.org/events/meetings/c2342b95-4d80-47c3-893c-25f0 7f2d8eb2/\n\nWeb developers report that[ keeping up with changes to the pl atform is a major issue for them](https://web.dev/deep-dive-into-developer -pain-points/). Developers have difficulty keeping up with changes in the web platform\, such as the introduction of new features and the resolution of interoperability issues\, and knowing when features are well-establish ed in their users’ browsers.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nEven though many developers enjoy access to detailed information about their audiences and the browsers they use (e.g.\, through site analytics\, support metric s\, user interviews\, etc.)\, others don’t or work at a remove from end users. A new project won’t have a measurable audience until it launches. A library maintainer or application vendor might have\, at best\, an indi rect view of the capabilities of users’ browsers.\n\n\n\n\n\n\n\n\n\n\n\ n\n\n\n\nDespite the glut of information about browser support\, releases\ , and global usage\, these developers are left on their own to draw a plat form-wide support picture\, with ample opportunity for errors and confusio n. \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nThe Baseline project is one way that in tends to help these developers by offering a shortcut past the complexity. \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nThis session will discuss the lessons we l earned in the WebDX CG\, open questions we have\, and possible ways forwar d to serve the web developer community.\n\nAgenda\n\n**Chairs:**\nKadir To pal\n\n**Description:**\nWeb developers report that[ keeping up with chang es to the platform is a major issue for them](https://web.dev/deep-dive-in to-developer-pain-points/). Developers have difficulty keeping up with cha nges in the web platform\, such as the introduction of new features and th e resolution of interoperability issues\, and knowing when features are we ll-established in their users’ browsers.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n Even though many developers enjoy access to detailed information about the ir audiences and the browsers they use (e.g.\, through site analytics\, su pport metrics\, user interviews\, etc.)\, others don’t or work at a remo ve from end users. A new project won’t have a measurable audience until it launches. A library maintainer or application vendor might have\, at be st\, an indirect view of the capabilities of users’ browsers.\n\n\n\n\n\ n\n\n\n\n\n\n\n\n\n\nDespite the glut of information about browser support \, releases\, and global usage\, these developers are left on their own to draw a platform-wide support picture\, with ample opportunity for errors and confusion. \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nThe Baseline project is one way that intends to help these developers by offering a shortcut past the complexity.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nThis session will discuss the lessons we learned in the WebDX CG\, open questions we have\, and possible ways forward to serve the web developer community.\n\n**Goal(s):**\nBroad er awareness of the problem that is being addressed and identifying ideas that are worth exploring further\n\n\n**Materials:**\n- [slides](https://l ists.w3.org/Archives/Public/www-archive/2023Sep/att-0011/Beyond_Interop_Ba seline_and_more.pdf)\n- [minutes](https://www.w3.org/2023/09/13-beyond-int erop-minutes.html)\n- [Session proposal on GitHub](https://github.com/w3c/ tpac2023-breakouts/issues/60)\n\n**Track(s):**\n- developer experience STATUS:CONFIRMED CREATED:20230905T054036Z LAST-MODIFIED:20230919T113651Z SEQUENCE:2 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Nervion-Arenal II - Level -1 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:791150bf-5a8d-4fe8-a38f-51a1cc821862 DTSTAMP:20230921T103405Z SUMMARY:Collaboration between W3C and Ecma International DTSTART;TZID=Europe/Madrid:20230913T110000 DTEND;TZID=Europe/Madrid:20230913T120000 DESCRIPTION:https://www.w3.org/events/meetings/791150bf-5a8d-4fe8-a38f-51a1 cc821862/\n\nECMAScript is core to the Web Platform\, so collaboration bet ween the W3C and Ecma International has been key for many evolution initia tives on both sides. Ecma TC39\, the committee were ECMAScript (a.k.a. JS) is standardized\, has an efficient and inclusive process for standards de velopment\, which shares many qualities with the W3C process.\n\n\n\n\n\n\ n\nThe organizations have a formal liaison relationship (enabling represen tatives of one organization to participate in the other\, for example)\, b ut on the ground\, Ecma TC39 has relied heavily on certain individuals in each organization to bridge the gaps. Many TC39 proposals have significant architectural impact on the Web Platform\, and these impacts have been re viewed in WHATWG HTML threads as well as W3C TAG reviews.\n\n\n\n\n\n\n\nL ike the W3C\, Ecma is expanding in its work areas. For example\, Ecma has a new initiative to standardize source maps in TC39-TG4. Overall\, new wor k in the web space within Ecma tends to take TC39's success as a model to repeat. This is going well for source maps so far.\n\n\n\n\n\n\n\nThe idea of this session is to start with a short presentation of where Ecma and T C39 are today and how we work together\, and then proceed to an open discu ssion about how we can work in the future\, in what areas and working mode s\, etc.\n\nAgenda: https://github.com/w3c/tpac2023-breakouts/issues/38#is suecomment-1716997295\n\nAgenda\n\n**Chairs:**\nDaniel Ehrenberg\, Samina Husain\n\n**Description:**\nECMAScript is core to the Web Platform\, so co llaboration between the W3C and Ecma International has been key for many e volution initiatives on both sides. Ecma TC39\, the committee were ECMAScr ipt (a.k.a. JS) is standardized\, has an efficient and inclusive process f or standards development\, which shares many qualities with the W3C proces s.\n\n\n\n\n\n\n\nThe organizations have a formal liaison relationship (en abling representatives of one organization to participate in the other\, f or example)\, but on the ground\, Ecma TC39 has relied heavily on certain individuals in each organization to bridge the gaps. Many TC39 proposals h ave significant architectural impact on the Web Platform\, and these impac ts have been reviewed in WHATWG HTML threads as well as W3C TAG reviews.\n \n\n\n\n\n\n\nLike the W3C\, Ecma is expanding in its work areas. For exam ple\, Ecma has a new initiative to standardize source maps in TC39-TG4. Ov erall\, new work in the web space within Ecma tends to take TC39's success as a model to repeat. This is going well for source maps so far.\n\n\n\n\ n\n\n\nThe idea of this session is to start with a short presentation of w here Ecma and TC39 are today and how we work together\, and then proceed t o an open discussion about how we can work in the future\, in what areas a nd working modes\, etc.\n\n**Goal(s):**\nIdentify areas and ways to work t ogether in the future\n\n\n**Materials:**\n- [slides](https://docs.google. com/presentation/d/13hTQM2iVsAObKQ5XoJ2n0WJ32JhHGqsJ-xmumL8oH6s/edit)\n- [ recording](https://www.w3.org/2023/09/breakouts/recording-38.html)\n- [Ses sion proposal on GitHub](https://github.com/w3c/tpac2023-breakouts/issues/ 38) STATUS:CONFIRMED CREATED:20230905T053846Z LAST-MODIFIED:20230921T103405Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Triana - Level -1 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:16be075a-4b62-4712-bff5-5d3b509746f1 DTSTAMP:20230923T163129Z SUMMARY:Page Embedded Permission Control (Permission Element) DTSTART;TZID=Europe/Madrid:20230913T110000 DTEND;TZID=Europe/Madrid:20230913T120000 DESCRIPTION:https://www.w3.org/events/meetings/16be075a-4b62-4712-bff5-5d3b 509746f1/\n\nMost user interactions on permission prompts are negative. Fo r notifications (the most requested permission type)\, Google Chrome metri cs data shows that the percentage of prompts that are ignored\, dismissed or blocked by the user add up to approx 92% on desktop platforms and 85% o n mobile devices. \n\n\n\n\n\n\n\nA permission model designed to be initia ted by the user would solve these issues. If the user initiates the permis sion request it ensures that:\n\n\n\n\n\n\n\n- The user understands the pu rpose of the permission\, or at least has enough context to feel comfortab le engaging in an activity that uses this permission.\n\n\n\n- The user’ s current flow or task is related to granting this permission and as such it’s unlikely that the permission request could be interruptive.\n\n\n\n - The user agent can ensure the subsequent UI is placed near the current f ocus of attention of the user. This is because the user has just interacte d with some piece of UI to request the permission which means their focus is likely in the area. Because of the above\, it is unlikely that such a p lacement is interruptive or annoying.\n\n\n\n\n\nThis breakout would discu ss a proposal for Permission Embedded Permission Control [[explainer](http s://github.com/andypaicu/PEPC/blob/main/explainer.md)] [[deck](https://doc s.google.com/presentation/d/1fzMEeyWbdpBS7HN9WumIOSbqB3pl-MG2DTo_5-lvgus/e dit#slide=id.g27df7eff9c5_0_226)] and intends to continue the dialog from the [w3c Workshop on Permissions](https://www.w3.org/Privacy/permissions-w s-2022/report#beyond-prompts) held December 2022.\n\n\n\nSession [notes](h ttps://docs.google.com/document/d/1pJFCADgasiqojESz2VePkVwaDdlfDqpN5JSqo4T 4mMs/edit#heading=h.ocs3ne1w3v4g)\n\nAgenda\n\n**Chairs:**\nPenelope McLac hlan\n\n**Description:**\nMost user interactions on permission prompts are negative. For notifications (the most requested permission type)\, Google Chrome metrics data shows that the percentage of prompts that are ignored \, dismissed or blocked by the user add up to approx 92% on desktop platfo rms and 85% on mobile devices. \n\n\n\n\n\n\n\nA permission model designed to be initiated by the user would solve these issues. If the user initiat es the permission request it ensures that:\n\n\n\n\n\n\n\n- The user under stands the purpose of the permission\, or at least has enough context to f eel comfortable engaging in an activity that uses this permission.\n\n\n\n - The user’s current flow or task is related to granting this permission and as such it’s unlikely that the permission request could be interrup tive.\n\n\n\n- The user agent can ensure the subsequent UI is placed near the current focus of attention of the user. This is because the user has j ust interacted with some piece of UI to request the permission which means their focus is likely in the area. Because of the above\, it is unlikely that such a placement is interruptive or annoying.\n\n\n\n\n\nThis breakou t would discuss a proposal for Permission Embedded Permission Control [[ex plainer](https://github.com/andypaicu/PEPC/blob/main/explainer.md)] [[deck ](https://docs.google.com/presentation/d/1fzMEeyWbdpBS7HN9WumIOSbqB3pl-MG2 DTo_5-lvgus/edit#slide=id.g27df7eff9c5_0_226)] and intends to continue the dialog from the [w3c Workshop on Permissions](https://www.w3.org/Privacy/ permissions-ws-2022/report#beyond-prompts) held December 2022.\n\n\n\nSess ion [notes](https://docs.google.com/document/d/1pJFCADgasiqojESz2VePkVwaDd lfDqpN5JSqo4T4mMs/edit#heading=h.ocs3ne1w3v4g)\n\n**Goal(s):**\nFeedback o n a proposal to create a Page Embedded Permission Control (Permission Elem ent)\n\n\n**Materials:**\n- [slides](https://docs.google.com/presentation/ d/1fzMEeyWbdpBS7HN9WumIOSbqB3pl-MG2DTo_5-lvgus/edit#slide=id.g27df7eff9c5_ 0_226)\n- [minutes](http://www.w3.org/2023/09/tpac-breakouts/35-minutes.pd f)\n- [live google doc minutes](https://docs.google.com/document/d/1pJFCAD gasiqojESz2VePkVwaDdlfDqpN5JSqo4T4mMs/edit#heading=h.ocs3ne1w3v4g)\n- [Ses sion proposal on GitHub](https://github.com/w3c/tpac2023-breakouts/issues/ 35)\n\n**Track(s):**\n- privacy STATUS:CONFIRMED CREATED:20230905T053831Z LAST-MODIFIED:20230923T163129Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Giralda III - Level -2 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:e5cc2d3f-6da6-4751-9417-18b80a524893 DTSTAMP:20230923T162856Z SUMMARY:Scoped Custom Element Registry DTSTART;TZID=Europe/Madrid:20230913T110000 DTEND;TZID=Europe/Madrid:20230913T120000 DESCRIPTION:https://www.w3.org/events/meetings/e5cc2d3f-6da6-4751-9417-18b8 0a524893/\n\nThis session discusses [scoped custom element registry propos al](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-C ustom-Element-Registries.md).\n\nAgenda\n\n**Chairs:**\nRyosuke Niwa\n\n** Description:**\nThis session discusses [scoped custom element registry pro posal](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scope d-Custom-Element-Registries.md).\n\n**Goal(s):**\nCome up with a concrete spec proposal / PR with multi-vendor support\n\n\n**Materials:**\n- [minut es](http://www.w3.org/2023/09/tpac-breakouts/15-minutes.pdf)\n- [live goog le doc minutes](https://docs.google.com/document/d/1e1anpmGiYyAHZYg7oRkLVs GrqYWTjFCKSqyjp8p9n4I/edit#heading=h.lnl9lfwg4kxd)\n- [Session proposal on GitHub](https://github.com/w3c/tpac2023-breakouts/issues/15)\n\n**Track(s ):**\n- web components STATUS:CONFIRMED CREATED:20230905T053634Z LAST-MODIFIED:20230923T162856Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Estepa - 1st floor CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:f5d2712b-a0bc-4529-90df-621f69e0d3ed DTSTAMP:20230919T113011Z SUMMARY:Technical Roadmap at W3C DTSTART;TZID=Europe/Madrid:20230913T110000 DTEND;TZID=Europe/Madrid:20230913T120000 DESCRIPTION:https://www.w3.org/events/meetings/f5d2712b-a0bc-4529-90df-621f 69e0d3ed/\n\nThis session will go over [ongoing strategy issues](https://g ithub.com/w3c/strategy/issues) and discuss how we could engage with the co mmunity on strategy.\n\nAgenda\n\n**Chairs:**\nPhilippe Le Hegaret\n\n**De scription:**\nThis session will go over [ongoing strategy issues](https:// github.com/w3c/strategy/issues) and discuss how we could engage with the c ommunity on strategy.\n\n**Goal(s):**\nDefining how to evolve the technica l roadmap of W3C\n\n\n**Materials:**\n- [slides](https://www.w3.org/2023/T alks/TPAC/bk-technical-roadmap/)\n- [minutes](https://www.w3.org/2023/09/1 3-techroad-minutes.html)\n- [Session proposal on GitHub](https://github.co m/w3c/tpac2023-breakouts/issues/9)\n\n**Track(s):**\n- getting work done STATUS:CONFIRMED CREATED:20230905T053558Z LAST-MODIFIED:20230919T113011Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Magnolia - Low Level CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:53380d18-eb3f-47f2-a6ac-435ce6294e0c DTSTAMP:20230919T112943Z SUMMARY:The Impact of Generative AI on the Web DTSTART;TZID=Europe/Madrid:20230913T110000 DTEND;TZID=Europe/Madrid:20230913T120000 DESCRIPTION:https://www.w3.org/events/meetings/53380d18-eb3f-47f2-a6ac-435c e6294e0c/\n\nIn this session\, we will discuss the possible impacts of gen erative AI on the Web. As it is an emerging topic and its consequences sti ll need to be better understood\, we will focus on technical and governanc e challenges in three main dimensions: data collection on the Web\, Integr ation of LLMs in a search engine\; production and publication of synthetic contents on the Web.\n\n\n\n\n\n\n\nTo facilitate the discussion\, we wil l start from three main questions\, which can be discussed in different gr oups depending on the number of participants:\n\n\n\n\n\n\n\n- What are th e limits of scraping web data to train Generative AI and what technical me asures should be implemented to ensure privacy\, prevent copyright infring ement\, and effectively manage content creator consent?\n\n\n\n\n\n\n\n- W hat are the potential impacts of incorporating LLMs (Large Language Models ) as chatbot interfaces into search engines? How would this change the web traffic and digital economy once the chatbot could respond directly to us ers instead of providing links?\n\n\n\n\n\n\n\n- How could Web technologie s help detect AI-generated content posted on the Web\, restrain the dissem ination of sensitive content\, and provide accountability?__\n\nAgenda\n\n **Chairs:**\nDiogo Cortiz\, Reinaldo Ferraz\, Vagner Diniz\n\n**Descriptio n:**\nIn this session\, we will discuss the possible impacts of generative AI on the Web. As it is an emerging topic and its consequences still need to be better understood\, we will focus on technical and governance chall enges in three main dimensions: data collection on the Web\, Integration o f LLMs in a search engine\; production and publication of synthetic conten ts on the Web.\n\n\n\n\n\n\n\nTo facilitate the discussion\, we will start from three main questions\, which can be discussed in different groups de pending on the number of participants:\n\n\n\n\n\n\n\n- What are the limit s of scraping web data to train Generative AI and what technical measures should be implemented to ensure privacy\, prevent copyright infringement\, and effectively manage content creator consent?\n\n\n\n\n\n\n\n- What are the potential impacts of incorporating LLMs (Large Language Models) as ch atbot interfaces into search engines? How would this change the web traffi c and digital economy once the chatbot could respond directly to users ins tead of providing links?\n\n\n\n\n\n\n\n- How could Web technologies help detect AI-generated content posted on the Web\, restrain the dissemination of sensitive content\, and provide accountability?__\n\n**Goal(s):**\nThe session aims to introduce the theme and discuss the possible consequences of Generative AI for the Web. We also want to stimulate a debate with p eople from different backgrounds on how Web technologies should respond to those changes. We also plan to elaborate and consolidate the result of the session to guide further discussion on the topic.\n\n\n**Materials:**\ n- [minutes](https://www.w3.org/2023/09/13-GenerativeAI-minutes.html)\n- [ Session proposal on GitHub](https://github.com/w3c/tpac2023-breakouts/issu es/6)\n\n**Track(s):**\n- AI STATUS:CONFIRMED CREATED:20230905T053538Z LAST-MODIFIED:20230919T112943Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Ecija - 1st floor CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:972d3fe0-ceab-42bf-9be7-1205179af501 DTSTAMP:20230919T113320Z SUMMARY:Updates on the "Trustable Internet" project DTSTART;TZID=Europe/Madrid:20230913T110000 DTEND;TZID=Europe/Madrid:20230913T120000 DESCRIPTION:https://www.w3.org/events/meetings/972d3fe0-ceab-42bf-9be7-1205 179af501/\n\nThis session will introduce updates for the Trustable Interne t (formerly Trusted Internet) project and discuss standardization aspects. We are trying to materialize Trustable Internet that makes data on the In ternet more trustworthy. Last year\, we introduced a concept that assemble s an endorsement overlay layer on top of the Internet (or the Web). The en dorsement layer has additional information (endorsement data) for data on the Internet that desires "endorsement\," such as Social Network posts\, t o provide additional information to viewers to judge the credibility of th e data. After the last W3C TPAC\, we published a white paper \, then demonstrated a prototype implementation based on the concept menti oned in the above at IETF 116\, March 2023. We are refining the data model and the systems architecture of the overlay\,\n\nAgenda: https://github.c om/y-sakuma-fjlab/ti_tpac2023_breakout/tree/main\n\nAgenda\n\n**Chairs:**\ nYoshitomo Sakuma\, Shigeya Suzuki\n\n**Description:**\nThis session will introduce updates for the Trustable Internet (formerly Trusted Internet) p roject and discuss standardization aspects. We are trying to materialize T rustable Internet that makes data on the Internet more trustworthy. Last y ear\, we introduced a concept that assembles an endorsement overlay layer on top of the Internet (or the Web). The endorsement layer has additional information (endorsement data) for data on the Internet that desires "endo rsement\," such as Social Network posts\, to provide additional informatio n to viewers to judge the credibility of the data. After the last W3C TPAC \, we published a white paper\, then demonstrated a prototyp e implementation based on the concept mentioned in the above at IETF 116\, March 2023. We are refining the data model and the systems architecture o f the overlay\,\n\n**Goal(s):**\nGet feedback on the activity\, and find o ut possibilities of standardization on some of the components used in the overlay architecture.\n\n\n**Materials:**\n- [slides](https://github.com/y -sakuma-fjlab/ti_tpac2023_breakout/blob/main/W3CTPAC_TrustableInternet.pdf )\n- [minutes](https://www.w3.org/2023/09/13-trustable-internet-minutes.ht ml)\n- [Session proposal on GitHub](https://github.com/w3c/tpac2023-breako uts/issues/30)\n\n**Track(s):**\n- trust STATUS:CONFIRMED CREATED:20230905T053802Z LAST-MODIFIED:20230919T113320Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Santa Cruz - Level -1 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:04553884-088e-41b5-9a16-5e46caca6c55 DTSTAMP:20230919T113617Z SUMMARY:Vector graphics and animations DTSTART;TZID=Europe/Madrid:20230913T110000 DTEND;TZID=Europe/Madrid:20230913T120000 DESCRIPTION:https://www.w3.org/events/meetings/04553884-088e-41b5-9a16-5e46 caca6c55/\n\nExploration of the modern use cases for web vector graphics\, the current solutions and their limitations\, and potential future improv ements. Responsive vector graphics. Parametric Shapes. Better CSS integrat ion.\n\nAgenda\n\n**Chairs:**\nFernando Serboncini\, Chris Harrelson\n\n** Description:**\nExploration of the modern use cases for web vector graphic s\, the current solutions and their limitations\, and potential future imp rovements. Responsive vector graphics. Parametric Shapes. Better CSS integ ration.\n\n**Goal(s):**\nFigure out potential plan for vector graphics mov ing forward\n\n\n**Materials:**\n- [slides](https://docs.google.com/docume nt/d/1mMdmuXMUamXtNtiPgzj6Jg5XDmFshkiXNYqg-W2jzLI/edit)\n- [minutes](https ://www.w3.org/2023/09/13-vector-graphics-minutes.html)\n- [Session proposa l on GitHub](https://github.com/w3c/tpac2023-breakouts/issues/55) STATUS:CONFIRMED CREATED:20230905T054010Z LAST-MODIFIED:20230919T113617Z SEQUENCE:3 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Azalea - Low Level CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:ae47e209-26bf-44f3-8ac8-7936879c979d DTSTAMP:20230926T140459Z SUMMARY:W3C Accessibility Maturity Model Update DTSTART;TZID=Europe/Madrid:20230913T110000 DTEND;TZID=Europe/Madrid:20230913T120000 DESCRIPTION:https://www.w3.org/events/meetings/ae47e209-26bf-44f3-8ac8-7936 879c979d/\n\nW3C Accessibility Maturity Model Task Force will present an u pdate on our latest public working draft (https://www.w3.org/TR/maturity-m odel/)\, and our last 2 years of work. We will answer questions from parti cipants\, and present real world examples of our model being put to use.\n \nAgenda\n\n**Chairs:**\nDavid Fazio\n\n**Description:**\nW3C Accessibilit y Maturity Model Task Force will present an update on our latest public wo rking draft (https://www.w3.org/TR/maturity-model/)\, and our last 2 years of work. We will answer questions from participants\, and present real wo rld examples of our model being put to use.\n\n**Goal(s):**\nProvide a W3C Accessibility Maturity Model update\n\n\n**Materials:**\n- [minutes](http s://www.w3.org/2023/09/13-Maturity-minutes.html)\n- [recording](https://ww w.w3.org/2023/09/breakouts/recording-48.html)\n- [Session proposal on GitH ub](https://github.com/w3c/tpac2023-breakouts/issues/48)\n\n**Track(s):**\ n- accessibility STATUS:CONFIRMED CREATED:20230905T053941Z LAST-MODIFIED:20230926T140459Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Prado - Level -1 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:9629039f-522a-4578-a06c-561cf26b7e8d DTSTAMP:20230919T113446Z SUMMARY:WebRTC use cases and requirements under high-demanding real-time co mmunication scenarios DTSTART;TZID=Europe/Madrid:20230913T110000 DTEND;TZID=Europe/Madrid:20230913T120000 DESCRIPTION:https://www.w3.org/events/meetings/9629039f-522a-4578-a06c-561c f26b7e8d/\n\nWebRTC has been playing an increasingly important role in mor e high-demanding scenarios. As the industry is exploring innovative ways t o leverage WebRTC\, they also identify some potential issues and requireme nts for this technology. \n\n\n\nThis session is proposed by a few real-ti me communication service providers (including clouding service provider\, mobile operators\, social network platforms\, e-commerce platforms\, etc) and they would like to share the use cases\, development experiences\, pai n points\, and discuss possible solutions with global WebRTC community.\n\ n\n\nSee [current proposal](https://github.com/webrtc-live-streaming-tf/we brtc-use-cases).\n\nAgenda\n\n**Chairs:**\nLin Li\, Shishen Zhang\n\n**Des cription:**\nWebRTC has been playing an increasingly important role in mor e high-demanding scenarios. As the industry is exploring innovative ways t o leverage WebRTC\, they also identify some potential issues and requireme nts for this technology. \n\n\n\nThis session is proposed by a few real-ti me communication service providers (including clouding service provider\, mobile operators\, social network platforms\, e-commerce platforms\, etc) and they would like to share the use cases\, development experiences\, pai n points\, and discuss possible solutions with global WebRTC community.\n\ n\n\nSee [current proposal](https://github.com/webrtc-live-streaming-tf/we brtc-use-cases).\n\n**Goal(s):**\n- introduce the industry use cases and i mplementation practices of WebRTC under scenarios such as live streaming w ebcast \n\n\n\n- share the development experiences\, especially pain point s of WebRTC implementation\n\n\n\n- discuss and propose possible solutions \, such as an API for fixed GOP length\, XR standardization for RTT calcul ation on receiving end\, etc\n\n\n**Materials:**\n- [slides](https://www.w 3.org/2023/07/breakout_high_demanding_RTC_TPAC/high_demanding_RTC.pdf)\n- [minutes](https://www.w3.org/2023/09/13-WebRTC-usecases-minutes.html)\n- [ Session proposal on GitHub](https://github.com/w3c/tpac2023-breakouts/issu es/41)\n\n**Track(s):**\n- performance STATUS:CONFIRMED CREATED:20230905T053903Z LAST-MODIFIED:20230919T113446Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Nervion I - Level -1 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:8d0475f0-f133-4fc7-87f8-0493024263a8 DTSTAMP:20230928T055958Z SUMMARY:Working Together With the AB DTSTART;TZID=Europe/Madrid:20230913T110000 DTEND;TZID=Europe/Madrid:20230913T120000 DESCRIPTION:https://www.w3.org/events/meetings/8d0475f0-f133-4fc7-87f8-0493 024263a8/\n\nAn overview of AB projects and priorities\, focusing on those to which W3C Members\, Team\, and IEs are invited and encouraged to parti cipate. These include:\n\n\n\n* [W3C Process](https://www.w3.org/Consortiu m/Process/) and [Process CG](https://www.w3.org/community/w3process/)\n\n* [Vision](https://w3c.github.io/AB-public/Vision)\n\n* [Incubation](https: //github.com/w3c/AB-memberonly/issues/81)\n\n* [Code of Conduct](https://w ww.w3.org/Consortium/cepc/) and [PWE CG](https://www.w3.org/community/pwe/ )\n\n\n\n_Post-TPAC note: This session did not take place._\n\nAgenda\n\n* *Chairs:**\nTzviya Siegman\, Wendy Reid\, Chris Wilson\n\n**Description:** \nAn overview of AB projects and priorities\, focusing on those to which W 3C Members\, Team\, and IEs are invited and encouraged to participate. The se include:\n\n\n\n* [W3C Process](https://www.w3.org/Consortium/Process/) and [Process CG](https://www.w3.org/community/w3process/)\n\n* [Vision](h ttps://w3c.github.io/AB-public/Vision)\n\n* [Incubation](https://github.co m/w3c/AB-memberonly/issues/81)\n\n* [Code of Conduct](https://www.w3.org/C onsortium/cepc/) and [PWE CG](https://www.w3.org/community/pwe/)\n\n\n\n_P ost-TPAC note: This session did not take place._\n\n**Goal(s):**\nShare in formation about how general membership can contribute to the work of the A dvisory Board\n\n\n**Materials:**\n- [Session proposal on GitHub](https:// github.com/w3c/tpac2023-breakouts/issues/29) STATUS:CONFIRMED CREATED:20230905T053756Z LAST-MODIFIED:20230928T055958Z SEQUENCE:2 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Lebrija - 1st floor CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:8fa37b1e-563b-4b1c-8729-3f371d774780 DTSTAMP:20230928T055753Z SUMMARY:Cookie Layering Working Session DTSTART;TZID=Europe/Madrid:20230913T121500 DTEND;TZID=Europe/Madrid:20230913T131500 DESCRIPTION:https://www.w3.org/events/meetings/8fa37b1e-563b-4b1c-8729-3f37 1d774780/\n\nFollowing up on [last year's breakout session on cookies](htt ps://docs.google.com/presentation/d/1RWEEt3eO7hfQF5jkm3GdpkCEeR6yBWmbnlg_u aGkwwE/edit#slide=id.p) we want to start hacking on [cookie layering](http s://github.com/httpwg/http-extensions/issues/2084) and make it more concre te.\n\n\n\nWe're aiming for a focused working session\, not a presentation or large group discussion.\n\n\n\n_Post-TPAC note: No minutes were taken at this session. Participants collectively [drafted some of the algorithms ](https://gist.github.com/annevk/b6784a10dab2d1c0684f253f225603b0) that co uld end up in Fetch and in the Cookie RFC._\n\nAgenda\n\n**Chairs:**\nJoha nn Hofmann\, Anne van Kesteren\n\n**Description:**\nFollowing up on [last year's breakout session on cookies](https://docs.google.com/presentation/d /1RWEEt3eO7hfQF5jkm3GdpkCEeR6yBWmbnlg_uaGkwwE/edit#slide=id.p) we want to start hacking on [cookie layering](https://github.com/httpwg/http-extensio ns/issues/2084) and make it more concrete.\n\n\n\nWe're aiming for a focus ed working session\, not a presentation or large group discussion.\n\n\n\n _Post-TPAC note: No minutes were taken at this session. Participants colle ctively [drafted some of the algorithms](https://gist.github.com/annevk/b6 784a10dab2d1c0684f253f225603b0) that could end up in Fetch and in the Cook ie RFC._\n\n**Goal(s):**\nProduce tentative modifications to Fetch and Coo kies\n\n\n**Materials:**\n- [Session proposal on GitHub](https://github.co m/w3c/tpac2023-breakouts/issues/4)\n\n**Track(s):**\n- privacy STATUS:CONFIRMED CREATED:20230905T053531Z LAST-MODIFIED:20230928T055753Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Giralda III - Level -2 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:7ea3022f-4424-45da-ba98-2953baf7d997 DTSTAMP:20230923T163319Z SUMMARY:Cross-Browser Automated Accessibility Testing in WPT Interop 2023 a nd Beyond DTSTART;TZID=Europe/Madrid:20230913T121500 DTEND;TZID=Europe/Madrid:20230913T131500 DESCRIPTION:https://www.w3.org/events/meetings/7ea3022f-4424-45da-ba98-2953 baf7d997/\n\nThe [Interop 2023 Accessibility Investigation](https://github .com/web-platform-tests/interop-2023-accessibility-testing) has yielded a new implementation-independent accessibility testing infrastructure\, and [over 500 new automated accessibility tests](https://wpt.fyi/results/?labe l=master&label=experimental&aligned&q=label%3Aaccessibility)… And we are n't done yet. \n\n\n\n\n\n\n\nIn 2023\, contributors from Apple\, Mozilla\ , Google\, Bocoup\, Igalia\, Adobe\, and more kickstarted new work that is now actively running in every major browser engine.\n\n\n\n\n\n\n\nCome h ear a summary of [the work so far](https://github.com/web-platform-tests/i nterop-2023-accessibility-testing/issues/3)\, learn how to contribute new tests\, and discuss future proposals (such as [AOM #197](https://github.co m/WICG/aom/issues/197)) for improving automated\, sustainable accessibilit y testing beyond what is possible today.\n\nAgenda: https://github.com/web -platform-tests/interop-2023-accessibility-testing/issues/59\n\nAgenda\n\n **Chairs:**\nJames Craig\n\n**Description:**\nThe [Interop 2023 Accessibil ity Investigation](https://github.com/web-platform-tests/interop-2023-acce ssibility-testing) has yielded a new implementation-independent accessibil ity testing infrastructure\, and [over 500 new automated accessibility tes ts](https://wpt.fyi/results/?label=master&label=experimental&aligned&q=lab el%3Aaccessibility)… And we aren't done yet. \n\n\n\n\n\n\n\nIn 2023\, c ontributors from Apple\, Mozilla\, Google\, Bocoup\, Igalia\, Adobe\, and more kickstarted new work that is now actively running in every major brow ser engine.\n\n\n\n\n\n\n\nCome hear a summary of [the work so far](https: //github.com/web-platform-tests/interop-2023-accessibility-testing/issues/ 3)\, learn how to contribute new tests\, and discuss future proposals (suc h as [AOM #197](https://github.com/WICG/aom/issues/197)) for improving aut omated\, sustainable accessibility testing beyond what is possible today.\ n\n**Goal(s):**\nGather feedback on current automated accessibility testin g\, and extension proposals for WebDriver and other test interfaces…\n\n \n**Materials:**\n- [minutes](https://www.w3.org/2023/09/13-interop-2023-a 11y-minutes.html)\n- [Session proposal on GitHub](https://github.com/w3c/t pac2023-breakouts/issues/53)\n\n**Track(s):**\n- accessibility STATUS:CONFIRMED CREATED:20230905T054005Z LAST-MODIFIED:20230923T163319Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Prado - Level -1 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:27a383b4-c8ae-4246-8641-1e757488d4d6 DTSTAMP:20230923T162849Z SUMMARY:DOM / Template Parts API DTSTART;TZID=Europe/Madrid:20230913T121500 DTEND;TZID=Europe/Madrid:20230913T131500 DESCRIPTION:https://www.w3.org/events/meetings/27a383b4-c8ae-4246-8641-1e75 7488d4d6/\n\nThis is a session to discuss DOM / Template Parts API propose d in https://github.com/WICG/webcomponents/blob/gh-pages/proposals/DOM-Par ts.md.\n\n\n\nProposals:\n\n- [DOM Parts Declarative API](https://github.c om/WICG/webcomponents/blob/gh-pages/proposals/DOM-Parts-Declarative-Templa te.md)\n\n- [DOM Parts Imperative API](https://github.com/WICG/webcomponen ts/blob/gh-pages/proposals/DOM-Parts-Imperative.md)\n\nAgenda\n\n**Chairs: **\nRyosuke Niwa\n\n**Description:**\nThis is a session to discuss DOM / T emplate Parts API proposed in https://github.com/WICG/webcomponents/blob/g h-pages/proposals/DOM-Parts.md.\n\n\n\nProposals:\n\n- [DOM Parts Declarat ive API](https://github.com/WICG/webcomponents/blob/gh-pages/proposals/DOM -Parts-Declarative-Template.md)\n\n- [DOM Parts Imperative API](https://gi thub.com/WICG/webcomponents/blob/gh-pages/proposals/DOM-Parts-Imperative.m d)\n\n**Goal(s):**\nMake a progress towards making a spec / spec PR\n\n\n* *Materials:**\n- [minutes](http://www.w3.org/2023/09/tpac-breakouts/13-min utes.pdf)\n- [live google doc minutes](https://docs.google.com/document/d/ 1ZmKfLXGvgmoF0p_gZMngCic3pLv7IJyD3TIgBZVKP0g/edit)\n- [Session proposal on GitHub](https://github.com/w3c/tpac2023-breakouts/issues/13)\n\n**Track(s ):**\n- web components STATUS:CONFIRMED CREATED:20230905T053626Z LAST-MODIFIED:20230923T162849Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Estepa - 1st floor CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:9f1667d4-a23b-4893-80aa-06d5ecca8434 DTSTAMP:20230923T163515Z SUMMARY:Ethical AI in a Rapidly Evolving Landscape - deep dive DTSTART;TZID=Europe/Madrid:20230913T121500 DTEND;TZID=Europe/Madrid:20230913T131500 DESCRIPTION:https://www.w3.org/events/meetings/9f1667d4-a23b-4893-80aa-06d5 ecca8434/\n\nHave you ever wondered if AI Ethics is an Engineering or a Pr oduct issue? Which software development life cycle phase should you start addressing ethics in your AI system? How do we ensure that ethics are inte grated into the solutions by design and not only implemented on top as an afterthought? \n\n\n\n\n\n\n\nAddressing the need for fairness and accountability in AI\, this talk will explore our efforts to navigate cutt ing-edge technology while ensuring the ethical development of AI solutions . We will examine the requisite shift in perspective and straightforward\, actionable measures that empower enterprises to seamlessly infuse ethical AI into their core values\, steering clear of prevalent pitfalls.\n\nAgen da: https://docs.google.com/document/d/1od0BwLAHxemYRtJnsR7cf8fL7t9z-9RoNm uMVPTdl3o/edit\n\nAgenda\n\n**Chairs:**\nChristos Bacharakis\, Dr. Humera Noor Minhas\n\n**Description:**\nHave you ever wondered if AI Ethics is an Engineering or a Product issue? Which software development life cycle pha se should you start addressing ethics in your AI system? How do we ensure that ethics are integrated into the solutions by design and not only imple mented on top as an afterthought? \n\n\n\n\n\n\n\nAddressing the ne ed for fairness and accountability in AI\, this talk will explore our effo rts to navigate cutting-edge technology while ensuring the ethical develop ment of AI solutions. We will examine the requisite shift in perspective a nd straightforward\, actionable measures that empower enterprises to seaml essly infuse ethical AI into their core values\, steering clear of prevale nt pitfalls.\n\n**Goal(s):**\nUnderstand how to navigate cutting-edge tech nology and build an open web while ensuring the ethical development of AI solutions.\n\n\n**Materials:**\n- [slides](https://docs.google.com/present ation/d/1kOQppEX-SNDLPMEe13Mg-yIQuym7MKl7Eb2CJvaDBbQ/edit#slide=id.p1)\n- [minutes](http://www.w3.org/2023/09/tpac-breakouts/72-minutes.pdf)\n- [liv e google doc minutes](https://docs.google.com/document/d/1od0BwLAHxemYRtJn sR7cf8fL7t9z-9RoNmuMVPTdl3o/edit)\n- [Session proposal on GitHub](https:// github.com/w3c/tpac2023-breakouts/issues/72)\n\n**Track(s):**\n- AI STATUS:CONFIRMED CREATED:20230905T054146Z LAST-MODIFIED:20230923T163515Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Ecija - 1st floor CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:c6e71b80-0b1d-4a04-88e2-d3588bbc60d8 DTSTAMP:20230919T113727Z SUMMARY:Facilitating media content distribution across industries DTSTART;TZID=Europe/Madrid:20230913T121500 DTEND;TZID=Europe/Madrid:20230913T131500 DESCRIPTION:https://www.w3.org/events/meetings/c6e71b80-0b1d-4a04-88e2-d358 8bbc60d8/\n\nA huge amount of media content is produced every day\, includ ing TV and radio programs\, ebooks\, and news articles. These are provided through various online distribution and broadcasting services. \n\n\n\n\n \n\n\nHowever\, the reach of such content is limited by the means of provi sion. This reduces the opportunity for users to access information. \n\n\n \n\n\n\n\nContent providers expect that content will be widely distributed among media industries and other industries such as tourism\, education a nd health care\, thus creating an ecosystem in which users consume various types of media content through their daily life.\n\n\n\n\n\n\n\nIn this s ession\, we will share use cases and challenges where media content is uti lized across services and industries and consider how metadata can facilit ate an advanced and evolving collaboration among media industry. \n\n\n\n\ n\n\n\nThe focus of the session will be on the possibilities of utilizing metadata across industries and its challenges by sharing ideas from differ ent media industries. Technical discussion such as metadata formats\, sche mas and ontologies within and outside of the W3C is positioned as a future activity.\n\nAgenda\n\n**Chairs:**\nHiroki Endo\n\n**Description:**\nA hu ge amount of media content is produced every day\, including TV and radio programs\, ebooks\, and news articles. These are provided through various online distribution and broadcasting services. \n\n\n\n\n\n\n\nHowever\, t he reach of such content is limited by the means of provision. This reduce s the opportunity for users to access information. \n\n\n\n\n\n\n\nContent providers expect that content will be widely distributed among media indu stries and other industries such as tourism\, education and health care\, thus creating an ecosystem in which users consume various types of media c ontent through their daily life.\n\n\n\n\n\n\n\nIn this session\, we will share use cases and challenges where media content is utilized across serv ices and industries and consider how metadata can facilitate an advanced a nd evolving collaboration among media industry. \n\n\n\n\n\n\n\nThe focus of the session will be on the possibilities of utilizing metadata across i ndustries and its challenges by sharing ideas from different media industr ies. Technical discussion such as metadata formats\, schemas and ontologie s within and outside of the W3C is positioned as a future activity.\n\n**G oal(s):**\nShare the use cases and issues where media content utilizes met adata to distribute across industries\, and identify hints for future coop eration across the media industry\n\n\n**Materials:**\n- [slides](https:// lists.w3.org/Archives/Public/www-archive/2023Sep/att-0012/20230913_TPAC202 3_Breakout_Facilitating-media-content-distribution-across-industries.pdf)\ n- [minutes](https://www.w3.org/2023/09/13-cross-industry-media-content-mi nutes.html)\n- [Session proposal on GitHub](https://github.com/w3c/tpac202 3-breakouts/issues/63) STATUS:CONFIRMED CREATED:20230905T054100Z LAST-MODIFIED:20230919T113727Z SEQUENCE:2 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Azalea - Low Level CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:b8205527-bbd9-46b6-9efe-bf9395ff52e3 DTSTAMP:20230923T163332Z SUMMARY:Getting your feature adopted: learn to work with technical writers DTSTART;TZID=Europe/Madrid:20230913T121500 DTEND;TZID=Europe/Madrid:20230913T131500 DESCRIPTION:https://www.w3.org/events/meetings/b8205527-bbd9-46b6-9efe-bf93 95ff52e3/\n\nMembers of the MDN team and the Open Web Docs collective will present on the topic of technical documentation of web features\, its imp ortance for feature adoption\, its process\, and how you (as a spec editor or feature implementer) can collaborate with us on it.\n\nAgenda: https:/ /docs.google.com/document/d/1pNHLKwPs0nZ5KCY_cV05unjnL1iHKlb7CW2CQwbGGrs/e dit\n\nAgenda\n\n**Chairs:**\nPatrick Brosset\, Rachel Andrew\, Florian Sc holz\n\n**Description:**\nMembers of the MDN team and the Open Web Docs co llective will present on the topic of technical documentation of web featu res\, its importance for feature adoption\, its process\, and how you (as a spec editor or feature implementer) can collaborate with us on it.\n\n** Goal(s):**\nTo help makers of the web realise the importance of on-time\, up-to-date\, and high-quality documentation\, and what they can do to help .\n\n\n**Materials:**\n- [minutes](http://www.w3.org/2023/09/tpac-breakout s/57-minutes.pdf)\n- [live google doc minutes](https://docs.google.com/doc ument/d/1pNHLKwPs0nZ5KCY_cV05unjnL1iHKlb7CW2CQwbGGrs/edit#heading=h.obp8gh sfj9p6)\n- [Session proposal on GitHub](https://github.com/w3c/tpac2023-br eakouts/issues/57)\n\n**Track(s):**\n- developer experience STATUS:CONFIRMED CREATED:20230905T054019Z LAST-MODIFIED:20230923T163332Z SEQUENCE:2 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Nervion-Arenal II - Level -1 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:150dc0a1-ee6a-4bad-9417-804bf76284bf DTSTAMP:20230919T113046Z SUMMARY:Interoperable and verifiable credentials for cross-border trade DTSTART;TZID=Europe/Madrid:20230913T121500 DTEND;TZID=Europe/Madrid:20230913T131500 DESCRIPTION:https://www.w3.org/events/meetings/150dc0a1-ee6a-4bad-9417-804b f76284bf/\n\nParties such as Sellers\, Buyers\, Traders and Transport oper ators engaged in the trading of goods internationally work predominantly i n digital siloed systems. These are typically laborious and expensive to c onnect and hence much of the time\, trade takes place over paper or at bes t digital file formats that assure neither authenticity nor provenance. Ad ditionally\, they would benefit immensely from 2 functions of:\n\n\n\n* En abling users to control commercially-sensitive information whilst not comp romising the reliability of the Verifiable Credentials being presented\, w hich is important in cross-border trade.\n\n* Enabling Verifiable Credenti als to be paper-friendly in order to ease the transition to the digital me dium by the paper-centric cross-border trade community.\n\n\n\nSingapore ’s Infocomm Media Development Authority will introduce TradeTrust as a f ramework for interoperable verifiable and transferable trade documents. Tr adeTrust is powered by OpenAttestation\, an open-source technology framewo rk created by the Government Technology Agency of Singapore (GovTech) for issuing verifiable documents. In production since 2018\, besides for cross -border trade uses\, OpenAttestation has been implemented in other domains such as academic credentials and vaccination certs.\n\nAgenda\n\n**Chairs :**\nRachel Yager\, Kylie Goh\n\n**Description:**\nParties such as Sellers \, Buyers\, Traders and Transport operators engaged in the trading of good s internationally work predominantly in digital siloed systems. These are typically laborious and expensive to connect and hence much of the time\, trade takes place over paper or at best digital file formats that assure n either authenticity nor provenance. Additionally\, they would benefit imme nsely from 2 functions of:\n\n\n\n* Enabling users to control commercially -sensitive information whilst not compromising the reliability of the Veri fiable Credentials being presented\, which is important in cross-border tr ade.\n\n* Enabling Verifiable Credentials to be paper-friendly in order to ease the transition to the digital medium by the paper-centric cross-bord er trade community.\n\n\n\nSingapore’s Infocomm Media Development Author ity will introduce TradeTrust as a framework for interoperable verifiable and transferable trade documents. TradeTrust is powered by OpenAttestation \, an open-source technology framework created by the Government Technolog y Agency of Singapore (GovTech) for issuing verifiable documents. In produ ction since 2018\, besides for cross-border trade uses\, OpenAttestation h as been implemented in other domains such as academic credentials and vacc ination certs.\n\n**Goal(s):**\nShare information\, gather feedback\, find like-minded partners to collaborate on a) using and possibly enhancing W3 C verifiable credentials in support or cross-border trade and b) developin g the relationship to OpenAttestation.\n\n\n**Materials:**\n- [slides](htt ps://github.com/w3c/tpac2023-breakouts/files/12596215/W3C.TPAC.2023.230890 6.pdf)\n- [minutes](https://www.w3.org/2023/09/13-tradetrust-minutes.html) \n- [Session proposal on GitHub](https://github.com/w3c/tpac2023-breakouts /issues/12)\n\n**Track(s):**\n- trust STATUS:CONFIRMED CREATED:20230905T053622Z LAST-MODIFIED:20230919T113046Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Santa Cruz - Level -1 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:04625253-cec9-4c78-8c17-b1fea5c50d23 DTSTAMP:20230919T112954Z SUMMARY:ServiceWorker and Loading Performance DTSTART;TZID=Europe/Madrid:20230913T121500 DTEND;TZID=Europe/Madrid:20230913T131500 DESCRIPTION:https://www.w3.org/events/meetings/04625253-cec9-4c78-8c17-b1fe a5c50d23/\n\nThe session is going to be a presentation part and discussion part.\n\n\n\n\n\n\n\nStarting ServiceWorkers is known to be a slow proces s\, and web users need to wait for its startup if the ServiceWorker interc epts loading the page resources. At the same time\, the ServiceWorker brin gs flexibility to the transport layer\, and it behaves as a client-side pr oxy. Developers can implement offline support or provide client-side conte nt modification with it.\n\n\n\n\n\n\n\nWe have a couple of early ideas to minimize the performance cost\, such as [the static routing API](https:// github.com/yoshisatoyanagisawa/service-worker-static-routing-api)\, and [s kip no-op fetch handler](https://github.com/yoshisatoyanagisawa/service-wo rker-skip-no-op-fetch-handler). For the first half of the session\, we’r e going to present performance problems that we’re observing\, outline o f proposed APIs and how it works\, and estimated performance improvements. \n\n\n\n\n\n\n\nFor the second half\, we’d like to discuss ServiceWorker and performance with the community and ask for feedback on our ideas.\n\n Agenda\n\n**Chairs:**\nShunya Shishido\n\n**Description:**\nThe session is going to be a presentation part and discussion part.\n\n\n\n\n\n\n\nStart ing ServiceWorkers is known to be a slow process\, and web users need to w ait for its startup if the ServiceWorker intercepts loading the page resou rces. At the same time\, the ServiceWorker brings flexibility to the trans port layer\, and it behaves as a client-side proxy. Developers can impleme nt offline support or provide client-side content modification with it.\n\ n\n\n\n\n\n\nWe have a couple of early ideas to minimize the performance c ost\, such as [the static routing API](https://github.com/yoshisatoyanagis awa/service-worker-static-routing-api)\, and [skip no-op fetch handler](ht tps://github.com/yoshisatoyanagisawa/service-worker-skip-no-op-fetch-handl er). For the first half of the session\, we’re going to present performa nce problems that we’re observing\, outline of proposed APIs and how it works\, and estimated performance improvements.\n\n\n\n\n\n\n\nFor the sec ond half\, we’d like to discuss ServiceWorker and performance with the c ommunity and ask for feedback on our ideas.\n\n**Goal(s):**\nThis session aims to discuss and learn about ServiceWorkers performance issues. We’re going to present some newly proposed ServiceWorker APIs and optimizations to address performance issues as well\, we’d like to discuss and gather feedback from the community.\n\n\n**Materials:**\n- [slides](https://docs .google.com/presentation/d/1aoHncqpr-3bC-Wh5yVjL1WO5YHyFiwTdarzDMjdwpuU/ed it#slide=id.p)\n- [minutes](https://www.w3.org/2023/09/13-serviceworkers-m inutes.html)\n- [Session proposal on GitHub](https://github.com/w3c/tpac20 23-breakouts/issues/7)\n\n**Track(s):**\n- performance STATUS:CONFIRMED CREATED:20230905T053545Z LAST-MODIFIED:20230919T112954Z SEQUENCE:2 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Nervion I - Level -1 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:919c2a7d-e925-4249-8a29-09001c15b48a DTSTAMP:20230919T113409Z SUMMARY:SocialWeb Test suite discussion DTSTART;TZID=Europe/Madrid:20230913T121500 DTEND;TZID=Europe/Madrid:20230913T131500 DESCRIPTION:https://www.w3.org/events/meetings/919c2a7d-e925-4249-8a29-0900 1c15b48a/\n\nContinuing the SocialWeb Test Suite discussion\, including te st suite challenges and strategies\, as well as demos of the in-progress t est suite approaches.\n\nAgenda\n\n**Chairs:**\nDmitri Zagidulin\, nightpo ol .\, James Gallagher\n\n**Description:**\nContinuing the SocialWeb Test Suite discussion\, including test suite challenges and strategies\, as wel l as demos of the in-progress test suite approaches.\n\n**Goal(s):**\nAppr ise the SocialWeb developer community of the current test suite status\n\n \n**Materials:**\n- [minutes](https://www.w3.org/2023/09/13-socialweb-test -suite-minutes.html)\n- [Session proposal on GitHub](https://github.com/w3 c/tpac2023-breakouts/issues/36) STATUS:CONFIRMED CREATED:20230905T053835Z LAST-MODIFIED:20230919T113409Z SEQUENCE:2 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Lebrija - 1st floor CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:6d209c82-549d-4506-bc36-764ac4326b14 DTSTAMP:20230923T163543Z SUMMARY:The Future of Powerful APIs on the Web Platform DTSTART;TZID=Europe/Madrid:20230913T121500 DTEND;TZID=Europe/Madrid:20230913T131500 DESCRIPTION:https://www.w3.org/events/meetings/6d209c82-549d-4506-bc36-764a c4326b14/\n\nPowerful APIs have been a constant source of contention when balancing the needs of making the web platform competitive while still pro viding the fundamental guarantees such as security and privacy. Given the trend of web-platform derivative application runtimes such as Electron bec oming popular\, the potential and user needs of this is clear - but how we can deliver such functionality while providing the security and privacy g uarantees of a browser remains an unsolved problem. \n\n\n\n\n\n\n\nAs a s imple example of this being a problem - fundamental platform functionality \, such as accessing files is still in an unsatisfying state\, leaving the web platform as a less desirable platform for developers to target seriou s applications against. Is there a path where we can have a standardized r eplacement for Electron\, and if so\, what kind of fundamental architectur al changes would that entail? \n\n\n\n\n\n\n\nThis session would like to i nvite members of the community who are interested in contributing towards a solution to this. Of the participants\, we would like to create a task f orce to identify unmet user needs on the web platform\, attempt to find a path forward to tackle this problem space\, and compile a set of principl es and requirements that solutions developed to address these needs should follow. This venture will function as a TAG-endorsed task force\, and the participants will be invited by the TAG chairs. Members may include curre nt or former members of the TAG.\n\n\n\n\n\n\n\nThe task force would be i dentifying ways to bridge the gap between the Web Platform and native appl ication platforms\, while protecting security and user privacy\, aligning with the TAG's Ethical Principles\, Design Principles\, the in-development Privacy Principles and the Privacy & Security Questionnaire. We would nee d to ensure this effort has multi-stakeholder interest\, while ensuring cr oss-browser and platform support.\n\nAgenda\n\n**Chairs:**\nSangwhan Moon\ , Lea Verou\, Daniel Appelquist\n\n**Description:**\nPowerful APIs have be en a constant source of contention when balancing the needs of making the web platform competitive while still providing the fundamental guarantees such as security and privacy. Given the trend of web-platform derivative a pplication runtimes such as Electron becoming popular\, the potential and user needs of this is clear - but how we can deliver such functionality wh ile providing the security and privacy guarantees of a browser remains an unsolved problem. \n\n\n\n\n\n\n\nAs a simple example of this being a prob lem - fundamental platform functionality\, such as accessing files is stil l in an unsatisfying state\, leaving the web platform as a less desirable platform for developers to target serious applications against. Is there a path where we can have a standardized replacement for Electron\, and if s o\, what kind of fundamental architectural changes would that entail? \n\n \n\n\n\n\n\nThis session would like to invite members of the community who are interested in contributing towards a solution to this. Of the partici pants\, we would like to create a task force to identify unmet user needs on the web platform\, attempt to find a path forward to tackle this proble m space\, and compile a set of principles and requirements that solutions developed to address these needs should follow. This venture will functio n as a TAG-endorsed task force\, and the participants will be invited by t he TAG chairs. Members may include current or former members of the TAG.\n \n\n\n\n\n\n\nThe task force would be identifying ways to bridge the gap between the Web Platform and native application platforms\, while protecti ng security and user privacy\, aligning with the TAG's Ethical Principles\ , Design Principles\, the in-development Privacy Principles and the Privac y & Security Questionnaire. We would need to ensure this effort has multi- stakeholder interest\, while ensuring cross-browser and platform support.\ n\n**Goal(s):**\nSolicit feedback on problem space\, iterate on focus area for task force\, and recruit participants.\n\n\n**Materials:**\n- [slides ](https://docs.google.com/presentation/d/1-1Q-2206wTjWadU0NtXozEWyGZbnaz1A BHCWL_MCNaM/edit#slide=id.p)\n- [minutes](http://www.w3.org/2023/09/tpac-b reakouts/76-minutes.pdf)\n- [live google doc minutes](https://docs.google. com/document/d/1vRO6xher_AiHDOkQIClgz4wCI8tEAJdHifLU-M2epOI/edit#heading=h .xxa48zxk3cpj)\n- [Session proposal on GitHub](https://github.com/w3c/tpac 2023-breakouts/issues/76) STATUS:CONFIRMED CREATED:20230905T140310Z LAST-MODIFIED:20230923T163543Z SEQUENCE:2 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Giralda V - Level -2 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:6047d4b8-20ae-4909-8868-696b14a213ff DTSTAMP:20230921T103632Z SUMMARY:Tracking spec maintenance DTSTART;TZID=Europe/Madrid:20230913T121500 DTEND;TZID=Europe/Madrid:20230913T131500 DESCRIPTION:https://www.w3.org/events/meetings/6047d4b8-20ae-4909-8868-696b 14a213ff/\n\nThe web platform includes [lots of specifications](https://gi thub.com/w3c/browser-specs/blob/main/specs.json)\, and we don't have an ea sy way of distinguishing the ones that are adequately maintained\, vs the ones that need more investment. \n\n\n\nSome considerations include (but a ren't limited to):\n\n\n\n* Stable specs might not need much investment fo r long periods of time.\n\n* We should include specs that have only one im plementation\, so that:\n\n * If a group starts showing interest in writ ing a second implementation\, their issues should be very visible.\n\n* Sp ecs should triage issues fairly quickly\, but it could be ok for low prior ity issues to sit around.\n\n* We probably need a [consistent set of label s](https://w3c.github.io/issue-metadata.html).\n\n* Chrome needs to do a l ot of the maintenance\, but the whole community should buy into the system and see the results.\n\n\n\nFuture discussion will happen on the [spec-pr od@w3.org mailing list](https://lists.w3.org/Archives/Public/spec-prod/).\ n\nAgenda: https://github.com/jyasskin/spec-maintenance/blob/main/meetings /2023-tpac/agenda.md\n\nAgenda\n\n**Chairs:**\nJeffrey Yasskin\n\n**Descri ption:**\nThe web platform includes [lots of specifications](https://githu b.com/w3c/browser-specs/blob/main/specs.json)\, and we don't have an easy way of distinguishing the ones that are adequately maintained\, vs the one s that need more investment. \n\n\n\nSome considerations include (but aren 't limited to):\n\n\n\n* Stable specs might not need much investment for l ong periods of time.\n\n* We should include specs that have only one imple mentation\, so that:\n\n * If a group starts showing interest in writing a second implementation\, their issues should be very visible.\n\n* Specs should triage issues fairly quickly\, but it could be ok for low priority issues to sit around.\n\n* We probably need a [consistent set of labels]( https://w3c.github.io/issue-metadata.html).\n\n* Chrome needs to do a lot of the maintenance\, but the whole community should buy into the system an d see the results.\n\n\n\nFuture discussion will happen on the [spec-prod@ w3.org mailing list](https://lists.w3.org/Archives/Public/spec-prod/).\n\n **Goal(s):**\nSketch a plan to sustainably identify specs that are falling behind on their maintenance needs\n\n\n**Materials:**\n- [slides](https:/ /jyasskin.github.io/spec-maintenance/meetings/2023-tpac/slides.html)\n- [m inutes](https://www.w3.org/2023/09/13-spec-maintenance-minutes.html)\n- [b rainstorming results](https://github.com/jyasskin/spec-maintenance/blob/ma in/meetings/2023-tpac/brainstorm.md)\n- [Session proposal on GitHub](https ://github.com/w3c/tpac2023-breakouts/issues/59)\n\n**Track(s):**\n- gettin g work done STATUS:CONFIRMED CREATED:20230905T054029Z LAST-MODIFIED:20230921T103632Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Magnolia - Low Level CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:477d72e8-6beb-427a-a320-f77e97aca326 DTSTAMP:20230919T113432Z SUMMARY:`AsyncContext` integration with web APIs DTSTART;TZID=Europe/Madrid:20230913T121500 DTEND;TZID=Europe/Madrid:20230913T131500 DESCRIPTION:https://www.w3.org/events/meetings/477d72e8-6beb-427a-a320-f77e 97aca326/\n\n[`AsyncContext`](https://github.com/tc39/proposal-async-conte xt/) is a stage 2 TC39 proposal that allows propagating values across an a sync execution flow\, much like Node.js's [`AsyncLocalStorage`](https://no dejs.org/dist/latest-v20.x/docs/api/async_context.html). However\, when bu ilding this capability into the web platform we must consider the integrat ion with web APIs – should `setTimeout` propagate the async context from the point it is called into the callback? What about event registration?\ n\n\n\n\n\n\n\nFurthermore\, [Chrome has been working](https://bit.ly/task -attribution) on associating script-initiated actions from their causes fu rther up the async call stack (tracking a task's attribution)\, which is u seful browser-internally to enable metrics and web API improvements that w ould not be possible otherwise. Task attribution is the same as propagatin g browser-internal values across an async execution flow\, so if we can en sure all of the task attribution use cases are covered by `AsyncContext`\, the former could be built on top of the latter\, in the specs and in brow ser engines.\n\nAgenda\n\n**Chairs:**\nAndreu Botella\, Daniel Ehrenberg\n \n**Description:**\n[`AsyncContext`](https://github.com/tc39/proposal-asyn c-context/) is a stage 2 TC39 proposal that allows propagating values acro ss an async execution flow\, much like Node.js's [`AsyncLocalStorage`](htt ps://nodejs.org/dist/latest-v20.x/docs/api/async_context.html). However\, when building this capability into the web platform we must consider the i ntegration with web APIs – should `setTimeout` propagate the async conte xt from the point it is called into the callback? What about event registr ation?\n\n\n\n\n\n\n\nFurthermore\, [Chrome has been working](https://bit. ly/task-attribution) on associating script-initiated actions from their ca uses further up the async call stack (tracking a task's attribution)\, whi ch is useful browser-internally to enable metrics and web API improvements that would not be possible otherwise. Task attribution is the same as pro pagating browser-internal values across an async execution flow\, so if we can ensure all of the task attribution use cases are covered by `AsyncCon text`\, the former could be built on top of the latter\, in the specs and in browser engines.\n\n**Goal(s):**\nGet feedback from browser vendors and other interested parties as to which web APIs should propagate the async context.\n\n\n**Materials:**\n- [Session proposal on GitHub](https://githu b.com/w3c/tpac2023-breakouts/issues/39) STATUS:CONFIRMED CREATED:20230905T053853Z LAST-MODIFIED:20230919T113432Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Triana - Level -1 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:28f365bf-67ee-4245-99ff-cf42b9dbb899 DTSTAMP:20230923T163224Z SUMMARY:Alternative to customized builtins (custom elements with is=) DTSTART;TZID=Europe/Madrid:20230913T143000 DTEND;TZID=Europe/Madrid:20230913T153000 DESCRIPTION:https://www.w3.org/events/meetings/28f365bf-67ee-4245-99ff-cf42 b9dbb899/\n\nThis is a session to discuss an alternative to customized bui ltins based on the outcome of https://github.com/WebKit/standards-position s/issues/97\n\nAgenda\n\n**Chairs:**\nRyosuke Niwa\n\n**Description:**\nTh is is a session to discuss an alternative to customized builtins based on the outcome of https://github.com/WebKit/standards-positions/issues/97\n\n **Goal(s):**\nCome up with a concrete alternative proposal with multi-vend or support to customized builtins\n\n\n**Materials:**\n- [minutes](http:// www.w3.org/2023/09/tpac-breakouts/44-minutes.pdf)\n- [live google doc minu tes](https://docs.google.com/document/d/10hRHzZWwBuz0aJqBZ63alfzYBxKdhN8WI NHizioNfok/edit)\n- [Session proposal on GitHub](https://github.com/w3c/tp ac2023-breakouts/issues/44)\n\n**Track(s):**\n- web components STATUS:CONFIRMED CREATED:20230905T053919Z LAST-MODIFIED:20230923T163224Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Estepa - 1st floor CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:fcde7756-f9a9-4ad5-b67a-0d7049e5b10b DTSTAMP:20230919T113351Z SUMMARY:AT-Driver: Get Involved DTSTART;TZID=Europe/Madrid:20230913T143000 DTEND;TZID=Europe/Madrid:20230913T153000 DESCRIPTION:https://www.w3.org/events/meetings/fcde7756-f9a9-4ad5-b67a-0d70 49e5b10b/\n\nA short introduction to the AT-Driver specification\, what it is\, why we're writing it and why assistive technology vendors\, browsers and wider community should get involved. This will be an opportunity for people to ask questions\, raise issues and learn more about the spec and i ts application.\n\nAgenda\n\n**Chairs:**\nLola Odelola\n\n**Description:** \nA short introduction to the AT-Driver specification\, what it is\, why w e're writing it and why assistive technology vendors\, browsers and wider community should get involved. This will be an opportunity for people to a sk questions\, raise issues and learn more about the spec and its applicat ion.\n\n**Goal(s):**\nTo share information about the AT-Driver specificati on\n\n\n**Materials:**\n- [slides](https://docs.google.com/presentation/d/ 15Q95ljoUGLz4kBSTq_E15QsIpt2KVomVCIPtpH-Ra00/edit?usp=sharing)\n- [minutes ](https://www.w3.org/2023/09/13-at-driver-minutes.html)\n- [Session propos al on GitHub](https://github.com/w3c/tpac2023-breakouts/issues/34)\n\n**Tr ack(s):**\n- accessibility STATUS:CONFIRMED CREATED:20230905T053824Z LAST-MODIFIED:20230919T113351Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Prado - Level -1 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:fc9a0282-22ee-4db6-8d23-ce231a37e4ad DTSTAMP:20230919T113514Z SUMMARY:Challenges with Incubation DTSTART;TZID=Europe/Madrid:20230913T143000 DTEND;TZID=Europe/Madrid:20230913T153000 DESCRIPTION:https://www.w3.org/events/meetings/fc9a0282-22ee-4db6-8d23-ce23 1a37e4ad/\n\nThis session is to define expectations & guidance for advanci ng work in incubation and when to move it out (both to a WG or to a closin g report)\, and how we need to adjust various practices and Process (e.g. WG chartering) to support this. Also in scope is the topic of "how should CGs be used at the W3c?" More background to be found at https://github.c om/w3c/AB-memberonly/issues/81.\n\nAgenda\n\n**Chairs:**\nChris Wilson\n\n **Description:**\nThis session is to define expectations & guidance for ad vancing work in incubation and when to move it out (both to a WG or to a c losing report)\, and how we need to adjust various practices and Process ( e.g. WG chartering) to support this. Also in scope is the topic of "how s hould CGs be used at the W3c?" More background to be found at https://git hub.com/w3c/AB-memberonly/issues/81.\n\n**Goal(s):**\nConsensus on role of CGs in incubation\, and general expectations for how to advance work.\n\n \n**Materials:**\n- [minutes](https://www.w3.org/2023/09/13-incubation-min utes.html)\n- [Session proposal on GitHub](https://github.com/w3c/tpac2023 -breakouts/issues/45)\n\n**Track(s):**\n- getting work done STATUS:CONFIRMED CREATED:20230905T053924Z LAST-MODIFIED:20230919T113514Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Magnolia - Low Level CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:3d55226e-0fdd-4836-b5fa-edaa77e10d34 DTSTAMP:20231010T102053Z SUMMARY:CSSWG Anchor Positioning DTSTART;TZID=Europe/Madrid:20230913T143000 DTEND;TZID=Europe/Madrid:20230913T153000 DESCRIPTION:https://www.w3.org/events/meetings/3d55226e-0fdd-4836-b5fa-edaa 77e10d34/\n\nCompare the current spec of [CSS Anchor Positioning](https:// drafts.csswg.org/css-anchor-position-1/) and the [alternative proposal](ht tps://fantasai.inkedblade.net/style/specs/css-anchor-exploration/) by Appl e\, list the individual issues where the current spec can be improved\, an d try to reach consensus or resolve those issues.\n\nAgenda: https://githu b.com/w3c/tpac2023-breakouts/issues/66#issuecomment-1717428654\n\nAgenda\n \n**Chairs:**\nTab Atkins Jr.\n\n**Description:**\nCompare the current spe c of [CSS Anchor Positioning](https://drafts.csswg.org/css-anchor-position -1/) and the [alternative proposal](https://fantasai.inkedblade.net/style/ specs/css-anchor-exploration/) by Apple\, list the individual issues where the current spec can be improved\, and try to reach consensus or resolve those issues.\n\n**Goal(s):**\nClose the gap between the current spec and the proposal as much as possible.\n\n\n**Materials:**\n- [minutes](https:/ /www.w3.org/2023/09/13-css-irc)\n- [Session proposal on GitHub](https://gi thub.com/w3c/tpac2023-breakouts/issues/66) STATUS:CONFIRMED CREATED:20230905T054115Z LAST-MODIFIED:20231010T102053Z SEQUENCE:2 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Azalea - Low Level CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:574987d8-a141-4734-b396-4673e4b0a549 DTSTAMP:20230921T102958Z SUMMARY:Design Tokens for Accessibility Settings: Empowering Inclusive Desi gn with CSS DTSTART;TZID=Europe/Madrid:20230913T143000 DTEND;TZID=Europe/Madrid:20230913T153000 DESCRIPTION:https://www.w3.org/events/meetings/574987d8-a141-4734-b396-4673 e4b0a549/\n\nThe Rhonda Weiss Center for Accessible IDEA Data is excited t o host this breakout session on Design Tokens for Accessibility Settings. As an organization dedicated to promoting accessibility and inclusivity\, we firmly believe in taking an accessibility-first approach in all aspects of the product development life cycle. \n\n\n\nIDEA stands for the Indiv iduals with Disabilities Education Act. It is a federal law in the United States that ensures students with disabilities receive appropriate special education and related services to meet their unique educational needs. \n \n\n\nIn this session\, we will review our groundbreaking efforts to devel op an open-source tool for generating accessible reports of IDEA data. Dis cover how design tokens take center stage in delivering essential digital accessibility accommodations to end-users. This interactive discussion wil l showcase the pivotal role of design tokens in ensuring inclusivity and u sability in accessing and interpreting IDEA data reports. \n\n\n\nDesign t okens serve as reusable and platform-agnostic values that define the prope rties of a design system. By harnessing the power of CSS with design token s\, we can enhance the inclusivity and accessibility of the user experienc e\, particularly for individuals with multiple disabilities or intersectio nality. \n\n\n\nWe will explore the idea of utilizing CSS tokens specifica lly tailored to address different disabilities and user needs. We'll delve into the proposed tokens for digital accommodations\, such as those for l ow vision\, color-blindness\, dyslexia\, ADHD\, deafness and hard of heari ng\, motor disabilities\, cognitive disabilities\, photosensitive epilepsy \, aging-related impairments\, blindness\, and more. \n\n\n\nThe session w ill provide an opportunity to: \n\n\n\n1. Discuss the benefits and challen ges of using CSS tokens for accessibility settings. \n\n2. Share experienc es and best practices in implementing design tokens for accessibility. \n\ n3. Brainstorm additional design tokens and discuss their potential impact on improving accessibility. \n\n4. Explore ways to integrate design token s into existing design systems and development workflows. \n\n5. Collabora te on strategies to promote the adoption of design tokens for accessibilit y in the web development community. \n\n\n\nJoin us for an engaging and in teractive discussion where we aim to collectively gather ideas\, insights\ , and practical approaches for leveraging CSS tokens to enhance accessibil ity. Whether you're a designer\, developer\, accessibility advocate\, or s imply interested in inclusive design\, your perspectives and contributions are valuable.\n\nAgenda: https://github.com/WeissCenter/w3c-tpac2023-brea kouts/blob/main/agenda.md\n\nAgenda\n\n**Chairs:**\nMarcelo Paiva\, Fred E dora\n\n**Description:**\nThe Rhonda Weiss Center for Accessible IDEA Data is excited to host this breakout session on Design Tokens for Accessibili ty Settings. As an organization dedicated to promoting accessibility and i nclusivity\, we firmly believe in taking an accessibility-first approach i n all aspects of the product development life cycle. \n\n\n\nIDEA stands for the Individuals with Disabilities Education Act. It is a federal law i n the United States that ensures students with disabilities receive approp riate special education and related services to meet their unique educatio nal needs. \n\n\n\nIn this session\, we will review our groundbreaking eff orts to develop an open-source tool for generating accessible reports of I DEA data. Discover how design tokens take center stage in delivering essen tial digital accessibility accommodations to end-users. This interactive d iscussion will showcase the pivotal role of design tokens in ensuring incl usivity and usability in accessing and interpreting IDEA data reports. \n\ n\n\nDesign tokens serve as reusable and platform-agnostic values that def ine the properties of a design system. By harnessing the power of CSS with design tokens\, we can enhance the inclusivity and accessibility of the u ser experience\, particularly for individuals with multiple disabilities o r intersectionality. \n\n\n\nWe will explore the idea of utilizing CSS tok ens specifically tailored to address different disabilities and user needs . We'll delve into the proposed tokens for digital accommodations\, such a s those for low vision\, color-blindness\, dyslexia\, ADHD\, deafness and hard of hearing\, motor disabilities\, cognitive disabilities\, photosensi tive epilepsy\, aging-related impairments\, blindness\, and more. \n\n\n\n The session will provide an opportunity to: \n\n\n\n1. Discuss the benefit s and challenges of using CSS tokens for accessibility settings. \n\n2. Sh are experiences and best practices in implementing design tokens for acces sibility. \n\n3. Brainstorm additional design tokens and discuss their pot ential impact on improving accessibility. \n\n4. Explore ways to integrate design tokens into existing design systems and development workflows. \n\ n5. Collaborate on strategies to promote the adoption of design tokens for accessibility in the web development community. \n\n\n\nJoin us for an en gaging and interactive discussion where we aim to collectively gather idea s\, insights\, and practical approaches for leveraging CSS tokens to enhan ce accessibility. Whether you're a designer\, developer\, accessibility ad vocate\, or simply interested in inclusive design\, your perspectives and contributions are valuable.\n\n**Goal(s):**\nThe session goal is to explor e the use of Design Tokens and CSS for accessibility\, discussing benefits \, challenges\, and integration strategies\, and collaboratively gather in sights for enhancing web accessibility through design tokens.\n\n\n**Mater ials:**\n- [minutes](https://www.w3.org/2023/09/13-inclusive-design-tokens -minutes.html)\n- [recording](https://www.w3.org/2023/09/breakouts/recordi ng-10.html)\n- [Session proposal on GitHub](https://github.com/w3c/tpac202 3-breakouts/issues/10)\n\n**Track(s):**\n- accessibility STATUS:CONFIRMED CREATED:20230905T053609Z LAST-MODIFIED:20230921T102958Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Ecija - 1st floor CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:c754e1ec-3abb-4f31-ab2f-25d9598034aa DTSTAMP:20230919T113458Z SUMMARY:Developer experience research and spec development DTSTART;TZID=Europe/Madrid:20230913T143000 DTEND;TZID=Europe/Madrid:20230913T153000 DESCRIPTION:https://www.w3.org/events/meetings/c754e1ec-3abb-4f31-ab2f-25d9 598034aa/\n\nTo develop features and discuss alternative designs\, standar dization groups often ponder the needs of web app developers. To collect f eedback from developers\, ad-hoc mechanisms are being used\, including:\n\ n\n\n* Invitations to participate in the group\, in group meetings or in g roup discussions\n\n* Presentations in developer conferences and podcasts\ n\n* Shoutouts on social networks\, possibly associated with formal or mor e informal surveys\n\n* Internal research programs run by a company\n\n* B roader developer surveys such as [State of CSS](https://stateofcss.com/en- US)\, [State of JavaScript](https://stateofjs.com/en-US)\, or the older [M DN DNA survey](https://mdn.dev/archives/insights/reports/mdn-web-developer -needs-assessment-2020.html).\n\n\n\nCould more systematic developer resea rch be conducted and made available to groups when they need it? The WebDX Community Group proposes this breakout session to discuss [providing deve loper research as a service in standardization groups](https://github.com/ web-platform-dx/developer-research/blob/main/research-strategy.md#providin g-developer-research-as-a-service-for-standards-organizations) and collect requests for research data that groups may need.\n\n\n\nFor additional ba ckground\, the WebDX Community Group\, created last year\, conducts [resea rch](https://github.com/web-platform-dx/developer-research/tree/main#web-d eveloper-experience-research-workstream) to make available quantitative an d qualitative data to all aspects of the web platform feature life cycle. Current research data is the result of MDN short surveys and contributions to existing survey programs.\n\nAgenda: https://www.w3.org/2023/Talks/TPA C/breakouts/developer-research/\n\nAgenda\n\n**Chairs:**\nFrançois Daoust \n\n**Description:**\nTo develop features and discuss alternative designs\ , standardization groups often ponder the needs of web app developers. To collect feedback from developers\, ad-hoc mechanisms are being used\, incl uding:\n\n\n\n* Invitations to participate in the group\, in group meeting s or in group discussions\n\n* Presentations in developer conferences and podcasts\n\n* Shoutouts on social networks\, possibly associated with form al or more informal surveys\n\n* Internal research programs run by a compa ny\n\n* Broader developer surveys such as [State of CSS](https://stateofcs s.com/en-US)\, [State of JavaScript](https://stateofjs.com/en-US)\, or the older [MDN DNA survey](https://mdn.dev/archives/insights/reports/mdn-web- developer-needs-assessment-2020.html).\n\n\n\nCould more systematic develo per research be conducted and made available to groups when they need it? The WebDX Community Group proposes this breakout session to discuss [provi ding developer research as a service in standardization groups](https://gi thub.com/web-platform-dx/developer-research/blob/main/research-strategy.md #providing-developer-research-as-a-service-for-standards-organizations) an d collect requests for research data that groups may need.\n\n\n\nFor addi tional background\, the WebDX Community Group\, created last year\, conduc ts [research](https://github.com/web-platform-dx/developer-research/tree/m ain#web-developer-experience-research-workstream) to make available quanti tative and qualitative data to all aspects of the web platform feature lif e cycle. Current research data is the result of MDN short surveys and cont ributions to existing survey programs.\n\n**Goal(s):**\nBriefly present av ailable developer research data\, exchange on ideas to provide developer r esearch as a service for groups\, and collect possible requests for data o n specific features\n\n\n**Materials:**\n- [slides](https://www.w3.org/202 3/Talks/TPAC/breakouts/developer-research/)\n- [minutes](https://www.w3.or g/2023/09/13-webdx-minutes.html)\n- [Session proposal on GitHub](https://g ithub.com/w3c/tpac2023-breakouts/issues/42)\n\n**Track(s):**\n- developer experience STATUS:CONFIRMED CREATED:20230904T172132Z LAST-MODIFIED:20230919T113458Z SEQUENCE:4 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Nervion-Arenal II - Level -1 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:5c154507-b6a9-41ff-b68b-03fafe050ce0 DTSTAMP:20231010T101701Z SUMMARY:Embracing the possibilities of ePub format DTSTART;TZID=Europe/Madrid:20230913T143000 DTEND;TZID=Europe/Madrid:20230913T153000 DESCRIPTION:https://www.w3.org/events/meetings/5c154507-b6a9-41ff-b68b-03fa fe050ce0/\n\nePub format is a powerful open web technology for digital boo ks. Considering the standard's possibilities\, digital books can be more i nteractive and provide different experiences without letting accessibility best practices out of this scenario.\n\n\n\n\n\n\n\nIn this session\, we will present[ some experiments](https://edupub.ceweb.br/english/) with ePu b books and discuss the potential of ePub technology and the challenges an d opportunities for publishers and users. Participants are welcome to pres ent experiments to enrich the discussion.\n\n\n\n\n\n\n\nTo facilitate the discussion\, we will work with three main questions the participants can discuss.\n\n\n\n\n\n\n\n- How a more interactive book can improve or get w orse the publication accessibility?\n\n\n\n- What are the challenges and o pportunities for publishers in this field?\n\n\n\n- How can authors explor e this kind of experience in digital books?\n\n\n\n_Post-TPAC note: No min utes were taken at this session._\n\nAgenda\n\n**Chairs:**\nReinaldo Ferra z\, Diogo Cortiz\, Hartmut Richard Glaser\n\n**Description:**\nePub format is a powerful open web technology for digital books. Considering the stan dard's possibilities\, digital books can be more interactive and provide d ifferent experiences without letting accessibility best practices out of t his scenario.\n\n\n\n\n\n\n\nIn this session\, we will present[ some exper iments](https://edupub.ceweb.br/english/) with ePub books and discuss the potential of ePub technology and the challenges and opportunities for publ ishers and users. Participants are welcome to present experiments to enric h the discussion.\n\n\n\n\n\n\n\nTo facilitate the discussion\, we will wo rk with three main questions the participants can discuss.\n\n\n\n\n\n\n\n - How a more interactive book can improve or get worse the publication acc essibility?\n\n\n\n- What are the challenges and opportunities for publish ers in this field?\n\n\n\n- How can authors explore this kind of experienc e in digital books?\n\n\n\n_Post-TPAC note: No minutes were taken at this session._\n\n**Goal(s):**\nThe session aims to share use cases and best pr actices about the ePub technology and discuss the challenges and opportuni ties for developers\, publishers\, and users. We encourage people to submi t experiments to a showcase platform.\n\n\n**Materials:**\n- [slides](http s://docs.google.com/presentation/d/1CaK_vd9Pg2wmF8-I6zUwM_SmTvcDiMeLAJqsmb -voi0/edit#slide=id.g1e6a7baa5d8_0_0)\n- [Session proposal on GitHub](http s://github.com/w3c/tpac2023-breakouts/issues/21) STATUS:CONFIRMED CREATED:20230905T053713Z LAST-MODIFIED:20231010T101701Z SEQUENCE:2 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Giralda V - Level -2 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:43317b7e-b0cd-4684-a03d-fdd06d742f43 DTSTAMP:20230923T163059Z SUMMARY:Identity Wallets and the Web DTSTART;TZID=Europe/Madrid:20230913T143000 DTEND;TZID=Europe/Madrid:20230913T153000 DESCRIPTION:https://www.w3.org/events/meetings/43317b7e-b0cd-4684-a03d-fdd0 6d742f43/\n\nThe identity space has recently seen a surge in interest\, pa rticularly from governmental entities\, in what is known as the three-part y model. This model is seen as an advancement from the current two-party i dentity systems\, and involves a verifier (website)\, a holder (wallets)\, and issuers working together to enable the exchange of identity documents such as ISO mDocs or W3C VCs. However\, this ecosystem currently lacks na tive browser support\, and instead relies on general purpose and cumbersom e primitives like OS intents. In this session\, we aim to explore the use cases and overall landscape of this growing ecosystem and consider whether and how browser APIs could be leveraged to support it.\n\nAgenda\n\n**Cha irs:**\nTim Cappalli\, sam goto\n\n**Description:**\nThe identity space ha s recently seen a surge in interest\, particularly from governmental entit ies\, in what is known as the three-party model. This model is seen as an advancement from the current two-party identity systems\, and involves a v erifier (website)\, a holder (wallets)\, and issuers working together to e nable the exchange of identity documents such as ISO mDocs or W3C VCs. How ever\, this ecosystem currently lacks native browser support\, and instead relies on general purpose and cumbersome primitives like OS intents. In t his session\, we aim to explore the use cases and overall landscape of thi s growing ecosystem and consider whether and how browser APIs could be lev eraged to support it.\n\n**Goal(s):**\nAnswer the following questions: are there browser vendors interested in this space? what are the most compell ing use cases? what are the web platforms APIs that seem to have an inters ection in this space? where should we meet to continue this discussion?\n\ n\n**Materials:**\n- [minutes](http://www.w3.org/2023/09/tpac-breakouts/31 -minutes.pdf)\n- [Session proposal on GitHub](https://github.com/w3c/tpac2 023-breakouts/issues/31)\n\n**Track(s):**\n- trust STATUS:CONFIRMED CREATED:20230905T053808Z LAST-MODIFIED:20230923T163059Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Santa Cruz - Level -1 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:09ac96f4-d42e-4550-94d0-112287693ab7 DTSTAMP:20230919T113632Z SUMMARY:Privacy Principles DTSTART;TZID=Europe/Madrid:20230913T143000 DTEND;TZID=Europe/Madrid:20230913T153000 DESCRIPTION:https://www.w3.org/events/meetings/09ac96f4-d42e-4550-94d0-1122 87693ab7/\n\nAn open discussion of the [TAG privacy principles draft](http s://w3ctag.github.io/privacy-principles/) with its authors.\n\nAgenda: htt ps://github.com/w3ctag/privacy-principles/blob/main/meetings/2023-09-tpac/ breakout/agenda.md\n\nAgenda\n\n**Chairs:**\nJeffrey Yasskin\, Daniel Appe lquist\n\n**Description:**\nAn open discussion of the [TAG privacy princip les draft](https://w3ctag.github.io/privacy-principles/) with its authors. \n\n**Goal(s):**\nSpread awareness of what's in the document\, and gather feedback.\n\n\n**Materials:**\n- [slides](https://raw.githack.com/w3ctag/p rivacy-principles/main/meetings/2023-09-tpac/breakout/slides.html)\n- [min utes](https://www.w3.org/2023/09/13-privacy-principles-minutes.html)\n- [S ession proposal on GitHub](https://github.com/w3c/tpac2023-breakouts/issue s/58)\n\n**Track(s):**\n- privacy STATUS:CONFIRMED CREATED:20230905T054023Z LAST-MODIFIED:20230919T113632Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Giralda III - Level -2 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:46ce9082-710a-4fe2-8cf8-5dcdc207c877 DTSTAMP:20230923T163137Z SUMMARY:SocialWeb Data Portability Discussion DTSTART;TZID=Europe/Madrid:20230913T143000 DTEND;TZID=Europe/Madrid:20230913T153000 DESCRIPTION:https://www.w3.org/events/meetings/46ce9082-710a-4fe2-8cf8-5dcd c207c877/\n\nCoordination discussion for exporting and importing SocialWeb data\, including accounts\, contacts and social graphs\, posts and other content\, bookmarks\, lists\, and various metadata.\n\nAgenda\n\n**Chairs: **\nDmitri Zagidulin\, nightpool .\, James Gallagher\n\n**Description:**\n Coordination discussion for exporting and importing SocialWeb data\, inclu ding accounts\, contacts and social graphs\, posts and other content\, boo kmarks\, lists\, and various metadata.\n\n**Goal(s):**\nIdentify use cases and coordinate timeline\n\n\n**Materials:**\n- [minutes](https://www.w3.o rg/2023/09/13-social-minutes.html)\n- [Session proposal on GitHub](https:/ /github.com/w3c/tpac2023-breakouts/issues/37) STATUS:CONFIRMED CREATED:20230905T053839Z LAST-MODIFIED:20230923T163137Z SEQUENCE:2 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Lebrija - 1st floor CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:eda72eb7-93e2-4993-be9c-caeaad7f7a1f DTSTAMP:20230913T071532Z SUMMARY:W3C Business Ecosystems for Essential Services DTSTART;TZID=Europe/Madrid:20230913T143000 DTEND;TZID=Europe/Madrid:20230913T153000 DESCRIPTION:https://www.w3.org/events/meetings/eda72eb7-93e2-4993-be9c-caea ad7f7a1f/\n\nIn this session\, we explore the transformative potential of W3C Business Ecosystems for vital sectors\, including healthcare\, financi al services\, education\, infrastructure\, digital assets\, and computatio nal intelligence. A comprehensive understanding of these ecosystems can he lp maximize efficiency\, improve service delivery\, and increase customer satisfaction in these sectors. We will dive into sector-specific implicati ons and discuss the development of potential W3C business ecosystems. Lear n how these systems can revolutionize service delivery and contribute towa rds a more connected\, efficient\, and intelligent future.\n\nAgenda\n\n** Chairs:**\nRachel Yager\n\n**Description:**\nIn this session\, we explore the transformative potential of W3C Business Ecosystems for vital sectors\ , including healthcare\, financial services\, education\, infrastructure\, digital assets\, and computational intelligence. A comprehensive understa nding of these ecosystems can help maximize efficiency\, improve service d elivery\, and increase customer satisfaction in these sectors. We will div e into sector-specific implications and discuss the development of potenti al W3C business ecosystems. Learn how these systems can revolutionize serv ice delivery and contribute towards a more connected\, efficient\, and int elligent future.\n\n**Goal(s):**\nThe primary goal of this session is to p rovide a roadmap for community and business groups across diverse sectors\ , namely Healthcare\, Financial\, Education\, Infrastructure\, Digital Ass ets\, and Computational Intelligence. We aim to highlight the potential of W3C Business Ecosystems in transforming these vital services\, offering i nsights into how these ecosystems can be leveraged for improved efficiency and service delivery. \n\n\n\n\n\n\n\nThe secondary objective is to promo te awareness of [W3C Chapter](https://chapters.w3.org/) forums and activit ies within vital business ecosystems. By doing so\, we aim to foster engag ement and facilitate meaningful connections among participants.\n\n**Mater ials:**\n- [Session proposal on GitHub](https://github.com/w3c/tpac2023-br eakouts/issues/23) STATUS:CANCELLED CREATED:20230905T053724Z LAST-MODIFIED:20230913T071532Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Giralda V - Level -2 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:c13a3ae8-979c-4157-9c74-b28aba314878 DTSTAMP:20230919T113546Z SUMMARY:Web of Things Scenarios at Home Assistant DTSTART;TZID=Europe/Madrid:20230913T143000 DTEND;TZID=Europe/Madrid:20230913T153000 DESCRIPTION:https://www.w3.org/events/meetings/c13a3ae8-979c-4157-9c74-b28a ba314878/\n\n[Home Assistant](https://www.home-assistant.io/) is a smart h ome platform with a very strong community. The W3C Web of Things standards can be used within Home Assistant in different ways and bring two communi ties together with the following potential benefits:\n\n\n\n- Easier integ ration of future IoT devices to Home Assistant\n\n- Cross Ecosystem Commun ication\n\n- Other ways to communicate with Home Assistant\n\n- Getting wi der feedback and use cases for WoT standards\n\n\n\nThere is interest for this session by @mmcool\, @joshco and @relu91. We will decide later for co -chairs.\n\nAgenda\n\n**Chairs:**\nEge Korkan\n\n**Description:**\n[Home A ssistant](https://www.home-assistant.io/) is a smart home platform with a very strong community. The W3C Web of Things standards can be used within Home Assistant in different ways and bring two communities together with t he following potential benefits:\n\n\n\n- Easier integration of future IoT devices to Home Assistant\n\n- Cross Ecosystem Communication\n\n- Other w ays to communicate with Home Assistant\n\n- Getting wider feedback and use cases for WoT standards\n\n\n\nThere is interest for this session by @mmc ool\, @joshco and @relu91. We will decide later for co-chairs.\n\n**Goal(s ):**\nWoT integration proposals to Home Assistant\n\n\n**Materials:**\n- [ slides](https://docs.google.com/presentation/d/1C-uQLogQbf8e62hXoaE3WnxB0D mh40EXOCb_7Qthyug/edit#slide=id.p)\n- [minutes](https://www.w3.org/2023/09 /13-wot-home-assistant-minutes.html)\n- [Session proposal on GitHub](https ://github.com/w3c/tpac2023-breakouts/issues/50) STATUS:CONFIRMED CREATED:20230905T053946Z LAST-MODIFIED:20230919T113546Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Triana - Level -1 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:9a8981ae-8b11-4aff-b2ed-84b8bdecf781 DTSTAMP:20230923T163247Z SUMMARY:Web Worker Quality of Service DTSTART;TZID=Europe/Madrid:20230913T143000 DTEND;TZID=Europe/Madrid:20230913T153000 DESCRIPTION:https://www.w3.org/events/meetings/9a8981ae-8b11-4aff-b2ed-84b8 bdecf781/\n\n**Web Worker Quality of Service**\n\n\n\n\n\n\n\n\n\n\n\n\n\n \n\n[Web Workers](https://html.spec.whatwg.org/multipage/workers.html#work ers) enable multithreading in web browsers. By offloading compute-intensiv e workload to worker threads\, we can achieve better UI smoothness and res ponsiveness. Till now\, we have been using a cookie-cutter approach to off load such "background" jobs to Web Workers. Compute workloads have varied characteristics\, some tasks are latency sensitive while some can function better in a consistent level of performance for prolonged periods of time . To satisfy tasks with different performance expectations\, modern CPUs i ncorporate a hybrid architecture with high-performance and high-efficiency cores. Operating systems have APIs to control a thread's Quality of Servi ce (QoS). Under the hood\, hardware schedulering tools look at various per formance monitoring units and give hints to the Operating System which mak es the decision to deploy the task to a performance core or an efficiency core.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nWe propose introducing a quality of s ervice attribute to the Web Workers so that applications and libraries hav e a way to explicitly label a worker’s preference of performance. User A gents can take this hint to configure platform thread and possibly affect the scheduling policy.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nSee the [Explainer]( https://github.com/riju/web-worker-quality-of-service/blob/main/explainer. md).\n\nAgenda\n\n**Chairs:**\nRijubrata Bhaumik\, Yoav Weiss\n\n**Descrip tion:**\n**Web Worker Quality of Service**\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n [Web Workers](https://html.spec.whatwg.org/multipage/workers.html#workers) enable multithreading in web browsers. By offloading compute-intensive wo rkload to worker threads\, we can achieve better UI smoothness and respons iveness. Till now\, we have been using a cookie-cutter approach to offload such "background" jobs to Web Workers. Compute workloads have varied char acteristics\, some tasks are latency sensitive while some can function bet ter in a consistent level of performance for prolonged periods of time. To satisfy tasks with different performance expectations\, modern CPUs incor porate a hybrid architecture with high-performance and high-efficiency cor es. Operating systems have APIs to control a thread's Quality of Service ( QoS). Under the hood\, hardware schedulering tools look at various perform ance monitoring units and give hints to the Operating System which makes t he decision to deploy the task to a performance core or an efficiency core .\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nWe propose introducing a quality of servi ce attribute to the Web Workers so that applications and libraries have a way to explicitly label a worker’s preference of performance. User Agent s can take this hint to configure platform thread and possibly affect the scheduling policy.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nSee the [Explainer](http s://github.com/riju/web-worker-quality-of-service/blob/main/explainer.md). \n\n**Goal(s):**\nExtend Web Workers to utilize little/E cores. Get Wider Stakeholder feedback.\n\n\n**Materials:**\n- [slides](https://www.w3.org/2 023/Talks/TPAC/breakouts/web-worker-qos/)\n- [minutes](http://www.w3.org/2 023/09/tpac-breakouts/47-minutes.pdf)\n- [live google doc minutes](https:/ /docs.google.com/document/d/16N8ksiOzWLNGxhuagSNAgMcdQOW-KFy4Nn2aGsjf6EA/e dit#heading=h.mqwe74gibuzg)\n- [recording](https://www.w3.org/2023/09/brea kouts/recording-47.html)\n- [Session proposal on GitHub](https://github.co m/w3c/tpac2023-breakouts/issues/47)\n\n**Track(s):**\n- performance STATUS:CONFIRMED CREATED:20230905T053937Z LAST-MODIFIED:20230923T163247Z SEQUENCE:2 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Nervion I - Level -1 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:1bd7f849-0b67-4aea-bce0-cd8fa2be19d3 DTSTAMP:20230923T162853Z SUMMARY:Cross ShadowRoot ARIA support DTSTART;TZID=Europe/Madrid:20230913T160000 DTEND;TZID=Europe/Madrid:20230913T170000 DESCRIPTION:https://www.w3.org/events/meetings/1bd7f849-0b67-4aea-bce0-cd8f a2be19d3/\n\nThis is a session to discuss ARIA support across shadow DOM b oundaries. This is a continuation of https://github.com/WICG/webcomponents /issues/1005.\n\nAgenda\n\n**Chairs:**\nRyosuke Niwa\n\n**Description:**\n This is a session to discuss ARIA support across shadow DOM boundaries. Th is is a continuation of https://github.com/WICG/webcomponents/issues/1005. \n\n**Goal(s):**\nCome up with a concrete proposal with multi-vendor suppo rt to make ARIA work across shadow boundaries\n\n\n**Materials:**\n- [minu tes](http://www.w3.org/2023/09/tpac-breakouts/14-minutes.pdf)\n- [live goo gle doc minutes](https://docs.google.com/document/d/1DG1eMnVDqQTJe4DdQ5c7f CTXnbneRypYHdSh5s8LsgA/edit)\n- [Session proposal on GitHub](https://githu b.com/w3c/tpac2023-breakouts/issues/14)\n\n**Track(s):**\n- accessibility\ n- web components STATUS:CONFIRMED CREATED:20230905T053630Z LAST-MODIFIED:20230923T162853Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Estepa - 1st floor CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:7b49ce0e-7a95-4570-95c1-48f842a91ed0 DTSTAMP:20231103T141448Z SUMMARY:Feel the Vibe: enhancing haptics for accessibility and more fun DTSTART;TZID=Europe/Madrid:20230913T160000 DTEND;TZID=Europe/Madrid:20230913T170000 DESCRIPTION:https://www.w3.org/events/meetings/7b49ce0e-7a95-4570-95c1-48f8 42a91ed0/\n\nHaptic feedback technologies\, which stimulates the users' se nse of touch through vibration\, motion\, and forces\, has enormous potent ial to make digital experiences more enriching and accessible.\n\n\n\nIn t his session\, we will explore the current state of haptics technology and dive into its applications for improving user experiences and accessibilit y in various digital contexts. We will also discuss the challenges and opp ortunities in integrating haptic technologies into WebApps and Native Apps .\n\n\n\nTopics may include:\n\n\n\n- Current status of haptics APIs\, har dware capabilities\, and global standardization efforts in this field\;\n\ n- Experimental exploration in using haptics to convey non-visual informat ion/experiences\, such as directional navigation\, notifications\, etc\;\n \n- Design considerations for using haptics in a way that works for divers e users and latest research achievements\;\n\n\n\nWe welcome everyone to p articipate in this brainstorming session to explore how to make full use o f haptic technologies and benefit the community.\n\n\n\nSee [Intro video]( https://www.linkedin.com/feed/update/urn:li:activity:7099585039507615744)\ n\nAgenda\n\n**Chairs:**\nHarry Wang\, Selen Xu\n\n**Description:**\nHapti c feedback technologies\, which stimulates the users' sense of touch throu gh vibration\, motion\, and forces\, has enormous potential to make digita l experiences more enriching and accessible.\n\n\n\nIn this session\, we w ill explore the current state of haptics technology and dive into its appl ications for improving user experiences and accessibility in various digit al contexts. We will also discuss the challenges and opportunities in inte grating haptic technologies into WebApps and Native Apps.\n\n\n\nTopics ma y include:\n\n\n\n- Current status of haptics APIs\, hardware capabilities \, and global standardization efforts in this field\;\n\n- Experimental ex ploration in using haptics to convey non-visual information/experiences\, such as directional navigation\, notifications\, etc\;\n\n- Design conside rations for using haptics in a way that works for diverse users and latest research achievements\;\n\n\n\nWe welcome everyone to participate in this brainstorming session to explore how to make full use of haptic technolog ies and benefit the community.\n\n\n\nSee [Intro video](https://www.linked in.com/feed/update/urn:li:activity:7099585039507615744)\n\n**Goal(s):**\nT he session aims to 1) share use cases\, best practices\, and innovative ap proaches about haptic technology and its potential\; 2) discuss opportunit ies and challenges in standardizing haptics for Web\, the possibility to o ffer a new sensory channel for accessibility\; 3) create a platform for co llaboration and communication\, to encourage adoption of the haptic techno logies.\n\n\n**Materials:**\n- [slides](https://www.w3.org/2023/07/breakou t_haptics_TPAC/haptics.pdf)\n- [minutes](https://www.w3.org/2023/09/13-hap tics-minutes.html)\n- [Session proposal on GitHub](https://github.com/w3c/ tpac2023-breakouts/issues/19) STATUS:CONFIRMED CREATED:20230905T053702Z LAST-MODIFIED:20231103T141448Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Ecija - 1st floor CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:d7146840-5093-44bb-9ee4-4d4059b39f3a DTSTAMP:20230921T103750Z SUMMARY:Introducing "Trusted Web" vision DTSTART;TZID=Europe/Madrid:20230913T160000 DTEND;TZID=Europe/Madrid:20230913T170000 DESCRIPTION:https://www.w3.org/events/meetings/d7146840-5093-44bb-9ee4-4d40 59b39f3a/\n\nTrusted Web is a vision to improve trust in the Internet by e xpanding the area where data itself and data exchange activities can be ve rified without overly relying on a specific service. Trusted Web is an ong oing effort of the Trusted Web Promotion Council (TWPC) organized together by academia\, enterprises\, and the Headquarters for Digital Market Compe tition\, a part of the Japanese Government.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\ nTWPC published white papers (version 1.0 and 2.0) until last year. The wh ite paper discusses the backgrounds\, principles\, systems architecture\, governance mechanisms\, and guidelines for practical implementation. Ongoi ng discussions on data security technologies at W3C\, such as Verifiable C redentials and Decentralized Identifiers\, heavily influenced the architec ture and its discussion. Also\, the white paper reflects various feedbacks from multiple experimental projects or use case discussions.\n\n\n\n\n\n\ n\n\n\n\n\n\n\n\n\nTWPC members are working on the new whitepaper version to be published this fall.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nIn this session\ , one of the members of the TWPC introduces the current discussion and cur rent architectural and governance design.\n\nAgenda\n\n**Chairs:**\nShigey a Suzuki\n\n**Description:**\nTrusted Web is a vision to improve trust in the Internet by expanding the area where data itself and data exchange act ivities can be verified without overly relying on a specific service. Trus ted Web is an ongoing effort of the Trusted Web Promotion Council (TWPC) o rganized together by academia\, enterprises\, and the Headquarters for Dig ital Market Competition\, a part of the Japanese Government.\n\n\n\n\n\n\n \n\n\n\n\n\n\n\n\nTWPC published white papers (version 1.0 and 2.0) until last year. The white paper discusses the backgrounds\, principles\, system s architecture\, governance mechanisms\, and guidelines for practical impl ementation. Ongoing discussions on data security technologies at W3C\, suc h as Verifiable Credentials and Decentralized Identifiers\, heavily influe nced the architecture and its discussion. Also\, the white paper reflects various feedbacks from multiple experimental projects or use case discussi ons.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nTWPC members are working on the new wh itepaper version to be published this fall.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\ nIn this session\, one of the members of the TWPC introduces the current d iscussion and current architectural and governance design.\n\n**Goal(s):** \nShowing current status\, possibly receive feedbacks\n\n\n**Materials:**\ n- [slides](https://drive.google.com/file/d/1mp5aczWX63stNSL7ZgxfNfNVuFCDo 1mq/view?usp=drive_link)\n- [recording](https://www.w3.org/2023/09/breakou ts/recording-67.html)\n- [Session proposal on GitHub](https://github.com/w 3c/tpac2023-breakouts/issues/67)\n\n**Track(s):**\n- trust STATUS:CONFIRMED CREATED:20230905T054122Z LAST-MODIFIED:20230921T103750Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Santa Cruz - Level -1 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:e29ce12c-b91a-4714-95ec-a0a6775daafb DTSTAMP:20230921T103317Z SUMMARY:Introducing the Web Sustainability Guidelines (WSGs) DTSTART;TZID=Europe/Madrid:20230913T160000 DTEND;TZID=Europe/Madrid:20230913T170000 DESCRIPTION:https://www.w3.org/events/meetings/e29ce12c-b91a-4714-95ec-a0a6 775daafb/\n\nThis session will explore how the new [Web Sustainability Gui delines](https://w3c.github.io/sustyweb/) can serve as a catalyst for adva ncing digital sustainability and reducing the Web’s overall environmenta l impact. It will also examine how the Sustainable Web Design—’sustywe b’—community group found inspiration in WCAG and other W3C specificati ons to create these guidelines. Finally\, we’ll explore the benefits tha t adopting these guidelines could bring to the internet overall. See also the [At a Glance](https://w3c.github.io/sustyweb/glance.html) resource abo ut the guidelines.\n\n\n\nDiscussion topics will include:\n\n\n\n- Onboard TPAC attendees to emerging digital sustainability and sustainable web des ign guidelines. \n\n\n\n- Answer questions about the guidelines.\n\n\n\n- Foster a discussion about what this could mean long-term for W3C and the W eb overall.\n\nAgenda\n\n**Chairs:**\nTim Frick\, Alexander Dawson\, Łuka sz Mastalerz\n\n**Description:**\nThis session will explore how the new [W eb Sustainability Guidelines](https://w3c.github.io/sustyweb/) can serve a s a catalyst for advancing digital sustainability and reducing the Web’s overall environmental impact. It will also examine how the Sustainable We b Design—’sustyweb’—community group found inspiration in WCAG and other W3C specifications to create these guidelines. Finally\, we’ll exp lore the benefits that adopting these guidelines could bring to the intern et overall. See also the [At a Glance](https://w3c.github.io/sustyweb/glan ce.html) resource about the guidelines.\n\n\n\nDiscussion topics will incl ude:\n\n\n\n- Onboard TPAC attendees to emerging digital sustainability an d sustainable web design guidelines. \n\n\n\n- Answer questions about the guidelines.\n\n\n\n- Foster a discussion about what this could mean long-t erm for W3C and the Web overall.\n\n**Goal(s):**\nRaise awareness of the i mportance of digital sustainability\, answer questions\, and promote the W SGs as a useful resource for anyone to create more sustainable digital pro ducts and services.\n\n\n**Materials:**\n- [slides](https://w3c.github.io/ sustyweb/TPAC_Slides.pdf)\n- [minutes](https://www.w3.org/2023/09/13-susty web-minutes.html)\n- [recording](https://www.w3.org/2023/09/breakouts/reco rding-32.html)\n- [Session proposal on GitHub](https://github.com/w3c/tpac 2023-breakouts/issues/32)\n\n**Track(s):**\n- developer experience STATUS:CONFIRMED CREATED:20230905T053814Z LAST-MODIFIED:20230921T103317Z SEQUENCE:2 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Nervion-Arenal II - Level -1 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:3e3e6590-0956-4678-a0b8-4eab784fdd98 DTSTAMP:20230919T113301Z SUMMARY:Secure the Web Forward DTSTART;TZID=Europe/Madrid:20230913T160000 DTEND;TZID=Europe/Madrid:20230913T170000 DESCRIPTION:https://www.w3.org/events/meetings/3e3e6590-0956-4678-a0b8-4eab 784fdd98/\n\nThis session will be a precursor to our upcoming workshop\, [ Secure the Web Forward](https://www.w3.org/2023/03/secure-the-web-forward/ )\, which aims to increase the overall security of web applications by add ressing the need for clear\, guidelines for web developers\, identifying k ey emerging technologies and gaps.\n\n\n\nPotential discussion points incl ude:\n\n\n\n- the web developer security issues that were [highlighted in the recent survey](https://www.w3.org/blog/2023/securing-the-web-forward-a ddressing-developer-concerns-in-web-security/)\n\n- encouraging collaborat ion between web standards and open-source security initiatives\n\n- better documentation and guides for web developers\n\n- updates in commonly used libraries and web standard APIs\n\n- potential for a new security-focused task force between W3C and other organisations focusing on software secur ity such as the OpenSSF\, OWASP and OpenJS Foundations\n\nAgenda: https:// www.w3.org/2023/Talks/TPAC/breakouts/secure-forward/\n\nAgenda\n\n**Chairs :**\nDaniel Appelquist\n\n**Description:**\nThis session will be a precurs or to our upcoming workshop\, [Secure the Web Forward](https://www.w3.org/ 2023/03/secure-the-web-forward/)\, which aims to increase the overall secu rity of web applications by addressing the need for clear\, guidelines for web developers\, identifying key emerging technologies and gaps.\n\n\n\nP otential discussion points include:\n\n\n\n- the web developer security is sues that were [highlighted in the recent survey](https://www.w3.org/blog/ 2023/securing-the-web-forward-addressing-developer-concerns-in-web-securit y/)\n\n- encouraging collaboration between web standards and open-source s ecurity initiatives\n\n- better documentation and guides for web developer s\n\n- updates in commonly used libraries and web standard APIs\n\n- poten tial for a new security-focused task force between W3C and other organisat ions focusing on software security such as the OpenSSF\, OWASP and OpenJS Foundations\n\n**Goal(s):**\nRaise awareness of the different aspects of t he security topic\, get people talking to each other\, raise awareness of the upcoming workshop\n\n\n**Materials:**\n- [slides](https://www.w3.org/2 023/Talks/TPAC/breakouts/secure-forward/)\n- [minutes](https://www.w3.org/ 2023/09/13-secure-the-web-minutes.html)\n- [Session proposal on GitHub](ht tps://github.com/w3c/tpac2023-breakouts/issues/27) STATUS:CONFIRMED CREATED:20230905T053746Z LAST-MODIFIED:20230919T113301Z SEQUENCE:2 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Nervion I - Level -1 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:d98c0762-eb0c-4cf6-85eb-fff31dedc9e9 DTSTAMP:20230923T163435Z SUMMARY:Standardizing managed user agent behavior DTSTART;TZID=Europe/Madrid:20230913T160000 DTEND;TZID=Europe/Madrid:20230913T170000 DESCRIPTION:https://www.w3.org/events/meetings/d98c0762-eb0c-4cf6-85eb-fff3 1dedc9e9/\n\nMost popular user agents support “enterprise management” features which gives device owners control over the user agent. These feat ures can modify the user-facing behavior of the user agent\, such as by au tomatically configuring bookmarks or the home page\, or by disabling featu res such as integrated developer tools. They may also affect web-exposed b ehavior of the user agent such as by automatically granting or denying per missions. Recent incubations have also proposed new APIs which would only be exposed to sites when running on a managed browser.\n\nAgenda\n\n**Chai rs:**\nReilly Grant\, Jeffrey Yasskin\n\n**Description:**\nMost popular us er agents support “enterprise management” features which gives device owners control over the user agent. These features can modify the user-fac ing behavior of the user agent\, such as by automatically configuring book marks or the home page\, or by disabling features such as integrated devel oper tools. They may also affect web-exposed behavior of the user agent su ch as by automatically granting or denying permissions. Recent incubations have also proposed new APIs which would only be exposed to sites when run ning on a managed browser.\n\n**Goal(s):**\nExplore how to approach standa rdization when these management features have web-exposed behavior.\n\n\n* *Materials:**\n- [slides](https://docs.google.com/presentation/d/1IfZBNqFM 1l0yFPKj3AqRRGV4LV464EDVsVds0--00SM/edit)\n- [minutes](http://www.w3.org/2 023/09/tpac-breakouts/65-minutes.pdf)\n- [live google doc minutes](https:/ /docs.google.com/document/d/1brQFdsFsLtdhcMDmnyhqkpK5TTpDkAIsKVzYvkbs8Lw/e dit)\n- [Session proposal on GitHub](https://github.com/w3c/tpac2023-break outs/issues/65) STATUS:CONFIRMED CREATED:20230905T054111Z LAST-MODIFIED:20230923T163435Z SEQUENCE:2 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Azalea - Low Level CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:0b41175f-1b8d-46dd-be64-24335633dc04 DTSTAMP:20230923T163159Z SUMMARY:The cross-browser future of Installable Web Apps DTSTART;TZID=Europe/Madrid:20230913T160000 DTEND;TZID=Europe/Madrid:20230913T170000 DESCRIPTION:https://www.w3.org/events/meetings/0b41175f-1b8d-46dd-be64-2433 5633dc04/\n\nIn the first part of this session\, the various browser vendo rs and browser contributors discuss their current understanding and implem entation status of the concept of Installable Web Apps\, including\, but n ot limited to and not requiring\, prerequisites for enabling ["powerful fe atures"](https://www.w3.org/TR/permissions/#powerful-features).\n\nAgenda: https://bit.ly/installable-web-apps\n\nAgenda\n\n**Chairs:**\nThomas Stei ner\, Diego Gonzalez-Zuniga\, Kenneth Christiansen\, Marcos Caceres\n\n**D escription:**\nIn the first part of this session\, the various browser ven dors and browser contributors discuss their current understanding and impl ementation status of the concept of Installable Web Apps\, including\, but not limited to and not requiring\, prerequisites for enabling ["powerful features"](https://www.w3.org/TR/permissions/#powerful-features).\n\n**Goa l(s):**\nA stretch goal would be to get aligned on nothing less than the c ross browser future of Installable Web Apps\, per Web Manifest and related standards. A more realistic goal is the continuation of a dialog on the m atter\, and getting everyone at the same table as to potential areas of fu ture standardization.\n\n\n**Materials:**\n- [slides](https://bit.ly/insta llable-web-apps)\n- [minutes](http://www.w3.org/2023/09/tpac-breakouts/40- minutes.pdf)\n- [live google doc minutes](https://docs.google.com/document /d/1QzHTKGDxHol7KybdqY-rll1VGd1FIirvW-mtAFxPjC4/edit)\n- [Session proposal on GitHub](https://github.com/w3c/tpac2023-breakouts/issues/40) STATUS:CONFIRMED CREATED:20230905T053858Z LAST-MODIFIED:20230923T163159Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Magnolia - Low Level CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:9fe72d45-390a-4c2f-8f11-a37ee2a964d3 DTSTAMP:20230919T113657Z SUMMARY:The Login Status API DTSTART;TZID=Europe/Madrid:20230913T160000 DTEND;TZID=Europe/Madrid:20230913T170000 DESCRIPTION:https://www.w3.org/events/meetings/9fe72d45-390a-4c2f-8f11-a37e e2a964d3/\n\nWe want to discuss how the [Login Status API](https://github. com/privacycg/is-logged-in) could be used in [FedCM](https://github.com/fe didcg/FedCM) and other Web APIs to enhance user privacy and user experienc es.\n\n\n\n\n\n\n\nSome helpful context from previous discussions:\n\n\n\n https://github.com/privacycg/is-logged-in/issues/53\n\n\n\nhttps://github. com/privacycg/is-logged-in/pull/54\n\n\n\nhttps://github.com/privacycg/mee tings/blob/main/2023/telcons/08-24-minutes.md#notes\n\nAgenda\n\n**Chairs: **\nJohann Hofmann\, sam goto\n\n**Description:**\nWe want to discuss how the [Login Status API](https://github.com/privacycg/is-logged-in) could be used in [FedCM](https://github.com/fedidcg/FedCM) and other Web APIs to e nhance user privacy and user experiences.\n\n\n\n\n\n\n\nSome helpful cont ext from previous discussions:\n\n\n\nhttps://github.com/privacycg/is-logg ed-in/issues/53\n\n\n\nhttps://github.com/privacycg/is-logged-in/pull/54\n \n\n\nhttps://github.com/privacycg/meetings/blob/main/2023/telcons/08-24-m inutes.md#notes\n\n**Goal(s):**\nAlign implementers and other stakeholders on goals for the Login Status API\n\n\n**Materials:**\n- [minutes](https: //www.w3.org/2023/09/13-login-status-minutes.html)\n- [Session proposal on GitHub](https://github.com/w3c/tpac2023-breakouts/issues/61)\n\n**Track(s ):**\n- privacy STATUS:CONFIRMED CREATED:20230905T054041Z LAST-MODIFIED:20230919T113657Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Giralda III - Level -2 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:e3403253-1357-47f0-9790-5b9c9285f26e DTSTAMP:20231010T101654Z SUMMARY:View Transitions DTSTART;TZID=Europe/Madrid:20230913T160000 DTEND;TZID=Europe/Madrid:20230913T170000 DESCRIPTION:https://www.w3.org/events/meetings/e3403253-1357-47f0-9790-5b9c 9285f26e/\n\n[View Transitions](https://drafts.csswg.org/css-view-transiti ons-1/) allows developers to create animated transitions for DOM changes. The spec currently defines the feature for DOM changes within the same Doc ument but we're actively working on extending this to cross-document navig ations.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nThis session would go into the deta ils of concepts being added for View Transitions on cross-document navigat ions and a few other extensions/feature requests we're evaluating.\n\nAgen da\n\n**Chairs:**\nKhushal Sagar\n\n**Description:**\n[View Transitions](h ttps://drafts.csswg.org/css-view-transitions-1/) allows developers to crea te animated transitions for DOM changes. The spec currently defines the fe ature for DOM changes within the same Document but we're actively working on extending this to cross-document navigations.\n\n\n\n\n\n\n\n\n\n\n\n\n \n\n\nThis session would go into the details of concepts being added for V iew Transitions on cross-document navigations and a few other extensions/f eature requests we're evaluating.\n\n**Goal(s):**\nFeedback on API shape f or cross-document View Transitions\n\n\n**Materials:**\n- [slides](https:/ /docs.google.com/presentation/d/1Y5eBDiFz5w9Do4ozrmpjgUDY62cdtY6GyxoKPa6FA 7Q/edit?usp=sharing)\n- [minutes](https://www.w3.org/2023/09/13-css-minute s.html)\n- [Session proposal on GitHub](https://github.com/w3c/tpac2023-br eakouts/issues/20) STATUS:CONFIRMED CREATED:20230905T053707Z LAST-MODIFIED:20231010T101654Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Triana - Level -1 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:c3bc7b24-dc6a-4c17-b901-377d540f11f8 DTSTAMP:20230921T103811Z SUMMARY:W3C Accessibility Work Priorities for 2024 and Beyond DTSTART;TZID=Europe/Madrid:20230913T160000 DTEND;TZID=Europe/Madrid:20230913T170000 DESCRIPTION:https://www.w3.org/events/meetings/c3bc7b24-dc6a-4c17-b901-377d 540f11f8/\n\nAgenda:\n\n* Brief background: [W3C Accessibility 2023 Contex t](https://wai-mission.netlify.app/2023/)\n\n* Review in-progress [W3C Acc essibility Mission: Vision\, Mission\, Objectives](https://wai-mission.net lify.app/draft/). Any big things missing from the High-Level Objectives?\n \n* Exploring priorities for 2024: Discuss selected [Discussion topics](ht tps://github.com/w3c/wai-mission/discussions).\n\n\n\n**Note:** Before the breakout\, you can nominate topics for discussion by commenting in [GitHu b #70](https://github.com/w3c/tpac2023-breakouts/issues/70)\n\nAgenda: htt ps://github.com/w3c/tpac2023-breakouts/issues/70\n\nAgenda\n\n**Chairs:**\ nShawn Lawton Henry\, Kevin White\n\n**Description:**\nAgenda:\n\n* Brief background: [W3C Accessibility 2023 Context](https://wai-mission.netlify.a pp/2023/)\n\n* Review in-progress [W3C Accessibility Mission: Vision\, Mis sion\, Objectives](https://wai-mission.netlify.app/draft/). Any big things missing from the High-Level Objectives?\n\n* Exploring priorities for 202 4: Discuss selected [Discussion topics](https://github.com/w3c/wai-mission /discussions).\n\n\n\n**Note:** Before the breakout\, you can nominate top ics for discussion by commenting in [GitHub #70](https://github.com/w3c/tp ac2023-breakouts/issues/70)\n\n**Goal(s):**\nShare perspectives impacting WAI priorities for 2024-2025\n\n\n**Materials:**\n- [slides](https://githu b.com/w3c/tpac2023-breakouts/issues/70)\n- [minutes](https://www.w3.org/20 23/09/13-wai-2024-minutes.html)\n- [recording](https://www.w3.org/2023/09/ breakouts/recording-70.html)\n- [Session proposal on GitHub](https://githu b.com/w3c/tpac2023-breakouts/issues/70)\n\n**Track(s):**\n- accessibility STATUS:CONFIRMED CREATED:20230905T054134Z LAST-MODIFIED:20230921T103811Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Prado - Level -1 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:36a66bc5-7515-41a1-b7a8-625d4dadb338 DTSTAMP:20230919T113807Z SUMMARY:Web-based Digital Twins for Smart Cities DTSTART;TZID=Europe/Madrid:20230913T160000 DTEND;TZID=Europe/Madrid:20230913T170000 DESCRIPTION:https://www.w3.org/events/meetings/36a66bc5-7515-41a1-b7a8-625d 4dadb338/\n\nIn 2021\, W3C organized a [workshop on Smart Cities](https:// www.w3.org/2021/06/smartcities-workshop/report.html)\, and identified the stakeholders around Smart City standardization and reasonable applications for Smart City technologies. In addition\, we got initial input on how to organize the draft Charter for a potential Interest Group for further dis cussions.\n\n\n\n\n\n\n\nThen in 2022\, based on the the workshop results\ , we organized a [breakout session during TPAC 2022](https://www.w3.org/20 22/09/14-smartcities-minutes.html) with invited key stakeholders from rela ted SDOs\, e.g.\, ECHONET\, IPA DADC\, IEC SC3D\, ISO/IEC JTC1 WG11\, ITU- T SG20 and OGC.\n\n\n\n\n\n\n\nDuring the session\, we saw related SDOs' s tandardization activities so far\, and identified the following:\n\n\n\n* "Digital Twins" should be the key concept for Smart Cities standardization .\n\n\n\n* Web standards\, e.g.\, Web of Things (WoT)\, Decentralized Iden tifiers (DID) and Verifiable Credentials (VC)\, should be considered as po ssible key modules for the possible Web-based Digital Twins framework.\n\n \n\n* Standard vocabulary for semantic interoperability is also required f or the platform.\n\n\n\n* Collaboration by related SDOs is necessary for f urther discussion\, and W3C should become the central hub for the discussi on given Web standards play very important roles.\n\n\n\n\n\n\n\nBased on the discussion so far\, we've been discussing how to improve the [draft Ch arter](https://w3c.github.io/smartcities-workshop/draft-charter/index.html ) of the proposed Web-based Digital Twins for Smart Cities Interest Group\ , and would like to get input during this session at TPAC 2023 to finalize the draft Charter.\n\nAgenda: https://github.com/w3c/tpac2023-breakouts/i ssues/69#issuecomment-1717055145\n\nAgenda\n\n**Chairs:**\nKazuyuki Ashimu ra\n\n**Description:**\nIn 2021\, W3C organized a [workshop on Smart Citie s](https://www.w3.org/2021/06/smartcities-workshop/report.html)\, and iden tified the stakeholders around Smart City standardization and reasonable a pplications for Smart City technologies. In addition\, we got initial inpu t on how to organize the draft Charter for a potential Interest Group for further discussions.\n\n\n\n\n\n\n\nThen in 2022\, based on the the worksh op results\, we organized a [breakout session during TPAC 2022](https://ww w.w3.org/2022/09/14-smartcities-minutes.html) with invited key stakeholder s from related SDOs\, e.g.\, ECHONET\, IPA DADC\, IEC SC3D\, ISO/IEC JTC1 WG11\, ITU-T SG20 and OGC.\n\n\n\n\n\n\n\nDuring the session\, we saw rela ted SDOs' standardization activities so far\, and identified the following :\n\n\n\n* "Digital Twins" should be the key concept for Smart Cities stan dardization.\n\n\n\n* Web standards\, e.g.\, Web of Things (WoT)\, Decentr alized Identifiers (DID) and Verifiable Credentials (VC)\, should be consi dered as possible key modules for the possible Web-based Digital Twins fra mework.\n\n\n\n* Standard vocabulary for semantic interoperability is also required for the platform.\n\n\n\n* Collaboration by related SDOs is nece ssary for further discussion\, and W3C should become the central hub for t he discussion given Web standards play very important roles.\n\n\n\n\n\n\n \nBased on the discussion so far\, we've been discussing how to improve th e [draft Charter](https://w3c.github.io/smartcities-workshop/draft-charter /index.html) of the proposed Web-based Digital Twins for Smart Cities Inte rest Group\, and would like to get input during this session at TPAC 2023 to finalize the draft Charter.\n\n**Goal(s):**\nFollowing the [breakout di scussion during TPAC 2022](https://www.w3.org/2022/09/14-smartcities-minut es.html)\, we'll summarize the discussion around Smart Cities within W3C s o far\, share the [latest draft Charter for the proposed Web-based Digital Twins for Smart Cities IG](https://w3c.github.io/smartcities-workshop/dra ft-charter/index.html)\, and get input from stakeholders for the proposed IG to finalize the draft Charter\n\n\n**Materials:**\n- [slides](https://w ww.w3.org/2023/Talks/0913-smartcities-ka/)\n- [minutes](https://www.w3.org /2023/09/13-smartcities-minutes.html)\n- [Session proposal on GitHub](http s://github.com/w3c/tpac2023-breakouts/issues/69) STATUS:CONFIRMED CREATED:20230905T054130Z LAST-MODIFIED:20230919T113807Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Giralda V - Level -2 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:3b5b4c6b-e01a-4862-8b85-d6fde09bd228 DTSTAMP:20230919T113909Z SUMMARY:WebCodecs Serialization Format DTSTART;TZID=Europe/Madrid:20230913T160000 DTEND;TZID=Europe/Madrid:20230913T170000 DESCRIPTION:https://www.w3.org/events/meetings/3b5b4c6b-e01a-4862-8b85-d6fd e09bd228/\n\nYou can encode and decode using WebCodecs. But how do you se nd the encoded media over the network? You need to serialize it first. A container format like CMAF is overkill. If you're interested in WebCodec s and would like to send encoded media over the network is a lightweight w ay\, come to this breakout room.\n\n\n\n- [Related interest in a WebCodecs MoQ Media Format in the IETF](https://datatracker.ietf.org/meeting/117/ma terials/slides-117-moq-webcodes-container-00)\n\n- [Related Open Screen Pr otocol work](https://w3c.github.io/openscreenprotocol/#streaming-protocol) \n\nAgenda\n\n**Chairs:**\nPeter Thatcher\n\n**Description:**\nYou can enc ode and decode using WebCodecs. But how do you send the encoded media ove r the network? You need to serialize it first. A container format like C MAF is overkill. If you're interested in WebCodecs and would like to send encoded media over the network is a lightweight way\, come to this breako ut room.\n\n\n\n- [Related interest in a WebCodecs MoQ Media Format in the IETF](https://datatracker.ietf.org/meeting/117/materials/slides-117-moq-w ebcodes-container-00)\n\n- [Related Open Screen Protocol work](https://w3c .github.io/openscreenprotocol/#streaming-protocol)\n\n**Goal(s):**\nSee wh o is interested\; Figure out requirements\; Maybe discuss high-level solut ions\n\n\n**Materials:**\n- [minutes](https://www.w3.org/2023/09/13-webcod ecs-serialization-minutes.html)\n- [Session proposal on GitHub](https://gi thub.com/w3c/tpac2023-breakouts/issues/78) STATUS:CONFIRMED CREATED:20230911T155425Z LAST-MODIFIED:20230919T113909Z SEQUENCE:0 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Lebrija - 1st floor CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:b8617206-4c2b-4355-80da-fcf4eb628d1a DTSTAMP:20230919T113006Z SUMMARY:"You say Schemata\, I say Schemas" DTSTART;TZID=Europe/Madrid:20230913T171500 DTEND;TZID=Europe/Madrid:20230913T181500 DESCRIPTION:https://www.w3.org/events/meetings/b8617206-4c2b-4355-80da-fcf4 eb628d1a/\n\nA large variety of schema languages exist\, defined inside or outside of W3C\; to name a few: [RDF-Schema]\, [OWL]\, [SHACL]\, [ShEx]\, [XML-Schema]\, [JSON-Schema]... Each of these languages have been favored by different categories of users\, who in turn ignore\, neglect\, sometim es even despise the other languages\, deemed "too complicated"\, "less pow erful" or simply "not fit for purpose".\n\n\n\n\n\n\n\nIt might be temptin g to consider that any schema language is worth any other\, and that the " best" one is a matter of technological preferences. We argue on the contra ry that these languages differ in their core purpose\, and should be seen as complementary rather than competitors. More precisely:\n\n\n\n\n\n\n\n* ontology languages such as [RDF-Schema] and [OWL] focus on the **conceptu al modelling** of the domain\,\n\n\n\n* shape languages such as [SHACL] an d [ShEx] focus on the **logical modelling** of the data\,\n\n\n\n* structu ral schema languages such as [XML-Schema] and [JSON-Schema] focus of the * *physical modelling** of exchange formats.\n\n\n\n\n\n\n\nSticking to one schema language to cover all these aspects is therefore suboptimal. Creati ng bridges between their user communities\, to allow cross-fertilization a nd combined use\, is a promising approach.\n\n\n\n\n\n\n\nBut it is also c hallenging\, because it creates the need to maintain consistency across sc hemas at different levels. We will present different tools and methods tha t have been proposed to deal with this problem\, and discuss the standardi zation opportunities in this area.\n\n\n\n\n\n\n\n[RDF-Schema]: https://ww w.w3.org/TR/rdf-schema/\n\n\n\n[OWL]: https://www.w3.org/TR/owl2-primer/\n \n\n\n[SHACL]: https://www.w3.org/TR/shacl/\n\n\n\n[ShEx]: http://shex.io/ shex-primer/index.html\n\n\n\n[XML-Schema]: https://www.w3.org/TR/xmlschem a-1/\n\n\n\n[JSON-Schema]: https://json-schema.org/specification.html\n\nA genda\n\n**Chairs:**\nPierre-Antoine Champin\, Ege Korkan\n\n**Description :**\nA large variety of schema languages exist\, defined inside or outside of W3C\; to name a few: [RDF-Schema]\, [OWL]\, [SHACL]\, [ShEx]\, [XML-Sc hema]\, [JSON-Schema]... Each of these languages have been favored by diff erent categories of users\, who in turn ignore\, neglect\, sometimes even despise the other languages\, deemed "too complicated"\, "less powerful" o r simply "not fit for purpose".\n\n\n\n\n\n\n\nIt might be tempting to con sider that any schema language is worth any other\, and that the "best" on e is a matter of technological preferences. We argue on the contrary that these languages differ in their core purpose\, and should be seen as compl ementary rather than competitors. More precisely:\n\n\n\n\n\n\n\n* ontolog y languages such as [RDF-Schema] and [OWL] focus on the **conceptual model ling** of the domain\,\n\n\n\n* shape languages such as [SHACL] and [ShEx] focus on the **logical modelling** of the data\,\n\n\n\n* structural sche ma languages such as [XML-Schema] and [JSON-Schema] focus of the **physica l modelling** of exchange formats.\n\n\n\n\n\n\n\nSticking to one schema l anguage to cover all these aspects is therefore suboptimal. Creating bridg es between their user communities\, to allow cross-fertilization and combi ned use\, is a promising approach.\n\n\n\n\n\n\n\nBut it is also challengi ng\, because it creates the need to maintain consistency across schemas at different levels. We will present different tools and methods that have b een proposed to deal with this problem\, and discuss the standardization o pportunities in this area.\n\n\n\n\n\n\n\n[RDF-Schema]: https://www.w3.org /TR/rdf-schema/\n\n\n\n[OWL]: https://www.w3.org/TR/owl2-primer/\n\n\n\n[S HACL]: https://www.w3.org/TR/shacl/\n\n\n\n[ShEx]: http://shex.io/shex-pri mer/index.html\n\n\n\n[XML-Schema]: https://www.w3.org/TR/xmlschema-1/\n\n \n\n[JSON-Schema]: https://json-schema.org/specification.html\n\n**Goal(s) :**\nWe will discuss the complementarity of various schema languages\, and which tools are available (or missing...) to make them work together.\n\n \n**Materials:**\n- [slides](https://champin.net/2023/TPAC-Schemata)\n- [m inutes](https://www.w3.org/2023/09/13-schemata-minutes.html)\n- [Session p roposal on GitHub](https://github.com/w3c/tpac2023-breakouts/issues/8) STATUS:CONFIRMED CREATED:20230905T053553Z LAST-MODIFIED:20230919T113006Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Giralda V - Level -2 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:6ef3ef57-47bf-4e70-a97c-0361ffee978f DTSTAMP:20230919T163202Z SUMMARY:Accessible Foundation for Passwordless Experiences with FIDO Passke y DTSTART;TZID=Europe/Madrid:20230913T171500 DTEND;TZID=Europe/Madrid:20230913T181500 DESCRIPTION:https://www.w3.org/events/meetings/6ef3ef57-47bf-4e70-a97c-0361 ffee978f/\n\nFIDO is seeking community insights to get feedback on the tea m’s findings from UX research and through conducting screen reader audit s of live Passkey deployments. The Team will focus on 3 key accessibility areas exposed through our research and audits:\n\n\n\n1. What we know abo ut Passkey accessibility as it relates to accessibility of the website as a whole\n\n2. What we anticipate needing by ways of standardized support a s auto-fill becomes essential in Passkey experiences.\n\n3. What we don’ t know about alternative transport mechanism that are accessible and can r eplace/supplement/modify current solutions.\n\nAgenda\n\n**Chairs:**\nChri stina Hulka\, Joyce Oshita\, Kevin Goldman\n\n**Description:**\nFIDO is se eking community insights to get feedback on the team’s findings from UX research and through conducting screen reader audits of live Passkey deplo yments. The Team will focus on 3 key accessibility areas exposed through our research and audits:\n\n\n\n1. What we know about Passkey accessibilit y as it relates to accessibility of the website as a whole\n\n2. What we a nticipate needing by ways of standardized support as auto-fill becomes ess ential in Passkey experiences.\n\n3. What we don’t know about alternativ e transport mechanism that are accessible and can replace/supplement/modif y current solutions.\n\n**Goal(s):**\nCommunity insights and feedback\n\n\ n**Materials:**\n- [slides](http://www.w3.org/2023/Talks/fido-accessibilit y-breakout.pdf)\n- [minutes](http://www.w3.org/2023/09/fido-passkey-breako ut-20230913.docx)\n- [Session proposal on GitHub](https://github.com/w3c/t pac2023-breakouts/issues/64)\n\n**Track(s):**\n- accessibility STATUS:CONFIRMED CREATED:20230905T054105Z LAST-MODIFIED:20230919T163202Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Prado - Level -1 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:89a19590-3b11-41d1-8129-c03c870f6c29 DTSTAMP:20240301T194013Z SUMMARY:Beyond Text: WAI-Adapt AAC Symbol Specification\, for Visual Markup DTSTART;TZID=Europe/Madrid:20230913T171500 DTEND;TZID=Europe/Madrid:20230913T181500 DESCRIPTION:https://www.w3.org/events/meetings/89a19590-3b11-41d1-8129-c03c 870f6c29/\n\nThe background and a demonstration of the WAI-Adapt Symbols M odule\, the inaugural segment of the broader WAI-Adapt technical specifica tion. This module offers markup for symbols based on underlying semantics such as "food" or "help." Users can enjoy personalized web content\, with symbols rendered in their own preferred visual language. This is the first semantics codified for such symbols\, allowing for the diversity in symbo l choices across different institutions\, regions\, and cultures. A notabl e application is in video chapter headings\, facilitating at-a-glance acce ss. The result will likely benefit people of all types of abilities\, incl uding people with cognitive disabilities\, AAC symbol users and a general audience alike\, as the symbols enhance readability.\n\nAgenda\n\n**Chairs :**\nLionel Wolberger\n\n**Description:**\nThe background and a demonstrat ion of the WAI-Adapt Symbols Module\, the inaugural segment of the broader WAI-Adapt technical specification. This module offers markup for symbols based on underlying semantics such as "food" or "help." Users can enjoy pe rsonalized web content\, with symbols rendered in their own preferred visu al language. This is the first semantics codified for such symbols\, allow ing for the diversity in symbol choices across different institutions\, re gions\, and cultures. A notable application is in video chapter headings\, facilitating at-a-glance access. The result will likely benefit people of all types of abilities\, including people with cognitive disabilities\, A AC symbol users and a general audience alike\, as the symbols enhance read ability.\n\n**Goal(s):**\nBackground of the specification\, a demonstratio n and discussion.\n\n\n**Materials:**\n- [slides](https://raw.githack.com/ w3c/adapt/main/TPAC/2023/)\n- [minutes](https://www.w3.org/2023/09/13-adap t-minutes.html)\n- [recording](https://www.w3.org/2023/09/breakouts/record ing-71.html)\n- [Session proposal on GitHub](https://github.com/w3c/tpac20 23-breakouts/issues/71)\n\n**Track(s):**\n- accessibility STATUS:CONFIRMED CREATED:20230905T054140Z LAST-MODIFIED:20240301T194013Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Ecija - 1st floor CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:fb2d135a-2f5c-44d5-9558-1f987788e8ba DTSTAMP:20230923T163415Z SUMMARY:Fighting fraud without fingerprinting DTSTART;TZID=Europe/Madrid:20230913T171500 DTEND;TZID=Europe/Madrid:20230913T181500 DESCRIPTION:https://www.w3.org/events/meetings/fb2d135a-2f5c-44d5-9558-1f98 7788e8ba/\n\nMany critical anti-fraud use cases depend on highly re-identi fiable client information to discourage scaled abuse and detect specific a ttacks. Scaled abuse includes problems like bulk account creation\, passwo rd guessing\, and spam\, and generally centers on one client misrepresenti ng themselves as many (i.e. [Sybil attack](https://en.wikipedia.org/wiki/S ybil_attack)). Although these anti-fraud use cases generally do not track users\, the browser cannot distinguish these from information collected fo r the purpose of tracking. If we were to reduce fingerprinting by limiting access to entropy-rich information without solutions for anti-fraud\, we would encumber the people fighting fraud and accidentally encourage access gating or degraded experiences for benign users. We would like to explore whether some of these use cases can be satisfied without the risk of cros s-site user tracking.\n\n\n\n\n\n\n\nWe previously suggested a device atte station mechanism experiment (WEI) that tried to provide rate limiting and allow the platform to prove its authenticity without limiting browser mod ifications\, devtools\, extensions\, and similar. The feedback we received made it clear that we did not adequately anticipate the openness and inte roperability concerns of the web\, which we now share. As an alternative\, we would like to explore experimenting with a narrowed use case and discu ss how we can address interoperability and access concerns in our design. Specifically\, is there value in attesting that the request is associated with a single user by proof of a “scarce resource” such as a third-par ty identity or proof of hardware\, in a way that preserves privacy and all ows attesters to compete on the basis of their performance?\n\n\n\n\n\n\n\ nSpecifically we want to ask:\n\n\n\n\n\n\n\n1. Is there value in downscop ing to “attestation of a scarce resource” (e.g. third-party identity\, proof of hardware\, etc) with some protection against scaled misrepresent ation / over-claiming?\n\n\n\n 1. Confirm: [Enforce rate limiting again st a scarce client resource](https://github.com/antifraudcg/use-cases/blob /main/USE-CASES.md#enforce-rate-limiting-against-a-scarce-client-resource) is a capability that currently relies on collection of re-identifiable in formation.\n\n\n\n 2. How scarce does this resource need to be? \n\n\n\ n 3. What latency-tolerant use cases are relevant?\n\n\n\n 4. What o ther anti-fraud / defensibility requirements should we keep in mind?\n\n\n \n2. In order to preserve the openness of the web\, a diverse set of “so urces of scarcity” should be available to users. In order for the confid ence of all verdicts to not be compromised by a single source\, a quality bar has to be upheld.\n\n\n\n 1. Where should the discussion about how an issuer identifies suitable attesters take place?\n\n\n\n 2. Opinions on high barrier to entry and no feedback on observed quality vs. lower ba rrier to entry and feedback on observed quality\n\nAgenda\n\n**Chairs:**\n Philipp Pfeiffenberger\n\n**Description:**\nMany critical anti-fraud use c ases depend on highly re-identifiable client information to discourage sca led abuse and detect specific attacks. Scaled abuse includes problems like bulk account creation\, password guessing\, and spam\, and generally cent ers on one client misrepresenting themselves as many (i.e. [Sybil attack]( https://en.wikipedia.org/wiki/Sybil_attack)). Although these anti-fraud us e cases generally do not track users\, the browser cannot distinguish thes e from information collected for the purpose of tracking. If we were to re duce fingerprinting by limiting access to entropy-rich information without solutions for anti-fraud\, we would encumber the people fighting fraud an d accidentally encourage access gating or degraded experiences for benign users. We would like to explore whether some of these use cases can be sat isfied without the risk of cross-site user tracking.\n\n\n\n\n\n\n\nWe pre viously suggested a device attestation mechanism experiment (WEI) that tri ed to provide rate limiting and allow the platform to prove its authentici ty without limiting browser modifications\, devtools\, extensions\, and si milar. The feedback we received made it clear that we did not adequately a nticipate the openness and interoperability concerns of the web\, which we now share. As an alternative\, we would like to explore experimenting wit h a narrowed use case and discuss how we can address interoperability and access concerns in our design. Specifically\, is there value in attesting that the request is associated with a single user by proof of a “scarce resource” such as a third-party identity or proof of hardware\, in a way that preserves privacy and allows attesters to compete on the basis of th eir performance?\n\n\n\n\n\n\n\nSpecifically we want to ask:\n\n\n\n\n\n\n \n1. Is there value in downscoping to “attestation of a scarce resource ” (e.g. third-party identity\, proof of hardware\, etc) with some protec tion against scaled misrepresentation / over-claiming?\n\n\n\n 1. Confi rm: [Enforce rate limiting against a scarce client resource](https://githu b.com/antifraudcg/use-cases/blob/main/USE-CASES.md#enforce-rate-limiting-a gainst-a-scarce-client-resource) is a capability that currently relies on collection of re-identifiable information.\n\n\n\n 2. How scarce does t his resource need to be? \n\n\n\n 3. What latency-tolerant use cases ar e relevant?\n\n\n\n 4. What other anti-fraud / defensibility requiremen ts should we keep in mind?\n\n\n\n2. In order to preserve the openness of the web\, a diverse set of “sources of scarcity” should be available t o users. In order for the confidence of all verdicts to not be compromised by a single source\, a quality bar has to be upheld.\n\n\n\n 1. Where should the discussion about how an issuer identifies suitable attesters ta ke place?\n\n\n\n 2. Opinions on high barrier to entry and no feedback on observed quality vs. lower barrier to entry and feedback on observed qu ality\n\n**Goal(s):**\n1. Confirmation that anti-fraud use cases should se ek alternatives to fingerprinting-like practices. 2. Explore whether an ex periment with a narrow focus would have anti-fraud value\, and help tackle those use cases. 3. Collect requirements for open access to attesters tha t also ensures effectiveness of attesters for relying parties.\n\n**Attend ance:**\nThis session is restricted to TPAC registrants.\n\n**Materials:** \n- [slides](https://docs.google.com/presentation/d/1kZNg8YMtYpVgDrAk215mn fkISyGpO9SdeMffIHv98mI/edit#slide=id.p)\n- [minutes](http://www.w3.org/202 3/09/tpac-breakouts/62-minutes.pdf)\n- [live google doc minutes](https://d ocs.google.com/document/d/1Rr9pfGyJpQrNsTJ9VO183fbEgq9D7JwsoDlnnQgNXSE/edi t#heading=h.2cnghmlk7zlo)\n- [Session proposal on GitHub](https://github.c om/w3c/tpac2023-breakouts/issues/62)\n\n**Track(s):**\n- privacy STATUS:CONFIRMED CREATED:20230905T054053Z LAST-MODIFIED:20230923T163415Z SEQUENCE:2 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Giralda III - Level -2 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:009a5b81-0459-4ae4-9b33-f88dd9a9d89f DTSTAMP:20230919T113848Z SUMMARY:HDR on the web DTSTART;TZID=Europe/Madrid:20230913T171500 DTEND;TZID=Europe/Madrid:20230913T181500 DESCRIPTION:https://www.w3.org/events/meetings/009a5b81-0459-4ae4-9b33-f88d d9a9d89f/\n\nDiscussion [rendering of existing HDR content (images/video)] (https://github.com/whatwg/html/issues/9112)\, proposed HDR APIs (canvas/W ebGL/[GPU](https://github.com/ccameron-chromium/webgpu-hdr/blob/main/EXPLA INER.md))\, the need for [more expressive media queries](https://github.co m/w3c/csswg-drafts/issues/9306)\, and interactions with CSS colors.\n\n\n\ n[Slides](https://docs.google.com/presentation/d/18hvbKBF-v586kFlscpqQ9xYA W03euX6IwLX818G1XG0/edit?usp=sharing).\n\n\n\nSpecific issues:\n\n* Review of definitions of HDR displays and HDR content\n\n* Standardize rendering of HDR content ([issue](https://github.com/whatwg/html/issues/9112))\n\n* Add CSS property to limit HDR brightness ([issue](https://github.com/w3c/ csswg-drafts/issues/9074)\, [proposal](https://github.com/ccameron-chromiu m/hdr-headroom-limit/blob/main/EXPLAINER.md))\n\n * Default behavior for HDR content (no issue)\n\n* More expressive queries about HDR screen capab ilities ([issue](https://github.com/w3c/csswg-drafts/issues/9306))\n\n* We bGPU HDR support\n\n * Extended range support ([proposal](https://github. com/ccameron-chromium/webgpu-hdr/blob/main/EXPLAINER.md))\n\n * Tone mapp ed support to match HLG and PQ (no issue filed)\n\n* 2D Canvas and WebGL H DR support\n\n * WebGL floating point support ([drawingBufferStorage prop osal](https://github.com/KhronosGroup/WebGL/pull/3222))\n\n * 2D Canvas a nd ImageData floating point support ([issue](https://github.com/whatwg/htm l/issues/8708)\, [proposal](https://github.com/w3c/ColorWeb-CG/blob/main/c anvas_float.md))\n\n * 2D canvas HDR support ([proposal](https://github.c om/w3c/ColorWeb-CG/blob/main/hdr_html_canvas_element.md))\, or alternative ly use same metadata from WebGPU proposal\n\nAgenda\n\n**Chairs:**\nChrist opher Cameron\n\n**Description:**\nDiscussion [rendering of existing HDR c ontent (images/video)](https://github.com/whatwg/html/issues/9112)\, propo sed HDR APIs (canvas/WebGL/[GPU](https://github.com/ccameron-chromium/webg pu-hdr/blob/main/EXPLAINER.md))\, the need for [more expressive media quer ies](https://github.com/w3c/csswg-drafts/issues/9306)\, and interactions w ith CSS colors.\n\n\n\n[Slides](https://docs.google.com/presentation/d/18h vbKBF-v586kFlscpqQ9xYAW03euX6IwLX818G1XG0/edit?usp=sharing).\n\n\n\nSpecif ic issues:\n\n* Review of definitions of HDR displays and HDR content\n\n* Standardize rendering of HDR content ([issue](https://github.com/whatwg/h tml/issues/9112))\n\n* Add CSS property to limit HDR brightness ([issue](h ttps://github.com/w3c/csswg-drafts/issues/9074)\, [proposal](https://githu b.com/ccameron-chromium/hdr-headroom-limit/blob/main/EXPLAINER.md))\n\n * Default behavior for HDR content (no issue)\n\n* More expressive queries about HDR screen capabilities ([issue](https://github.com/w3c/csswg-drafts /issues/9306))\n\n* WebGPU HDR support\n\n * Extended range support ([pro posal](https://github.com/ccameron-chromium/webgpu-hdr/blob/main/EXPLAINER .md))\n\n * Tone mapped support to match HLG and PQ (no issue filed)\n\n* 2D Canvas and WebGL HDR support\n\n * WebGL floating point support ([dra wingBufferStorage proposal](https://github.com/KhronosGroup/WebGL/pull/322 2))\n\n * 2D Canvas and ImageData floating point support ([issue](https:/ /github.com/whatwg/html/issues/8708)\, [proposal](https://github.com/w3c/C olorWeb-CG/blob/main/canvas_float.md))\n\n * 2D canvas HDR support ([prop osal](https://github.com/w3c/ColorWeb-CG/blob/main/hdr_html_canvas_element .md))\, or alternatively use same metadata from WebGPU proposal\n\n**Goal( s):**\nContinue to converge on a vision for High Dynamic Range (HDR) on th e web.\n\n\n**Materials:**\n- [slides](https://docs.google.com/presentatio n/d/18hvbKBF-v586kFlscpqQ9xYAW03euX6IwLX818G1XG0/edit?usp=sharing)\n- [min utes](https://www.w3.org/2023/09/13-hdr-minutes.html)\n- [Session proposal on GitHub](https://github.com/w3c/tpac2023-breakouts/issues/74) STATUS:CONFIRMED CREATED:20230905T054155Z LAST-MODIFIED:20230919T113848Z SEQUENCE:2 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Nervion-Arenal II - Level -1 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:c4db57e5-99e9-496d-9b4e-87dd5c421966 DTSTAMP:20230923T163327Z SUMMARY:Installing Web Apps DTSTART;TZID=Europe/Madrid:20230913T171500 DTEND;TZID=Europe/Madrid:20230913T181500 DESCRIPTION:https://www.w3.org/events/meetings/c4db57e5-99e9-496d-9b4e-87dd 5c421966/\n\nWe will discuss about options to install applications using the web platform. API? Install banners? cross platform support? tracking c ampaign ids? Let's discuss what installation on the web looks like.\n\nAge nda\n\n**Chairs:**\nDiego Gonzalez-Zuniga\n\n**Description:**\nWe will dis cuss about options to install applications using the web platform. API? I nstall banners? cross platform support? tracking campaign ids? Let's discu ss what installation on the web looks like.\n\n**Goal(s):**\nAligning view s on installing apps from the web\n\n\n**Materials:**\n- [minutes](https:/ /lists.w3.org/Archives/Public/www-archive/2023Sep/att-0022/Web_Install_API _TPAC_23_discussion.pdf)\n- [Session proposal on GitHub](https://github.co m/w3c/tpac2023-breakouts/issues/56) STATUS:CONFIRMED CREATED:20230905T054014Z LAST-MODIFIED:20230923T163327Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Magnolia - Low Level CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:4def6ec0-23c7-4357-8732-af2fb591965b DTSTAMP:20230923T163024Z SUMMARY:Partitioning :visited links history DTSTART;TZID=Europe/Madrid:20230913T171500 DTEND;TZID=Europe/Madrid:20230913T181500 DESCRIPTION:https://www.w3.org/events/meetings/4def6ec0-23c7-4357-8732-af2f b591965b/\n\nThis breakout session will:\n\n\n\n\n\n\n\n- Briefly recap th e [Partitioning :visited links history explainer](https://github.com/kyras eevers/Partitioning-visited-links-history). \n\n\n\n\n\n\n\n- Discuss the proposed solution\, generate open questions\, and get cross-browser feedba ck.\n\n\n\n\n\n\n\n- Go over implementation progress in Chrome and highlig ht solutions that may be valuable to other developers.\n\n\n\n\n\n\n\n- Di scuss how to spec this proposal and how standardization choices now may af fect future privacy improvements to CSS\n\n\n\n\n\n\n\n- Determine what wo rk remains towards removing the [2010 privacy mitigations](https://develop er.mozilla.org/en-US/docs/Web/CSS/Privacy_and_the_:visited_selector).\n\nA genda\n\n**Chairs:**\nKyra Seevers\, Artur Janc\, Mike Taylor\n\n**Descrip tion:**\nThis breakout session will:\n\n\n\n\n\n\n\n- Briefly recap the [P artitioning :visited links history explainer](https://github.com/kyraseeve rs/Partitioning-visited-links-history). \n\n\n\n\n\n\n\n- Discuss the prop osed solution\, generate open questions\, and get cross-browser feedback.\ n\n\n\n\n\n\n\n- Go over implementation progress in Chrome and highlight s olutions that may be valuable to other developers.\n\n\n\n\n\n\n\n- Discus s how to spec this proposal and how standardization choices now may affect future privacy improvements to CSS\n\n\n\n\n\n\n\n- Determine what work r emains towards removing the [2010 privacy mitigations](https://developer.m ozilla.org/en-US/docs/Web/CSS/Privacy_and_the_:visited_selector).\n\n**Goa l(s):**\nGet cross-browser feedback on the partitioning proposal and stand ardization plan.\n\n\n**Materials:**\n- [minutes](http://www.w3.org/2023/0 9/tpac-breakouts/25-minutes.pdf)\n- [slides](https://docs.google.com/prese ntation/d/1e1fzGxChIqbhI178q49uWQJbXznBN1TNixfma5AAjhg/edit?usp=sharing)\n - [Session proposal on GitHub](https://github.com/w3c/tpac2023-breakouts/i ssues/25)\n\n**Track(s):**\n- privacy STATUS:CONFIRMED CREATED:20230905T053736Z LAST-MODIFIED:20230923T163024Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Azalea - Low Level CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:ca1ae937-699a-47f8-b930-94f7d49753e7 DTSTAMP:20230919T113252Z SUMMARY:Report to Members\, Hearing from Members DTSTART;TZID=Europe/Madrid:20230913T171500 DTEND;TZID=Europe/Madrid:20230913T181500 DESCRIPTION:https://www.w3.org/events/meetings/ca1ae937-699a-47f8-b930-94f7 d49753e7/\n\nA breakout session to report on the progress of the member re lations program offered by W3C to its members. Panelists and participants will discuss how W3C can contribute to the community of the members.\n\n\n \n\n\n\n\n- Do members want country or region-specific networking?\n\n\n\n - Any issues when you joined?\n\n\n\n- What is "Ambassador"? What is the e nvironment in which they are created?\n\n\n\n- Mutual aid among members?\n \n\n\n- What support would members like W3C to provide?\n\n\n\n- What do w e want Chapters for members?\n\nAgenda: https://github.com/w3c/tpac2023-br eakouts/issues/26#issuecomment-1717344984\n\nAgenda\n\n**Chairs:**\nNaomi Yoshizawa\n\n**Description:**\nA breakout session to report on the progres s of the member relations program offered by W3C to its members. Panelists and participants will discuss how W3C can contribute to the community of the members.\n\n\n\n\n\n\n\n- Do members want country or region-specific n etworking?\n\n\n\n- Any issues when you joined?\n\n\n\n- What is "Ambassad or"? What is the environment in which they are created?\n\n\n\n- Mutual ai d among members?\n\n\n\n- What support would members like W3C to provide?\ n\n\n\n- What do we want Chapters for members?\n\n**Goal(s):**\nW3C Member Relations will give shape to ideas from the members and return them to th e members.\n\n\n**Materials:**\n- [slides](https://www.w3.org/2023/Talks/T PAC/breakouts/member-report/)\n- [minutes](https://www.w3.org/2023/09/13-4 members-minutes.html)\n- [Session proposal on GitHub](https://github.com/w 3c/tpac2023-breakouts/issues/26) STATUS:CONFIRMED CREATED:20230905T053741Z LAST-MODIFIED:20230919T113252Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Triana - Level -1 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT BEGIN:VEVENT UID:30dd11d6-0eac-49ab-9ff1-743c5ef1b332 DTSTAMP:20230919T112926Z SUMMARY:Specification Markup and CSS Workshop for Editors and Team Contacts DTSTART;TZID=Europe/Madrid:20230913T171500 DTEND;TZID=Europe/Madrid:20230913T181500 DESCRIPTION:https://www.w3.org/events/meetings/30dd11d6-0eac-49ab-9ff1-743c 5ef1b332/\n\nW3C specifications use a common set of stylesheets and markup conventions\, which are documented at https://www.w3.org/StyleSheets/TR/2 021/README and maintained at https://github.com/w3c/tr-design (Bikeshed an d ReSpec output this format.)\n\n\n\nIn this breakout session we will:\n\n \n\n* Do a quick review of what capabilities are already built into our si te-wide CSS and HTML conventions\, so that you can use them effectively (a nd avoid custom styles)\n\n* Discuss when to put custom styles in your own CSS vs when to upstream them for everyone\n\n* Answer questions about our technical report styling and templates\n\n* Discuss possible improvements \, and maybe draft some up!\n\nAgenda\n\n**Chairs:**\nElika Etemad\n\n**De scription:**\nW3C specifications use a common set of stylesheets and marku p conventions\, which are documented at https://www.w3.org/StyleSheets/TR/ 2021/README and maintained at https://github.com/w3c/tr-design (Bikeshed a nd ReSpec output this format.)\n\n\n\nIn this breakout session we will:\n\ n\n\n* Do a quick review of what capabilities are already built into our s ite-wide CSS and HTML conventions\, so that you can use them effectively ( and avoid custom styles)\n\n* Discuss when to put custom styles in your ow n CSS vs when to upstream them for everyone\n\n* Answer questions about ou r technical report styling and templates\n\n* Discuss possible improvement s\, and maybe draft some up!\n\n**Goal(s):**\nPart 1: Educate editors and Team Contacts\; Part 2: Design and code improvements\n\n\n**Materials:**\n - [minutes](https://www.w3.org/2023/09/13-tr-design-minutes.html)\n- [Sess ion proposal on GitHub](https://github.com/w3c/tpac2023-breakouts/issues/3 ) STATUS:CONFIRMED CREATED:20230905T053522Z LAST-MODIFIED:20230919T112926Z SEQUENCE:2 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:Nervion I - Level -1 CATEGORIES:TPAC 2023,Breakout Sessions END:VEVENT END:VCALENDAR