Context Data & Intents Discussion Group, 3 Feb 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 3 Feb 2022 - 9am EST / 2pm GMT

WebEx info

• Meeting Link
  Meeting number: 2556 495 5451

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 minutes and action items from Context Data & Intents Discussion Group, 13 Jan 2022 #538 (5mins)
• Discussion: data series for blotters and charts, and related use cases (20 mins)
  • Review Define more context types used to visualize (or otherwise represent) financial data #442
• New issues related to chat messages submitted (15 mins)
  • StartChat and SendChatMessage #574
  • RichTextBlock data type #575
• AOB & Adjourn (5mins)

Minutes

• Date range type
  • Having a date range type to use in other complex types is necessary, this should be proposed for adding to the standard.
  • Attendants prefer the simpler type suggested, i.e.

    type: "fdc3.dateRange",
    starttime: "2020-09-01T08:00:00.000Z",
    endtime: "2020-10-31T08:00:00.000Z"
  }
  

  • If using JSON schema, the built-in support for ISO date and time format could be utilised (https://json-schema.org/understanding-json-schema/reference/string.html#dates-and-times)
• Indicator type
  • Use cases for applications sending indicators as part of charts was not 100% clear, more examples of type of workflow will help to illustrate
  • Indicator types need further work to not use abbreviations that may be obtuse (e.g. "ma" for "moving average"), it is better to be explicit
• Trade, Valuation, Position
  • Is the valuation type proposed with a single price, value and currency applicable to a wide range of financial products, e.g. if it is a complex derivative?
  • Does the suggested trade type meet most people's requirements? Further investigation is needed.
  • Is including trades in positions useful, or will a holding with just instrument and amount suffice for most use cases? What are the source and target applications in this case?
• Chart
  • A chart type would be useful for multiple use cases.
  • It is not entirely clear how a target application would understand the style attribute, or would allowable options would be (e.g. enum vs free text)

Action Items

• DateRange can be split out in a separate type PR for adding to the standard, as there is consensus around this type
• Extensions for trades, valuations and positions should be considered separately from charts, as they are mutually exclusive
• If indicators and style parts of chart can be cleared up, it can be proposed for adding to FDC3

[ggeorgievx]

Present ✅

[Julia-Ritter]

Julia / FINOS

[kriswest]

Kris / Cosaic

[rich-fts]

Rich Taylor / FinTech Studios

[reenaraichura]

Reena Raichura / Glue42

[rbruckheimer]

Rob Bruckheimer / Cosaic

[rikoe]

Riko / Adaptive

[timjenkel]

Tim / Wellington

[pierreneu]

Pierre Neu / Symphony

[tpina]

Tiago / Cosaic

[bertrand-s]

Bertrand / Symphony

[sarahaislinnstone]

Sarah Stone / Cosaic

[hughtroeger]

Hugh Troeger / FactSet

[agitana]

Aitana Myohl / FINOS

[jgavronsky]

Jane @ FINOS here

[lspiro-Tick42]

Leslie / Glue42

[dominicgifford]

Dom / IHS Markit