FDC3 for Web Browsers & Bridging Discussion group - 15th Jan 2026

[kriswest]

Group overview

Summary of the purpose and scope of the group

Relevant issue tags

If tags have been applied to relevant issues, provide details here.

Meeting Date

Thursday 15th Jan 2026 - 10am (US eastern timezone EDT/EST) / 3pm (London, GMT/BST)

Zoom info

• Join Zoom Meeting
• Meeting ID: 969 4029 4948
• Passcode: 636931
• Dial-in:

  Country	International Dial-in	Toll-free Dial-in
  US	+1 929 205 6099 (New York)	877 853 5247
  UK	+44 330 088 5830	0800 031 5717
  France	+33 1 8699 5831	0 800 940 415
  Find your local number	https://zoom.us/u/ad2WVnBzb8

Meeting notices

• FINOS Project leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.

• All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.

• FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact legal@finos.org with any questions.

• FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

• A Discussion Group has no direct decision-making power regarding the FDC3 standard - rather it is intended that anything they propose or work on will result in proposals (via Github issues and PRs) for the Standards Working Group participants to consider and vote on for inclusion in the standard.

Participation Requirements

Note: Meeting participants are expected to accept the terms of the FDC3 license (Community Specification License), understand the governance process and have a CLA in place.

Please click the following links at the start of the meeting if you have not done so previously.

• View the CSL
• View the GOVERNANCE of the Project
• Click here to start a PR.
  • Edit the page to add your details.
  • Hit the save button.
  • Click "Create Pull Request".
  • Click "Accept" on the EasyCLA dialog in the PR's discussion section.
• Click here to send email to become a voting participant on the FDC3 Project

Tracking Attendance

Note: Meeting participants are expected to add a comment to this GitHub issue in order that we can track attendance of FDC3 project meetings. Please do this at the start of the meeting.

Agenda

• Convene & roll call, review meeting notices (5mins)
• Review action items from previous meeting (5mins)
  • FDC3 for Web Browsers & Bridging Discussion group - 20th Nov 2025 #1702
• Progress on Add property to support analytics across apps #1290
  • New PR FDC3 API Metadata #1728
  • Discuss next steps for FDC3 security that follow on from Add property to support analytics across apps #1290
• Revisit status of Open-Source FDC3 for web implementations
• FDC3 2.2.2 release
  • Improve heartbeat argument handling in the FDC3 for Web reference implementation demo #1678
    • Server Context Refactor #1696
  • Conformance 2.2: Added New Tests Specified by Test-Pack. #1586
    • FDC3 2.2 Conformance Implementation #1455
    • Adding A Channel Change Event Listener Doesn't Send addEventListenerRequest #1605
    • Untyped event listener is sent to DA as typed #1608
    • When adding a listener on the user channel, the payload.channelId should be null. #1611
  • Esm modules fix #1677
• AOB & Adjourn (5mins)

Meeting Minutes

• Review of previous action items:

  • Several items from the previous meeting were discussed and updated.
  • The select agent functionality was deferred; @SeeWhatsOn will raise a discussion or close the issue if current information suffices.
  • Multiple application scopes in one window will remain paused until further development and after upcoming releases.
  • Progress noted on CommonJS declaration files and bundling (merged).
  • The homepage/getting started content issue remains; @kriswest and @robmoffat to combine course material and personal notes for a new guide
  • @kziemski’s drafting proposal for browser extension and managed deployment was delayed due to illness but will follow up next week.

• Progress on Add property to support analytics across apps (Add property to support analytics across apps #1290):

  • New PR for FDC3 API Metadata (FDC3 API Metadata #1728) is in draft; @julianna-ciq has contributed significant code and documentation.
  • Function signatures and compliance requirements are being updated, with metadata moved from optional to required for FDC3 3.0.
  • Separation between business context and metadata is explained; rationale and implementation details discussed.
  • Further conformance tests, reference/proxy implementation, and .NET/Golang specs will follow after consensus is reached.

• Next steps for FDC3 security (related to Add property to support analytics across apps #1290):

  • Security group will add relevant metadata properties in this or subsequent PRs.
  • Security specification work will proceed once metadata proposal is accepted.
  • No major edge cases identified yet; handling invalid properties in proxy discussed.

• Revisit status of Open-Source FDC3 for web implementations:

  • Reference implementation to be marked “not for production use”; SAIL project will provide production-ready web implementation.
  • PR needed to mark and set package as private; action agreed to stop NPM publishing for reference implementation.
  • Discussion on refactoring and maintenance responsibility; community to maintain reference implementation going forward.

• FDC3 2.2.2 Release:

  • Server context refactor (Server Context Refactor #1696) and heartbeat argument handling (Improve heartbeat argument handling in the FDC3 for Web reference implementation demo #1678) will be moved out of the 2.2.2 release scope.
  • Agreement to mark FDC3 for web imports as not production and halt NPM publishing.
  • ESM modules fix (Esm modules fix #1677) reviewed, progress made, but further work required by @Roaders.
  • Conformance 2.2 new tests (Conformance 2.2: Added New Tests Specified by Test-Pack. #1586) and related implementation issues (FDC3 2.2 Conformance Implementation #1455, Adding A Channel Change Event Listener Doesn't Send addEventListenerRequest #1605, Untyped event listener is sent to DA as typed #1608, When adding a listener on the user channel, the payload.channelId should be null. #1611) reviewed; @Roaders working on .NET agent tests.
  • All results from .NET agent conformance tests will be useful.

• AOB:

  • Details of an upcoming hackathon posted by Karl Moll; suggestion to share FDC3-specific info on mailing list
  • @kziemski and @robmoffat to coordinate for SAIL implementation meetings.

Action Items

• @SeeWhatsOn: Raise discussion or close the select agent functionality issue if resolved.
• @kriswest and @robmoffat: Share course material and notes for getting started guide
• @kziemski: Follow up on drafting proposal for managed browser extension and raise for community input.
• @kriswest: Push remaining documentation changes for FDC3 API Metadata (FDC3 API Metadata #1728) and create new issues for conformance tests and updates in .NET/Golang after approval.
• @kriswest: Raise PR to mark FDC3 reference implementation as “not for production use” and set as private; stop NPM publishing.
• @robmoffat: Support reverting demo directory removal and coordinate reference implementation maintenance.
• @Roaders: Continue work on ESM modules fix (Esm modules fix #1677); review and address issues.
• @Roaders: Run conformance tests against .NET agent and report results.
• All: Review FDC3 API Metadata PR (FDC3 API Metadata #1728) and provide feedback, especially on function signatures.
• All: Review FDC3 2.2.2 release PRs, especially conformance tests (Conformance 2.2: Added New Tests Specified by Test-Pack. #1586) and implementation fixes.
• Karl Moll: Share hackathon details to FDC3 mailing list.
• @kziemski and @robmoffat: Coordinate for SAIL implementation meetings, invite interested parties.

Untracked attendees

Full name	Affiliation	GitHub username

[Roaders]

Giles Roadnight / Morgan Stanley 🚀

[karlmoll]

Karl Moll / FINOS

[SeeWhatsOn]

Chris Watson / Elgin White

[pvoznyuk]

Pavlo Vozniuk / RBC

[karlmoll]

Promotion for the DTCC AI-powered Industry Hackathon (Supported by FINOS)
https://communications.dtcc.com/dtcc-hackathon-registration-18146.html

When: Feb 23-27
Registration Deadline: Jan 23
Where: Global!
Prizes: Funding via grants to FINOS to support ongoing development of winning projects as open source projects

[kziemski]

Kryspin Ziemski / QCOMPUTE