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 - 12 May 2022 #703

Closed
11 of 29 tasks
mistryvinay opened this issue May 10, 2022 · 17 comments
Closed
11 of 29 tasks

Context Data & Intents Discussion group - 12 May 2022 #703

mistryvinay opened this issue May 10, 2022 · 17 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 10, 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 12 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

  • (Create Interaction) Intent Proposal: Create Interaction #592

    • @pauldyson This is ready to move to a PR, see comments from discussion and on the issue:
      • @hampshan Re: interactionType = "Meeting" is it worth having an a sub-type field (e.g. Meeting / In-person)
      • additionalContext[] is good idea
      • @robmoffat what about adding a URL for the interaction? E.g. link to the Chat
      • @hampshan Who initiated the interaction (did client reach out? or did we contact them)
      • Should timestamp be a TimeRange? Or just a TimeRange in the additionContext field.
      • won't make it into 2.0 unless raised soon and reviewed async

  • (Naming Conventions) 681 Update Intent Naming Conventions #701

    • Approved, ready to merge

  • (Primitive types) 645 Adding privitive field type conventions to context spec #704

    • Country
      • Change ISOALPHA2 to COUNTRY_ISOALPHA2 and update country type and other PRs to match
      • Couple of additional countries additional ones from ISDA, mention in types convention @nemery to provide reference

  • (TimeRange) Standardize a context type representing a range of time: TimeRange #646

    • startTime should be optional as well as there are valid use cases (when submitting an order)
      • oneOf startTime or endTime should be specified (if possible to express that in the schema)
      • clarify that times should be used to help with timezones, rather than dates - also handles inclusive/exclusive better
      • supports milliseconds - add examples, check parsing in javascript
      • otherwise good to merge

  • (Currency) Standardize a context type representing a Currency #651

    • @nemery Looked into FPML
      • Mostly ISO standard currency codes with a few additions.
      • No sign of crypto.
      • Happy with sticking to major currency units
    • @hampshan Might be worth looking at ISO 20022 https://phemex.com/academy/iso-for-crypto-iso-20022
    • type won't be used everywhere, only when it needs broadcasting on its own
    • Incremental update later could add support for ISO 20022

  • (Valuation) Standardize a context type representing a Valuation #652

    • @nemery has a clear use to encapsulate valuation data and help you add multiple valuations as fields on a different type
    • @dominicgifford add an optional valuationTime field (not a range) as you may want to plot these over time (tracking error, slippage etc.)
      @hampshan add expiryTime
    • use case return data for requesting a valuation, composition in other types
    • ISOCODE -> CURRENCY_ISOCODE

  • (Order) Context Proposal: Order #644

    • need to pay intention to side in the definition (gets confusing depending on which side you are on and it needs to work for both)
    • @nemery @dominicgifford worked on this issue/added a proposal - there a lot to discuss which we didn't have time to dig into
      • Keen to get this into 2.0 with an experimental label so that it can be imrpvoed rapidly in subsequent versions
      • Closely related to/overlapping with Trade - these should be dealt with together

Action items

Untracked attendees

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

As theres a few mins left in the agenda timings, I suggest we review the intent naming PR (if you've had a chance to merge suggestions @mistryvinay) and the primitive types PR, if I've had a chance to raise it by tomorrow (I intend to).

Other PRs we could review and add to the ready to be merged list:

@kriswest
Copy link
Contributor

kriswest commented May 11, 2022 •
edited
Loading

Primitive types PR is ready for review:

@kriswest
Copy link
Contributor

kriswest commented May 11, 2022 •
edited
Loading

Also could we confirm which of the following can be agreed - I'll turn each into a PR if teh format in the issue is agreed:

@rikoe
Copy link
Contributor

rikoe commented May 12, 2022 •
edited
Loading

Riko Eksteen / Adpative 😈

@kriswest
Copy link
Contributor

Kris West / Cosaic 🚀

@nemery-flextrade
Copy link

Nathan Emery / FlexTrade

@pierreneu
Copy link

Pierre Neu / Symphony

@robmoffat
Copy link
Member

Rob / FINOS

@Julia-Ritter
Copy link
Contributor

Julia / FINOS

@bertrand-s
Copy link
Contributor

Bertrand / Symphony

@timjenkel
Copy link

Tim / Wellington

@hampshan
Copy link

Andrew Hampshire / UBS

@katherinelachelin
Copy link

Katherine Lachelin / Iress

@dominicgifford
Copy link
Contributor

Dom / S&P Global

@dimiter-georgiev
Copy link

Dimiter / Symphony

@hughtroeger
Copy link
Contributor

Hugh / FactSet

This was referenced May 12, 2022
Merged
Merged
Merged
Merged
@kriswest kriswest added the Context Data & Intents Contexts & Intents Discussion Group label May 16, 2022
@mistryvinay mistryvinay mentioned this issue May 24, 2022
Closed
16 tasks
@github-actions github-actions bot added the indexed When a meeting attendance is being tracked label May 26, 2022
@Julia-Ritter
Copy link
Contributor

Untracked attendees:

  • William Shotton / RBC

  • Frederic / Tick42

  • Vinay / Symphony

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