BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Sabre//Sabre VObject 4.5.8//EN
CALSCALE:GREGORIAN
NAME:W3C Breakouts Day 2024 Calendar
X-WR-CALNAME:W3C Breakouts Day 2024 Calendar
LAST-MODIFIED:20260316T161653Z
BEGIN:VTIMEZONE
TZID:Etc/UTC
BEGIN:STANDARD
DTSTART:20230318T130000
TZOFFSETFROM:+0000
TZOFFSETTO:+0000
TZNAME:UTC
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
UID:35ed70c7-c894-46ae-b2f7-a29696eebe31
DTSTAMP:20240312T132010Z
SUMMARY:ARIA Automation: A Demonstration of AT-Driver
DTSTART;TZID=Etc/UTC:20240312T130000
DTEND;TZID=Etc/UTC:20240312T140000
DESCRIPTION:https://www.w3.org/events/meetings/35ed70c7-c894-46ae-b2f7-a296
 96eebe31/\n\nSee how the AT-Driver spec is implemented to facilitate autom
 ated tests for assistive technologies.\n\nAgenda\n\n**Chairs:**\nLola Odel
 ola\n\n**Description:**\nSee how the AT-Driver spec is implemented to faci
 litate automated tests for assistive technologies.\n\n**Goal(s):**\nTo sho
 w interested parties how AT-Driver can be implemented.\n\n\n\n**Materials:
 **\n- [Session proposal on GitHub](https://github.com/w3c/breakouts-day-20
 24/issues/23)
STATUS:CANCELLED
CREATED:20240302T123753Z
LAST-MODIFIED:20240312T132010Z
SEQUENCE:4
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Koto
CATEGORIES:W3C Breakouts Day 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:aa06f202-7a9b-4605-ac95-26b2a6370278
DTSTAMP:20260312T144301Z
SUMMARY:Building Consensus on the Role of Real World Identities on the Web
DTSTART;TZID=Etc/UTC:20240312T130000
DTEND;TZID=Etc/UTC:20240312T140000
DESCRIPTION:https://www.w3.org/events/meetings/aa06f202-7a9b-4605-ac95-26b2
 a6370278/\n\nPeople already share their real identity on the Web\, but the
 y primarily share them through unsophisticated means: selfies\, photograph
 s of documents\, and typing out numbers from identity documents. Countries
  are increasingly issuing their residents' identity documents in digital\,
  cryptographic formats. Some jurisdictions\, like the EU\, will require th
 at digital credentials be respected in multiple contexts\, including on th
 e Web.\n\nWe are at a critical point for the use of these identities on th
 e Web\; they are\, for now\, not part of the web platform and are not bein
 g presented online by most users. How long this lasts does not depend enti
 rely on browsers. OpenID4VP describes multiple mechanisms to allow a websi
 te to request another application on the device that holds credentials to 
 ask the user to prove their identity.\n\nWork on building an API for prese
 nting digital identity documents and designing how that must interact with
  wallets and existing identity protocols has begun in WICG. While the disc
 ussion there does extend beyond the purely technical\, we think there is b
 enefit in bringing a discussion to a broader audience with emphasis on the
  ecosystem\, security\, and privacy impacts of that work.\n\nThe following
  are just some of the questions that don’t have clear consensus:\n\n* Wh
 at should a browser store about wallets\, credentials\, and their use?\n* 
 To what extent should we trust the issuing government? Does that include t
 rust for privacy properties?\n* What are the use cases we should support? 
 What justifies different approaches?  What common aspects are shared?\n* H
 ow does the role of the wallet as a user agent interact with that of the b
 rowser?\n* What criteria must be required of real-world identity protocols
  to be included in the web platform?\n* What conditions should be placed o
 n release of data?  Is consent the right control to apply here?  Or should
  a credential issuer have a say as well?\n* How do we ensure that use of c
 redentials is justified and proportionate? Is there a need to establish a 
 means to limit who can obtain credentials?\n\n**Goal(s):**\nWork toward a 
 consensus view of what the role of Real World Identity should be on the We
 b in the next 5-10 years.\n\n**Track(s):**\n- identity\n\nAgenda\n\n- 5 mi
 n: Chair describes the problem and state of the world for RWI and provides
  some leading open questions\n- 35 min: Open discussion of participant’s
  views on what the role of Real World Identity should be\n- 10 min: Focus 
 discussion toward common beliefs among attendees\, or common beliefs among
  constituencies\n\n**Materials:**\n- [Session proposal on GitHub](https://
 github.com/w3c/breakouts-day-2024/issues/12)
STATUS:CONFIRMED
CREATED:20240302T122830Z
LAST-MODIFIED:20260312T144301Z
SEQUENCE:5
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Ukulele
CATEGORIES:W3C Breakouts Day 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:7f29f666-3931-49f8-a44c-93bd9807ab2d
DTSTAMP:20260312T144407Z
SUMMARY:Nu Tracker: Helping you manage actions and horizontal review tasks 
 from the command line
DTSTART;TZID=Etc/UTC:20240312T130000
DTEND;TZID=Etc/UTC:20240312T140000
DESCRIPTION:https://www.w3.org/events/meetings/7f29f666-3931-49f8-a44c-93bd
 9807ab2d/\n\nThe move to Github for tracking our work - including actions\
 , and various horizontal review tasks - has been a boon for productivity\,
  and transparency. However\, it can be hard to keep up to date with all th
 e work that's going on\, especially for TF facilitators\, WG chairs\, peop
 le who take part in horizontal review activities\, and people who find the
  command line more accessible.\n\nWith a hat tipped to Tracker\, our long-
 time action management tool\, APA WG has been exploring the possibilities 
 for presenting the rich and robust GitHub process on the command line. But
  this isn't just for APA WG\; it's intended to be of use to TF facilitator
 s and WG chairs across W3C.\n\n**Goal(s):**\nDemonstrate our command-line 
 work tracking tool\, and seek feedback from potential users\n\nAgenda\n\n*
  Use cases for a new interface to the GitHub process\n* Demo of Nu Tracker
 \n* Roadmap\n* Questions and feedback\n\n**Materials:**\n- [Session propos
 al on GitHub](https://github.com/w3c/breakouts-day-2024/issues/11)
STATUS:CONFIRMED
CREATED:20240302T122823Z
LAST-MODIFIED:20260312T144407Z
SEQUENCE:4
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Lyre
CATEGORIES:W3C Breakouts Day 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:0fc23324-8bf1-47b8-b0cf-1f0f31befb09
DTSTAMP:20260312T144624Z
SUMMARY:RDF-Star and RDF 1.2
DTSTART;TZID=Etc/UTC:20240312T130000
DTEND;TZID=Etc/UTC:20240312T140000
DESCRIPTION:https://www.w3.org/events/meetings/0fc23324-8bf1-47b8-b0cf-1f0f
 31befb09/\n\nThis session will have a short presentation about the current
  state of the work the RDF-Star WG is undertaking\, followed by Q&A and di
 scussion.\n\n**Goal(s):**\nInform interested parties about RDF-Star (aka R
 DF 1.2)\n\nAgenda\n\n**Materials:**\n- [Session proposal on GitHub](https:
 //github.com/w3c/breakouts-day-2024/issues/21)
STATUS:CONFIRMED
CREATED:20240302T131546Z
LAST-MODIFIED:20260312T144624Z
SEQUENCE:4
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Erhu
CATEGORIES:W3C Breakouts Day 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:7c1b6bcd-9ee1-4570-ba4d-9ccad717e78f
DTSTAMP:20260312T144806Z
SUMMARY:Registries for W3C Specifications
DTSTART;TZID=Etc/UTC:20240312T130000
DTEND;TZID=Etc/UTC:20240312T140000
DESCRIPTION:https://www.w3.org/events/meetings/7c1b6bcd-9ee1-4570-ba4d-9cca
 d717e78f/\n\nThe Web of Things Working Group is working on defining a regi
 stry mechanism where the wide WoT community\, including other organization
 s like other SDOs\, can contribute WoT bindings of existing protocols and 
 media types. The WG has analyzed approaches within (official and not offic
 ial ones) and outside of W3C and in this breakout we want to share our fin
 dings with the wide W3C\, get inputs\, and collaborate on building knowled
 ge on how to manage registries for each technical report.\n\n**Goal(s):**\
 nDiscussion and Collection of Opinion\n\nAgenda\n\n**Agenda:**\n- Share th
 e registry analysis of the WoT WG with everyone and get feedback\n- Discus
 sion on managing registries in W3C\n\n**Materials:**\n- [Slides](https://d
 ocs.google.com/presentation/d/1zWnl7yWMKPjKgtjogZGDe-8xf4KTK3KakhPY0_uhsB4
 /edit?usp=sharing)\n- [Session proposal on GitHub](https://github.com/w3c/
 breakouts-day-2024/issues/18)
STATUS:CONFIRMED
CREATED:20240302T122851Z
LAST-MODIFIED:20260312T144806Z
SEQUENCE:4
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Kora
CATEGORIES:W3C Breakouts Day 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:fa279254-9abd-42c3-af11-5bb50851154b
DTSTAMP:20260312T144915Z
SUMMARY:Running Better Meetings - How to Facilitate at W3C
DTSTART;TZID=Etc/UTC:20240312T130000
DTEND;TZID=Etc/UTC:20240312T140000
DESCRIPTION:https://www.w3.org/events/meetings/fa279254-9abd-42c3-af11-5bb5
 0851154b/\n\nFacilitating meetings in technical spaces is an important ski
 ll\, and there are not many resources on how to do it for people new to th
 e practice or new to W3C. Based on the [meeting facilitation training](htt
 ps://www.w3.org/events/happenings/2023/meeting-facilitation-training/) dev
 eloped by the Positive Work Environments CG at W3C\, this session will pro
 vide a condensed version of the training covering how to effectively run m
 eetings in a W3C context\, how to handle code of conduct matters\, and how
  to handle conflict.\n\n**Goal(s):**\nProvide meeting facilitators with in
 formation and guidance on running better meetings.\n\nAgenda\n\n* Effectiv
 e meeting facilitation\n  * Setting the stage \n  * Tooling\n  * Fostering
  discussion \n* Introducing the code of conduct\n  * Role of the facilitat
 or\n* Handling difficult situations\n  * De-escalation\n\n**Materials:**\n
 - [recording](https://www.w3.org/2024/03/breakouts-day-2024/recordings/rec
 ording-13.html)\n- [Session proposal on GitHub](https://github.com/w3c/bre
 akouts-day-2024/issues/13)
STATUS:CONFIRMED
CREATED:20240302T122834Z
LAST-MODIFIED:20260312T144915Z
SEQUENCE:5
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Gamba
CATEGORIES:W3C Breakouts Day 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:0ac4bc8d-6dc8-48db-a822-7525eb9cd093
DTSTAMP:20260316T155658Z
SUMMARY:Exploring making site navigation more accessible\, with "well-known
  destinations"
DTSTART;TZID=Etc/UTC:20240312T140000
DTEND;TZID=Etc/UTC:20240312T150000
DESCRIPTION:https://www.w3.org/events/meetings/0ac4bc8d-6dc8-48db-a822-7525
 eb9cd093/\n\nNavigation around sites can be complex\, presenting barriers 
 for people who struggle to understand the visual layout\, or terminology t
 hat a site uses. However\, there are several key sections or pages that ca
 n be found across many sites. The WAI-Adapt Task Force is exploring an app
 roach (pending review) to address these barriers.\n\nThis session introduc
 es the problem\, shows how we envisage the solution working\, from the use
 r's perspective - via a demo of an interactive browser extension - and des
 cribes our proposed approach\, in order to answer your questions\, and gat
 her informal feedback before we apply for horizontal and wide review from 
 the community.\n\n**Goal(s):**\nRaise awareness of the challenges of site 
 navigation\, and a potential simple\, semantic\, standardized solution\n\n
 Agenda\n\n* Site navigation barriers\n* What support could look like in th
 e browser (demo)\n* WAI-Adapt's proposed solution\n* Next steps (i.e. seek
 ing review)\n* Discussion\n\n**Materials:**\n- [recording](https://www.w3.
 org/2024/03/breakouts-day-2024/recordings/recording-10.html)\n- [Session p
 roposal on GitHub](https://github.com/w3c/breakouts-day-2024/issues/10)
STATUS:CONFIRMED
CREATED:20240302T122819Z
LAST-MODIFIED:20260316T155658Z
SEQUENCE:4
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Lyre
CATEGORIES:W3C Breakouts Day 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:15220813-651d-4795-98ae-a17434c1e50f
DTSTAMP:20260316T155826Z
SUMMARY:FedCM request settings & CORS
DTSTART;TZID=Etc/UTC:20240312T140000
DTEND;TZID=Etc/UTC:20240312T150000
DESCRIPTION:https://www.w3.org/events/meetings/15220813-651d-4795-98ae-a174
 34c1e50f/\n\nRecently\, we have come to the [conclusion that FedCM should 
 use CORS for the identity assertion endpoint](https://github.com/fedidcg/F
 edCM/issues/428#issuecomment-1729629625). Other requests remain in questio
 n\, like for example\, the [accounts endpoint](https://fedidcg.github.io/F
 edCM/#fetch-accounts-list) have unique:\n\n- Security constraints: like th
 e response not being consumable by any script unless the user selects some
  browser UI\n- Privacy requirements: like not being able to expose the RP 
 to the IDP under any circumstance\, which makes CORS an unsuitable primiti
 ve for this kind of request\n\nRecently\, Google has put together [**a pro
 posal**](https://docs.google.com/document/d/1CpP9JAuqWi4yivOWQcarIqEyQzVcI
 xDdc8NA3HMw56I/edit) for finalizing the (security) properties of the accou
 nt endpoints request\, which involves interpreting the request as being "i
 nitiated" from the `/.well-known` file that directs the browser to fetch i
 t (the accounts endpoint). Today\, in practice that would make the account
 s endpoint request "same-origin" with the `/.well-known` that initiated it
 \, because FedCM requires that these requests be mutually same-origin.\n\n
 We've reached _some_ general agreement on this approach\, but would like t
 o discuss i with stakeholders including Fetch editors (@annevk)\, and also
  resolve outstanding discussion about how exactly cookies/credentials shou
 ld be treated with this request.\n\n**Goal(s):**\nResolve the topic of COR
 S & accounts endpoint requests\n\n**Track(s):**\n- identity\n\nAgenda\n\nD
 iscuss https://docs.google.com/document/d/1CpP9JAuqWi4yivOWQcarIqEyQzVcIxD
 dc8NA3HMw56I/edit\, and the associated email threads that preceded it.\n\n
 **Materials:**\n- [Session proposal on GitHub](https://github.com/w3c/brea
 kouts-day-2024/issues/7)
STATUS:CONFIRMED
CREATED:20240302T122808Z
LAST-MODIFIED:20260316T155826Z
SEQUENCE:5
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Ukulele
CATEGORIES:W3C Breakouts Day 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:9330e02e-2f20-4cb0-9fe3-22fd9dcdb629
DTSTAMP:20260316T160022Z
SUMMARY:Privacy Principles for the Web
DTSTART;TZID=Etc/UTC:20240312T140000
DTEND;TZID=Etc/UTC:20240312T150000
DESCRIPTION:https://www.w3.org/events/meetings/9330e02e-2f20-4cb0-9fe3-22fd
 9dcdb629/\n\nThe Technical Architecture Group Privacy [task force](https:/
 /github.com/w3ctag/privacy-principles)\, together with participation from 
 Privacy Interest Group\, has been working on a set of [privacy principles]
 (https://www.w3.org/TR/ethical-web-principles/) for the web. This is inten
 ded to be used by browser developers\, authors of web specifications\, rev
 iewers of web specifications (such as the TAG and other groups participati
 ng in horizontal review)\, and web developers themselves. Now this documen
 t is going through wide review in advance of publication as a W3C Statemen
 t. We will present the principles and then have an open discussion.\n\n**G
 oal(s):**\nIncrease awareness of the Privacy Principles\, answer questions
 \, gather feedback on how to improve the draft.\n\nAgenda\n\n* Brief [pres
 entation](https://github.com/w3ctag/privacy-principles/blob/main/meetings/
 2024-03-breakouts/slides.html) of an overview of the principles\n* Guided 
 discussion\n\n**Materials:**\n- [Session proposal on GitHub](https://githu
 b.com/w3c/breakouts-day-2024/issues/16)
STATUS:CONFIRMED
CREATED:20240302T122845Z
LAST-MODIFIED:20260316T160022Z
SEQUENCE:5
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Gamba
CATEGORIES:W3C Breakouts Day 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:fb7b6d9f-fc2f-456f-9fff-3a516f3ec7ab
DTSTAMP:20260316T160123Z
SUMMARY:Schemata Discussion - Follow up from TPAC23
DTSTART;TZID=Etc/UTC:20240312T140000
DTEND;TZID=Etc/UTC:20240312T150000
DESCRIPTION:https://www.w3.org/events/meetings/fb7b6d9f-fc2f-456f-9fff-3a51
 6f3ec7ab/\n\nAs a follow-up of [Schemata Breakout of TPAC23](https://githu
 b.com/w3c/tpac2023-breakouts/issues/8)\, we want to further discuss ways t
 o manage ontologies\, schemas\, and similar documents together. In the sco
 pe of the Thing Description Task Force at the Web of Things WG\, we have a
 nalyzed some approaches such as LinkML\, TreeLDR\, Eclipse Semantic Modell
 ing Framework\, that we want to present. We have also identified that the 
 topic of versioning\, packaging\, and serving these resources is a pressin
 g topic that is not specific to the WoT. After these\, we want to discuss 
 on how to better continue the discussions in this topic area within the W3
 C.\n\n**Goal(s):**\nDiscussion and Collection of Opinion\n\nAgenda\n\n- Re
 cap of the TPAC2023 Breakout\n- Results of [the analysis](https://github.c
 om/w3c/wot-thing-description/blob/egekorkan-patch-3/toolchain/tool-analysi
 s.md) of tools at the WoT WG\n- Versioning\, packaging and serving resourc
 es\n- Continuation of the work\n\n**Materials:**\n- [Slides](https://docs.
 google.com/presentation/d/193OFcFaxD0GqrRuOggwZe5eorgL1C1Epe2cAYN3JEkk/edi
 t?usp=sharing)\n- [Session proposal on GitHub](https://github.com/w3c/brea
 kouts-day-2024/issues/15)
STATUS:CONFIRMED
CREATED:20240302T122842Z
LAST-MODIFIED:20260316T160123Z
SEQUENCE:4
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Kora
CATEGORIES:W3C Breakouts Day 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:9e7690a7-cd77-4192-ab60-337243f9b70a
DTSTAMP:20260316T160242Z
SUMMARY:Web features\, Baseline status\, and standardization signals
DTSTART;TZID=Etc/UTC:20240312T140000
DTEND;TZID=Etc/UTC:20240312T150000
DESCRIPTION:https://www.w3.org/events/meetings/9e7690a7-cd77-4192-ab60-3372
 43f9b70a/\n\nHow do web developers talk about web features? What names do 
 they use? How do these features map to specifications\, fine-grained API f
 unctions and tests? What does a developer view tell us about the interoper
 ability of the web platform?\n\nThe [`web-features` project](https://githu
 b.com/web-platform-dx/web-features)\, [envisioned in 2022](https://www.w3.
 org/2022/09/TPAC/breakouts.html#webdx) and [launched in 2023](https://www.
 w3.org/2023/09/TPAC/demos/web-features.html)\, explores the set of interop
 erable features of the web platform by:\n\n- Creating feature definitions\
 , which identify and describe capabilities of web browsers.\n- Generating 
 [Baseline](https://github.com/web-platform-dx/web-features/blob/main/docs/
 baseline.md) support data\, which summarizes the availability of web featu
 res across key browsers and releases.\n- Publishing the `web-features` npm
  package\, which bundles feature identifiers with Baseline statuses.\n\nDe
 veloped by the WebDX Community Group and contributors\, web-features data 
 leverages compatibility data from the browser-compat-data project\, is alr
 eady [integrated in MDN](https://developer.mozilla.org/en-US/blog/baseline
 -evolution-on-mdn/)\, [Can I Use](https://caniuse.com/css-nesting)\, [Web 
 Platform Tests](https://github.com/web-platform-tests/wpt.fyi/blob/main/ap
 i/query/README.md#feature)\, and is starting to reach additional authors o
 f JavaScript libraries and dashboards.\n\nLooking forward\, feature identi
 fiers at the "right" level make it possible to tag signals from the web co
 mmunity in surveys\, browser standard positions\, bug trackers\, polyfills
  and usage counters. It also makes it easier to combine these signals with
  other projects that generate data out of specifications such as [`browser
 -specs`](https://github.com/w3c/browser-specs/) and [webref](https://githu
 b.com/w3c/webref).\n\nFeatures are also used in standardization groups\, i
 nformally to organize discussions\, but also formally to address transitio
 n requirements set forth by the W3C Process Document for advancing specifi
 cations on the Recommendation track. Within the Process\, [new features](h
 ttps://www.w3.org/2023/Process-20231103/#class-4) are defined as substanti
 ve changes that add new functionality\, and used to assess [implementation
  experience](https://www.w3.org/2023/Process-20231103/#implementation-expe
 rience)\, document functionality that is considered [at risk](https://www.
 w3.org/2023/Process-20231103/#at-risk)\, and scope changes that may be inc
 orporated in a specification depending on its maturity stage. This raises 
 questions on the intersection between web-features and W3C’s standardiza
 tion process\, including:\n\n- Can web-features provide useful information
  to working groups?\n- Can it also inform the standardization process\, e.
 g.\, to detect the need to transition a feature implemented by more than o
 ne browser out of incubation?\n- What additional data or tooling would mak
 e web-features a powerful tool for standards bodies?\n- How would **you** 
 like to see web-features data presented in standards work?\n\n**Goal(s):**
 \nShare updates on the web-features project\, its use to inform the standa
 rdization process\, and additional data\, tooling and visualizations to ma
 ke web-features a powerful tool for standards bodies.\n\nAgenda\n\n- Prese
 ntation (20mn - see [slides](https://docs.google.com/presentation/d/e/2PAC
 X-1vT5PiEfUCia_p-hIKu-LxQ90qwQks42FtsXTxI4wATYuG1OWEQlCnGcP7R_gENVnGUa82ZT
 GkQXQgRQ/pub))\n  - Web developers and web features\n  - Web features and 
 standardization\n  - First stab at gathering signals to inform standardiza
 tion process\n    - Late incubations\n    - Late Working Drafts\n    - Not
 -so-well supported Recommendations\n- Discussion (30mn)\n\n**Materials:**\
 n- [Session proposal on GitHub](https://github.com/w3c/breakouts-day-2024/
 issues/22)
STATUS:CONFIRMED
CREATED:20240302T115628Z
LAST-MODIFIED:20260316T160242Z
SEQUENCE:4
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Koto
CATEGORIES:W3C Breakouts Day 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:27e8a549-c121-4c70-a6f9-ac987528c27f
DTSTAMP:20260316T160407Z
SUMMARY:Ethical Implications of Generative AI
DTSTART;TZID=Etc/UTC:20240312T210000
DTEND;TZID=Etc/UTC:20240312T220000
DESCRIPTION:https://www.w3.org/events/meetings/27e8a549-c121-4c70-a6f9-ac98
 7528c27f/\n\nThe proliferation of Generative AI has disrupted many industr
 ies and is poised to change significant aspects of our society. Without gu
 ardrails\, we have often seen conversational AI agents overfitting to the 
 bias in the training data which negatively impacts users. At eyeo\, we bui
 ld machine learning solutions on a web-scale\, and in order to ensure our 
 models are fair and sustainable\, we have taken several concrete steps to 
 transform the input data and calibrate the model evaluation to reflect rea
 l-world scenarios. We believe it’s high time to start a discussion aroun
 d having a formal framework which outlines the ethical considerations for 
 the use of Generative AI and AI in general. During the session\, we will e
 xplore the challenges and opportunities that lie ahead from a technical an
 d social perspective.\n\nThis builds on our session on [Ethical AI during 
 TPAC 2023](https://github.com/w3c/tpac2023-breakouts/issues/72)\, with a f
 ocus on Generative AI.\n\n**Goal(s):**\nBrainstorm ideas on the ethics of 
 these new and upcoming technologies (Generative AI) and discuss the implic
 ations of adopting these on a large scale from a social\, economic and tec
 hnical perspective.\n\nAgenda\n\n1. Rise of Generative AI \n2. Role of the
  World Wide Web in the adoption of these technologies\n3. Steps we take at
  eyeo to de-bias our web-scale Machine Learning models\n4. Ethical Implica
 tions of the use of these technologies\n5. The future of setting ethical s
 tandards for Generative AI\n\n#### Additional Information \n\nDuring the c
 ourse of the session\, we will be making use of this **[Miro Board](https:
 //miro.com/app/board/uXjVNkFEEw8=/)**\, please make sure you are able to v
 iew this. The board is password-protected at the moment. At the beginning 
 of the session\, we will share the password with all the participants. \n\
 nWe have also planned a short presentation at the start of the session. Yo
 u can find the **[slide deck here](https://docs.google.com/presentation/d/
 1TdZvKi8AIsDUlWYeg9cHqRHA-tDiCuhe6m5B61o5sxs/edit#slide=id.g25c658642cb_2_
 1093)**\n\nFinally\, while preparing for the session we made notes and org
 anized relevant details pertaining to the existing literature on Ethics fo
 r AI and Generative AI. In case you are interested please have a look at t
 his **[Google Doc](https://docs.google.com/document/d/1jv7_4JD0ynIV_bFdf3h
 qm_sg74twHbflOOYWafnQFwg/edit)**\n\n**Materials:**\n- [Session proposal on
  GitHub](https://github.com/w3c/breakouts-day-2024/issues/19)
STATUS:CONFIRMED
CREATED:20240302T122856Z
LAST-MODIFIED:20260316T160407Z
SEQUENCE:4
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Lyre
CATEGORIES:W3C Breakouts Day 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:32f686e7-698e-4373-bb42-1f6ba5080bb3
DTSTAMP:20260316T160512Z
SUMMARY:FedCM multiple IDP support
DTSTART;TZID=Etc/UTC:20240312T210000
DTEND;TZID=Etc/UTC:20240312T220000
DESCRIPTION:https://www.w3.org/events/meetings/32f686e7-698e-4373-bb42-1f6b
 a5080bb3/\n\nWe would like to brainstorm ideas to solve the following prob
 lem: the FedCM API allows users to login to websites via some identity pro
 vider (IDP). Currently the API only allows the developer to specify a sing
 le IDP\, and we are working on [allowing multiple](https://github.com/fedi
 dcg/FedCM/issues/319) to be specified. It will be fairly easy to allow mul
 tiple IDPs in a single JavaScript call\, but this has an issue. When there
  are multiple totally independent providers\, we want each IDP to specify 
 their desire to be included in FedCM independently. This allows the websit
 e to embed independent IDP SDKs into their site but still allow these IDPs
  to be shown in an aggregated browser dialog. The challenge is how to achi
 eve this in a reasonable way. There are some brainstormed solutions [here]
 (https://github.com/w3ctag/design-reviews/issues/803#issuecomment-17715576
 47) but we'd love to further discuss this in a session.\n\n**Goal(s):**\nB
 rainstorm ideas to tackle the problem of allowing multiple independent IDP
 s\n\n**Track(s):**\n- identity\n\nAgenda\n\n**Materials:**\n- [recording](
 https://www.w3.org/2024/03/breakouts-day-2024/recordings/recording-9.html)
 \n- [Session proposal on GitHub](https://github.com/w3c/breakouts-day-2024
 /issues/9)
STATUS:CONFIRMED
CREATED:20240302T122815Z
LAST-MODIFIED:20260316T160512Z
SEQUENCE:6
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Ukulele
CATEGORIES:W3C Breakouts Day 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:413b7511-d5e7-491a-9666-0535c844d52c
DTSTAMP:20260316T160620Z
SUMMARY:How We Fund the Web Ecosystem
DTSTART;TZID=Etc/UTC:20240312T210000
DTEND;TZID=Etc/UTC:20240312T220000
DESCRIPTION:https://www.w3.org/events/meetings/413b7511-d5e7-491a-9666-0535
 c844d52c/\n\nThe Web has billions of users\, and most users have many\, ma
 ny dependencies on the web. The ecosystem around the web\, which includes 
 things like web engines\, is both incredibly complex and fundamentally cri
 tical.\n\nBut the model that has driven\, funded\, and sustained this ecos
 ystem isn’t ideal. There is no guarantee that it will be sustainable ove
 r the long term\, but beyond that\, it already falls quite short of fundin
 g everything that needs to be done. There is just too much. Many things go
  long ignored simply because prioritization is hard\, and funds are ultima
 tely limited. This includes everything from new features in popular langua
 ges like CSS and JS up to entire languages like MathML and SVG\, which hav
 e largely been the work of (often unpaid) individual contributors.\n\nIn t
 his session\, we intend to have a community discussion of alternative mode
 ls for funding the web ecosystem\, from collective funding pools to change
 s in open source project policies to changes in tax law\, and beyond.\n\n*
 *Goal(s):**\nTo help further discussions toward better solutions\n\nAgenda
 \n\n**Materials:**\n- [Session proposal on GitHub](https://github.com/w3c/
 breakouts-day-2024/issues/20)
STATUS:CONFIRMED
CREATED:20240302T122900Z
LAST-MODIFIED:20260316T160620Z
SEQUENCE:4
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Koto
CATEGORIES:W3C Breakouts Day 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:95000dca-932c-4b1d-a618-7a1d284d0edd
DTSTAMP:20260316T160806Z
SUMMARY:Low-latency input events in workers
DTSTART;TZID=Etc/UTC:20240312T210000
DTEND;TZID=Etc/UTC:20240312T220000
DESCRIPTION:https://www.w3.org/events/meetings/95000dca-932c-4b1d-a618-7a1d
 284d0edd/\n\nThe following proposal is based on [this email](https://lists
 .w3.org/Archives/Public/public-webapps/2023OctDec/0011.html) and related d
 iscussion in the Gamepad API repo. Posted here as Chair of the WebApps WG.
  \n\nThis proposal for a W3C breakout session aims to address a critical l
 imitation of the web as a platform for applications requiring low-latency 
 response to user inputs. Despite technological advancements\, the web's cu
 rrent input handling mechanisms are inadequate for such applications due t
 o their dependence on the main thread.\n\nUser input APIs\, which include 
 keyboard\, pointer\, gamepad\, HID\, USB\, MIDI\, Bluetooth\, and serial i
 nterfaces\, are currently designed to register handlers on the main thread
 . This design results in inconsistent and unreliable response times\, as t
 he main thread is frequently occupied with other processes. This limitatio
 n adversely affects a broad range of applications\, particularly those req
 uiring precise user inputs\, such as certain video games\, Digital Audio W
 orkstations (DAWs)\, synthesizers\, and art programs that rely on touch ge
 stures.\n\nWhile incorporating timestamps in input APIs could offer some i
 mprovement\, a more effective solution is to allow these APIs to be access
 ible from Web Workers. This change would significantly reduce input latenc
 y issues. Some APIs are already making progress in this direction\, but ot
 hers\, especially those tied to the DOM API like keyboard and pointer even
 ts\, face more complex challenges due to their inherent link to the main t
 hread.\n\nThis issue\, recently discussed with folks involved with the Gam
 epad API\, highlights the need for a comprehensive approach that encompass
 es various APIs. Therefore\, this session proposal seeks to gather communi
 ty input and collaboration to explore and develop solutions that enhance t
 he web's ability to handle user inputs with the necessary low latency. Thi
 s effort requires a broad perspective and collective action\, addressing t
 he current limitations and identifying feasible paths for improvement in w
 eb application responsiveness.\n\n**Goal(s):**\nSee if it's feasible to ro
 ute some HID events to workers\n\nAgenda\n\n**Materials:**\n- [Session pro
 posal on GitHub](https://github.com/w3c/breakouts-day-2024/issues/2)
STATUS:CONFIRMED
CREATED:20240302T122641Z
LAST-MODIFIED:20260316T160806Z
SEQUENCE:4
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Gamba
CATEGORIES:W3C Breakouts Day 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:f1c8369e-4fb9-46c7-8520-b10c59011cf4
DTSTAMP:20260316T161105Z
SUMMARY:Real Estate Community Group and the Web
DTSTART;TZID=Etc/UTC:20240312T210000
DTEND;TZID=Etc/UTC:20240312T220000
DESCRIPTION:https://www.w3.org/events/meetings/f1c8369e-4fb9-46c7-8520-b10c
 59011cf4/\n\nThe mission of the Real Estate Community Group is to provide 
 a forum for real estate-related technical discussions to track progress of
  technology features on the Web within W3C groups\, educate on the use of 
 Web technologies by external organizations\, and to identify use cases and
  requirements that existing and/or new specifications need to meet to deli
 ver a more inclusive\, robust experiences to the Real Estate ecosystem.  T
 his session will discuss the group\, answer questions and briefly demonstr
 ate the DO AudioTours technology built by Direct Offer.\n\nAdditional sess
 ion chair: Amy Chorew.\n\n**Goal(s):**\nGet support for the group\n\nAgend
 a\n\n* Introductions \n* Why we're creating the CG\n* Who are the potentia
 l actors in the group\n* What it does for the real estate industry\n* demo
  of DO AudioTours\n\n**Materials:**\n- [slides](https://docs.google.com/pr
 esentation/d/174Ae7o-XWDbe4VqtfLYIptalsIBubRpo/edit)\n- [recording](https:
 //www.w3.org/2024/03/breakouts-day-2024/recordings/recording-6.html)\n- [S
 ession proposal on GitHub](https://github.com/w3c/breakouts-day-2024/issue
 s/6)
STATUS:CONFIRMED
CREATED:20240302T122803Z
LAST-MODIFIED:20260316T161105Z
SEQUENCE:4
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Erhu
CATEGORIES:W3C Breakouts Day 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:637c8829-f322-4799-8787-2fefec8ce327
DTSTAMP:20260316T161323Z
SUMMARY:Incubation: the on ramp to new work
DTSTART;TZID=Etc/UTC:20240312T220000
DTEND;TZID=Etc/UTC:20240312T230000
DESCRIPTION:https://www.w3.org/events/meetings/637c8829-f322-4799-8787-2fef
 ec8ce327/\n\nThe process of incubation\, and some of its parameters\, are 
 not currently well-defined at W3C.  I'd like to gather perspectives to fur
 ther the work on Incubation in the AB (https://github.com/w3c/AB-memberonl
 y/blob/master/documents/Incubation.md).\n\nSome provoking questions to exp
 lore:\n- How should incubation work?\n- At what stage of "doneness" should
  work move from an incubation venue to a working group?\n- How should an i
 ncubation group be communicating their work to a broader venue to ease acc
 eptance as a WG deliverable?\n- What expectation of incubation should ther
 e be before work is accepted into a WG\, or into its charter?\n- What best
  practices should we define for referring to incubations?\n\n**Goal(s):**\
 nGather input and perspectives to further the AB work on improving incubat
 ion process\n\nAgenda\n\n**Materials:**\n- [Session proposal on GitHub](ht
 tps://github.com/w3c/breakouts-day-2024/issues/24)
STATUS:CONFIRMED
CREATED:20240302T123853Z
LAST-MODIFIED:20260316T161323Z
SEQUENCE:4
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Kora
CATEGORIES:W3C Breakouts Day 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:dbd11d7e-d721-49ce-99d2-72b91e0d7030
DTSTAMP:20260316T161421Z
SUMMARY:Installing web apps as a new platform feature
DTSTART;TZID=Etc/UTC:20240312T220000
DTEND;TZID=Etc/UTC:20240312T230000
DESCRIPTION:https://www.w3.org/events/meetings/dbd11d7e-d721-49ce-99d2-72b9
 1e0d7030/\n\nThis breakout session is to talk about ideas we have regardin
 g enabling installation of web apps and web content through the platform n
 atively. This is a new proposal that aims at democratizing application dis
 tribution. \n\nThe goals for the session are to describe and generate disc
 ussion about the challenges functionality like this might have. The sessio
 n is open to the public.\n\n**Goal(s):**\nDescribe and generate discussion
  about the challenges functionality like this might have.\n\nAgenda\n\n**M
 aterials:**\n- [Session proposal on GitHub](https://github.com/w3c/breakou
 ts-day-2024/issues/17)
STATUS:CONFIRMED
CREATED:20240302T122848Z
LAST-MODIFIED:20260316T161421Z
SEQUENCE:4
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Gamba
CATEGORIES:W3C Breakouts Day 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:6537214b-f033-4fe2-b8be-02724f3f4df0
DTSTAMP:20260316T161533Z
SUMMARY:Promote the PROPOSED Federated Identity Working Group
DTSTART;TZID=Etc/UTC:20240312T220000
DTEND;TZID=Etc/UTC:20240312T230000
DESCRIPTION:https://www.w3.org/events/meetings/6537214b-f033-4fe2-b8be-0272
 4f3f4df0/\n\nThis session will serve to answer questions about the propose
 d Federated Identity Working Group\, encouraging participation from all in
 terested parties.\n\n**Goal(s):**\nRaise awareness of and encourage partic
 ipation in the FedID WG\n\n**Track(s):**\n- identity\n\nAgenda\n\nAdminist
 rivia\n- [Code of Ethics and Professional Conduct](https://www.w3.org/Cons
 ortium/cepc/)\n- [Antitrust and Competition Guidance](https://www.w3.org/C
 onsortium/Legal/2017/antitrust-guidance)\n- [Policy on recording sessions]
 (https://github.com/w3c/tpac-breakouts/wiki/Policies#recording-sessions)\n
 - Check in with participants - questions\, goals\, understanding of W3C pr
 ocesses\n\nBackground\n- Charter text (see https://w3c.github.io/charter-d
 rafts/2024/wg-fedid.html) \n- Current state of the proposed charter (see h
 ttps://github.com/w3c/strategy/issues/427#issuecomment-1979221054) \n\n(Sh
 ort presentation) What is the Federated Identity WG?\n- What is in scope?\
 n- How does it relate to the Federated Identity CG?\n- Related areas of in
 terest (starting with the Privacy CG\, WICG Digital Identity)\n- Expected 
 timeline for the group / for the work.\n\nDiscussion\n\n**Materials:**\n- 
 [Session proposal on GitHub](https://github.com/w3c/breakouts-day-2024/iss
 ues/3)
STATUS:CONFIRMED
CREATED:20240302T122800Z
LAST-MODIFIED:20260316T161533Z
SEQUENCE:4
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Ukulele
CATEGORIES:W3C Breakouts Day 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:28cae5e2-8941-4d36-83fa-5a94f54a7d9a
DTSTAMP:20260316T161653Z
SUMMARY:Web security docs for MDN
DTSTART;TZID=Etc/UTC:20240312T220000
DTEND;TZID=Etc/UTC:20240312T230000
DESCRIPTION:https://www.w3.org/events/meetings/28cae5e2-8941-4d36-83fa-5a94
 f54a7d9a/\n\nAt the [Secure the Web Forward](https://www.w3.org/2023/03/se
 cure-the-web-forward/report.html) workshop in 2023\, writers from Open Web
  Docs led a [discussion about the state of web security docs on MDN](https
 ://www.w3.org/2023/03/secure-the-web-forward/report.html#documentation). O
 ne outcome from this was that OWD would draft an outline for some improved
  security documentation for MDN\, which would be written in 2024.\n\nWe've
  now written up a draft outline and it's had some internal review: https:/
 /docs.google.com/document/d/1p1GtjmTd1uQrO2PRb_uUflAfQpEsfs7hBaopYeuoPMM/e
 dit\, and we're ready for some more extensive review of the outline before
  we start writing docs.\n\nWe're very keen on finding security experts to 
 collaborate with us on this project\, both in these early stages as we sco
 pe the project\, and for detailed technical review of documents as we writ
 e them.\n\nIn this session\, we'll present the draft outline\, discuss any
  feedback\, and next steps\, which we hope will be making a start on the d
 ocumentation!\n\n**Goal(s):**\nReview MDN web security docs outline propos
 al\n\nAgenda: https://wbamberg.github.io/web-security-w3c-breakouts-march-
 2024/\n\nAgenda\n\n**Materials:**\n- [recording](https://www.w3.org/2024/0
 3/breakouts-day-2024/recordings/recording-14.html)\n- [Session proposal on
  GitHub](https://github.com/w3c/breakouts-day-2024/issues/14)
STATUS:CONFIRMED
CREATED:20240302T122838Z
LAST-MODIFIED:20260316T161653Z
SEQUENCE:5
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Koto
CATEGORIES:W3C Breakouts Day 2024,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:9c5c12b5-ccdb-42c7-a98a-ae766e1d416a
DTSTAMP:20240312T182341Z
SUMMARY:[CSS] Anchor Positioning
DTSTART;TZID=Etc/UTC:20240312T220000
DTEND;TZID=Etc/UTC:20240312T230000
DESCRIPTION:https://www.w3.org/events/meetings/9c5c12b5-ccdb-42c7-a98a-ae76
 6e1d416a/\n\nDiscuss contentious/important issues with the [CSS Anchor Pos
 ition spec](https://drafts.csswg.org/css-anchor-position/).\n\nNotably\, t
 he new "style interleaving" concept that it shares with Container Queries\
 , and the 'position-animation' proposal.\n\nAgenda\n\n**Chairs:**\nTab Atk
 ins Jr.\, Elika Etemad\n\n**Description:**\nDiscuss contentious/important 
 issues with the [CSS Anchor Position spec](https://drafts.csswg.org/css-an
 chor-position/).\n\nNotably\, the new "style interleaving" concept that it
  shares with Container Queries\, and the 'position-animation' proposal.\n\
 n**Goal(s):**\nCome to consensus on issues\n\n\n\n**Materials:**\n- [Sessi
 on proposal on GitHub](https://github.com/w3c/breakouts-day-2024/issues/8)
STATUS:CANCELLED
CREATED:20240302T122811Z
LAST-MODIFIED:20240312T182341Z
SEQUENCE:4
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Erhu
CATEGORIES:W3C Breakouts Day 2024,Breakout Sessions
END:VEVENT
END:VCALENDAR