Standard WG Meeting - April 23rd, 2026

[kriswest]

Date

Thursday 23rd April 2026 - 10am (US eastern timezone EDT) / 3pm (London, BST)

Zoom info

Register to the meeting series to receive an invitation:
https://zoom-lfx.platform.linuxfoundation.org/meeting/96839365264?password=b5c2bc6a-bc47-43a5-bc49-7be3e0b422c3&invite=true

Join Zoom Meeting:
https://zoom-lfx.platform.linuxfoundation.org/meeting/96839365264?password=b5c2bc6a-bc47-43a5-bc49-7be3e0b422c3

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

Agenda

• Convene & roll call, review meeting notices (5mins)
• Review action items from previous meeting (5mins)
  • Standard WG Meeting - March 26th 2026 #1808
• Announcements:
  • FDC3 2.2.2 release is out
    • Improving release workflow to add version sync guardrail and updating instructions #1864
  • OSFF Toronto outcomes
• Proposed FDC3 workshop at OSFF London (24th June 2026) @robmoffat
• Standard Cucumber steps for testing @robmoffat
• Review recently opened issues:
  • Investigate and improve OpenSSF scorecard result #1818
  • Deprecate node 20 and change testing matrix to node 22, 24 & 25 #1826
  • Switch SAST workflow from semgrep to codeql #1827
  • Replace webpack build in fdc3-conformance with vite to match other packages #1830
  • Allow apps to update their metadata that is returned in instanceMetadata #1846
  • Migrate NPM publishing to to Trusted Publishing #1849
  • Automate maintenance of ContextTypes enum and type in fdc3-standard #1852
  • Question: Resolving raised intents to the app that raised them #1860
• Review FDC3 3.0 candidates milestone: https://github.com/finos/FDC3/milestone/15
  • Work resumed on FDC3 Metadata
• AOB & Adjourn (5mins)

Minutes

• Action Items Review

  • Several previous actions are completed, particularly those tied to the FDC3 2.2.2 release.
  • Outstanding actions related to Java App Directory Reference Implementation, FDC3 Example Apps, website documentation, conformance test language, and homepage improvements were rolled over.
  • Items considered part of the FDC3 3.0 milestone will be tracked via the milestone rather than rolled over individually.
  • Action to clarify and conformance-test user channel changed event remains open.

• FDC3 2.2.2 Release

  • Release completed and published, with thanks noted for community reviews and contributions.
  • Minor issue with tagging due to oversight on root package versioning; resolved via maintainers.
  • Context package requires attention for final version sync.
  • A version sync guardrail and updated release instructions have been introduced via PR Improving release workflow to add version sync guardrail and updating instructions #1864; request for code review.

• Announcements

  • FDC3 2.2.2 release is out.
  • OSFF Toronto event reported as successful; FDC3 talks well received. Thanks to @SeeWhatsOn for representing FDC3 at the table.
  • Plans underway for OSFF London in June, with an FDC3 3.0 overview session confirmed.

• Proposed FDC3 Workshop at OSFF London

  • @robmoffat proposed an FDC3 workshop to offer hands-on experience and demo exchange, especially given strong interest in London.
  • Ideas include collaborative sessions, open demo slots, and involvement from multiple vendors and firms.
  • @robmoffat to coordinate logistics, with support from others on communications and encouraging participation.

• Standard Cucumber Steps for Testing

  • @robmoffat has consolidated BDD test step implementations (Go, Java, C#, TypeScript) into a single prospective repo to avoid code drift.
  • Proposal to add a new repo under the FDC3 project for these test steps, with appropriate documentation and maintenance by the FDC3 maintainers.
  • Next step: ensure compatibility with latest changes (e.g., migration to Vitest) and BDD script centralisation.
  • @robmoffat to explore and report back.

• Review of Recently Opened Issues

  • Investigate and improve OpenSSF scorecard result (Investigate and improve OpenSSF scorecard result #1818): Needs further community contributions.
  • Deprecate Node 20 and update testing matrix to Node 22, 24, 25 (Deprecate node 20 and change testing matrix to node 22, 24 & 25 #1826): Agreed to move to Node 24 as primary, update engines property, and switch to Trusted Publishing for NPM. @kriswest to action.
  • Switch SAST workflow from Semgrep to CodeQL (Switch SAST workflow from semgrep to codeql #1827): Community invited to take on migration.
  • Replace Webpack build in fdc3-conformance with Vite (Replace webpack build in fdc3-conformance with vite to match other packages #1830): PR open from new contributor; maintainers reviewing.
  • Allow apps to update their metadata returned in instanceMetadata (Allow apps to update their metadata that is returned in instanceMetadata #1846): Discussed expanding and standardising instance metadata fields (e.g., title, coordinates, version) and adding an update mechanism. @Roaders will consolidate the proposal.
  • Migrate NPM publishing to Trusted Publishing (Migrate NPM publishing to to Trusted Publishing #1849): Needed within ~80 days; @kriswest to begin by moving to Node 24.
  • Automate maintenance of ContextTypes enum/type in fdc3-standard (Automate maintenance of ContextTypes enum and type in fdc3-standard #1852): @kriswest proposed automating this, keeping the enum for developer convenience.
  • Question: Resolving raised intents to the app that raised them (Question: Resolving raised intents to the app that raised them #1860): Consensus that self-resolution should be off by default but configurable, to be handled via AgentProxy options in 3.0.

• Review of FDC3 3.0 Candidates Milestone

  • Work has resumed on FDC3 Metadata, with rebasing effort underway.
  • Most major items for the milestone have PRs or are being actively worked on.
  • The milestone will be used as the authoritative list for 3.0 scope. Good-first-issue labelling is effective and will continue.
  • Early plan to provide an alpha pre-release around OSFF London.

• AOB

  • No additional business raised; meeting adjourned on time.

Agenda Items Not Discussed

• All agenda items were discussed.

Action Items

• Merge Java App Directory Reference Implementation PR (@kriswest, @robmoffat)
• Prepare FDC3 Example Apps for independent use (@SeeWhatsOn, @robmoffat)
• Raise PR to update 'Get Involved' page on website with LF meeting and registration guidance (@kriswest)
• Clarify documentation regarding user channel changed event firing and plan conformance test (@kriswest, @Roaders)
• Standardise AppDirectory record types/schemas and provide validation utilities (open to contributions)
• Allow intent listeners to specify supported contexts (PR nearly ready, @Roaders)
• Review and integrate training content for homepage improvement (@kriswest, @robmoffat)
• Investigate and improve OpenSSF scorecard result (Investigate and improve OpenSSF scorecard result #1818, open to contributions)
• Switch SAST workflow from Semgrep to CodeQL (Switch SAST workflow from semgrep to codeql #1827, open to contributions)
• Move NPM workflows to Node 24 and migrate to Trusted Publishing (@kriswest, @bingenito)
• Replace Webpack build in fdc3-conformance with Vite (Replace webpack build in fdc3-conformance with vite to match other packages #1830, maintainers to review/merge PR)
• Consolidate and update proposal for app instance metadata update (Allow apps to update their metadata that is returned in instanceMetadata #1846) (@Roaders)
• Automate maintenance of ContextTypes enum/type in fdc3-standard (@kriswest)
• Review implementation of AgentProxy options for self-delivery in intent resolution and broadcasting (3.0, @Roaders, @kriswest)
• Coordinate logistics and comms for OSFF London FDC3 workshop (@robmoffat, @SeeWhatsOn)
• Explore and report back on centralisation of BDD/Cucumber steps/test scripts (@robmoffat)