FDC3 FDC3 for Web Browsers & Bridging Discussion group 17th April 2025

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 simialr 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 17 April 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.
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

[x] Convene & roll call, review meeting notices (5mins)
[x] Review action items from previous meeting(s) (5mins)
- #1551
- #1542
[x] Any feedback on 2.2.0 release testing?
[x] A note on destructuring the Desktop Agent API (@julianna-ciq)
[x] #1543
[x] #1545
[ ] #1546
[ ] #1250 and #1263
AOB & Adjourn

Minutes

Convene & Roll Call, Review Meeting Notices
- Meeting commenced and roll call conducted.
- Reviewed meeting notices, completed within allocated time.
Review Action Items from Previous Meeting(s)
- Desktop Agent Bridging Discussion group - 26th March 2025 #1551: No action items remain.
- FDC3 for Web Browsers Discussion group 20th March 2025 #1542:
  - User channel issue resolved; fix included in version 2.2.
  - Placeholder/callout updates made in documentation for SubAgent information.
  - Discussion on 2.3 branch proposals related to security and SubAgent.
Feedback on 2.2.0 Release Testing
- Conformance testing aspects discussed; Rob working on moving the framework to the monorepo.
- Mention of using AI to support conformance testing.
A Note on Destructuring the Desktop Agent API (@julianna-ciq)
- Julianna summarised the issue and proposed fixes were discussed.
  - DesktopAgentProxy has had its methods bound to this, but Channel, PrivateChannel and IntentResolution all need their functions binding or swapping out for arrow functions (which always stay bound)
    - We can't fix destructuring preload Desktop Agent implementations, but we could add a recommendation or requirement to a future version of the Standard.
- Action to raise issue related to destructuring, linked to #1550.
- Proposal to implement a linter for detecting destructuring issues.
#1543
- Discussed concept of altering the channel list at runtime.
  - @kriswest pointed to some potential issues regarding saved workspaces and layouts and the past assumption that the list of channels would stay the same.
- @robmoffat highlighted user channels as a workspace concept; Pavlo raised the idea of default user channels.
- @robmoffat and others to review proposed solution on issue (allow update of displayMetadata rather than channel.id)
#1545
- Giles proposed consistent functionality irrespective of registration method.
- Explored options for handling context types:
  1. Overloading signatures.
  2. Adding an option for backward compatibility.
  3. New method addIntentListenerWithContext.
- Action for Giles to update the issue with potential solutions and organise voting.
#1546
- To be discussed next time
#1250 and #1263
- To be discussed next time

Action Items

@julianna-ciq : Raise an issue linked to destructuring topic (#1550).
@Roaders : Update the issue on context handling in intent listeners (#1545) with proposed solutions.
@robmoffat review proposal on issue #1543 and see if it meets your needs in FDC3 Sail
@kriswest add #1546 and #1250/#1263 to next meeting agenda.