Standard WG Meeting - January 22nd, 2026

[kriswest]

Date

Thursday 22nd January 2026 - 10am (US eastern timezone EST) / 3pm (London, GMT)

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.

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)
  • Standard WG Meeting - December 18th, 2025 #1725
• Updates the to FDC3 maintainers meeting/groups
  • FDC3 Maintainers meeting 14th Jan 2026 #1729
• Update from the FINOS board meeting (@robmoffat) and the FDC3 Security strategic initiative
• New issues raised:
  • Discrepancies between the documentation and the API for FDC3 2.2 #1727
  • Improve Error Reporting When Desktop Agent *adaptor* Iframe doesn't load #1733
• FDC3 2.2 release planning
  • Reviews still needed on Conformance 2.2: Added New Tests Specified by Test-Pack. #1586
• Progress on Add property to support analytics across apps #1290
  • FDC3 API Metadata #1728
• AOB & Adjourn (5mins)

Meeting Minutes

• Review of previous action items:

  • App directory PRs to FINOS Labs: Repositories are set up, but maintainers/contributors have not yet been contacted to move their work. Ownership ideally should be with host organisations, especially Citi. Action item carried over.
  • ESM Support PR: @Roaders has progressed work on ESM module support; review is still pending and help requested from other maintainers and contributors (@SeeWhatsOn, @julianna-ciq).
  • FDC3 wiki maintenance: Progress on documentation around API and testing; further investment needed in contributor guidance.
  • AppD specification enhancement: Not yet done (@rmcneely-interopio); others can contribute to expand AppDirectory records for better AI support. More app lifecycle metadata and descriptive fields needed.
  • Engagement on bridging metadata: @kziemski and @novavi continue work with FDC3 and MCP communities; ongoing, left open.
  • Some action items rolled over due to absence of key contributors

• Updates from FDC3 maintainers meeting/groups:

  • Minutes from last maintainers' meeting available; decision reached to prune inactive members from Slack and mailing lists to focus discussions to the active group.
  • Future agendas to be posted immediately after meetings for collaborative editing.
  • Maintainers encouraged to add topics or invite participants as needed.

• Update from FINOS board meeting and FDC3 Security strategic initiative:

  • @robmoffat reported FINOS board approval for FDC3 as a strategic initiative in 2026, with dedicated resources for release work including identity and security.
  • Strong board support expressed by multiple organisations.
  • Priority is to finish FDC3 2.2, then move on to security work and FDC3 3.0 proposals.

• New issues raised:

  • Discrepancies between documentation and API for FDC3 2.2 (Discrepancies between the documentation and the API for FDC3 2.2 #1727): Specific errors identified (payload field issue, missing Boolean property in docs). Fixes to be addressed for 2.2 release, but at lower priority.
  • Error reporting when Desktop Agent adaptor iframe fails to load (Improve Error Reporting When Desktop Agent *adaptor* Iframe doesn't load #1733): Inadequate error messaging with agent/adaptor. Plan discussed to refactor for better error capture and reporting and to align with agreed protocol in documentation

• FDC3 2.2 release planning:

  • Reviews are still needed for Conformance 2.2 PR (Conformance 2.2: Added New Tests Specified by Test-Pack. #1586). @openfin-johans has completed a review; others are urged to do so to expedite release.
  • Release branch for 2.2 will be created after conformance PR is merged.
  • ESM PR (Esm modules fix #1677) also needs review; maintainers with module experience requested to assist.

• Progress on analytics property and API metadata:

  • @julianna-ciq and @kriswest are collaborating on work on API metadata (FDC3 API Metadata #1728), with a to-do list in progress.
  • Additional documentation and schema reviews are ongoing; security group to be engaged for parallel work once soon.
  • Practical/work session suggested to help contributors with the documentation process.

• AOB & Adjourn:

  • No other business raised.
  • Call for reviewers and organisational help, especially around meeting notices and agenda accuracy.

Action Items

• Contact Citi contributors to move app directory PRs to Finos Labs repositories (@robmoffat, @kriswest)
  • Confirm and assign maintainers for new app directory repositories
• Review Conformance 2.2 PR (Conformance 2.2: Added New Tests Specified by Test-Pack. #1586) as soon as possible (@robmoffat, @SeeWhatsOn, @openfin-johans, @kemereva, @bingenito)
• Fix documentation/API discrepancies in FDC3 2.2 (Discrepancies between the documentation and the API for FDC3 2.2 #1727) @kriswest
• Support API metadata documentation and coordinate with security group (@julianna-ciq, @robmoffat, @kriswest )
• Review ESM module PR (Esm modules fix #1677) – volunteers needed (@Roaders, @SeeWhatsOn, @julianna-ciq, @openfin-johans)
• Improve error reporting for Desktop Agent adaptor iframe load (Improve Error Reporting When Desktop Agent *adaptor* Iframe doesn't load #1733) (@kriswest - lower priority than reviewing Conformance 2.2: Added New Tests Specified by Test-Pack. #1586)
• Expand AppDirectory record to enhance AI/LLM support (open to contributions)
• Continue engagement on bridging metadata enhancements (@kziemski, @novavi)
• Create FDC3 2.2 release branch post-merge of Conformance 2.2: Added New Tests Specified by Test-Pack. #1586 into main (@kriswest)
• Attend to agenda and meeting notice process improvements (all maintainers)

Untracked attendees

Full name	Affiliation	GitHub username

[SeeWhatsOn]

Chris Watson / Elgin White ⌨️

[openfin-johans]

Johan Sandersson / HERE 🎁