FDC3 for Web Browsers Discussion group 20th March 2025 #1542
Description
Group overview
Group convened to work on proposals to enable vendor-agnostic FDC3 use in a web browser and now working on extending the adopted proposals and other issues relating to FDC3 use in Web Applications.
The main proposal and supporting software are now part of the current draft of FDC3 2.2 on the main branch of the FDC3 repo and website (main/unreleased version) and are due to be adopted as FDC3 2.2 shortly, see:
- https://fdc3.finos.org/docs/next/api/ref/GetAgent
- https://fdc3.finos.org/docs/next/api/specs/browserDesktopAgents
Beta releases of the software artefacts are available on NPM: https://www.npmjs.com/package/@finos/fdc3/v/2.2.0-beta.3
Relevant issue tags
Current open issues that relate to the above concepts with the label:
Meeting Date
Thursday 20th March 2025 - 11am EDT / 3pm GMT (we're between day-light savings time changes!)
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)
- Any questions relating to 2.2 adoption or 2.2.0 release (upto 10 mins)
- When the User Channel Changes, DA Proxy ContextListeners fail to recognise the change #1540 (5 mins)
- Support for Multiple Application Scopes (Agents) within a single window process #1250 and Question: Disposal/Teardown patterns in FDC3 #1263 (30 mins)
- Support changes to the set of User Channels in the Desktop Agent API #1543 (5 mins - if time)
- Adjourn
Minutes
- Review Action Items from Previous Meeting
- General meeting featured demos of 3 FDC3 implementations for the Web.
- Maintainers have reviewed conformance testing for version 2.2.
- Kris is updating clarification for issue Question: getAgent documentation clarification #1464, still awaiting feedback.
- Closed out DOM projection issues as they do not apply to current use cases.
- Inclusion of multiple application scopes added to the existing agenda.
- Questions Relating to 2.2 Adoption or 2.2.0 Release
- Adoption vote for version 2.2 is public, open until April 1. Registration details are in the FDC3 repository's governance markdown file.
- After the vote, the 2.2 Release PR should be merged, releasing both docs and NPM modules as 2.2.0
- When the User Channel Changes, DA Proxy ContextListeners fail to recognise the change #1540
- Discussion on the nature of user channels being dynamic or pre-configured.
- Kris suggests avoiding unnecessary complexity in features that may not have tangible use cases.
- Giles highlights triviality in supporting dynamic changes but questions its necessity.
- Participants urged to contribute comments on the issue while Julianna is tasked with code verification.
- Support for Multiple Application Scopes (Agents) within a single window process #1250 & Question: Disposal/Teardown patterns in FDC3 #1263
- Addressing the challenges of supporting multiple widgets without using iframes.
- Exploration of app identity and interaction within shared URLs.
- Intent resolver examples: managing multiple charting instances as separate entities.
- Discussion of desirability of platforms replacing internal messaging buses with inter-app communication using FDC3.
- Portability of implementations between platforms (container agnostic), architectural simplicity (use one communication mechanism rather than two), ease of integration with 3rd party apps.
- Support changes to the set of User Channels in the Desktop Agent API #1543
- Analysis of user channels' scope and associated communication methodologies.
- FDC3 recommends (SHOULD) a specific set of 8 channels
- Kris highlights the possible impact of optional features on Desktop Agent conformance.
- Encouragement given to propose specific API changes (with use cases) and evaluate necessity of conformance test implementations.
Action Items
- @kriswest to start an empty PR off to address Support for Multiple Application Scopes (Agents) within a single window process #1250 and Question: Disposal/Teardown patterns in FDC3 #1263 and mark out where additions will be needed in the Standard, to facilitate community input on proposed changes.
- @julianna-ciq to evaluate and confirm the presence of the discussed bug When the User Channel Changes, DA Proxy ContextListeners fail to recognise the change #1540
- Members advised to provide feedback on dynamic user channel implementation need and feasibility.
Untracked attendees
| Full name | Affiliation | GitHub username |
|---|---|---|