FDC3 Standards Working Group meeting Thursday 25th April 2024 @ 10am EDT / 3pm BST)

['Kristopher West' via FDC3 Project]

Hi All,

The next meeting of the FDC3 Standards Working Group is tomorrow @ 10 am (US eastern time zone EDT) / 3 pm (London, BST). Please find the agenda and joining details below and at: https://github.com/finos/FDC3/issues/1196

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

Agenda

• Convene & roll call, review meeting notices (5mins) 

• Review action items from previous meeting (5mins) 

• Summary of current topics in DIscussion group meetings. Upcoming meetings (5mins): 

• FDC3 Use cases discussion group: Thurs 2nd May 

• Understanding the FDC3 End-User Personas #1173 

• FDC3 Trader Persona #1183 

• FDC3 Identity & Threat Modelling discussion group: Thurs 9th May 

• FDC3 for Web Browsers discussion group: Thurs 16th May 

• FDC3 Desktop Agent Bridging discussion Group: Wed 22nd May 

• Updated proposal for: Add event listener support to the Desktop Agent API for changes to the current User channel #1136 (10mins) 

• Merged PR overview for: Refactoring ContextTypes to union type (instead of enum) #1138 (5mins) 

• Continue discussion of Adding debugging information to help app developers trace broadcast storms #1142 (20mins) 

• This is a similar request to others raised in the past, e.g. Question: App-specific context metadata #829 

• Multiple app developers have asked for ways to send some additional metadata with a context message, for ancillary purposes (debugging, tracking sequences of interactions for analytics purposes, providing some additional that might be used in a response) 

• There are two ways to solve for this - allow it to be sent through the API as an additional, optional, argument OR create a standard place to attach it directly to a context message. 

• Other issues or PRs under review for the community to be aware of (5mins): 

• Replace tsdx use in build of the FDC3 NPM module #1061 

• Remove TSDX from build system #1175 

• Update Use Cases #1096 

• Marketing Update #1181 

• Correcting an error in the fdc3.country docs as they differ from the schema #1194 

• Add openssf scorecard action and readme badge displaying score #1188 

•  Contribution opportunities (issues in need of a PR) (5mins): 

• Add vendor agnostic default window size and position settings to the App Directory app definition format #564 

• Intent Proposal: Create or Update Profile #591 

• 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 

• Improve OpenAPI (REST) documentation for the website with a docusaurus plugin #1001 

• Custom application config, retrievable via a standardized function #1006 

• Remove defunct version field from IntentResolution #1053 

• Missing desktopAgent from ImplementationMetadata #1057 

• Replace tsdx use in build of the FDC3 NPM module #1061 

• FDC3 should avoid union types in contexts and other objects #1105 

• Add event listener support to the Desktop Agent API for changes to the current User channel #1136 

• Adjourn 

See you there!

K

Kris West

Director, Consulting Services

p +44 7715104292│e kris...@interop.io

Finsemble and Glue42 are now interop.io