Context Data & Intents Discussion group - 1 Dec 2022

[mistryvinay]

Group overview

At the FDC3 Use Cases Roundtable London, October 5th 2021 participants agreed that the FDC3 lexicon needs to be expanded, both with additional intents and context types to support Use Cases, but also to include more primitive data types in order to construct complex types. A number of participants also agreed that now is an appropriate time to expand the Lexicon.
​
See #455 for full details of the meeting outcomes.
​
This group is being convened to discuss and arrange work to contribute further Context types and Intents to support Use Cases being implemented by participants.

Relevant issue tags

Current open issues that relate to the discussion group:

Issues will also be tagged with the labels:

Meeting Date

Thursday 1 Dec 2022 - 9am EST / 2pm GMT

WebEx info

• Meeting Link: https://finos.webex.com/finos/j.php?MTID=mbb193ae433ce8d4366adcecd94355734
• Meeting number: 2556 257 8293

More ways to join

• Join by video system:
  • Dial 25562578293@finos.webex.com
  • You can also dial 173.243.2.68 and enter your meeting number
• Join by phone
  • +1-415-655-0003 US Toll
  • +44-20319-88141 UK Toll
• Access code: 2556 257 8293

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.

Agenda

• Convene & roll call, review meeting notices (5mins)
• Review action items from previous meeting (5mins)
  • Context Data & Intents Discussion group - 3 Nov 2022 #845
• Guest Speaker: Ian Sloyan [Senior Advisor Data & Digital Solutions @ ISDA] (20mins)
  • Presenting the ISDA Common Domain Model (ISDA CDM)
• PR's that are ready to be reviewed (10mins)
  • WIP: #644 | Add Order and OrderLeg Context Types #824
  • 766 evolution of chat message data structure #779
• Discussion of open issues (15mins)
  • Actionable Notifications via Intent & Context #828
  • fdc3.ChatInitSettings is missing id and type is incorrectly defined #852
  • Question: Why do RecipientsID and RecipientsObject exist? #853
  • RecipientsObject interface has un unnecessary required type property #854
  • Question: Should ChatInitSettings options have a exported interface #855
  • Tighter definition for "otherConfig" in fdc3.chart context type #856
• PR's ready to merged into 2.1 Milestone release (1mins)
  • 592 intent proposal create interaction #747
  • 592 771 context proposal TransactionResult #761
  • 767 Add ViewChat Intent #796
  • 768 Add ViewMessages Intent & SearchCriteria Context #797
• AOB & Adjourn (5mins)

Minutes

• ISDA Common Domain Model presentation by Ian Sloyan
  • Introduction of CDM and how it allows for definition and execution of trade information
    • Greater focus on being able to define derivatives and on post-trade generally (rather than pre-trade, where FDC3 seems more focused)
    • Provides a data and process for post trade lifecycle
    • Also supports legal templates useful when dealing with OTC orders
  • Demo of CDM hierarchy using Rosetta UI
    • Walk through of the various fields and types used to define financial objects
  • Example of a vanilla interest rate swap (IRS) trade using Rosetta
    • Used Rosetta UI to view underlying sample data that was being used in the IRS demo
    • It was noted that CDM relies on inference for typing (e.g. an order is a swap because of what it contains, rather than what it is declared as), rather than the explicitly stated types (as FDC3 does)
  • @kriswest Highlighted FDC3's Context type fields as being the most obvious/immediate difference between CDM's and FDC3's approaches.
    • FDC3 currently promotes composition of types from other types - proliferating those type fields throughout a complex object
    • However, it does not have to, CDM models could be adopted to represent a type without composition, with sub-contexts still being broadcast-able separately from the full complex type, see: https://fdc3.finos.org/docs/api/spec#broadcasting-and-listening-for-multiple-context-types
  • CDM doesn't currently have a type to fully represent an order pre-trade, but does include many of the components and representations for positions and individual trades.
  • Rosetta UI access - will work with Ian Sloyan to provision some accounts so the FDC3 team can also review the CDM model in more detail.
  • Consent was sought and received from all participants to share the video of the session.
• WIP: #644 | Add Order and OrderLeg Context Types #824
  • Looking for more volunteers to support this PR
  • Need to ensure we get coverage for more asset types
  • @mistryvinay & Jane Gavronsky: Drive this discussion to a wider group
    • Speak to client list and firms on how they trade asset classes
    • Reach out to OMS/EMS providers and sell-side organisations
    • Bring back as a topic to next working group, possible email campaign or a "special meeting" specifically for defining order.
• 766 evolution of chat message data structure #779
  • Consolidate and merge all chat PRs into this one
• Actionable Notifications via Intent & Context #828
  • Based on feedback for this particular issue next steps would be to put this forward at the next Standards Working Group meeting for validation.
• fdc3.ChatInitSettings is missing id and type is incorrectly defined #852
  • Verified that this is a bug (in the schema definition which is failing to extend 'Context') and will be closed via the below PR once merged
  • make chatInitSettings inherit from Context #869
• Question: Why do RecipientsID and RecipientsObject exist? #853
  • Recipient object should be a union type
  • Possible flaw in how the generator handles schemas
  • Recipients is being created by a merge of 'contact' and 'contact list'
  • Probably validates correctly. But its not a valid set of types you can use
  • Team will continue to dig deeper into this issue.
• Issues that will be reviewed offline by the @finos/fdc3-maintainers and @Yannick-Symphony
  • RecipientsObject interface has un unnecessary required type property #854
  • Question: Should ChatInitSettings options have a exported interface #855
  • Tighter definition for "otherConfig" in fdc3.chart context type #856

Action Items

• @mistryvinay to work with Ian Sloyan to provision some demo accounts for Rosetta so we can explore in more detail the ISDA CDM model.
• @mistryvinay & Jane Gavronsky to see how we can widen the group for discussing how orders should be presented over FDC3

Untracked attendees

Full name	Affiliation	GitHub username

[mistryvinay]

Vinay / Symphony

[Julia-Ritter]

Julia / FINOS

[symphony-jean-michael]

Jean-Michael Legait / Symphony

[milindchidrawar]

Milind / Singletrack

[Yannick-Malins]

Yannick / Symphony 🦄

[timjenkel]

Tim / Wellington

[dominicgifford]

Dom / SPGI

[kriswest]

Kris / Cosaic

[pierreneu]

Pierre Neu / Symphony

[iansloyan]

Ian Sloyan / ISDA

[WatsonCIQ]

Chris Watson / Cosaic 👋