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 - 1 Sep 2022 #809

Closed
14 of 15 tasks
mistryvinay opened this issue Aug 30, 2022 · 12 comments
Closed
14 of 15 tasks

Context Data & Intents Discussion group - 1 Sep 2022 #809

mistryvinay opened this issue Aug 30, 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 Aug 30, 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 1 Sep 2022 - 9am EST / 2pm BST

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.

Agenda

Minutes

  • 592 intent proposal create interaction #747
    • @pauldyson indicated that such additional information is often not recorded, but he'll consider the need for it.
    • Additive changes could be made in a later PR
  • 592 771 context proposal TransactionResult #761
    • Add recommendation to use this context type for all CRUD operation intents in Intent specification
    • merge updates from 2.0 release
    • Update CHANGELOG.md with entries for this PR
    • @kriswest to send PR into @milindchidrawar PR with revised Overview
  • 766 evolution of chat message data structure #779
    • Consolidate chat PR's together ('ChatRoom' and 'SendChatMessage' #765 'View Messages' intent #768 766 evolution of chat message data structure #779)
      • Dependencies between these PR's are making review more difficult. Use cases for all are accepted by the group so consolidation of the PR will simplify review by SWG.
    • Currently the proposal is quite specific for chat messages but the fdc3.message type proposed could be used, for example, by the fdc3.email type.
    • Description of fdc3.message needs to cover all use-cases
    • entities element uses string IDs, but doesn't demonstrate how they might be used in the message text and should be updated to do so.
    • Can message container contain HTML?
      • yes, in the text element under the appropriate mime-type.
      • however plain text should always be provided as a fallback
        • This is not currently outlined in the docs or schema - the text['text/plain'] property could/should be required in the schema and described in docs if that's what is intended
    • No formal spec or example for representing markdown.
    • @hampshan asked if there was a MIME type for markdown?
      • Yes there are two, but not individual ones for different markdown flavours. If this were to be used the Standard should recommend or require a particular flavour.
    • @kriswest: please link to any external standard/references for MIME types (both in the context type and references page)
  • 765 'ChatRoom' & 'ChatMessage' contexts and 'SendChatMessage' Intent #794
    • Deal with review comments and suggestions.
    • Consider expanding the description of StartChat to include more details on use-cases for starting a chat from a different application (e.g. a research app or OMS)
  • 767 Add ViewChat Intent #796
  • 768 Add ViewMessages Intent & SearchCriteria Context #797
    • Is this a general search criteria, or a specific search criteria for chat? The context specifically limits the criteria and query construction that can be used in a search...
      • Option 1: Make this more flexible to support all search purposes
        • We don't want to define a query for all use-cases at the moment, it would be too large an undertaking
      • Option 2: Refactor it to be chat specific, with a rename to fdc3.chat.searchcriteria
    • Further options for supporting more complex search criteria were discussed
      • E.g. use a Google type search
        • All search clauses are combined with OR
        • Then ranked results are returned based on those OR search criteria values
        • Ranked in order of filter word occurrences
      • Empty search criteria could supported to allow reset of filters (which is a common issue in FDC3 for filters based on context broadcasts)
      • Rename contexts array to criteria to acknowledge that it may contain strings, not just contexts

Action Items

Rolled over from previous meetings

Untracked attendees

Full name Affiliation GitHub username
@mistryvinay mistryvinay added help wanted Extra attention is needed meeting Context Data & Intents Contexts & Intents Discussion Group labels Aug 30, 2022
@mistryvinay
Copy link
Contributor Author

Vinay Mistry / Symphony

@Julia-Ritter
Copy link
Contributor

Julia / FINOS

@robmoffat
Copy link
Member

Rob / FINOS

@kriswest
Copy link
Contributor

kriswest commented Sep 1, 2022

Kris / Cosaic

@Yannick-Malins
Copy link
Contributor

Yannick / Symphony

@symphony-jean-michael
Copy link
Contributor

symphony-jean-michael commented Sep 1, 2022 •
edited
Loading

Jean-Michael Legait / Symphony

@hampshan
Copy link

hampshan commented Sep 1, 2022

Andrew Hampshire / UBS

@dominicgifford
Copy link
Contributor

Dom / SPGI

@pauldyson
Copy link
Contributor

Paul / Singletrack

@pgn-vole
Copy link

pgn-vole commented Sep 1, 2022 •
edited
Loading

Yacine Zalouani / UBS

@hughtroeger
Copy link
Contributor

Hugh Troeger / FactSet

@Julia-Ritter
Copy link
Contributor

Untracked attendees:

  • Tim Jenkel / Wellington
  • Jim Bunting / Cosaic
  • Anant / Wellington

@mistryvinay mistryvinay mentioned this issue Oct 4, 2022
Closed
14 tasks
@github-actions github-actions bot added the indexed When a meeting attendance is being tracked label Oct 7, 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