FDC3 FDC3 for Web Browsers & Bridging Discussion group

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 DD MMM yyyy - 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 [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 (5mins)
- #1686
[x] Status of OpenSource FDC3-for-web reference implementations
[x] FDC3 NPM module release planning
- Propose scope for release - software changes only, no Standard revisions - cheery pick a release branch
  - #1692
  - #1693
    - #1695
  - #1691
    - #1694
    - Any other common-js changes? E.g. Bundling?
  - #1678
    - #1696 - breaking change... a smaller change could be made
  - #1683
    - #1684
  - #1667 - some of this should go in next FDC3 Standard version, but do we need to repeat some of the cleanup in BrowserTypes for this release?
  - #1638
    - #1645
  - #1589
    - #1629
  - #1610
    - #1613
  - #1586
    - #1455
    - #1605
    - #1608
    - #1611
[x] #1685
[x] Check-in/any updates on #1250 & #1263
[ ] AOB & Adjourn (5mins)

Minutes

Review of previous action items:
@kriswest and @julianna-ciq discussed outstanding metadata work; plan to meet and draft a guidance document for future PRs, highlighting the increasing documentation needs for FDC3. Agreement to seed knowledge in the GitHub wiki for easier contribution.
Collation and backport of PRs/fixes for upcoming 2.2.2 release:
- @kriswest presented a list of changes proposed for cherry-picking into the release and reiterated that the release will be software-only, not affecting the Standard.
- Action to add messaging for app state changes (hidden/frozen) in web browsers to notify desktop agents—ongoing investigation and discussion.
- Multiple related issues (reconnection, desktop agent state changes) raised; further investigation planned.
- Agreement to exclude the heartbeat argument handling issue (#1678) from this release unless use cases arise.
- Discussion on confusing dependency in @finos/fdc3-commonjs; @Roaders to update PR and investigate bundling declaration files to remove circular dependencies.
- Minor schema/type cleanup (context simplification) discussed; consensus that inclusion in the release is low priority but could be completed if time allows.
- DesktopAgentProxy destructuring/binding added to Standard for next version; agreed to include fix in software now.
- Fixes for source maps and dynamic intent handler registration in web packages noted—include as maintenance updates.
- The major conformance PR (#1586) requires further review by maintainers before merge; controls release timeline.
Status of open source FDC3-for-web reference implementations:
Deferred in @robmoffat's absence. Discussion of SAIL and reference implementation separation; agreement that Toolbox and related code should be clearly marked as not for production use.
"Select Agent" functionality:
Discussion between @SeeWhatsOn and @kriswest on connecting apps not started by a Desktop Agent, particularly for browser agents. The failover mechanism was reviewed; further practical examples and use case documentation needed. Plan to convert the topic to a GitHub discussion.
Support for Multiple Application Scopes/Agents in a single window process:
No active work; agreed to keep monitoring for developments and revisit as contributors have time or proposals.
Homepage and "Getting Started" content:
@kriswest to raise an issue soliciting community contributions; highlighted importance of explaining the FDC3 value proposition for new users.
Alternative FDC3 acronyms:
Brief discussion led by @paulgoldsmith and @openfin-johans on terminology; ongoing consideration, but no decision reached.
Any Other Business:
- Mention of overlap with security and use cases groups.
- @kziemski updated on MCP and WebMCP developments; plans to propose FDC3 bridging to WebMCP and register relevant intents with emerging AI agent scenarios. To present further details next week.

Action Items

[ ] @kriswest and @julianna-ciq to meet and to complete metadata PR (#1290 & #1595).
[ ] @kriswest and @julianna-ciq to seed documentation guidance into the GitHub wiki.
[ ] @Roaders to update and finalise PR for @finos/fdc3-commonjs declaration files and investigate bundling (rollup DTS plugin).
[ ] @openfin-johans, @Roaders, and @julianna-ciq to review PR #1586 (Conformance 2.2) and shepherd towards merge.
[ ] @kriswest to raise an issue for homepage/Getting Started content and solicit contributions.
[ ] @SeeWhatsOn to convert "Select Agent" functionality issue to a GitHub discussion and provide practical example/use case from SAIL.
[ ] All maintainers to periodically revisit open issues and terminology PR/discussion.
[ ] @kziemski to draft and share proposal for FDC3-WebMCP bridge and register relevant intents.

Rolled over from previous meeting:

[ ] (Open) Community contributors: Invited to work on documentation clarifications, improved introductory material, and flagged PRs (#1660, #1646, #1486).