Context Data & Intents Discussion group - 31 March 2022

[rikoe]

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 31 Mar 2022 - 9am EST / 2pm BST

WebEx info

• Meeting Link
  Meeting number: 2556 257 8293

More ways to join

• Join by video system:
  • Dial 25564955451@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: 255 649 55451

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. As such, participation in a Discussion group is not required for contributing to any particular issue or FDC 2.0 as a whole.

Agenda

• Convene & roll call, review meeting notices (5mins)
• Review action items from previous meeting (5mins)
  • Context Data & Intents Discussion group - 17 Mar 2022 #627
• Discuss data type and intents for orders/products (15 mins)
  • Context Proposal: Order #644
• Review open PRs (15 mins)
  • 600 ViewProfile addition and ViewContact deprecation #619
  • 574 StartChat: ChatInitSettings and ChatRoomRef #620
  • 587 ViewResearch addition #623
  • How to submit a new intent #624
  • 589 intent proposal view interactions #625
  • 590 intent proposal start email #632
• Review new issues (10 mins)
  • Standardize recommended formats for 'primitive' Context fields #645
  • Standardize a context type representing a range of time: TimeRange #646
  • Standardize a context type representing a Currency #651
  • Standardize a context type representing a Valuation #652
• AOB & Adjourn (5mins)

Minutes

• Order context proposal (Issue 644):
  • Quite a simple first-draft effort at putting an order together.
  • Some discussion around this - FIX thought to be too "non-standard" (written in pencil)
  • FPML / Financial Objects: They mostly try to be exhaustive data types, whereas this is the minimal set of things that can be sent for another application to work. They are pushing around context data vs actual data.
  • Johan: this is about satisfying the customer, interop comes later.
  • We don't want to be the XKCD n+1 standards problem
  • Focus on Order, Trade, Instrument over the next couple of weeks
• Chat Intents
  • Discussion around startChat / viewChat: what are the verbs we are using?
  • Review of the PR
  • App field is the metadata for the platform.
  • Will move to typescript / jsonSchema as the standard progresses.

Action Items

• ...

[reenaraichura]

Reena Raichura / Glue42

[Julia-Ritter]

Julia / FINOS

[kriswest]

Kris / Cosaic

[Soul-Master]

Sumit / LSEG

[openfin-johans]

Johan / OpenFin 🎁

[rikoe]

Riko / Adaptive

[robmoffat]

Rob / FINOS

[WatsonCIQ]

Chris Watson / Cosaic

[bertrand-s]

Bertrand / Symphony

[pauldyson]

Paul / Singletrack

[jimbunting]

Jim / Cosaic

[timjenkel]

Tim / Wellington

[dominicgifford]

Dom / SPGI

[nemery-flextrade]

Nathan / FlexTrade

[jgavronsky]

Jane @ FINOS here

[Julia-Ritter]

Untracked attendees:

Matt Jamieson / White Dog
Yacine Zalouani / UBS
Mike McClung / Cosaic
William Stewart / FINBOURNE Technology

[kriswest]

@nemery-flextrade @pauldyson @dominicgifford @rikoe and others (including @rbruckheimer who raised the original proposals), just a reminder to take a look at the following issues and provide your views on them before we next meet:

• Standardize recommended formats for 'primitive' Context fields #645
• Standardize a context type representing a range of time: TimeRange #646
• Standardize a context type representing a Currency #651
• Standardize a context type representing a Valuation #652
• Standardize a context representing a Trade #655
• Improve the definition of the Position context type #656
• (and to a lesser extent) Standardize a context type representing a Chart #654

I'm sure some have a bearing on/overlap with @nemery-flextrade's :

• Context Proposal: Order #644

I'm happy to contribute to them/the relevant PRs, but would appreciate the definitions being refined by participants more closely involved in the use-cases than I.