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

Standard WG Meeting - March 23, 2023 #934

Closed
10 of 26 tasks
kriswest opened this issue Mar 20, 2023 · 14 comments
Closed
10 of 26 tasks

Standard WG Meeting - March 23, 2023 #934

kriswest opened this issue Mar 20, 2023 · 14 comments
Labels
indexed When a meeting attendance is being tracked meeting Standard WG Meeting

Comments

@kriswest
Copy link
Contributor

kriswest commented Mar 20, 2023 •
edited
Loading

Date

Thursday 23rd March 2023 - 10am EDT / 2pm GMT (Note daylight savings time in US but NOT UK)

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

Agenda

Minutes

  • A reminder was provided of the previously proposed timeline for FDC3 2.1:
    • Issues for inclusion should have already been raised
    • PRs should be raised by the April SWG meeting
    • Aiming for votes on inclusion to happen at the May SWG meeting
  • Work has begun on the accumulated action items from previous meetings
    • Any volunteers wishing to participate in implementation should contact the FDC3 maintainers - contribution of PRs is the best place to start the journey of becoming an FDC3 maintainer.
  • A reminder was provided that FINOS is recruiting SMEs and testers for the proposed FDC3 practitioner certification program - see: https://share.hsforms.com/1jgeYsjC-T7CYXq7bRQC6Iw1fux8
  • Question: customConfig vs hostManifests in v2 #900
    • @kriswest asked if any participants want to speak for or against the proposed change (to make customConfig accessible to applications) - however, no one present wished to.
      • Hence, @kriswest recommended that we return to the originally suggested change: deprecate and later remove customConfig from the appD record (as it inaccessible to apps through the FDC3 API and proprietary mechanisms should probably stick to working through hostManifests).
  • Proposal to add .NET interfaces and context declarations #931
    • @bingenito provided an overview of his approach to producing standardized interfaces for the FDC3 desktop agent API and standardized context types in .NET
    • The main library is based on hand-created, concrete types for context object, rather than JSON handling classes such as those provided by Newtonsoft's JSON.net or System.Text.Json
      • The primary library is mostly interfaces
      • a secondary library is provided with JSON helper functions that implement serialization/deserialization from classes implementing the interfaces - this separation ensures that the underlying JSON support can be implemented with whatever libraary/version is preferred.
    • @kriswest asked if @bingenito had encountered a use case for being able to swap the implementation of the desktop agent client out / dynamic loading of an implementation (as is possible with Javascript, enabling Write Once Run Anywhere [WORA])
      • Generally, no - most firms are using .Net apps internally rather than externally and hence on a specific desktop agent
        • The interfaces still have a lot of value without WORA - as does including them in the FDC3 standard
        • They provide a better pattern for implementation than interfaces based directly on JSON handling classes
        • Including them and maintaining them in the Standard will 'keep us honest' by forcing us to avoid or address early Typescript specific constructs, such as union types, that are difficult to replicate in other languages (a couple of union types already existing necessitate the use of marker interfaces in C# to achieve the same polymorphism)
    • a brief overview of the testing of the context types and serialization in the libraries (via validation of generated JSON via the published JSON schemas) was provided, e.g. https://github.com/morganstanley/fdc3-dotnet/blob/main/src/Tests/MorganStanley.Fdc3.Tests/Context/ChartTests.cs
    • @bingenito and @kriswest both recommended the inclusion of the interfaces in the main FDC3 project as they are not implementations (which would go into a separate software project) and they will be easier to test and maintain against the standard there.
    • @kriswest indicated that adding these to the Standard will require a fair amount of documentation work and project infrastructure work to publish a nuget package containing them - but also that this was a worthwhile endeavour
      • contribution of effort from firms that will benefit from these types will be sought.
    • @kriswest asked that the community begin review of packages provided and that we return to this topic at a future meeting to decide the issue
      • It was also indicated that this may not be at the next meeting which is likely to be focused on PRs for FDC3 2.1.
  • Apology from @kriswest for inadvertently skipping over the training topic in the meeting agenda 😱 😞

Action Items

Rolled over from previous meetings:

FDC3 2.1 TODO list

Untracked attendees

Full name Affiliation GitHub username
@bingenito
Copy link
Member

Brian Ingenito / Morgan Stanley

@mistryvinay
Copy link
Contributor

Vinay Mistry / Symphony 🎵

@openfin-johans
Copy link
Contributor

Johan Sandersson / OpenFin 🥨

@chuck-adaptive
Copy link

chuck-adaptive commented Mar 23, 2023 •
edited
Loading

Chuck Danielsson / Adaptive 🧙‍♂️

@kriswest
Copy link
Contributor Author

Kris West / Finsemble 🚀

@psmulovics
Copy link
Contributor

Peter Smulovics / Morgan Stanley

@novavi
Copy link

novavi commented Mar 23, 2023

Derek Novavi / S&P Global

@carmenmassbaum
Copy link

Carmen Massbaum - Wellington Management

@ColinEberhardt
Copy link
Contributor

Colin / Scott Logic 🐱

@robmoffat
Copy link
Member

Rob / FINOS 🤯

@hampshan
Copy link

hampshan commented