Context Data & Intents Discussion group - 28 April 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 28 Apr 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. 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 Context Data & Intents Discussion group - 31 March 2022 #643 (5mins)
• Discuss issues (35mins)
  • Recommended format for ‘primitive’ Context Fields Standardize recommended formats for 'primitive' Context fields #645
  • Intent naming guidelines Intent naming conventions #681
  • Start Email 590 intent proposal start email #632 (needs review)
  • Context Proposals for (Requires PRs to be raised)
    • Standardize a context type representing a Currency #651
    • Standardize a context type representing a Valuation #652
    • Standardize a context type representing a Chart #654
    • Standardize a context representing a Trade #655
    • Improve the definition of the Position context type #656
    • Context Proposal: Order #644
• PRs that are ready to be merged (5mins)
  • List of additions that are ready to be included into the 2.0 standard
    • View Profile 600 ViewProfile addition and ViewContact deprecation #619
    • View Interactions 589 intent proposal view interactions #625
    • Start Chat 574 StartChat: ChatInitSettings and ChatRoomRef #620
    • View Research 587 ViewResearch addition #623
• AOB & Adjourn (5mins)

Minutes

• Standardize recommended formats for 'primitive' Context fields #645
  • Recommended format for primitive context fields.
  • Next Steps raise PR
• Intent naming conventions #681
  • Need a volunteer to raise the PR?
  • Working group volunteer can comment an issue.
• 590 intent proposal start email #632
  • PR needs to be reviewed and approved by an FDC3 maintainer.
• Standardize a context type representing a Currency #651
  • Proposal on sub-unit codes for currencies, also crypto @nemery-flextrade
  • Agreement not to over-complicate this but rather refer to existing standards
  • Investigate FPML currency code - ISO code + bunch of other stuff, will comment on issue @mattjamieson
  • China have separate on-shore and off-shore representations @timjenkel
  • Can include in FDC3 2.0 standards providing we agree on a format
  • Include this topic in the next meeting agenda
• Standardize a context type representing a Valuation #652
  • Change currency ISOCODE to currency code
  • Primitive context fields PR define what currency code looks like - name + accepted values
  • Currency type on its own could still be valuable but can be simple currency code wrapped in type
  • Is a component of a trade, position or order type
  • Someone needed to take ownership of valuation, trade, position, order (with financial knowledge)
  • Revisit valuation after trade
• Standardize a context representing a Trade #655
  • Maybe come back to it after 2.0
  • Should we add this as experimental?
  • Needs proper attention, e.g. side etc.
  • Trade is an order that has been completed. Its past tense.
  • Use language to be clear, especially around direction
  • Anyone take on development of this proposal? Nathan can help out. Execution side of things important.
  • Also look at other standards - this is the key. Deciding where we draw the line. “Just enough”. Supposed to reference external standards where we can.
  • @dominicgifford will help @nemery-flextrade on this (+valuation, order)
• Improve the definition of the Position context type #656
  • How should lifetime be represented? Settled on time range type
• Context Proposal: Order #644
  • How should lifetime be represented? Settled on time range type
  • Should we pull @tim’s side proposal upwards into primitive types?
  • Side as enum does not apply to position where holding determines it
  • Holding should be renamed?

Action Items

• 590 intent proposal start email #632
  • @finos/fdc3-maintainers FDC3 maintainers to review and approve PR
• Intent naming conventions #681
  • all Require a volunteer to raise the PR for this.
• Standardize a context type representing a Currency #651
  • @nemery-flextrade Proposal on sub-unit codes for currencies, also crypto
  • @mattjamieson Investigate FPML currency code - ISO code + bunch of other stuff, will comment on issue
• Standardize a context type representing a Valuation #652
  • @nemery-flextrade & @dominicgifford Develop this proposal leveraging subject matter experts
• Standardize a context representing a Trade #655
  • @nemery-flextrade & @dominicgifford Develop this proposal leveraging subject matter experts
• Standardize a context representing a Trade #655
  • @nemery-flextrade & @dominicgifford Develop this proposal leveraging subject matter experts

[Julia-Ritter]

Julia / FINOS

[nemery-flextrade]

Nathan / FlexTrade

[mistryvinay]

Vinay / Symphony

[timjenkel]

Tim / Wellington

[nkolba]

Nick / Kolbito

[dimiter-georgiev]

Dimiter / Symphony

[openfin-johans]

Johan / OpenFin 🎁

[bertrand-s]

Bertrand / Symphony

[WatsonCIQ]

Chris Watson / Cosaic

[rikoe]

Riko Eksteen / Adaptive

[dominicgifford]

Dom / SPGI

[Julia-Ritter]

Untracked attendees:

Matt Jamieson / White dog
Terry Thorsen / Cosiac
Ben Gold / Wellington
Kris West / Cosiac
James McLeod / FINOS
William Shotton / RBC
Nick Kolba