Context Data & Intents Discussion group - 6 Apr 2023

[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 6 Apr 2023 - 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 - 2 Mar 2023 #916
• Discussion of open issues (30mins)
  • Question: What use cases and Intents related to Orders, Trades and Positions are there? #904
  • Should we split context & intent out of the main FDC3 standard? #940
• Issues requiring a PR (10mins)
  • Actionable Notifications via Intent & Context #828
  • Tighter definition for "otherConfig" in fdc3.chart context type #856
• CD&I 2.1 consolidated PR (3mins)
  • [WIP] Context data and intents consolidated update branch 2.1 #936
• AOB & Adjourn (5mins)

Minutes

• Question: What use cases and Intents related to Orders, Trades and Positions are there? #904
  • Simplified approach for defining Orders, Trade and Positions.
  • New proposed objects can be found here, Context Data & Intents Discussion group - 2 Mar 2023 #916
  • Working with @nemery-flextrade for a PR submission
• Should we split context & intent out of the main FDC3 standard? #940
  • Maintainers team broadly supportive for an easier and quicker way of adding Intents and Context more frequently.
  • For each and every Context and Intent that is defined and created. A PR is submitted back to the main standard.
  • Standard is only released periodically when we have a major milestone release like 2.0
  • Previous proposal of merging new additions by rolling the version number for a separate NPM module.
  • Still need to be conscious of the governance process around new submissions and voting into the Standard.
    • Since all parts of FDC3 were merged we only really do that once a year.
  • Or do we create a separate NPM module to handle additions.
    • Essentially whats on the FDC3/Overview pages defining Contexts and Intents as concepts stays in the Standard.
    • The actual specific types of Context and the specific Intent names do not really matter much versus the API versions.
      • You can make up any Intent or Context and you can use it with a version of the FDC3 API.
      • There's only a very light-tight restriction on Context. It must have a type and it should have an Id field and name field if there's a display name or an any Id's involved.
      • Beyond that different versions of FDC3 do not need to know where the Intent and Contents came from
    • Would be nice to be able to move to a rolling basis where we release more frequently, say, every quarter.
    • That would involve separating the governance of these a little bit from the main FDC3 Standard, which contains the API's
      • No need for a separate project or repository but rather a separate NPM module.
        • With the ability to vote on new additions which would be released in batches more frequently (every few months)
        • Also slight changes to website to separate out the specific lists of Intents and Context into a different area of the site thats not hooked to the Standards versions in the same way.
    • Proposal: Create a website or section of the website that is a Catalog of object definitions
      • Community can add PR's for new additions in to the catalogue
      • We can all see their definitions and a separate NPM module that contains types for them all.
      • Then publish incremental updates using semantic versioning e.g. v.1.0.0
      • This would be different from the current Standards version numbering.
      • Anything that is trying to change Intents and Context types as concepts would have to go back up to the FDC3 Standards working group.
      • Standardising types could be governed separately
• Tighter definition for "otherConfig" in fdc3.chart context type #856
  • @dominicgifford do we want to overload the context object with object data
    • But rather with vendor specific payloads within them
    • Need to use standardised types so any chart provider can be used in workflows
    • @robmoffat proposal to make 'otherConfig' an array of context objects.
      • Encouraging use of standardised types and the establishment of areas for proprietary extensions within them.
      • If we've got a standardised type, you'll understand the top level of the object and a variable bits might be. And if those variable bits are typed, you can check them.
    • @kriswest prefers the standardisation of types
      • Place proprietary content within them using a patter like chart.otherConfig
      • Encouraging people to standardise and use published types.

Action Items

• Volunteers for creating a PR for Clarify handling of malformed context objects by Desktop Agents #872
• @kriswest request to raise a PR for Actionable Notifications via Intent & Context #828
• @kriswest to reach out to ChartIQ team for a PR for Tighter definition for "otherConfig" in fdc3.chart context type #856
• @nemery-flextrade Create branch for new PR's relating to new Context types described above (Question: What use cases and Intents related to Orders, Trades and Positions are there? #904 )

Untracked attendees

Full name	Affiliation	GitHub username

[mistryvinay]

Vinay Mistry / Symphony 🎵

[robmoffat]

Rob / FINOS 🐈

[jimbunting]

Jim / Finsemble

[Julia-Ritter]

Julia / FINOS

[dominicgifford]

Dom / S&P

[kriswest]

Kris West / Finsemble 🚀