Versions Compared

Old Version 1

changes.mady.by.user Espen Overbye

Saved on

compared with

New Version Current

changes.mady.by.user Tosha Ellison

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

NameOrganisation

Espen Overbye

OpenFin
Ben McBride 
Dylan PraulFinTech Studios
Frank Tarsillo (Deactivated)IHS Markit
Johan SanderssonFactSet
Jonathan TeperJP Morgan
Former user (Deleted)Refinitiv
Mark ValeirasChartIQ
Rhyddian OldsJP Morgan
Riko EksteenJP Morgan
Tim KoleckeCitadel
Mark DennisFidessa
Rob Underwood (Deactivated)FINOS
Tosha EllisonFINOS

Outstanding Action Items

  •  Group: Fill gaps in confluence page

...

TimeItemWhoNotes from the Meeting
5 minConvene & roll call

Espen Overbye


10 minReview action items from previous meetings (see above)

Espen Overbye


10 min

New Participant Intros

  • new participants in FDC3 and new attendees to the meeting introduce themselves
    • organization and role
    • why is interoperability important to you / your organization?
    • what do you hope to accomplish with FDC3?

Group, Espen Overbye

coordinating

Mark Valeiras from ChartIQ introduced himself. Looking to adhere to the FDC3 standard, using what exists and influencing it as it gets built out.

30 min

Working Group Updates

  • API WG
  • App Directory WG
  • Context Data WG
  • Intents WG
  • Use Cases WG

Espen Overbye

Tim Kolecke

Frank Tarsillo (Deactivated)

Former user (Deleted)

Jonathan Teper


Context Data updated provided by Tim

  • The Context Data WG passed by consensus an initial specification for Context Data.
  • The structure is a little different from the original specification so Tim encouraged the group to look at the new spec.
  • Any questions or comments should be sent via confluence, which also has info on mtgs, specs, etc. The community can comment on the specification during this two-week comment period via Confuence, email, or GithHub.

AppDirectory update provided by Frank

  • The AppD draft specification is under review and is expected to be presented for ratification in the next meeting.
  • Showed the new website that provides (will provide) all of the information and background to provide context, examples, etc. as well as the API specs.
  • Uses simple markdown and the build process will push the content back to the FDC3 site - so the changes (through change control) get pushed back. Simply change in the repository to make a PR to make any modifications. (Rob noted that you must be a CCLA in place to contribute.)
  • If you are a Java developer these projects, including the client binding examples, stubs, etc. are available as sono type. 

    Image Added
  • You can also check out the Swagger implementation here. 

Image Added

  • Espen noted that there is ongoing work to present an overall picture of how FDC3 fits together including consistent documentation.

JT Provided an update on Use Cases

  • The group has ratified 9 use cases and is reaching out to other WGs to present them as well as having a session at the OSSF mtg during which they will work with Intents, Context, API and AppD to review the use cases and relevance across WGs.
  • Created new backlog section to create new use cases and this will get reviewed following current use case review in the other WGs, which is the current priority.

Espen provided an update for API and Intents

  • Both groups have specifications that have passed ratification within the WGs and the PMC.
  • Very close to having ratification in all groups.
20 minAOB & adjourn

Group, Espen Overbye

coordinating

Riko noted that there is a need for unified place where definitions are stored for intents and types along with discovery, facilitation and governance around collaboration on these. If there is time this may be discussed at the OSSF mtg.

Espen also encouraged teams/individuals to come to this and other WG mtgs and present how they are sung FDC3

Decisions Made


Action Items

...