Context Data & Intents Discussion group - 4 May 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 4 May 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) #978
• Review action items from previous meeting (5mins)
  • Context Data & Intents Discussion group - 6 Apr 2023 #941
• Discussion of open issues (35mins)
  • Should we split context & intent out of the main FDC3 standard? #940
    • How-to separate the governance of Context/Intent types from the API
    • Process for updating NPM module as soon as changes are merged
    • Better definition on how-to customise or extend Context types
• Issues requiring a PR (5mins)
  • Actionable Notifications via Intent & Context #828
  • Tighter definition for "otherConfig" in fdc3.chart context type #856
  • Question: What use cases and Intents related to Orders, Trades and Positions are there? #904
• CD&I 2.1 consolidated PR (1mins)
  • [WIP] Context data and intents consolidated update branch 2.1 #936
• AOB & Adjourn (5mins)

Minutes

• Should we split context & intent out of the main FDC3 standard? #940
  • General consensus for need to release Context objects and Intents more frequently
    • Current process is holding back new additions, some of which have been waiting almost 10 months
    • Vendor feedback from the field if a capability is not within the standard, therefore I cant use FDC3
      • This is not true. You can create you own Intents and Context types whenever you like and start using them
      • But you don't fully achieve the goal of being able to Interop without prior bilateral agreements
      • If somebody has to define and a counter party in another firm have to agree, make a bilateral agreement on that type
    • Goal is put the types in a standard such that all parties use the standard and whats available
    • By changing the process and how we do governance on Context and Intents standards we can aim to release more frequently.
  • But how can we achieve this?
    • @robmoffat put forward a proposal #904 to use a repository style approach, where you create proposals and push them to a repository after they are agreed upon.
      • When a PR is approved a new NPM module would be created and made available immediately, its also visible on the FDC3 website
      • New additions could exist under a companies own namespacing, allowing for company specific types as well.
      • Unlike our current process, whereby if a PR is approved and even merged. It's still not available via an NPM module or visible on the FDC3 website
      • The SWG have asked us to bring batches of additions to adopt, because of how those meetings work essentially
        • It's considered inefficient for the standards working group, which is the only governance body at the moment to be doing this all the time.
      • @novavi also mentioned that splitting Context and Intents into a separate package makes complete sense.
      • Being able to iterate on additions faster is good.
      • Need to provide clear guidance on best practices for developing, describing and packaging new Contexts.
      • @kriswest next steps would be to come up with a plan and governance process, what would it be, what does it look like
        • Different governance processes for standard type and proprietary types submissions
        • Will this be governed by the SWG or is it practical to do it through the community at large to vote-in new additions
          • Alternatively appointed maintainers could help provide governance
        • Have a separate section on the website or a separate website altogether that embodies types like a repository
          • Each of these types has a version and change log
          • We can also open this up for private type submissions

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 in (Question: What use cases and Intents related to Orders, Trades and Positions are there? #904 )
• @mistryvinay work with maintainers to create draft proposal for governing Context and Intents

Untracked attendees

Full name	Affiliation	GitHub username

[milindchidrawar]

Milind Chidrawar / Singletrack

[novavi]

Derek Novavi / S&P Global

[mistryvinay]

Vinay Mistry / Symphony 🎵

[kriswest]

Kris West / Finsemble 🚀