2018-11-02 Meeting

Espen noted  that Mao and team have done a great first pass at https://fdc3-intents.finos.org/ and that there is still some work to do to tie the different sites/docs together.

The group reviewed process and next steps as discussed in the last meeting.

Rob proposed there be a "task force" to take on not just tooling but also identifying where there are gaps in the documentation and creating consistency across all FDC3 WGs. This is important to provide context to participants on activities across all WGs as well as to enable new developers/participants to get up to speed more quickly. 

It was suggested that this could form part of the discussion on Day 2 of OSSF. 

Espen will initiate setting up the "team" via email including volunteers on the call: Espen, Mao and Rob (and it was suggested Frank Tarsillo would be a good addition).

The Intents and API specifications had been approved by their respective working groups and had been presented to the wider FDC3 group for comment for at least the required two week period. With no substantive issues or objections raised the next step was to ratify by the PMC.

A verbal vote was held to ratify the API Specification with the following results:

Espen - Yes

Johan - Yes

Saori - Yes

JT - Yes

Tim - Yes

Neil - Yes

The group being quorate and the majority vote being in favour, the API Specification was ratified.

A verbal vote was held to ratify the Intents Specification with the following results:

Johan - Yes

Neil - Yes

Saori - Abstain w/out cause

Tim - Yes

JT - Abstain w/out cause

Espen - Yes

The group being quorate and the majority vote being in favour, the Intents Specification was ratified.

With OSSF coming up in two weeks (Nov 14-15) a proposal had been circulated to the FDC3 group to hold a number of working sessions on Day 2. The group discussed attendance and topics with the following items to note:

• The group can have a room for most of the day (post meeting update - room is reserved for FDC3 from 11:00 until around 4:30 or 5:00)
• A whiteboard and dial-in (for remote joiners) was requested
• It's not a requirement to be an existing participant in the WGs to attend the session(s) although anyone new should be considered to be auditing the discussions so as not to derail progress
• Any and all decisions made would follow due process
• Proposed Agenda:
  • Session 1: Cross WG info session - plenum
  • Session 2: Discussing / ironing out cross group inconsistencies, plenum or break out sessions
  • Session 3: Use case to Intent/Context/API/App Directory mapping, plenum or break out session 

Saori informed the group that there has started to be some activity on the Plexus program around and API definition for a multi-broker, multi-bus specification. This activity is in progress and important for the FDC3 PMC to know about it.

This is happening in the open in GitHub within the Plexus Program and can be found here. The authors are a combination of Tick42 and Deutsche Bank teams.

The group discussed having a joint session with Financial Objects FDC3 and Plexus - and maybe Symphony and the importance of understanding where the FDC3 API falls short and Plexus covers the gap, who "owns" the payload, what Use Cases are applicable, etc.