Group overview
Newly rebranded "Use Cases and Workflows" discussion group for FDC3, replacing "Context Data and Intents".
The remit of this discussion group is:
- talking about existing or potential financial use-cases
- unlocking the power of standardisation
- discussing new ways to collaborate either inside the organisation or firm-to-firm
- sharing expert insights about how to make the most out of FDC3
- and collaborating to shaping the future of financial workflows.
Relevant issue tags
Current open issues that relate to the discussion group:
Specific issues will also be tagged with the labels:
Meeting Date
Thursday 5th February 2026 - 10am (US eastern timezone EST) / 3pm (London, GMT)
Zoom info
- Join Zoom Meeting
- Meeting ID: 910 0100 5768
- Passcode: 402734
- Dial-in:
| Country |
International Dial-in |
Toll-free Dial-in |
| US |
+1 253 215 8782 (New York) |
877 369 0926 |
| 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.
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
Minutes
- CDM JSON Schema Hosting Solution
- Problem: CDM JSON schemas exist but aren’t publicly resolvable via stable URLs, blocking tooling that uses $ref / URL-based schema resolution.
- Proposal: Host CDM schemas on FINOS infra, similar to how FDC3 schemas are hosted.
- Implementation approach: copy schemas into the FINOS CDM website so they can be retrieved by URL.
- Benefit: URLs act as unique schema identifiers; enables automated schema retrieval and resolution by tools.
- Note: FINOS projects are hosted across different platforms/backends (e.g., CDM builder), so hosting needs a consistent, predictable pattern.
- CDM ↔ FDC3 integration planning
- Eleanor’s team to meet Rob next week to discuss integration approach.
- Concept: project CDM objects into FDC3 objects (projection/mapping layer).
- Open question: determine the required FDC3 output object shape/size (how “thin” vs “rich” the target should be).
- Agreement: FDC3 remains distinct (interaction/interop model), CDM remains a data model description; FDC3 objects may reference CDM rather than become CDM.
- Integration gaps / mapping challenges
- Known weak spots: order/trade/product types not as mature or widely integrated as needed.
- Suggested approach: allow CDM as payload where appropriate, but immediate priority is publishing schemas in addressable form.
- Ian to reach out to find resources/owners to publish and maintain the URL-addressable JSON schemas.
- Idea raised: possibly “lift”/reuse CDM product model portions where it helps.
- Trade Order Product Pull Request
- MCP integration + FDC3 adoption strategy
- Kryspin: current focus is making gRPC a pluggable transport for MCP servers.
- Interest: map “closer to the wire” for multiple messaging methods; suggested creating a demo repo to prove the approach.
- Clarified: FINOS Labs = experimental incubation path; projects can graduate to main FINOS.
- Concern: MCP ecosystem lag vs broader agent frameworks; proposed using sub-agents + natural discovery/understanding of MCP servers.
- Adoption angle: increase FDC3 exposure via MCP UE / integrations.
Action Items
Untracked attendees
| Full name |
Affiliation |
GitHub username |
|
|
|
Group overview
Newly rebranded "Use Cases and Workflows" discussion group for FDC3, replacing "Context Data and Intents".
The remit of this discussion group is:
Relevant issue tags
Current open issues that relate to the discussion group:
Specific issues will also be tagged with the labels:
Meeting Date
Thursday 5th February 2026 - 10am (US eastern timezone EST) / 3pm (London, GMT)
Zoom info
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.
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
Minutes
typeto be able to describe orders in more detail #1374 Add anfdc3.rfqcontext type to handle defining RFQ's over FDC3 #1461 PR modelling trade order product + RFQ based on client work.Action Items
Untracked attendees