Standard WG Meeting - July 23rd, 2026

[kriswest]

Date

Thursday 23rd July 2026 - 10am (US eastern timezone EST/EDT) / 3pm (London, GMT/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 - May 28th, 2026 #1904
• Provide programmatic (runtime) access to standardized context type schemas #1993
• FDC3 v3 Release Roadmap proposal #1988
• Ambiguity: bare-appId raiseIntent cannot distinguish "open new instance" from "target app, resolve normally" #1940
• other open issues in scope for 3.0: https://github.com/finos/FDC3/issues?q=is%3Aopen+milestone%3A%22FDC3+3.0%22
• AOB & Adjourn (5mins)
• FDC3 v3 alpha web implementer feedback: route-scoped identity, context-only apps, and custom context guidance #1943

Minutes

• Review action items from previous meeting

  • Several previously open action items are now complete (see below for rolled over/incomplete items).
  • Some actions remain open and have been rolled over to the next meeting (see action items below).

• Programmatic (runtime) access to standardised context type schemas (Provide programmatic (runtime) access to standardized context type schemas #1993)

  • Initial PR submitted by Nima Chalet (Rocket Fin) to expose context schemas at runtime.
  • Requested changes: instead of generating new JS objects for schemas, leverage bundled schemas from the schema package; automate type name array maintenance.
  • No objections to adding these functions to the package; update pending from contributor.

• FDC3 v3 Release Roadmap proposal (FDC3 v3 Release Roadmap proposal #1988)

  • Discussion on proposed timeline vs. roadmap; consensus that timing is useful for tracking momentum and for OSFF announcement planning.
  • Outstanding items are largely review of significant PRs (e.g., Java binding/WSCP protocol), documentation, and binding updates.
  • Some non-blocking/infrastructure items moved to a new "project infrastructure" milestone.
  • Aim remains to be ready for voting in September, in time to release by OSFF.

• Ambiguity: bare-appId raiseIntent cannot distinguish "open new instance" from "target app, resolve normally" (Ambiguity: bare-appId raiseIntent cannot distinguish "open new instance" from "target app, resolve normally" #1940)

  • Discussed and agreed that the exploration/fix for this issue is not a requirement for v3.0.
  • Item moved to v3.1 milestone since no implementations have reported it as blocking.

• Other open issues in scope for 3.0

  • Reviewed all open issues and milestones; prioritisation focused on breaking/API changes for v3.0, with additive/non-breaking or infrastructure tasks moved to v3.1 or separate milestones.
  • Items discussed and moved:
    • "Allow apps to update their metadata", "allow apps to decide to receive their own broadcasts", "improve error reporting for desktop agent iframe" all moved to v3.1.
    • Infrastructure/maintenance/documentation clarifications grouped under new milestone.
    • Conformance test coverage is a high priority; agreement that tests for new/changed API should accompany PRs.
    • Outstanding conformance test PRs and doc changes to be tackled in bulk.
    • Remaining API binding (Java, .NET, Go) and WSCP protocol PRs need focused review and update.

• AOB & Adjourn

  • Brief discussion on maintaining security/patching cadence (Dependabot PRs), and clarifying merging policy for website-impacting updates.
  • General agreement that the project is on track to meet the September deadline for v3.0 release, pending completion of reviews and documentation.
  • Noted need for continued attention on Java binding and cross-language sync.
  • No other business was raised.

• FDC3 v3 alpha web implementer feedback: route-scoped identity, context-only apps, and custom context guidance (FDC3 v3 alpha web implementer feedback: route-scoped identity, context-only apps, and custom context guidance #1943)

  • Not discussed during this meeting.

Action Items

• Merge Java App Directory Reference Implementation PR (@kriswest, @robmoffat) — still outstanding and high priority.
• Raise PR to update 'Get Involved' page on website with LF meeting and registration guidance (@kriswest)
• Standardise AppDirectory record types/schemas and provide validation utilities; create and link issue to 3.0 scope (@kriswest)
• Review and integrate training content for homepage improvement (@kriswest, @robmoffat) — deprioritised, but content exists for future repurposing.
• Review and update .NET/C# API binding for FDC3 API Metadata (Update .NET/C# API binding to support FDC3 API Metadata as a required feature #1892) (@bingenito)
• Review and update Go API binding for FDC3 API Metadata (Update Go API binding to support FDC3 API Metadata as a required feature #1893) (@kemereva)
• Review and test Cucumber steps port PR (Cucumber testing steps port #1890) (awaiting upstream migration, @robmoffat to ping Juan)
• Investigate and address bundle bloat and unused code in @finos/fdc3 (@Roaders, @hughtroeger, @kriswest, @factset)
• Raise a follow-up PR to correct intent result type documentation to include contextWithMetadata (@julianna-ciq to implement, per meeting)
• Complete/merge open documentation PRs (esp. homepage elevator pitch, clarifications, type generation) (@kriswest)
• Review and update all language bindings and ensure cross-sync prior to v3.0 release (@robmoffat, @kemereva, @bingenito, @julianna-ciq)
• Review/merge existing outstanding PRs for v3.0 items (see milestone tracker, all maintainers).
• Automate maintenance of array of context types from schemas (pending update by Nima Chalet).
• Ensure conformance test definitions and tests are added alongside API/feature PRs (@Roaders, @kemereva, @julianna-ciq, @kriswest, @robmoffat).