Standard WG Meeting - February 26th, 2026

[kriswest]

Date

Thursday 26th February 2026 - 10am (US eastern timezone EST) / 3pm (London, GMT)

Zoom info

Important

Please note the new Zoom details below
Please do register for the meeting and sign-in with a (free) LF account if at all possible.

• Join Zoom Meeting
• Register to the meeting series

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: It is no longer necessary to comment on the meeting agenda to indicate your attendance - however please do register for the meeting series using the link above.

Agenda

• Convene & roll call, review meeting notices (5mins)
• Review action items from previous meeting (5mins)
  • Standard WG Meeting - January 22nd, 2026 #1735
• FDC3 meetings moving to LF meetings platform (new meeting invites will be issues/registration link shared)
• FDC3 Conformance 2.2 status
  • Conformance 2.2: Added New Tests Specified by Test-Pack. #1586 & Removed version numbers from conformance test names #1726
  • Conformance tests should confirm matching FDC3 version number is returned #1750
  • Conformance tests should accept both unqualified and fully qualified app ids as valid responses #1762
    • Support fully qualified app ids to be returned by desktop agent and not fail conformance tests #1767
  • Missing Conformance Tests #1768
  • Custom mocha conformance test reporter #1769
  • Question: Conformance Test Clarification #1771
• Question: Where to rehouse FDC3 Example apps #1758
• FDC3 2.2.2 (or 2.3.0?) release status
  • Esm modules fix #1677
• Progress towards FDC3 3.0
• AOB & Adjourn (5mins)

Meeting Minutes

• App Directory PRs & Repositories:

  • FINOS Labs repositories have been set up for app directory implementations. PR for Java reference implementation is ready for review and merge. Node.js implementation still outstanding; .NET contribution from NatWest is a possibility.

• FDC3 Meetings Platform Migration:

  • Meetings are moving to the Linux Foundation (LF) Meetings platform. Attendees should register per series for correct attendance tracking and calendar updates. Meeting agenda/notice templates will be reworked for the new platform.

• FDC3 Conformance 2.2 Status:

  • The main Conformance 2.2 PR has been reviewed and merged, with further simplifications and bug fixes applied.
  • ESM module PR (Esm modules fix #1677) is near completion; final reviews and testing are required.
  • Some lower-priority actions, including improved error reporting for desktop agent adapter iframe load, are being rolled over.
  • Discussion on expanding AppDirectory records for AI/LLM usage; issue to be created for further discussion.
  • Bridging metadata enhancements: PR/issue suggested rather than continued tracking as a meeting action.
  • FDC3 2.2 release branch will be created after ESM changes are merged and final "surgical adjustment" is applied.
  • Several conformance test improvements discussed, including:
    • Support for fully qualified and unqualified app IDs (PR in review, @Roaders).
    • Gap analysis identified areas for new or improved tests (e.g. basic test for addEventListener on user channel, malformed context error responses).
    • Plan to clarify documentation and add/expand tests in future versions (e.g. conformance for certain events, method binding, destructuring).
    • Agreement to create separate GitHub issues for each new test or improvement (@Roaders to action).
    • Manual channel change test: clarified expectations and potential workarounds for agents without a user channel UI; not a blocker for conformance.

• Custom Mocha Conformance Test Reporter:

  • New Mocha reporter improves feedback during long-running conformance tests (thanks @Roaders).
  • Discussion on possibly contributing improvements upstream to Mocha; agreed to take the fix in FDC3 now and consider an upstream PR.

• FDC3 Example Apps:

  • No immediate actions; agreed that example apps should be rehoused for independent use. No urgency.

• FDC3 2.2.2 (or 2.3.0?) Release Status:

  • ESM module fix is the main outstanding item.
  • After merge and final adjustments, the release branch will be created.
  • Roadmap: release 2.2.2, possibly a quick 2.3.0 for context-cleared features, then focus on 3.0 (metadata, security, Java binding).

• Progress Towards FDC3 3.0:

  • Main focus after 2.2.2 release: metadata and security enhancements, Java binding.
  • Hugh's context type update to be merged for next version.

• AOB:

  • No further business due to time constraints.

Action Items

• Review and merge ESM module PR (Esm modules fix #1677); final testing required (@Roaders, @SeeWhatsOn, @julianna-ciq, @openfin-johans, @hughtroeger).
• Create FDC3 2.2 release branch post-ESM merge, and prepare for release including context-cleared event removal (@kriswest).
• Review and merge Java app directory reference implementation PR (@kriswest, @robmoffat).
• Expand AppDirectory record to enhance AI/LLM support (open to contributions; @kziemski, @novavi, @rmcneely-interopio, @SeeWhatsOn).
• Improve error reporting for Desktop Agent adaptor iframe load (@kriswest; lower priority).
• Attend to agenda and meeting notice process improvements for LF Meetings migration (all maintainers, @kriswest).
• Create GitHub issues for each new conformance test or improvement identified in the gap analysis (including: addEventListener basic test, malformed context error, optional feature validation, method destructuring, etc.) (@Roaders).
• Clarify documentation regarding user channel changed event firing; plan for future conformance test (@kriswest, @Roaders).
• Consider contributing custom Mocha reporter improvements upstream (@Roaders).
• Review and merge custom Mocha reporter PR (@kriswest, @robmoffat, @SeeWhatsOn).
• Prepare FDC3 Example Apps for independent use in a new location when time allows (@SeeWhatsOn).
• If time allows, add website guidance for joining LF Meetings and registering (@kriswest).

[paulgoldsmith]

Paul Goldsmith / Morgan Stanley

[SeeWhatsOn]

Chris Watson / Elgin White

[hughtroeger]

Hugh Troeger / FactSet