Standard WG Meeting - May 25th, 2023

[kriswest]

Date

Thursday 25 May 2023 - 10am EST / 3pm BST

WebEx info

• Meeting Link
  Meeting number: 665 568 411

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.

Agenda

• Convene & roll call, review meeting notices (5mins)
• Review action items from the previous meeting (5mins)
  • Standard WG Meeting - April 27, 2023 #970
• Announcements (10mins)
  • FINOS Open House and Members meeting schedules: https://finosopenhouseandmembermeet.sched.com/
  • Context Data & Intents meeting: Thursday 8th June 9am EST / 2pm BST
    • Rethinking the governance & processes
  • Voting on the inclusion of Desktop Agent Bridging in FDC3
    • 544 Desktop Agent Bridging #968
  • FDC3 Workbench updated for 2.0
    • fdc3 2.0 workbench update #947
  • Other PRs recently merged:
    • 871 clarify channels behaviour and fix a markdown issue in API spec #971
    • 827 Adding appD error route examples #973
    • BMO In Community Page #975
    • fixing broken links and outdated content in getting started pages/readme #983
    • Add a body background color declaration to website light theme #986
• Check consensus on PRs ready to be merged into 2.1 predraft (15 mins):
  • 872 Clarify malformed context handling #972 (ready to merge)
  • 980 Correcting appd interop.appChannels to use id instead of name #981 (needs editor review)
  • Add deprecation tags to customConfig entries in appD schema #982 (needs editor review)
  • updating definition of otherConfig in fdc3.chart to use an array of context objects #985 (needs editor review, to merge into Consolidated PR for Context Data & Intents (CD&I) updates for 2.1 #994)
  • 866 app add listener timeouts #987 (needs maintainer & editor review)
  • Consolidated PR for Context Data & Intents (CD&I) updates for 2.1 #994 (awaiting final additions)
  • appD pom files included in npm package are lacking license #996
    • Remove source files from NPM module #999 (ready to merge)
    • Remove old app directory files #1000 🎉 (ready to merge)
  • Clarify intended behavior on void intent results #1004 (ready to merge)
• Multiple Language Bindings #990 (15 mins)
  • .NET issue Proposal to add .NET interfaces and context declarations #931
• Discuss other issues still outstanding for 2.1 (5 mins)
  • PRs needed:
  • Anything from the 2.1-candidates milestone that should be included?
• AOB & Adjourn (5mins)

Minutes

• PRs ready to be merged into 2.1 predraft:
  • Consent received to merge:
    • 872 Clarify malformed context handling #972 (ready to merge)
    • Remove source files from NPM module #999 (ready to merge)
    • Remove old app directory files #1000 (ready to merge)
    • Clarify intended behavior on void intent results #1004 (ready to merge)
  • Consent received to merge after reviews completed:
    • 980 Correcting appd interop.appChannels to use id instead of name #981 (needs editor review)
    • updating definition of otherConfig in fdc3.chart to use an array of context objects #985 (needs editor review, to merge into Consolidated PR for Context Data & Intents (CD&I) updates for 2.1 #994)
  • Objections to merging raised:
    • Add deprecation tags to customConfig entries in appD schema #982 (needs editor review)
      • Several participants (@robmoffat @lspiro-Tick42 A participant from Citi) spoke up for a use-case for vendor-agnostic configuration intended for an app (rather than a Desktop Agent, as is the case with hostManifests).
      • It was suggested that:
        • An API addition would be needed to retrieve the config in a vendor agnostic way
        • A better name could be applied to the element to clarify its intended use (e.g. applicationConfig)
        • A new issue could/should be raised to supercede the deprecation issue (Question: customConfig vs hostManifests in v2 #900)
  • Not checked
    • 866 app add listener timeouts #987 (needs maintainer & editor review)
      • to be checked after re-reviewed by maintainers - significant changes on the day of the meeting.
    • Consolidated PR for Context Data & Intents (CD&I) updates for 2.1 #994 (awaiting final additions)
• @kriswest gave a brief overview of PRs needed: and invited contribution from the community on the,.
  • Meeting participants were also asked to review the 2.1-candidates milestone and comment on anything that they thought should be included?
• Multiple Language Bindings #990
  • @robmoffat introduced the issue and highlighted recent work on .NET (@bingenito), Java (@timjenkel) and Python (@chuck-adaptive) bindings produced for FDC3
    • @psmulovics indicated a willingness to migrate the .NET contribution to a FINOS repo
  • There was general consensus that other language bindings for FDC3 should exist
    • @rikoe remarked that it would be useful if FDC3 could be described in a language agnostic way with something like JSONSchema (although that, unfortunately, does not support function signatures) and that adding other languages will increase the maintenance burden for FDC
  • There was discussion of where language bindings should go
    • @kriswest Language bindings != implementations, which should always be outside of FDC3
    • @kriswest You'd likely want Nuget/Maven/whatever python uses packages for the interfaces or types supporting each binding
      • The FDC3 maintainer team should be/may need to be expanded to help keep these up-to-date
      • Firms wishing to contribute or adopt standardized bindings for particular languages should consider putting someone forward to maintain them if possible.
    • @rikoe We could move the Typescript sources out of the main FDC3 repo while doing this, it would make sense for each language to have its own repo.
      • @kriswest although it would be useful to keep documentation together in one place for maintenance purposes
      • @kriswest reminded the group about @bingenito's past comment that bringing in and maintaining other language bindings would help 'keep us honest' by avoiding typescript specific constructs that are hard to replicate in other languages (e.g. union types in function signatures)
  • The end of the meeting curtailed discussion, which should continue at the next meeting

Action Items

• Maintainers and Editor to complete outstanding reviews
• @kriswest merge approved PRs (when necessary reviews are competed)
• @kriswest raise a new issue for replacing customConfig/making it retrievable via API/renaming it.
• @kriswest add 866 app add listener timeouts #987 to next meeting agenda
• @kriswest add Multiple Language Bindings #990 to next/a future meeting agenda

Rolled over from previous meetings:

• @kriswest Open an email vote on the inclusion of Desktop Agent Bridging as part of the FDC3 Standard
• Proposal to add .NET interfaces and context declarations #931
  • Review of the proposed .NET interfaces by firms that will benefit from them is needed - along with a commitment to help with the update of the FDC3 documentation to include them.
• @kriswest Refer questions about the need for more 'authentication' in FDC3 to FDC3 for Web Browsers group
  • referred but not yet discussed
• @kriswest @nkolba @pierreneu to work on proposals/PRs demonstrating possible solutions to Question: App-specific context metadata #829. These should include example use-cases demonstrating the need for and utility of the revision
• @finos/fdc3-maintainers to investigate adding code coverage scanning to repo and to propose a unit testing policy/raise a PR to add to governance and resolve Unit Test Policy #832.
• @kriswest or volunteer: raise PR to resolve Add /intents and /contexts endpoints to the AppD API #719
  • Add optional/recommended API endpoints for /intents and /contexts to the appD API.

Untracked attendees

Full name	Affiliation	GitHub username

[novavi]

Derek Novavi / S&P Global

[robmoffat]

Rob / FINOS 🐈‍⬛

[mistryvinay]

Vinay Mistry / Symphony 🎵

[mattjamieson]

Matt / WhiteDog

[psmulovics]

Peter Smulovics / Morgan Stanley 🏦

[openfin-johans]

Johan / OpenFin 🎁

[kriswest]

Kris West / Finsemble 🚀

[tpina]

Tiago Pina / Finsemble

[rikoe]

Riko Eksteen / Adaptive

[WatsonCIQ]

Chris Watson / Finsemble 👋