rikoe commented 2 years ago

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 17 Feb 2022 - 9am EST / 2pm GMT

WebEx info

Meeting Link Meeting number: 2556 495 5451

More ways to join

Join by video system:
- Dial 665568411@finos.webex.com
- 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: 665 568 411

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

[x] Convene & roll call, review meeting notices (5mins)
[x] Review action items from previous meeting (5mins)
[x] Discuss new issues (30 mins)
- [x] #574
- [x] #575
- [x] #586
- [x] #587
- [ ] #588
- [ ] #589
- [ ] #590
- [x] #591
- [x] #592
[x] Confirm action items for date ranges, charts, trades, valuations etc. #443 (10 mins)
[x] AOB & Adjourn (5mins)

Minutes

Previous meeting: Cosaic will split up chart PR into separate PRs for date range, charts and positions/orders/valuations. Charting will not include style and indicators for now, but will include separate settings area.
Initial discussion was of the proposed fdc3.ChatInit type and SendChatMessage intent. The group was generally in favour of these additions, and happy for it to proceed to PR and be proposed to the SWG.
There was some discussion around the ChatRoomRef return type, and the information contained therein, e.g. appName. @kriswest pointed out that it may fit better with the existing AppMetadata concept, which may need some API improvements to fully support this use case.
The RichTextBlock proposal for messages was also well received and could add significant value to more use cases than just chat for FDC3, especially in the absence of existing standards for concise rich text transfer via JSON. @bertrand-s was asked to expand the issue with examples of JSON payloads with rich text.
Everyone agreed that adding rich text support as an experimental feature to FDC3 would have the most value. Feedback from usage could then be incorporated into iterating on the idea and full standardisation.
The proposal for a ViewOrganization intent was well received, but there was consensus that a ViewProfile that applies to both Contact and Organization would be even better. In this case, ViewContact would be deprecated but not removed from the standard.
ViewResearch was equally well received and the group agreed to propose it for standardisation.
ViewOrders has more complexity and overlap of use cases and asset classes, so will stand over to the next meeting, along with undiscussed intent proposals from the agenda.

Action Items

[ ] @bertrand-s to raise a PR for #574 for further discussion and proposal to SWG
[ ] @bertrand-s to add rich text usage samples to #575
[x] @kriswest to add issue about an extension to the FDC3 API to support getting references for own app metadata
- 603
[ ] @pauldyson to raise a PR for ViewProfile intent, deprecate ViewContact
[ ] @pauldyson to raise a PR for ViewResearch intent