Context Data & Intents Discussion group - 3 Nov 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 3 Nov 2022 - 9am EST / 1pm 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 - 6 Oct 2022 #826
• Issues that require more discussion (10mins)
  • Provide Notification API's #387
    • Actionable Notifications via Intent & Context #828
• PR's that are ready to be reviewed (5mins)
  • WIP: #644 | Add Order and OrderLeg Context Types #824
• Revisit proposals for standardised Contexts (5mins)
  • Standardize a context representing a Trade #655
  • Improve the definition of the Position context type #656
• PR's that are awaiting updates (0mins)
• 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
  • Adding optional market identifiers to the Instrument context #819
• Insights into business workflows that could be candidates for further extending FDC3 capabilities? (5mins)
• AOB & Adjourn (5mins)

Minutes

• Actionable Notifications via Intent & Context #828
  • Some further discussions and feedback regarding this proposal
    • @gerard-ciq demonstrated this proposal: https://user-images.githubusercontent.com/1701764/201643126-f8766d05-d080-42ab-86d1-e2afdd23d317.mp4
  • To edit an existing notification an id field must be included in the notification Context, identifying which is to be updated.
    • Implementations should return the notification object as an intent result, with the id field and any other relevant metadata set. This object can then be edited and resubmitted to edit the notitication.
    • This makes the interfaces to create or update notifications identical (the only difference being that the id is set in the notification) - hence we perhaps should use a single intent (CreateOrUpdateNotification) rather than two separate ones.
  • Is "GetNotifications" the correct naming? It's not quite returning notifications, it's returning a channel that you can use to receive messages about new and updated notifications. "GetNotificationsChannel" or "GetNotificationsStream"?
    • The original use case for channel results from intents was referred to as a 'feed'. How about GetNotificationFeed?
• WIP: #644 | Add Order and OrderLeg Context Types #824
  • Unfortunately we could not cover this proposal as the creator was not on the call. Will push this back to next meeting.
  • @robmoffat has also introduced us to the ISDA CDM (Common Domain Model) who are also defining data models in the financial space.
  • Invite a CDM representative to our next meeting to tell us more about CDM and discuss how we can leverage the CDM in context types.
• Revisited open PRs for feedback - most are very close to complete and ready to be consolidated for presentation to the SWG:
  • 592 intent proposal create interaction #747
  • 592 771 context proposal TransactionResult #761
  • 766 evolution of chat message data structure #779
  • 765 'ChatRoom' & 'ChatMessage' contexts and 'SendChatMessage' Intent #794
  • 767 Add ViewChat Intent #796
  • 768 Add ViewMessages Intent & SearchCriteria Context #797

Action Items

• @ALL Asks for other vendors that may use thefdc3.order type to ensure there is an agreement with WIP: #644 | Add Order and OrderLeg Context Types #824
• Speak to @nemery-flextrade, @dominicgifford, @hampshan see if they can attend the next meeting
• @mistryvinay add CDM speaker to the December agenda

Untracked attendees

Full name	Affiliation	GitHub username

[milindchidrawar]

Milind Chidrawar / Singletrack

[pierreneu]

Pierre Neu @ Symphony

[mistryvinay]

Vinay Mistry / Symphony

[Julia-Ritter]

Julia / FINOS

[gerard-ciq]

Gerard Petersen / Cosaic

[kriswest]

Kris / Cosaic 🚀

[eteridvalishvili]

Eteri / FINOS

[robmoffat]

Rob / FINOS

[WatsonCIQ]

Chris Watson / Cosaic

[hughtroeger]

Hugh Troeger / FactSet