Context Data & Intents Discussion group - 8 Jun 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 8 June 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 [email protected]
  • 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 [email protected] 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 - 4 May 2023 #977
• Discussion of open issues (35mins)
  • Should we split context & intent out of the main FDC3 standard? #940
    • Continuation discussion from last month
    • How-to separate the governance of Context/Intent types from the API
    • Google Doc tracking proposal
• 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 (1min)
  • Consolidated PR for Context Data & Intents (CD&I) updates for 2.1 #994
• AOB & Adjourn (5mins)

Minutes

• Should we split context & intent out of the main FDC3 standard? #940
  • Workgroup started to draft proposal for Governance of Context and Intents Types, being tracked in this Google Doc
  • Need a quicker way to govern and release kind of context and intents, but not change the existing governance in place for the API itself.
  • Design Goal / Objectives
    • Have two Docusaurus sites.
      • Main site: Contains the Standard and Intents and Context.
      • Second Site: Host catalog of Context and Intents
    • Both sites can be versioned independently
    • Governance workflow process whereby maintainers / community can vote in new additions
      • Note: Governance would not be required for proprietary formats
    • Support proposal for new Types by just raising an issue. Reduce burden of raising a PR.
    • Use Schema Store as inspiration to catalog all Types example here
      • We include Type details for:
        • name: Name for Type
        • description: Summary or description
        • fdc3-context: List of supported context types
        • url: Link to the JSON schema definition
    • Automation: Once we simplify how schema definitions are listed in a catalog we need to focus on how to automate creation of these catalog entries.

Action Items

• @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 proposal for governing Context and Intents

Untracked attendees

Full name	Affiliation	GitHub username

[mistryvinay]

Vinay Mistry / Symphony 🎵

[kriswest]

Kris West / Interop.io 🚀

[robmoffat]

Rob / FINOS 🥪