FDC3 General Meeting - 16 Sep 2026

Date

16 Sep 2026 - 10am EST / 3pm GMT

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 [email protected] 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.

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

The FDC3 General meeting serves as an update on the activity in the FDC3 Standard over the last 6 months.

Summary of Recent Activity

Recent Merges & Changes:
- New requirement for implementers of the FDC3 API in web apps to bind functions to support destructuring, addressing issues reported by a number of users or app developers in the past.
- Multiple updates and additions to context types, including clarifications and new fields added.
- Go language binding
  - Add-hoc discussion about whether formal interfaces should be released to support Go implementations, similar to finos/fdc3-dotNet.
- Added dynamic content listener support to browser desktop agent reference implementation.
- Clarified behaviour for repeated addContextListener and addIntentListener calls; error introduced for incorrect repeated intent listener registrations to ensure consistent behaviour.
- clearContext function and contextClearedEvent added to the channel API for improved application support (e.g., clearing filters).
Conformance:
- FDC3 conformance project has been ported into the monorepo, with ongoing investigation into issues, especially around channel tests and timeouts (noted by @robmoffat and @openfin-johans).
  - The migrated version had a number of changes made to it (including TypeScript changes necessary to get it to build in the FDC3 mono-repo) and there are unfortunately reports of problems with it.
  - Comparison to tags of fdc3-conformance-framework project is recommended to determine if the issue were existing or introduced during the migration.
- A full reimplementation by one of the FDC3 maintainers is in progress - although it is noted that adoption of a revised framework implementation will require the agreement of multiple participating firms - particularly if the current implementation cannot be relied on.
Upcoming & In-progress Features:
- Work-in-progress on FDC3 security with a planned cross-firm demo for the next OSFF; involvement from multiple firms and potential for further participants.
- Proposals to expand FDC3 API to allow for metadata broadcasting, including features like message signatures, tracing, and enhanced message tracking.
- Sub-agent proposal to allow multiple logical apps/widgets in one window to use FDC3 independently.
- Ability to add an intent with a context filter, supporting multiple handlers based on context—primarily useful for dynamic registration and development use.
Issues & Maintenance:
- Ongoing refinement of documentation for clarity, particularly around stateful channel nature and terminology (debate on renaming "desktop agent" due to evolving industry usage and AI terminology).
- Proposal to parameterise URLs in the app directory for context-driven navigation.
- Plan to allow addContextListener to accept multiple context types for the same handler, improving filtering and rendering.
- Proposal to add a classification field to fdc3.instrument context type (@hughtroeger), marked potentially experimental.
- Maintenance needed on FDC3 workbench (e.g., migration from MUI4 to MUI5).
- CommonJS build issues to be followed up (@hughtroeger with Eric).
Older/Parked Issues:
- Items such as window spawning and dynamic user channel changes have been parked due to complexity and pending use cases.
- Notification APIs and actionable notifications remain open as potentially high-value additions, with detailed proposals ready for community input.

Action Items

[ ] @kemereva to respond to and clarify Go interface/library question, and consider how/if to release interfaces for Go.
[ ] @robmoffat to link relevant conformance PRs to outstanding issues (#1611, #1608, etc.) and confirm they are resolved upon merge.
[ ] @hughtroeger to follow up with Eric regarding CommonJS build issues and report back.
[ ] All maintainers to review the open issue on renaming terminology (desktop agent, FDC3 runtime, etc.) and contribute suggestions for improvements at the next standards working group.
[ ] @hughtroeger to update and submit the PR for the classification field for instrument contexts, marking the new field as @experimental.
[ ] Volunteers (anyone interested) to work on migrating FDC3 workbench from MUI 4 to MUI 5.
[ ] All maintainers to periodically review and prune older issues, focusing on those regaining relevance.