FDC3 Standard WG Meeting - September 25th, 2025

Date

Thursday 25th September 2025 - 10am (US eastern timezone EDT) / 3pm (London, 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 [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

[x] Convene & roll call, review meeting notices (5mins)
[ ] Review action items from previous meeting (5mins)
- #1656
[x] Note recently merged PRs:
- #1645 (note new compliance requirement for web implementations - mostly needs to be implemented by preload DAs, as it is already implemented in DesktopAgentProxy instances returned by getAgent)
- #1642
- #1613
[x] Contributions sought to resolve issues:
- #1486
- #1646
- #1660
- #1672
- #1673
- #1674
[x] #1609
[ ] Is it time for an FDC3 major release?
- The following items are worth discussing in that content (other issues could also be included in the release):
- API:
  - New requirement to bind API calls (#1645)
  - New channel.clearContext(...) fn (#1379)
  - New metadata function signatures (PR TBC)
    - #735
  - Procedures for resolving fully-qualified appIds and unqualified appIds (#1523)
  - Remove API deprecated functions (proposed)
  - #1646
- AppD:
  - Remove deprecated API endpoints (proposed)
- CommonJs build (already broken in 2.2, see #1609)
[ ] #1657
- What changes would simplify comprehension of the Standard for App developers?
- What changes are more or less disruptive or breaking?
[x] AOB & Adjourn (5mins)
Review of Action Items from Previous Meeting
- Context clearing PR merged following review by @bingenito.
- @julianna-ciq and @kriswest to reconnect on the context metadata PR; conformance test rewrite proving challenging to complete before OSFF New York.
- Updates to conformance test framework discussed; @robmoffat to investigate syncing latest working 2.0 version and applying 2.2 updates to aid future replacement.
- Node and Java App Directory PRs reviewed by @robmoffat; further feedback and adoption into FinOS Labs needed, maintainers invited to review.
- Parameterised URL support: @kemereva to provide a demonstration in future; not carried over as a recurring action, but open for future contribution/feedback.
Recently Merged PRs
- Noted a new compliance requirement for JS/web implementations: API-returned objects must bind this (#1645).
- Context clearing function and behaviour now merged, including clear context support DesktopAgentProxy. WOrk needed to support in the reference implementation.
- Dynamic intent handler registration now available in the FDC3 web reference implementation.
Contributions Sought to Resolve Issues
- Additional documentation needed to clarify context type definition as JSON (not only TypeScript).
- Contribution sought to implement support for an array of contextTypes in fdc3.addContextListener() (#1646) – will require type, documentation, proxy, and reference implementation updates. @kriswest/@robmoffat can support contributors.
- Documentation needed to clarify the stateful nature of channels (#1660).
- Issues raised for FDC3 Workbench: version check for 2.2 (#1672), context example updates (#1673), and support for listening to events (#1674); contributions invited.
CJS Build Changes Breaking Node Consumers (#1609)
- Breaking change in JS libraries noted for Node/CommonJS consumers; discussion concluded that moving forward with standard ESM and updating tsconfig is preferable to reverting to CommonJS. @Roaders to raise a PR to update all imports/extensions and @hughtroeger to help test; PR builds or RC releases to be used for validation.
Is it Time for an FDC3 Major Release?
- The group discussed whether upcoming changes (e.g. binding requirements, clearContext, metadata signature updates, resolution procedures, removal of deprecated functions, context listener array support) are sufficient to justify a major (3.0) release instead of 2.3.
- Consensus that if breaking changes are being made, all deprecated APIs should be removed at the same time.
- The need for clear scope and community comment for a 3.0 release was emphasised; feedback invited on the issue.
Terminology Changes
- Discussion of renaming or clarifying key FDC3 terms to improve comprehension and reduce ambiguity, especially for new adopters and non-financial sectors.
  - "Desktop Agent" identified as particularly problematic; terms like "Orchestrator" or "API" suggested as alternatives. "Server" was discussed but seen as potentially confusing.
  - The group supports treating "FDC3" as a brand rather than an acronym, following industry precedent (e.g. ECMA).
  - Confusion caused by the term "Private Channel" highlighted; alternative names or merging its features into regular channels proposed.
- No immediate action agreed; topic and naming discussion to continue at next meeting, with @SeeWhatsOn to document suggestions/issues and @kriswest to summarise transcript feedback.
AOB & Adjourn
- Suggestions for contributions welcomed, including documentation, website/branding improvements, and small maintenance tasks (e.g. FDC3 Workbench).
- The topic of classifications for instrument context was briefly mentioned as a future discussion item.

Action Items

[ ] @julianna-ciq and @kriswest to reconnect and plan next steps for context metadata PR and conformance test rewrite.
[ ] @robmoffat to locate and confirm a working FDC3 conformance framework 2.0 tag and proceed with correct 2.2 update path.
[ ] @finos/fdc3-maintainers to complete review of Node and Java App Directory appD implementations and coordinate feedback/adoption into FinOS Labs.
[ ] Contributor sought to implement array support in fdc3.addContextListener() (type, docs, proxy, reference implementation); contact @kriswest/@robmoffat for support.
[ ] @kriswest to draft and update documentation clarifying channel statefulness and context type definition as JSON.
[ ] @Roaders to raise a PR updating FDC3 module resolution and imports for ESM/node compatibility, with @hughtroeger to test.
[ ] @SeeWhatsOn to document terminology and naming suggestions/issues on the relevant GitHub issue.
[ ] @kriswest to bring back naming and major release scope as agenda items for next meeting.
[ ] All: Feedback on scope/timing of next major release and on naming/terminology invited via comments/issues.