Use Cases and Workflows Discussion Group - 5th September 2024

mistryvinay commented 2 months ago

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 5 September 2024 - 9am (US eastern timezone EST) / 2pm (London, BST)

Zoom info

Join Zoom Meeting
Meeting ID: 969 4029 4948
Passcode: 636931

Dial-in:	Country	International 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

[x] Convene & roll call, review meeting notices (5mins)
[x] Review action items from previous meeting (5mins)
- [x] #1299
[x] Discussion of open issues (10mins)
- [x] #1164
- [x] #1173
- [x] Review proposals for types related to persona workflows the list below (20 mins)
- [x] #1183
- [ ] #1218
- [ ] #1219
- [ ] #1220
- [ ] #1221
- [ ] #1222
- [ ] #1223
- [ ] #1224
[x] AOB & Adjourn (5mins)

Minutes

Roll call and introduction for Use Cases and Workflows Discussion Group
Walk through of previous exercise in identifying FDC3 end user personas
- 1173
Drill down on #1183
- Review of proposed types listed here
- @madeleine raised concern with usage of CreateOrder and how it could be perceived to created an actual order as opposed to sharing context to another application/system (e.g. OMS).
- FDC3 is focused around interop and not having to type things in twice
- @kriswest mentioned intention was to help you jump off into a form for creating an order locally that you'd then submit to another system, somewhere else.
- @mjkingnyc when creating orders from a buy side PM to a buyside trader, seen as an internal function. When passing orders between firms, FIX is the default infrastructure that would be used.
- @kriswest covered the standard prefixes which are part of the standard.
- Updated the proposal to StartOrder to avoid any confusion
Partnering with FIX Community to better understand workflows
- @madeleine mentioned collaborative work with FIX community and possible ways of including FIX identifiers within FDC3 context objects.
- Enabling use-cases like tracking order progress within external systems.
- @kriswest many objects have the ability to reference multiple ID's. We could look to support a FIX ID.
ViewRisk Context Type Proposal
- Explored what would be required to support ViewRisk context type
- @kriswest typical information for viewing risk on organization, whole portfolio, position, an instrument product.
- @mjkingnyc lets view risk as a position. Because it's typically a single instrument. Or even in a complex derivatives world, it's represented by one thing.
- @kriswest Position is one of the existing standard types, There is a ticket open to enhance position, it's essentially defined by an instrument. Like all context types it has an ID field which can point to one or more identifiers.
ViewBlockTrades and ViewLiquidity Context Type Proposals
- @mjkingnyc showed interest in reviewing the requirements to build context types for ViewBlockTrades and ViewLiquidity
Walkthrough of generating context pages from schema files
- @robmoffat referenced this work and the set of instructions on how to submit new types to the FDC3 project
- @kriswest @mistryvinay discuss what's remaining for automation of documentation before sharing with community.

Action Items

[ ] @mjkingnyc explore definition of Context type for ViewBlockTrades and ViewLiquidity
[ ] @yeahjim1 share Context proposals for FDC3 Trader Persona with ISV's to gauge feedback and interest.
[ ] @pvoznyuk review CDM model https://cdm.finos.org/
[ ] @robmoffat review the CDM object builder https://github.com/finos/cdm-object-builder
[ ] @unqorkRules schedule demo of how CDM models are used within Unqork

Untracked attendees

Full name	Affiliation	GitHub username

mistryvinay commented 2 months ago

Vinay Mistry / Symphony 🎵

robmoffat commented 2 months ago

Rob Moffat / FINOS 📦

yeahjim1 commented 2 months ago

Jim Bunting / interop

mjkingnyc commented 2 months ago

Mike King/ S3 Partners

kriswest commented 2 months ago

Kris West / interop.io 🚀

pvoznyuk commented 2 months ago

Pavlo Vozniuk / RBC CM

finos / FDC3