-
Notifications
You must be signed in to change notification settings - Fork 165
Description
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 3 April 2025 - 9am (US eastern timezone EST) / 2pm (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.
-
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.
- 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)
- Improving Participation in the Discussion Group (20 mins)
- Are there specific topics or formats that would encourage more participation.
- Review meeting format, cadence and duration. Guest contributors boost interest.
- Members could take turns leading a topic or sharing insights, even briefly.
- Review proposals for types related to persona workflows the list below (10 mins)
- AOB & Adjourn (5mins)
Minutes
- Improving Participation in the Discussion Group
- Discussion on improving the meetings by shifting focus from technical details to identifying use cases and workflows, and exploring the possibility of guest speakers and more open forum discussions.
- @julianna-ciq @kriswest proposal to transform meetings into use cases and office hours sessions, allowing attendees to bring their own topics and share insights, aiming to make meetings more valuable and engaging.
- Improve available FDC3 Materials / Content
- @ameetj85 involve subject matter experts in explaining the value of FDC3 to non-experts, potentially through videos or live Q&A sessions, to facilitate easier adoption and understanding of the standard.
- Idea to promote the ease and benefits of contributing to FDC3, targeting mid-senior developers who may have encountered gaps in the schema, to increase community participation and standard evolution.
- Consideration of conducting surveys to gather feedback on FDC3 usage and identify popular features, aiming to reach a wider audience and understand user needs better.
- Trade, Order, Product and RFQ context types #1503
- Discussion on the proposal for updates to trade order products.
- @albertherd is reviewing for potential workflows for a current project.
Action Items
- From March: @kriswest to review and provide feedback on City's reference implementations for FDC3 at the next maintainers meeting.
- From March: @Lecss to create a proposal for improving the FDC3 'Getting Started' guide with an NPM package-like experience focusing on incremental discovery.
- From March: Swati to connect with @robmoffat to explore converting the AI-powered JSON schema generator work into a blog post for the FDC3 labs/website.
Untracked attendees
| Full name | Affiliation | GitHub username |
|---|---|---|