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 - 3rd March 2022 #612

Closed
15 of 18 tasks
kriswest opened this issue Mar 2, 2022 · 14 comments
Closed
15 of 18 tasks

Context Data & Intents Discussion group - 3rd March 2022 #612

kriswest opened this issue Mar 2, 2022 · 14 comments
Labels
Context Data & Intents Contexts & Intents Discussion Group help wanted Extra attention is needed meeting

Comments

@kriswest
Copy link
Contributor

kriswest commented Mar 2, 2022 •
edited by rikoe
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 03 March 2022 - 9am EST / 2pm GMT

WebEx info

  • Meeting Link
    Meeting number: 2555 803 6153
    Password: 5mqDb2CM2ZF)

More ways to join

  • Join by video system:
  • Join by phone
    • +1-415-655-0003 US Toll
    • +44-20319-88141 UK Toll
  • Access code: 2555 803 6153

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

  • Discuss/reaffirm why we are proposing standardized intents
    • Why is it helpful to add the intent names to the standard?
      • Groups the same action from multiple apps under same intent for findIntent/raiseIntent
      • Can program directly to the named intent (add a ViewChart button etc.)
      • If we don't standardize names we promote fragmentation (viewChat, viewCharting, visualize etc.)
    • Its not a good use of time for working group to consider lots of individual proposals for intent names (as we did for ViewHoldings)
      • Decision: Aim to raise a single batch of considered issues and associated PRs for inclusion in FDC3 2.0 (including any breaking changes)
  • Intent Proposal: ViewInteractions #589
    • When working with a client it's helpful to be able to view your interactions with the client or firm
      • E.g. Research is a primary interaction that is tracked by firms against individuals and clients,
    • Some further discussion of naming or purpose (should it be plural, or include 'history')
      • Might include upcoming interactions - so not just history (to be clarified in the description)
      • Use case is always multiple interactions, NOT retrieving a single interaction
      • Decision: rename ViewInteractions
    • Future discussion: naming conventions for intents that retrieve data vs. those that trigger a UI (e.g. GetInteractions vs. ViewInteractions)
    • Approved by group, @pauldyson to raise PR
  • Intent Proposal: StartEmail #590
    • Clarify that CRM systems often start off emails (rather than Outlook) - usually retrieving something via the CRM to send to the recipient (e.g. selecting research, which then gets logged by CRM) and tracking the email
    • Likely to want to specify more about the email e.g. set title, body, template, content to attach?
      • Use case for RichText data
      • additional fields should be optional
      • Use mailto: link spec and options as inspiration
      • Will require a context defining an email context as an alternative to Contact or ContactList (should support them all)
    • Action: Clarify description, add email context type to proposal, add fdc3.nothing as a context option (bring up blank email)
    • discuss again next meeting
  • Intent Proposal: Create or Update Profile #591
    • Easy to understand
    • Action: rename CreateOrUpdateContact, add fdc3.nothing as a context option (bring up blank form), add detail about returning data (Contact context with updated data).
    • No objections to this moving to a PR as well
  • Intent Proposal: Create Interaction #592
    • Defer to next meeting
    • Define some interaction types
  • StartChat and SendChatMessage #574
    • discuss next meeting
    • Updates to proposal pending
  • RichTextBlock data type #575
    • Briefly discussed templating messages
    • Updates to proposal pending
    • Still recommended for an @experimental flag
  • Action: Start up discussion on coming up with a intent naming / standard verbs

Action Items

Untracked attendees

Full name Affiliation GitHub username

https://finos.webex.com/finos/j.php?MTID=m57c360c6c75eabef623127be2973d856
Meeting number: 2555 803 6153
Password: 5mqDb2CM2ZF
@kriswest kriswest added help wanted Extra attention is needed meeting Context Data & Intents Contexts & Intents Discussion Group labels Mar 2, 2022
@Julia-Ritter
Copy link
Contributor

Julia / FINOS

@nemery-flextrade
Copy link

Nathan / Flex

@pauldyson
Copy link
Contributor

Paul / Singletrack

@kriswest
Copy link
Contributor Author

kriswest commented Mar 3, 2022

Kris / Cosaic

@pierreneu
Copy link

Pierre Neu / Symphony

@agitana
Copy link
Member

agitana commented Mar 3, 2022

Aitana Myohl / FINOS

@hampshan
Copy link

hampshan commented Mar 3, 2022

Andrew Hampshire / UBS

@lspiro-Tick42
Copy link

Leslie / Glue42

@Soul-Master
Copy link

Sumit / LSEG

@dominicgifford
Copy link
Contributor

Dom / S&P Global

@hughtroeger
Copy link
Contributor

Hugh Troeger / FactSet

@jgavronsky
Copy link

Jane @ FINOS here

@bertrand-s
Copy link
Contributor

Bertrand / Symphony

@Julia-Ritter
Copy link
Contributor

Untracked attendees:

  • Sarah Stone/ Cosaic
  • Nico Pretorius / Scott Logic
  • Yacine Zalouani / UBS
  • Dimiter Georgiev / Symphony
  • Matt Jamieson / White Dog
  • Vinay Mistry / Symphony

@rikoe rikoe mentioned this issue Mar 16, 2022
Closed
12 tasks
@rikoe rikoe closed this as completed Mar 16, 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 meeting
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests