FDC3 for Web Browsers & Bridging Discussion group 15th May 2025 #1591
Description
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 15th May 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 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)
- Review action items from previous meeting (5mins)
- Missing source maps in npm packages #1589
- 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
- Work in progress review:
- AOB & Adjourn (5mins)
Minutes
-
Review Action Items from Previous Meeting
- @julianna-ciq was to raise an issue regarding the exclusion of Intent Resolution, Channel, and PrivateChannel from recent work (fix: better support 1.2 DAs by not requiring appMetadata in getInfo responses #1550).
- A note on supporting destructuring in JavaScript binding for the Desktop Agent should be added.
- @Roaders votes for stricter requirements (MUST).
- @robmoffat to review issue Support changes to the set of User Channels in the Desktop Agent API #1543, focused on renaming channels.
- @julianna-ciq was to raise an issue regarding the exclusion of Intent Resolution, Channel, and PrivateChannel from recent work (fix: better support 1.2 DAs by not requiring appMetadata in getInfo responses #1550).
-
Issue: Missing Source Maps in npm Packages (Missing source maps in npm packages #1589)
- Identified build issue with sourcemap files by @Roaders.
- @julianna-ciq will handle the removal of broken .map files, with no objections raised.
-
Issue: Support the Ability to Specify Where I Would Like a New App to Open (Support the ability to specify where I would like a new app to open #1546)
- Discussion on enhancing open parameters to specify app placement.
- Proposal includes using InteropOptions with "metadata" or "placement" to guide app opening locations.
- Historical context provided by @kriswest, noting earlier opposition due to complexity concerns.
- No immediate conclusion reached; further discussion encouraged.
-
Subagents Issue (Support for Multiple Application Scopes (Agents) within a single window process #1250)
-
Work in Progress Reviews
- @Roaders is working on (WIP) implement addIntentListenerWithContext #1590
- Clarification re repeated addContextListener and addIntentListener calls #1394 and Resolving Fully-qualified and unqualified AppId values #1523 need review by @finos/fdc3-editors.
- Context Clearing #1379 is ready for finalisation.
Action Items
- @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).
- @kriswest: Collaborate with @novavi on addressing subagents issue (Support for Multiple Application Scopes (Agents) within a single window process #1250).
- @Roaders: Update issue Support the ability to specify where I would like a new app to open #1546 with further proposals and invite feedback.
- @finos/fdc3-editors: Review PRs Clarification re repeated addContextListener and addIntentListener calls #1394 and Resolving Fully-qualified and unqualified AppId values #1523.
Untracked attendees
| Full name | Affiliation | GitHub username |
|---|---|---|