Riko Eksteen

Adaptive

rikoe

Mark Valeiras

ChartIQ

Leslie Spiro

Glue42

James McLeod

FINOS

Malcom Chedzoy

JPM

Nick Kolba

OpenFin

Evgeny Kovalyov

Refinitiv

Christi Reid

Adaptive

Colin Eberhardt

ScottLogic

Time Dinsdale

OpenFin

Sanjay Nagpal

Credit Suisse

Phil Broadbent

OpenFin

Vinod Mehta

FactSet

5 min

Convene & roll call

Riko Eksteen

5 min

Approve Past Meeting Minutes

• Review https://finosfoundation.atlassian.net/wiki/spaces/FDC3/pages/1188135044/2019-09-26+Meeting+Notes

• All older minutes have now been marked as approved

• (added by Aitana) Next WG is scheduled for Nov 28th (Thanksgiving in the US) is it OK to reschedule this meeting for Thursday, November 5th at the same time?

Everyone

Approved

5 min

Review action items from previous meetings

Everyone

10 mins

Working group member onboarding:

• GitHub Teams

• Confluence Members

@James McLeod (Unlicensed)

Riko will validate with FINOS Confluence team members, and look at creating an FDC3 API working group team on GitHub.

20 mins

Discussion topic: FDC3 entry point

OpenFin’s FDC3 service exposes a window.fdc3 object as entry point to the FDC3 API interface, and others may be doing the same. Should we formalise the way FDC3 is accessed across desktop agents to ensure compatibility.

What is the implication for so-called multi-agent environments (if that is something we should be considering)?

Also see: https://fdc3.finos.org/docs/1.0/api/DesktopAgent

Everyone

Global or module?

Could be an unnecessary complication/is it a real problem?

Riko will create a GitHub issue and we will socialise that way.

We need to collect requirements and decide priority.

20 mins

Discussion topic: Do we need a wider scope, i.e. an FDC3 protocol

This is a catch-all topic for multiple related issues which came up during our previous meeting:

• APIs define an interface, but does not describe behaviour

• Should we provide .NET API support (for e.g. WPF interop)

• Cross-machine and client-server workflows

• Exposure of FDC3-like operations via REST or other mechanisms (e.g. URL handlers)

• npm & other package support

Everyone

Is it correct to assume it is a walled garden? This would require explicit bridges between them.

Does it reduce the value of FDC3 if applications operate within a specific implementation?

Agreeing on context is important for transference of data.

The group decided that people are fine with FDC3 operating within the context of a particular desktop agent for now and a wider protocol is not required. Building bridges should be cheap if required.

20 mins

API GitHub Issue Review (see GitHub issue list):

• #18: Should we have an FDC3 URI?

• #19: Align AppMetadata and IntentMetadata with other FDC3 specifications

• #21: publish NPM module for TS interface

• #97: Make all API classes interfaces

• #118: Turning off context sharing via Channels API

• #121: Modifications to the Channels API + Window selectors

• #126: Create documentation for new Channels API

• #127: Bug: IntentResolution.data property not supported by addIntentListener callback

Everyone

Issues will be reviewed at the next meeting

5 min

AOB & adjourn

5 December will be the next meeting

1.1 spec release would be desirable