BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Sabre//Sabre VObject 4.5.8//EN
CALSCALE:GREGORIAN
NAME:W3C Breakouts Day 2025 Calendar
X-WR-CALNAME:W3C Breakouts Day 2025 Calendar
LAST-MODIFIED:20260204T180051Z
BEGIN:VTIMEZONE
TZID:Etc/UTC
BEGIN:STANDARD
DTSTART:20240331T130000
TZOFFSETFROM:+0000
TZOFFSETTO:+0000
TZNAME:UTC
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
UID:3c15ca06-8876-442e-a385-8eab2b64a55c
DTSTAMP:20260204T175637Z
SUMMARY:Browser experience of ActivityPub social networking
DTSTART;TZID=Etc/UTC:20250326T130000
DTEND;TZID=Etc/UTC:20250326T140000
DESCRIPTION:https://www.w3.org/events/meetings/3c15ca06-8876-442e-a385-8eab
 2b64a55c/\n\nA breakout session to discuss how browser users can interact 
 with ActivityPub-enabled people and objects on the Web. For example: follo
 wing people\, liking and commenting on text or images.\n\n**Goal(s):**\nIn
 vestigate how browser users can interact with ActivityPub-enabled people a
 nd objects on the Web and define next steps\n\nAgenda\n\n- review use case
 s\n- review discovery draft document\n- open discussion\n\n**Materials:**\
 n- [Session proposal on GitHub](https://github.com/w3c/breakouts-day-2025/
 issues/4)
STATUS:CONFIRMED
CREATED:20250314T182133Z
LAST-MODIFIED:20260204T175637Z
SEQUENCE:7
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Marigold
CATEGORIES:W3C Breakouts Day 2025,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:bedbccc0-b160-4a2b-a16e-ed95326da038
DTSTAMP:20260204T175714Z
SUMMARY:Federated Credential Management (FedCM) Demo + Roadmap
DTSTART;TZID=Etc/UTC:20250326T130000
DTEND;TZID=Etc/UTC:20250326T140000
DESCRIPTION:https://www.w3.org/events/meetings/bedbccc0-b160-4a2b-a16e-ed95
 326da038/\n\nWhere do we stand with [FedCM](https://github.com/w3c-fedid/F
 edCM)? We'll show you and talk about the roadmap for where we think things
  are going next.\n\n**Goal(s):**\nFedCM Update\n\nAgenda\n\n**Materials:**
 \n- [Session proposal on GitHub](https://github.com/w3c/breakouts-day-2025
 /issues/1)
STATUS:CONFIRMED
CREATED:20250314T182117Z
LAST-MODIFIED:20260204T175714Z
SEQUENCE:7
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Yucca
CATEGORIES:W3C Breakouts Day 2025,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:47c8159d-9fea-4778-9b04-bd28a479a7c2
DTSTAMP:20260204T175838Z
SUMMARY:More performant\, diverse Web engines
DTSTART;TZID=Etc/UTC:20250326T130000
DTEND;TZID=Etc/UTC:20250326T140000
DESCRIPTION:https://www.w3.org/events/meetings/47c8159d-9fea-4778-9b04-bd28
 a479a7c2/\n\nThis session will explore how to **diversify the ecosystem of
  Web user agents by enabling profile applications** to increase efficiency
  and optimize user experience on Web and WebView-based apps while maintain
 ing compatibility with existing standards and the **One-Web** principle. \
 n\n#### Background\n\nIn early January\, W3C organized the [WebAI and High
 -Performance Web Application Technology seminar](https://www.w3.org/2024/0
 1/webevolve-series-events/ai-and-highperf/zh.index.html) for the Chinese c
 ommunity. One of the outcomes of the discussions was the launch of a new C
 G to support more variety and more performant Web user agents. \n\nThe CG 
 aims to diversify the **ecosystem of Web user agents** by enabling **profi
 le standards to increase efficiency and optimize user experience** on Web 
 and WebView-based apps while maintaining compatibility with existing stand
 ards. Standard profiles and modularity might ease the design and implement
 ation of lighter and more efficient engines for specific-scenario purposes
  when a full-fledged (embedded) browser is not required (e.g.\, MiniApps\,
  WoT edge apps\, and apps for wearables or constrained infotainment system
 s) and may serve as common ground for cross-platform development framework
 s. \n\nPackage distribution strategies should be considered in conjunction
  with profile standards to ensure optimal content presentation across dive
 rse platforms. Profile standards should be built with mobile-friendly feat
 ures by default\, ensuring a superior user experience and leveraging the u
 nique capabilities of mobile devices.\n\nThe CG was titled _High-Performan
 ce Baseline for Web Apps_ as a placeholder\, but we know it could be misle
 ading -also the initial description. In this breakout session\, we would l
 ike to clarify the objectives and get the community's feedback to include 
 these insights in the final chapter. The title\, scope\, and objectives wi
 ll be discussed in this session.\n\n#### Audience\n\nThis session welcomes
  vendors of embedded browsers\, hybrid cross-platform app frameworks\, JS 
 engines\, and others interested in exploring the modularity of the Web sta
 ndards. We aim to collect use cases where standard profiles help enrich th
 e Web ecosystem by opening new possibilities in unexplored scenarios and s
 upporting innovation on the Web while protecting the principles of **One-W
 eb** and **interoperability**.\n\nWe also want close alignment with other 
 incubation groups working on similar topics (i.e.\, **WebViews CG**\, **W
 ebDX**\,  **WinterTC**) and bi-directional conversations with core standa
 rdization groups for advice and pushing for new standardization requiremen
 ts while avoiding fragmentation. \n\nCheck more information\, including re
 search on [this explainer](https://github.com/espinr/high-perf-apps/blob/m
 ain/explainer.md) and on [this blog post](https://www.w3.org/community/hig
 h-perf-baseline/2025/03/09/a-proposal-for-high-performance-web/).\n\n**Goa
 l(s):**\nDiscuss potential objectives\, scope\, and interest from the comm
 unity in this new incubation activity.\n\nAgenda\n\n1. Adaptive Web Engine
 s ([slides](https://www.w3.org/2025/Talks/adaptive-engines-breakouts-2025.
 pdf)) (10') - @ysbcc\n2. Early discussions and objectives ([slides](https:
 //www.w3.org/2025/Talks/adaptive-discussion-breakouts-2025.html)) (10') - 
 @espinr \n3. Discussion - everyone\n\n**Materials:**\n- [recording](https:
 //www.w3.org/2025/03/breakouts-day-2025/recordings/recording-6.html)\n- [v
 ic yao's slides](https://www.w3.org/2025/Talks/adaptive-engines-breakouts-
 2025.pdf)\n- [martin's slides](https://www.w3.org/2025/Talks/adaptive-disc
 ussion-breakouts-2025.html)\n- [Session proposal on GitHub](https://github
 .com/w3c/breakouts-day-2025/issues/6)\n\n**Track(s):**\n- browsers
STATUS:CONFIRMED
CREATED:20250314T182200Z
LAST-MODIFIED:20260204T175838Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Cactus
CATEGORIES:W3C Breakouts Day 2025,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:a6b80080-4af5-43f4-bc55-823cc6fdf8b7
DTSTAMP:20260204T175954Z
SUMMARY:Simplifying Site Navigation: A Standardized Approach for Accessible
  Destinations
DTSTART;TZID=Etc/UTC:20250326T130000
DTEND;TZID=Etc/UTC:20250326T140000
DESCRIPTION:https://www.w3.org/events/meetings/a6b80080-4af5-43f4-bc55-823c
 c6fdf8b7/\n\nWebsite visitors often expect and seek familiar pages such as
  contact us\, login\, or shopping cart. But navigating websites can be a c
 hallenge\, especially for users who find complex layouts and variable term
 inology difficult. Building on last year’s feedback\, this session from 
 WAI-Adapt Task Force introduces a fresh\, semantic approach to navigation 
 that leverages HTML link relation types to define such well known destinat
 ions on any page. We will also demo our updated browser extension which em
 bodies this new strategy— simplifying navigation without compromising on
  design.  \n \nWe will also facilitate discussion on open challenges ident
 ified by the Cognitive and Learning Disabilities Accessibility Task Force 
 (COGA) regarding the clear presentation of destination types. For example\
 , a help resource may be categorized as a “Virtual Advisor\,” “Email
  Helpline\,” or “Call Support.” The goal is to ensure that users can
  simply understand the nature of each option and set accurate expectations
  before engagement.\n\n**Goal(s):**\nHighlight the challenge\; Showcase so
 lutions\; and Engage the community\n\nAgenda\n\n1.	Understanding Navigatio
 n Barriers: A brief look at navigation challenges and why consistency matt
 ers. \n2.	Demo: Walkthrough of our updated browser extension employing the
  new semantic approach. \n3.	WAI-Adapt’s Proposed Solution: Explanation 
 of our approach based on standardizing navigation declarations using HTML 
 link elements and how it builds on last year’s feedback.  \n4.	Interacti
 ve Discussion: Brainstorming on open concerns from COGA to present various
  type of destinations to users. \n5.	Next Steps: Inviting feedback and out
 lining plans for horizontal and wide community review.\n\n**Materials:**\n
 - [Session proposal on GitHub](https://github.com/w3c/breakouts-day-2025/i
 ssues/9)
STATUS:CONFIRMED
CREATED:20250314T182226Z
LAST-MODIFIED:20260204T175954Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Agave
CATEGORIES:W3C Breakouts Day 2025,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:6269dcfb-9958-42df-97de-d41804191ccf
DTSTAMP:20260204T180051Z
SUMMARY:W3C Global meetings structure - Focus on AC meetings
DTSTART;TZID=Etc/UTC:20250326T130000
DTEND;TZID=Etc/UTC:20250326T140000
DESCRIPTION:https://www.w3.org/events/meetings/6269dcfb-9958-42df-97de-d418
 04191ccf/\n\nW3C\, in conjunction with the AB\, is looking at its Events s
 trategy. The Events strategy consists of aligning each event to the global
  objectives of the Consortium. Each event needs to fulfill a specific goal
  which serves W3C\, their Members and the community. \nMeetings are organi
 zed for specific reasons and goals. In general\, meeting are organized for
  different purposes:\n- Gather targeted stakeholders to move forward on so
 me problematic\n- Inform and explain\n- Make decisions\n- Create interacti
 ons between participants\n\nWe will focus this discussion on the AC meetin
 gs: The participation to these meetings has significantly decreased when t
 he hybrid mode has been re-initiated in 2023\, after the pandemic. The goa
 l of the meeting may not be inline with the expectations anymore. We are t
 hen looking at restructuring this meeting and need to hear from our commun
 ity.\n\n**Goal(s):**\nGather feedback from the W3C Members and AC Reps to 
 come up with a restructuring proposal\n\nAgenda\n\n- Presentation of the c
 ontext\n- Gathering feedback (questions will be available to target the di
 scussion)\n\n**Materials:**\n- [Session proposal on GitHub](https://github
 .com/w3c/breakouts-day-2025/issues/13)\n\n**Track(s):**\n- organization
STATUS:CONFIRMED
CREATED:20250314T182254Z
LAST-MODIFIED:20260204T180051Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Aloe
CATEGORIES:W3C Breakouts Day 2025,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:6b2387f3-1d06-46b1-9285-dc5e22aa47f7
DTSTAMP:20260204T174952Z
SUMMARY:How would AI Agents change the Web platform?
DTSTART;TZID=Etc/UTC:20250326T140000
DTEND;TZID=Etc/UTC:20250326T150000
DESCRIPTION:https://www.w3.org/events/meetings/6b2387f3-1d06-46b1-9285-dc5e
 22aa47f7/\n\nAs a significant development since the release of [_AI & the 
 Web_ W3C Team report](https://www.w3.org/reports/ai-web-impact/)\, Machine
  Learning models\, and in particular Large Language Models (LLMs)\, are in
 creasing deployed to complement and sometimes radically transform how user
 s interact with the Web.\n\nIn this session\, after a quick introduction o
 f the various ways these new AI agents are being surfaced today\, we will 
 have an open discussion on how this new paradigm may change the platform i
 tself\, and what (if anything) we should do as a community to prepare its 
 potential impact on Web standards.\n\n**Goal(s):**\nBuild shared understan
 ding of impact of AI agents on the Web Platform\n\nAgenda\n\n* Presentatio
 n: [How would AI Agents change the Web platform?](https://www.w3.org/2025/
 Talks/dhm-ai-agents/) (Dominique Hazael-Massieux)\n* Discussion: what shou
 ld W3C do in this space and how to approach it?\n\n**Materials:**\n- [Sess
 ion proposal on GitHub](https://github.com/w3c/breakouts-day-2025/issues/7
 )
STATUS:CONFIRMED
CREATED:20250314T182207Z
LAST-MODIFIED:20260204T174952Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Agave
CATEGORIES:W3C Breakouts Day 2025,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:97790087-97c8-4d89-b3ce-c3a80ef8c343
DTSTAMP:20260204T175042Z
SUMMARY:Mitigate Threats for Digital Credentials API: Episode II - Attack o
 f...
DTSTART;TZID=Etc/UTC:20250326T140000
DTEND;TZID=Etc/UTC:20250326T150000
DESCRIPTION:https://www.w3.org/events/meetings/97790087-97c8-4d89-b3ce-c3a8
 0ef8c343/\n\nIn the [first episode](https://github.com/w3c/tpac2024-breako
 uts/issues/98) we focused on high-level threats related to the [Formal Obj
 ection received for the addition of the Digital Credentials API](https://l
 ists.w3.org/Archives/Public/public-review-comments/2024Sep/0017.html).\n\n
 Considering that the [W3C Council has overruled the Formal Objection](http
 s://www.w3.org/2025/02/council-report-fedid-dig-cred.html)\, the Digital C
 redentials API is by design strongly linked to its Threat Model.\n\nIn thi
 s episode\, we will therefore focus on a specific model about the step of 
 Presenting Credentials on the Web\, [asking ourselves](https://github.com/
 adamshostack/4QuestionFrame): What are we working on? What can go wrong? W
 hat are we going to do about it? Did we do a good job?\n\nThis breakout is
  intended to be a collaborative\, working session. The focus will be on ga
 ining consensus on threats and mitigations.\n\n**Goal(s):**\nThe focus wil
 l be on gaining consensus on the mitigations.\n\nAgenda\n\n**Materials:**\
 n- [Session proposal on GitHub](https://github.com/w3c/breakouts-day-2025/
 issues/17)
STATUS:CONFIRMED
CREATED:20250314T182335Z
LAST-MODIFIED:20260204T175042Z
SEQUENCE:7
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Marigold
CATEGORIES:W3C Breakouts Day 2025,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:6bd2c029-8937-4045-979f-5a14d03f5178
DTSTAMP:20260204T175209Z
SUMMARY:Revisit the purpose of the AB
DTSTART;TZID=Etc/UTC:20250326T140000
DTEND;TZID=Etc/UTC:20250326T150000
DESCRIPTION:https://www.w3.org/events/meetings/6bd2c029-8937-4045-979f-5a14
 d03f5178/\n\nAs a member elected body\, the Advisory Board has been playin
 g a unique and important role in W3C community since 1998. It not only pro
 vides ongoing guidance to W3C Team on various topics\, forms the Council w
 ith the TAG to handle formal objections\, and also leads the development o
 f several key W3C polices\, such as Vision document\, Process Document\, C
 ode of Conduct\, etc. \n\nWith W3C Inc up and running as a new legal entit
 y since Jan 1 2023\, W3C has built its new governance structure. The W3C B
 oard of Directors have ultimate authority on W3C's strategic direction and
  have fiduciary responsibility over W3C Inc as a whole. \n\nGiven this bac
 kground\, it is time for the Advisory Board to work with the W3C community
  and revisit its purpose.\n\n**Goal(s):**\nTo seek members input about the
  purpose of the AB\, the unique values that the AB can bring to the W3C co
 mmunity\, the expectations/suggestions/comments for the AB.\n\nAgenda\n\n-
  [AB to give a brief intro of their current work list](https://www.w3.org/
 2025/Talks/ab-breakouts-day-2025.pdf) - 5 min\n- Open discussion about AB 
 purpose - 40 min\n- Wrap up - 5 min\n\n**Materials:**\n- [Session proposal
  on GitHub](https://github.com/w3c/breakouts-day-2025/issues/16)\n\n**Trac
 k(s):**\n- organization
STATUS:CONFIRMED
CREATED:20250314T182326Z
LAST-MODIFIED:20260204T175209Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Aloe
CATEGORIES:W3C Breakouts Day 2025,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:0fc7fa64-1f95-4832-89e0-0e3f48a613e8
DTSTAMP:20260204T175435Z
SUMMARY:Scoped custom element registry
DTSTART;TZID=Etc/UTC:20250326T140000
DTEND;TZID=Etc/UTC:20250326T150000
DESCRIPTION:https://www.w3.org/events/meetings/0fc7fa64-1f95-4832-89e0-0e3f
 48a613e8/\n\nA session to discuss scoped custom element registry:\n\n- htt
 ps://github.com/whatwg/html/issues/10854\n- https://github.com/whatwg/dom/
 pull/1341\n\n**Goal(s):**\nReaching a consensus on the spec PRs\n\nAgenda\
 n\n**Materials:**\n- [Session proposal on GitHub](https://github.com/w3c/b
 reakouts-day-2025/issues/18)
STATUS:CONFIRMED
CREATED:20250318T133929Z
LAST-MODIFIED:20260204T175435Z
SEQUENCE:4
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Yucca
CATEGORIES:W3C Breakouts Day 2025,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:c9a9bb2c-d8d4-4ad2-b216-319d044f8919
DTSTAMP:20260204T175528Z
SUMMARY:web-features and Baseline - We're feature complete! What's next?
DTSTART;TZID=Etc/UTC:20250326T140000
DTEND;TZID=Etc/UTC:20250326T150000
DESCRIPTION:https://www.w3.org/events/meetings/c9a9bb2c-d8d4-4ad2-b216-319d
 044f8919/\n\nThe [WebDX Community Group](https://www.w3.org/community/webd
 x/) has done a lot of work in 2024 to increase the coverage of its [web-fe
 atures data](https://github.com/web-platform-dx/web-features/). Now that t
 he data roughly [covers the entire web platform feature set](https://githu
 b.com/web-platform-dx/web-features/issues/788#issuecomment-2687732794)\, l
 et's review the work done so far\, the use cases that web-features\, and  
 [Baseline](https://web-platform-dx.github.io/web-features/)\, have unlocke
 d\, and let's open it up for discussion on the next important questions to
  tackle: how to maintain the web-features data over time\, as the web plat
 form evolves\, keeping in mind web developers' best interest at heart.\n\n
 **Goal(s):**\nTo update participants on WebDX\, the work we've done so far
 \, the use cases we've unlocked thanks to the data\, and the open question
 s that are next for us to solve. To ask the audience for input into these 
 open questions.\n\nAgenda\n\n[Agenda\, written content\, and meeting notes
 ](https://docs.google.com/document/d/1LJ8cgfo1o6cuiS0curhuRqZMWRAu1czBVD7C
 UYDtXuQ/edit?usp=sharing).\n\n[Slides](https://patrickbrosset.com/slides/b
 reakouts-day-2025/)\n\n**Materials:**\n- [slides](https://patrickbrosset.c
 om/slides/breakouts-day-2025/)\n- [slides (pdf)](https://lists.w3.org/Arch
 ives/Public/www-archive/2025Mar/att-0002/web-features.pdf)\n- [recording](
 https://www.w3.org/2025/03/breakouts-day-2025/recordings/recording-8.html)
 \n- [Session proposal on GitHub](https://github.com/w3c/breakouts-day-2025
 /issues/8)\n\n**Track(s):**\n- browsers
STATUS:CONFIRMED
CREATED:20250314T182215Z
LAST-MODIFIED:20260204T175528Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Cactus
CATEGORIES:W3C Breakouts Day 2025,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:851cf7e8-8d42-4316-87a1-34660435ea79
DTSTAMP:20260204T171740Z
SUMMARY:Approximate geolocation
DTSTART;TZID=Etc/UTC:20250326T210000
DTEND;TZID=Etc/UTC:20250326T220000
DESCRIPTION:https://www.w3.org/events/meetings/851cf7e8-8d42-4316-87a1-3466
 0435ea79/\n\nDiscuss a [proposal](https://github.com/w3c/geolocation/issue
 s/182) to extend [Geolocation API](https://www.w3.org/TR/geolocation/) to 
 introduce the concepts of **approximate** and **precise** location data.\n
 \nSharing precise location information puts the user's privacy at risk as 
 it can reveal sensitive information about the user's personal life such as
  home address\, workplace\, or place of worship. However\, users may still
  wish to share location information to enable a more localized experience 
 or facilitate a transaction. Approximate information about the user's loca
 tion (for instance\, a postal code) has a lower privacy risk and is typica
 lly sufficient for most applications. Extending Geolocation API to support
  approximate location would empower users to protect their location privac
 y and enable sites to request safer defaults when precise location is not 
 needed.\n\n**Goal(s):**\nIntroduce the proposal and get feedback\n\nAgenda
 \n\n* Review [motivations](https://github.com/explainers-by-googlers/appro
 ximate-geolocation/blob/main/README.md#motivation)\n* Discuss [proposal](h
 ttps://github.com/explainers-by-googlers/approximate-geolocation/blob/main
 /README.md#proposal)\n* Open discussion\n\n**Materials:**\n- [Session prop
 osal on GitHub](https://github.com/w3c/breakouts-day-2025/issues/5)
STATUS:CONFIRMED
CREATED:20250314T182141Z
LAST-MODIFIED:20260204T171740Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Agave
CATEGORIES:W3C Breakouts Day 2025,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:76765958-7255-4ef6-b23e-ca07ea6169f7
DTSTAMP:20260204T171906Z
SUMMARY:DOM Parts
DTSTART;TZID=Etc/UTC:20250326T210000
DTEND;TZID=Etc/UTC:20250326T220000
DESCRIPTION:https://www.w3.org/events/meetings/76765958-7255-4ef6-b23e-ca07
 ea6169f7/\n\nA session to discuss [DOM parts](https://github.com/WICG/webc
 omponents/blob/gh-pages/proposals/DOM-Parts.md)\n\n**Goal(s):**\nCome to a
  consensus on a concrete next step\n\nAgenda\n\n**Materials:**\n- [Session
  proposal on GitHub](https://github.com/w3c/breakouts-day-2025/issues/19)
STATUS:CONFIRMED
CREATED:20250318T133934Z
LAST-MODIFIED:20260204T171906Z
SEQUENCE:4
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Yucca
CATEGORIES:W3C Breakouts Day 2025,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:e3212ca5-bf9f-4c8f-858c-fe24b1569440
DTSTAMP:20260204T174529Z
SUMMARY:Revisiting in-band text tracks in MediaSource Extensions
DTSTART;TZID=Etc/UTC:20250326T210000
DTEND;TZID=Etc/UTC:20250326T220000
DESCRIPTION:https://www.w3.org/events/meetings/e3212ca5-bf9f-4c8f-858c-fe24
 b1569440/\n\nThe [MediaSource Extensions (MSE)](https://www.w3.org/TR/medi
 a-source/) spec has included in-band text tracks since the first published
  working draft\, but that part of the spec have lacked browser adoption fo
 r a very long time.\n\nRecently\, WebKit has added experimental support fo
 r in-band text tracks in MSE. Work on this has highlighted a number of cha
 llenges in bytestream formats and the MSE specifications.\n\nThe purpose o
 f this breakout session is to gather together\, discuss those challenges a
 nd come to agreement on the direction to tackle them in the MSE specificat
 ions.\n\n**Goal(s):**\nClarify some finer points about how in-band text tr
 acks in MSE should work and define next steps for improvements in the spec
 ifications.\n\nAgenda\n\nBasic familiarity with MediaSource Extensions is 
 expected for attendees.\n\nTo make the session easier to follow\, the sess
 ion will start with a very brief introduction of specific formats that wil
 l be relevant for the discussions\, such as:\n\n* WebVTT in ISO BMFF (MP4)
 \n* WebVTT in WebM: S_TEXT/WEBVTT and D_WEBVTT/kind\n\nAfter that introduc
 tion\, a number of topics will be discussed. For each topic there is at le
 ast one question that we hope to answer.\n\n* Cues vs samples vs MSE coded
  frames\n  * Should the MSE spec refer explicitly to cues\, and if so\, ho
 w?\n* Would it be desirable for MSE to have a concept of sparse stream gap
 s? Could the bytestream formats allow it?\n  * The SourceBuffer with only 
 a text track problem\n  * Use cases other than text tracks\n* Embedded CEA
 /CTA-608/708 signalling\n  * Would support of embedded CTA-708 in MSE be d
 esirable?\n  * What would be the best way to accomodate embedded text trac
 ks like this?\n* Cues across segment boundaries: ISO BMFF\, WebM and proce
 ssing in MSE\n  * Should the MSE spec mandate cues are extended instead of
  duplicated?\n  * Should the MSE spec mandate that when cues are extended\
 , they are updated and "oncuechange" is emitted\, instead of removed and r
 e-added?\n* MSE WebM bytestream: are the current WebVTT representations ac
 ceptable for MSE?\n  * Should we advocate for any specific improvements?\n
   * Should the MSE WebM bytestream spec be updated to refer to any specifi
 c WebVTT representation?\n\nInterested parties are encouraged to call atte
 ntion to any other existing challenges with in-band text tracks in MSE and
  the related technologies.\n\nThis list is not final and given the limited
  time\, it may not be possible to cover all the topics\, much less agree o
 n answers for most of the questions. These discussions can still serve as 
 a starting point for later work in the working groups.\n\n**Materials:**\n
 - [slides](https://ntrrgc.github.io/w3c-breakouts-2025-mse-text-tracks/)\n
 - [slides archived in zip on w3.org](https://www.w3.org/2025/Talks/mse-tex
 t-tracks-breakouts-2025.zip)\n- [recording](https://www.w3.org/2025/03/bre
 akouts-day-2025/recordings/recording-14.html)\n- [Session proposal on GitH
 ub](https://github.com/w3c/breakouts-day-2025/issues/14)
STATUS:CONFIRMED
CREATED:20250314T182308Z
LAST-MODIFIED:20260204T174529Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Marigold
CATEGORIES:W3C Breakouts Day 2025,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:09b7b3fd-9e91-4696-a96d-ee8df6c404f3
DTSTAMP:20260204T174623Z
SUMMARY:Vectors of Neglect
DTSTART;TZID=Etc/UTC:20250326T210000
DTEND;TZID=Etc/UTC:20250326T220000
DESCRIPTION:https://www.w3.org/events/meetings/09b7b3fd-9e91-4696-a96d-ee8d
 f6c404f3/\n\nSVG has been around almost as long as the need for a web vect
 or format has existed. Today\, SVG browser support is passable\, but there
  are gaps in that support and performance could be much better. It’s pro
 posed as an Interop focus each year\, and each year it gets turned down. W
 hat are the factors that make it so difficult to get implementor love for 
 SVG\, and how can we change things for the better?\n\n\n**Goal(s):**\nBrai
 nstorm ways to change the narrative and overcome inertia\n\nAgenda\n\n**Ma
 terials:**\n- [slides](https://notes.igalia.com/p/armvoqf-h#/) ([slides as
  pdf](https://www.w3.org/2025/Talks/svg-breakouts-day-2025.pdf))\n- [recor
 ding](https://www.w3.org/2025/03/breakouts-day-2025/recordings/recording-1
 2.html)\n- [Session proposal on GitHub](https://github.com/w3c/breakouts-d
 ay-2025/issues/12)
STATUS:CONFIRMED
CREATED:20250314T182245Z
LAST-MODIFIED:20260204T174623Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Aloe
CATEGORIES:W3C Breakouts Day 2025,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:007ac283-b5ff-4fd9-aef4-ca5bea9927ca
DTSTAMP:20260204T174755Z
SUMMARY:Web platform documentation
DTSTART;TZID=Etc/UTC:20250326T210000
DTEND;TZID=Etc/UTC:20250326T220000
DESCRIPTION:https://www.w3.org/events/meetings/007ac283-b5ff-4fd9-aef4-ca5b
 ea9927ca/\n\nSession to talk about how we document web technologies and ho
 w we could create more positive feedback loops between specifications and 
 technical docs (on MDN\, and generally).\n\n**Goal(s):**\nGet technical wr
 iters and specification authors talking and discuss setting up a space whe
 re we could meet more frequently.\n\nCollect feedback on the idea of setti
 ng up a W3C Documentation Community Group (Docs CG) as outlined in \nhttps
 ://docs.google.com/document/d/1rLt1wT_y7OF9VINVGFj9U5x2C_z9_3aZeOtMh-p_Qf8
 /edit\n\nAgenda\n\n- Florian to introduce and present the Docs CG proposal
  \n- Discussion\n- Summary & next steps\n\n**Materials:**\n- [Session prop
 osal on GitHub](https://github.com/w3c/breakouts-day-2025/issues/10)\n\n**
 Track(s):**\n- browsers
STATUS:CONFIRMED
CREATED:20250314T182231Z
LAST-MODIFIED:20260204T174755Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Cactus
CATEGORIES:W3C Breakouts Day 2025,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:cbe08311-3069-46c5-88f6-3a02dacf3bc2
DTSTAMP:20260204T170208Z
SUMMARY:Collective funding\, governance and prioritization of a browser eng
 ine projects
DTSTART;TZID=Etc/UTC:20250326T220000
DTEND;TZID=Etc/UTC:20250326T230000
DESCRIPTION:https://www.w3.org/events/meetings/cbe08311-3069-46c5-88f6-3a02
 dacf3bc2/\n\nToday\, each of the three main\, open source browser engine p
 rojects have a steward organization which contribute\, by far\, the lion's
  share of the project's commits - 75-95%. They also take on the infrastruc
 ture around it\, both physical an managerial. They decide how to allocate 
 available resources.  Other contributors add wildly varying levels of cont
 ributions\, but in all cases it is dictated by them toward work that they 
 decide.\n\nBut we are beginning to explore some other ideas involving pool
 s of money: The Chromium Fund\, Igalia's Open Prioritization and now whole
  engines like Servo and Ladybird.  In this breakout session we'll discuss 
 what we're exploring\, questions that are arising and how to deal with new
  challenges.\n\n**Goal(s):**\nTo discuss the challenges and brainstorm ide
 as toward greater collective ownership\n\nAgenda\n\n**Materials:**\n- [sli
 des](https://www.slideshare.net/secret/bemrjvllhd7fd6) ([slides on w3.org]
 (https://www.w3.org/2025/Talks/collective-breakouts-2025.pdf))\n- [blog po
 st](https://bkardell.com/blog/Breakouts2025.html)\n- [Session proposal on 
 GitHub](https://github.com/w3c/breakouts-day-2025/issues/11)\n\n**Track(s)
 :**\n- browsers
STATUS:CONFIRMED
CREATED:20250314T182239Z
LAST-MODIFIED:20260204T170208Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Cactus
CATEGORIES:W3C Breakouts Day 2025,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:308e7ede-24d8-4eab-b8fb-03e33d795bd0
DTSTAMP:20260204T170446Z
SUMMARY:Improving Notification Handling with AriaNotify
DTSTART;TZID=Etc/UTC:20250326T220000
DTEND;TZID=Etc/UTC:20250326T230000
DESCRIPTION:https://www.w3.org/events/meetings/308e7ede-24d8-4eab-b8fb-03e3
 3d795bd0/\n\nFor people who are blind or have low vision\, identifying dyn
 amic changes (non-user-initiated) in the content of a web app is very chal
 lenging. ARIA live regions are the only mechanism available today that com
 municate content changes down to the accessibility layer so that users can
  hear about them.\n\nARIA live regions are inconsistently implemented\, ha
 ve poor developer ergonomics\, and are being used in ways that they weren'
 t designed for (e.g.\, as a confirmation of action or notification-like AP
 I for changes unrelated to "live regions"). We propose an imperative notif
 ication API designed to replace the usage of ARIA live regions in scenario
 s where a visual "live region" isn't necessary.\n\nThis talk will provide 
 an overview of the proposed solution\, [AriaNotify](https://github.com/Mic
 rosoftEdge/MSEdgeExplainers/blob/main/Accessibility/AriaNotify/explainer.m
 d)\, what will be included in the first version of the API\, and what func
 tionality we are hoping to work with ATs to unblock improved notification 
 handling for authors and end users.\n\n**Goal(s):**\nAPI Overview and Feed
 back\n\nAgenda\n\n**Agenda:**\n1. [Slides](https://docs.google.com/present
 ation/d/1aoleJpv04kdQ3kMYlkInU9W-bdnrdf_9-aHyMgBEXW0/edit?usp=sharing) ([s
 lides in PDF](https://www.w3.org/2025/Talks/aria-notify-breakouts-2025.pdf
 ))\n2. Open for discussion/feedback\n\n**Materials:**\n- [slides](https://
 docs.google.com/presentation/d/1aoleJpv04kdQ3kMYlkInU9W-bdnrdf_9-aHyMgBEXW
 0/edit?usp=sharing)\n- [recording](https://www.w3.org/2025/03/breakouts-da
 y-2025/recordings/recording-2.html)\n- [Session proposal on GitHub](https:
 //github.com/w3c/breakouts-day-2025/issues/2)
STATUS:CONFIRMED
CREATED:20250314T182127Z
LAST-MODIFIED:20260204T170446Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Agave
CATEGORIES:W3C Breakouts Day 2025,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:89d32797-5c4d-4bab-a9c0-0eca1ed1a114
DTSTAMP:20260204T171357Z
SUMMARY:Synchronising Sensors With Geotagged Video (WebVMT)
DTSTART;TZID=Etc/UTC:20250326T220000
DTEND;TZID=Etc/UTC:20250326T230000
DESCRIPTION:https://www.w3.org/events/meetings/89d32797-5c4d-4bab-a9c0-0eca
 1ed1a114/\n\n### Scope\n\nExplore web use cases\, requirements and related
  issues for location-aware video cameras with additional sensors.\n\n### B
 ackground\n\n[Web Video Map Tracks (WebVMT)](https://webvmt.org/) is a var
 iant of [WebVTT](https://www.w3.org/TR/webvtt1/) that is designed to synch
 ronise location and sensor data with video for the web. This open format i
 s aimed at users of drones\, dash cams\, body cameras and smartphones\, an
 d was published as a [W3C/OGC Group Note](https://www.w3.org/TR/webvmt/) i
 n September 2023 by the [Spatial Data on the Web WG](https://www.w3.org/gr
 oups/wg/sdw/).\n\n### Discussion\n\nUnderstanding how web communities use 
 geotagged video is key to identifying missing features and ensuring that u
 sers' requirements are properly addressed.\n\nParticipants are invited to:
 \n\n * Highlight new use cases\n * Suggest ideas for enhancements\n * Disc
 uss integration with web interfaces\n \nPrevious issues can be found in th
 e [WebVMT Community Group](https://github.com/webvmt/community-group) and 
 more use cases are outlined in the [W3C Group Note](https://www.w3.org/TR/
 webvmt/#use-cases). Implementations based on these ideas have been [protot
 yped in the OGC Testbeds](https://webvmt.org/demos/testbed) to ensure that
  WebVMT features properly address community needs.\n\n**Goal(s):**\nIdenti
 fy missing web requirements for geotagged video use cases with sensors.\n\
 nAgenda\n\n* Short presentation - slides ([PDF](https://github.com/w3c/sdw
 /blob/gh-pages/proposals/geotagging/webvmt/meetings/2025-03-26_Breakout.pd
 f) or [HTML](https://github.com/w3c/sdw/blob/gh-pages/proposals/geotagging
 /webvmt/meetings/2025-03-26_BreakoutHTML.zip))\n * Discussion of use cases
 \, requirements & related issues\n * [Summarise conclusions](https://githu
 b.com/w3c/breakouts-day-2025/issues/15#issuecomment-2761958505)\n\n**Mater
 ials:**\n- [Session proposal on GitHub](https://github.com/w3c/breakouts-d
 ay-2025/issues/15)
STATUS:CONFIRMED
CREATED:20250314T182318Z
LAST-MODIFIED:20260204T171357Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Aloe
CATEGORIES:W3C Breakouts Day 2025,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:05ea55d3-1efa-48da-98e4-76ff8a79afb6
DTSTAMP:20260204T171622Z
SUMMARY:Template Instantiation
DTSTART;TZID=Etc/UTC:20250326T220000
DTEND;TZID=Etc/UTC:20250326T230000
DESCRIPTION:https://www.w3.org/events/meetings/05ea55d3-1efa-48da-98e4-76ff
 8a79afb6/\n\nA session to discuss [Template Instantiation](https://github.
 com/WICG/webcomponents/blob/gh-pages/proposals/Template-Instantiation.md).
 \n\n**Goal(s):**\nCome to a consensus on a concrete next step\n\nAgenda\n\
 n**Materials:**\n- [Session proposal on GitHub](https://github.com/w3c/bre
 akouts-day-2025/issues/20)
STATUS:CONFIRMED
CREATED:20250318T133940Z
LAST-MODIFIED:20260204T171622Z
SEQUENCE:4
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Yucca
CATEGORIES:W3C Breakouts Day 2025,Breakout Sessions
END:VEVENT
END:VCALENDAR