Standard WG Meeting - Sept 28th, 2023

[kriswest]

Date

Thursday 28 Sept 2023 - 10am (US eastern timezone EDT/EST) / 3pm (London, GMT/BST)

Zoom info

• Join Zoom Meeting
• Meeting ID: 969 4029 4948
• Passcode: 636931
• Dial-in:

  Country	International Dial-in	Toll-free Dial-in
  US	+1 929 205 6099 (New York)	877 853 5247
  UK	+44 330 088 5830	0800 031 5717
  France	+33 1 8699 5831	0 800 940 415
  Find your local number	https://zoom.us/u/ad2WVnBzb8

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 previous meeting (5mins)
  • Standard WG Meeting - July 23, 2023 #1040
• Announcements (10mins)
  • FDC3 2.1 adoption and NPM module release
    • Change summary
  • Updated FDC3 Training course is live: Introduction to FDC3 (LFEL1000):
  • FDC3 Certification beta will be starting on Monday (look out for the invite)
  • FDC3 Standard licence change to the Community Specification Licence
    • Proposal for the FDC3 project to adopt the new FINOS Standards Governance model (including the Community Specification License) #412
    • SPDX
    • Github readme
    • License & Notices file in the FDC3 repo
    • What do you need to do?
• FDC3 Identity and Threat Modelling Discussion Group (10mins)
  • FDC3 Identity & Threat Modelling - Discussion group #1078
  • Proposal of new maintainer, Yannick Malins, as chair
• Update the FDC3 Charter document #1023 (5 mins)
  • Update to the FDC3 scope and charter #1079
• What are the priorities for the next FDC3 version? (25mins)
  • Supported Platforms
    • Multiple Language Bindings #990
      • Proposal to add .NET interfaces and context declarations #931
      • Java (No issues raised)
      • Python (No issue raised)
    • FDC3 For Web browsers #896
  • AppD issues:
    • Provide better documentation and examples for AppD auth support #559
    • Revive and update or replace AppD reference implementation #563
    • Add vendor agnostic default window size and position settings to the App Directory app definition format #564
    • Allow an AppD application record to reference other apps that are *required* for it to run #674
    • Add /intents and /contexts endpoints to the AppD API #719
    • Proposals arising from Identity & Threat modeling discussion group
  • API issues:
    • Upgrade exposure of originating app identity to a requirement (MUST) from recommended (SHOULD) #735
    • Question: App-specific context metadata #829
    • Custom application config, retrievable via a standardized function #1006
    • Remove defunct version field from IntentResolution #1053
    • Missing desktopAgent from ImplementationMetadata #1057
    • Proposals arising from Identity & Threat modeling discussion group
  • Context & Intents
    • Intent Proposal: Create or Update Profile #591
    • Improve the definition of the Position context type #656
    • Actionable Notifications via Intent & Context #828
    • Question: What use cases and Intents related to Orders, Trades and Positions are there? #904
  • Desktop Agent Bridging
    • Issues arising during implementation by stakeholders
  • Project infrastructure & maintenance
    • Improve OpenAPI (REST) documentation for the website with a docusaurus plugin #1001
    • Replace tsdx use in build of the FDC3 NPM module #1061
    • Should we split context & intent out of the main FDC3 standard? #940
      • Replace existing Context pages with JSON schema definitions #1068
      • Update npm-build action and other github actions to later version of node #1072
  • New issues?
• Adjourn

Minutes

• FDC3 2.1 adoption and NPM module release:
  • FDC3 2.1 introduces a long-awaited 5th Part to the FDC3 Standard (Agent Bridging) that allows Desktop Agents to collaborate via a 'Bridge', enabling interop for apps managed by those Desktop Agents to span across them, and even across a user’s different PCs and other devices.
  • Inter-agent communication has been a goal of FDC3 since its first version, now realized through collaboration between Desktop Agent vendors (including Interop.io and OpenFin), banks (NatWest, Citi & StateStreet), asset Managers (Wellington) and a number of other participants. FINOS also hosts a project contributed by NatWest Markets which implements a 'Bridge', with plugin support for working with an organization's in-house infrastructure, known as the FDC3 Backplane.
  • FDC3 2.1 also includes small but important refinements to FDC3's other APIs, the Desktop Agent API and App Directory. However, these remain compatible with the previous version.
  • New use cases are catered for by additions to the Context data and Intents Parts of the Standard, including:
    • Improved interactions with Chat or CRM applications
    • Contexts to be used with Order & Execution Management Systems (OMS/EMS) workflows.
  • For full details see the FDC3 changelog
  • Beta node module released (testing and feedback needed): https://www.npmjs.com/package/@finos/fdc3/v/2.1.0-beta.2
• FDC3 Standard license change to the Community Specification Licence
  • @kriswest provided an overview of the change and the reason for it + a quick guide on what is needed from contributors to continue contributing under the new license:
    • Raise a PR, for example to the Notices.md file (example PR: [DONT MERGE] Update NOTICES.md #1070)
    • EasyCLA will check whether the contributor is authorized (no is after the license change until they take the following actions)
      • 
    • Click on the link in the comment 'Please click here to be authorized', which will check for a compatible Contributor License Agreement (either specific to FDC3 or to the FINOS foundation).
      • If one is found you will be authorized automatically for future contributions
      • If one is not found, instructions are provided for completing a compatible CLA (either a corporate CLA or an Individual CLA)
• FDC3 Identity and Threat Modelling Discussion Group
  • @kriswest proposed @Yannick-Malins as a new FDC3 maintainer and requested the consent of the Standards Working group to appoint him, which was given.
  • @Yannick-Malins gave an overview of the scope for the discussion group (see FDC3 Identity & Threat Modelling - Discussion group #1078)
    • Will focus first on modeling the issues/risk/problems faced by FDC3 adopters, before working on solutions to those through extensions to the FDC3 Standard.
    • First meeting to be held on Thursday 12 Oct 2023 - 11am (US eastern timezone EST) / 4pm (London, BST)
• Update the FDC3 Charter document #1023
  • @kriswest summarized the purpose of, and proposed changes to the Charter and Scope documents in Update to the FDC3 scope and charter #1079
  • No objections to the changes were raised, although @novavi suggested that Chat applications be added to the list of non-financial applications used in financial workflows.
  • FDC3 Maintainers to and Editor to review and merge the change
• What are the priorities for the next FDC3 version?
  • @kriswest provided a run-through of the existing issues above - these are not prioritized
  • No particular prioritization was provided, hence, @kriswest will determine agendas for future meetings based on the list and attempt to complete or close all outstanding issues
    • @kriswest also:
      • proposed that we write new content to explain FDC3's technology use cases (as opposed to the functional use case originally used to establish the standard) and that content written for the FDC3 training courses includes such content (as it was necessary to explain FDC3, and hence is probably necessary to include in the FDC3 website as well).
      • Provided an outline of maintenance work that the FDC3 project infrastructure needs doing - and pointed out that these are ideal tasks for prospective new maintainers to undertake in order to build a history of contribution to FDC3.

Action Items

• ALL test the FDC3 NPM module 2.1.0-beta.2 and report back on any issues - its should be compatible with all apps using the 2.0.x modules
• @fdc3-maintainers Review and merge charter/scope updates
• @kriswest create the next meeting agenda based on open issue list or new issues raised by participants
• @kriswest raise an issue to add technical use cases content to the FDC3 website and instruction (drawing from the training material)
• @kriswest @hughtroeger remove references to the fdc3-desktop-agent from the FDC3 website.

Untracked attendees

Full name	Affiliation	GitHub username

[mistryvinay]

Vinay Mistry / Symphony 🎵

[novavi]

Derek Novavi / S&P Global

[kriswest]

Kris West / Interop.io 🚀

[pierreneu]

Pierre Neu / Symphony

[openfin-johans]

Johan Sandersson / OpenFin 🎁

[Yannick-Malins]

Yannick Malins / Symphony

[timjenkel]

Tim Jenkel / Wellington

[mattjamieson]

Matt Jamieson / WhiteDog

[hughtroeger]

Hugh Troeger / FactSet