Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Context Data & Intents Discussion group - 26 May 2022 #732

Closed
13 of 16 tasks
mistryvinay opened this issue May 24, 2022 · 12 comments
Closed
13 of 16 tasks

Context Data & Intents Discussion group - 26 May 2022 #732

mistryvinay opened this issue May 24, 2022 · 12 comments
Labels
Context Data & Intents Contexts & Intents Discussion Group help wanted Extra attention is needed indexed When a meeting attendance is being tracked meeting

Comments

@mistryvinay
Copy link
Contributor

mistryvinay commented May 24, 2022 •
edited
Loading

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:
image

Issues will also be tagged with the labels:
image
image

Meeting Date

Thursday 26 May 2022 - 9am EST / 2pm GMT

WebEx info

More ways to join

  • Join by video system:
  • 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

Minutes

  • Issues Discussed

    • (CreateInteraction) Intent Proposal: Create Interaction #592
      • @pauldyson provided an overview of the proposal - which is ntended to simplify creation of interaction records in a CRM
      • Hard to standardize all values for interationType, but should suggest values
      • @hampshan would like to see
        • an optional duration/timerange field, distinct from timestamp
        • initiator of the interaction
      • @kriswest
        • could you have an (optional) interaction with organisation(s) rather than contacts? Useful in a return type
        • interactionType optional and desciption is required, which seemed odd to me
          • @pauldyson you can often determine type from source system - however thats not always available
            • make interactionType required
      • Add a source/venue/subtype field to record additional info on the interactionType
    • (Improve Instrument) Improve the definition of Instrument context type - add MIC #707
      • generally agreed on adding market field with MIC subfield
      • to be discussed again at a future meeting

  • Review proposal for standardised Intents

    • (Order) Context Proposal: Order #644
      • Consider adding a PriceType field (absolute/percentage/yield etc.)
      • @hampshan to review proposal with UBS people familiar with all order types - particularly regarding types of pricing
      • Not going to include in 2.0 but hopefully can go into the predraft of next version ASAP (which gets it online for review)
      • @dimiter It'd be helpful for us to see the standard worked out also usable for backend systems to help us connect backand frontend - feedback we get from users of bots (usually built by sellside), however each uses a different model due to lack of standard.
      • @robmoffat Can we socialize this proposal with the FO SIG which provides another venue for this type of modelling
      • @dimiter @hampshan @nemery expressed some interest
      • @nemery to continue with PR and raise as WIP for review
    • (Trade) Standardize a context representing a Trade #655
      • Not currently linked to order changes - but the quantity type will be based on the same structure - candidate for a new field convention
      • @nemery to move forward (possibly in same PR as order)
    • (Position) Improve the definition of the Position context type #656
      • Heavily dependent on an array of trades and should be handled in same PR

  • List of additions that are ready to be included into the 2.0 standard (5mins)

  • FINOS - Open Finance Forum London

Action items

Untracked attendees

Full name Affiliation GitHub username
@mistryvinay mistryvinay added help wanted Extra attention is needed meeting labels May 24, 2022
@pauldyson
Copy link
Contributor

Paul / Singletrack

@milindchidrawar
Copy link
Contributor

Milind Chidrawar / Singletrack

@mistryvinay
Copy link
Contributor Author

Vinay / Symphony

@Julia-Ritter
Copy link
Contributor

Julia / FINOS

@hampshan
Copy link

Andrew Hampshire @ UBS

@nemery-flextrade
Copy link

Nathan / FlexTrade

@dimiter-georgiev
Copy link

Dimiter / Symphony

@kriswest
Copy link
Contributor

Kris West / Cosaic

@timjenkel
Copy link

Tim / Wellington
I will be dropping off at 9:30

@robmoffat
Copy link
Member

Rob / FINOS

@jgavronsky
Copy link

Jane @ FINOS here

@hughtroeger
Copy link
Contributor

Hugh Troeger / FactSet

@mistryvinay mistryvinay mentioned this issue Jun 7, 2022
Closed
14 tasks
@mistryvinay mistryvinay added the Context Data & Intents Contexts & Intents Discussion Group label Jun 7, 2022
@github-actions github-actions bot added the indexed When a meeting attendance is being tracked label Jun 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Context Data & Intents Contexts & Intents Discussion Group help wanted Extra attention is needed indexed When a meeting attendance is being tracked meeting
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests