FDC3 for Web Browsers & Bridging Discussion group - 19th June 2025

[kriswest]

Group overview

Discussion group focused on FDC3 use in Web browsers and the Bridging of FDC3 Desktop Agents to allow interop to span across them (based on similar techniques to FDC3 comms in a Web browser).

Software support for both FDC3 in a Web Browser and Desktop Agent Bridging are provided in the FDC3 2.2 NPM module: https://www.npmjs.com/package/@finos/fdc3/v/2.2.0

Relevant issue tags

Current open issues that relate to the above concepts with the labels:

Meeting Date

Thursday 19th June 2025 - 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)
• OSFF London reminders
• Review action items from previous meeting (15-20mins)
  • FDC3 for Web Browsers & Bridging Discussion group 15th May 2025 #1591
• New issues:
  • CJS build changes breaking Node consumers #1609
  • FDC3 Workbench intent raising control could be more intuitive #1612
  • Question: Strategy for Latest Context between two types: fdc3.instrument and fdc3.instrumentList while ignoring others #1616
• Issues arising from work on 2.2 conformance
  • Implementation issue being fixed in the proxy or reference implementation
  • What is missing from the conformance tests
• Work in progress review (for any topics not covered under action items review above):
  • Context Clearing #1197
    • Context Clearing #1379
  • Should the desktop agent support both unqualified appIds and fully qualified ones? #1475
    • Resolving Fully-qualified and unqualified AppId values #1523
  • Clarify: What should happen on repeated listener addition for the same contextType/intent #1390
    • Clarification re repeated addContextListener and addIntentListener calls #1394
  • Support specifying supported context when registering an intent listener #1545
    • (WIP) implement addIntentListenerWithContext #1590
• Other open issues under discussion:
  • Support the ability to specify where I would like a new app to open #1546
  • Support for Multiple Application Scopes (Agents) within a single window process #1250 & Question: Disposal/Teardown patterns in FDC3 #1263 (defer until after OSFF?)
  • any others identified by participants
• AOB & Adjourn

Minutes

• CJS build changes breaking Node consumers #1609
  • The issue raised was discussed - we're in need of feedback on the CJS build, which this is.
  • Follow-up questions to the author were raised and the issue responded to - we can certainly adjust the CJS build, but should not do so at the expense of web apps, which are the primary consumer of our modules. Hence, the maintainers have a strong desire to keep to a separate CJS module, which is (or should be) easy to switch an application to.
  • We need to find a contributor willing to work on tests and a solution
• FDC3 Workbench intent raising control could be more intuitive #1612
  • Issue was discussed and it was agreed this is working, but the controls could be more intuitive (for example disable intent selection until the required context is entered). @kriswest and @Roaders to update the issue description.
• Question: Strategy for Latest Context between two types: fdc3.instrument and fdc3.instrumentList while ignoring others #1616
  • The issue was discussed and there was consensus that there is a valid use case that will require additions or changes to the API to enable. There are a couple of possible solutions, which include:
    • The metadata proposal Add property to support analytics across apps #1290 (which could include a timestamp
      • However, it was identified that we'd either need a new getAllCurrentContexts() function which returns all the contexts and their metadata or make a breaking change to getCurrentContext() so that it can return metadata.
    • A new overload for addContextListener that can take multiple types (rather than just null or a single type name), which would allow a DA to return the most recent context from the filtered set of types (rather than just the most recent of any or just one specific type).
• Context Clearing #1379
  • Largely complete - @kemereva has been short on time to work on it
  • PR is currently failing CI checks (in @finos/fdc3-agent-proxy) due to a possible build issue - possibly in need of review from another maintainer to complete
  • PR could be merged into a branch of the FINOS/fdc3 repo to enable collab and debug
• Resolving Fully-qualified and unqualified AppId values #1523
  • Consensus that this is ready to be merged
  • @finos/fdc3-editors to complete their review then @kriswest to merge
• Clarification re repeated addContextListener and addIntentListener calls #1394
  • @finos/fdc3-editors to complete their review then @kriswest to merge
  • a follow-up issue will be needed to implement the change in the reference implementation and it will need a conformance test

Action Items

• @kriswest and @Roaders to update the issue description for FDC3 Workbench intent raising control could be more intuitive #1612.
• @julianna-ciq and @kriswest to create issues for the proposed solutions to Question: Strategy for Latest Context between two types: fdc3.instrument and fdc3.instrumentList while ignoring others #1616
• @julianna-ciq to look at updating the PR for Add property to support analytics across apps #1290 with a proposal for handling getCurrentContext() with metadata.
• @kemerava to either fix failing tests for Context Clearing #1379 or merge it into a finos/fdc3 repo branch for antoher maintainer to pick up and complete.
• @finos/fdc3-editors & @kriswest complete review of Resolving Fully-qualified and unqualified AppId values #1523 and merge
• @finos/fdc3-editors & @kriswest complete review of Clarification re repeated addContextListener and addIntentListener calls #1394 and merge
  • @kriswest raise an issue for followup work on Clarification re repeated addContextListener and addIntentListener calls #1394

Rolled over from previous meetings:

• @julianna-ciq: Raise issue linked to missing aspects in fix: better support 1.2 DAs by not requiring appMetadata in getInfo responses #1550 and add a note on destructuring support.
• @Roaders: Remove broken .map files from npm packages (Missing source maps in npm packages #1589).
• @Roaders: Update issue Support the ability to specify where I would like a new app to open #1546 with further proposals and invite feedback.

Untracked attendees

Full name	Affiliation	GitHub username

[novavi]

Derek Novavi / S&P Global

[lspiro-Tick42]

Leslie Spiro / interop.io

[robmoffat]

Rob Moffat / FINOS

[Roaders]

Giles Roadnight / Morgan Stanley 🚀

[kriswest]

Kris West / NatWest 🚀

[julianna-ciq]

Julianna Langston / interop.io

[diafwill]

Vincent/ ORISHAS FINANCE

[kriswest]

Kris West / NatWest 🚀

[pvoznyuk]

Pavlo Vozniuk / RBC CM