No FDC3 Standards Working Group meeting tomorrow (28th March 2024)

['Kristopher West' via FDC3 Project]

Hi All,

Due to my own travel plans, and that of other FDC3 maintainers over Easter, we're short a chair for tomorrow's FDC3 Standards Working Group meeting and will be cancelling it. This will (we hope) give the maintainers some time to catch up on a number of maintenance and review tasks before our next meeting on Thursday 25^th April. Those include:

• PR Reviews:
• Refactoring ContextTypes to union type (instead of enum) #1138
• Refactors ContextTypes&Intent to union type instead of enum #1139
• Replace existing Context pages with JSON schema definitions #1068
• 1068 Generating context docs from schema files #1151
• Remove defunct version field from IntentResolution #1053
• Remove the IntentResolution.version field as defunct #1170
• Replace tsdx use in build of the FDC3 NPM module #1061
• Remove TSDX from build system #1175
• Missing desktopAgent from ImplementationMetadata #1057
• Refine the varying schemas for ImplementationMetadata #1177
• Broadcast Example not compatible with schema #1178
• Correction to bridging broadcast and findIntent examples that didn't match schema #1179
  
  
• Further work needed on PRs:
• Add content guidelines and other tweaks to community page #1169
• Finish converting community page to a react component and make a few other changes detailed in PR comments
• WIP: Adding .NET signatures to FDC3 documentation #1108
  
  
• Issues in need of a PR or proposal update:
• 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
• Custom application config, retrievable via a standardized function #1006
• Improve OpenAPI (REST) documentation for the website with a docusaurus plugin #1001
• Add /intents and /contexts endpoints to the AppD API #719
• Allow an AppD application record to reference other apps that are *required* for it to run #674
• Intent Proposal: Create or Update Profile #591
• Add vendor agnostic default window size and position settings to the App Directory app definition format #564
• Provide better documentation and examples for AppD auth support #559
  
  

We're also due to continue discussion of the following issue at the next meeting: 

• Adding debugging information to help app developers trace broadcast storms #1142

A solution for which may have multiple other use cases, including providing information for use in analytics (by linking several separate API calls to the same business workflow or interaction) or to help direct responses to an interaction (App-specific context metadata #829).

Other upcoming FDC3 meetings:

• Thursday 4^th April: FDC3 Use Cases and Workflows Discussion Group
• A less technical meeting looking at use cases firms are keen to implement that warrant additions to the FDC3 standard to support.
• Thursday 11^th April: FDC3 Identity & Threat Modelling
• A meeting exploring interop use cases that could be implemented if we had better support for confirming app/user/desktop agent identities (and hence more trust or better-protected communications) in FDC3 - expected to enable more integration between apps from buy- and sell-side organisations, amongst others.
• Thursday 18^th April: FDC3 Web Browsers Discussion group
• A meeting for working on proposals to bring FDC3 to Web Browsers, securely and while preserving the vendor agnostic nature of FDC3-enabled apps - currently working on the final proposal drafts!
• Wednesday 24^th April: FDC3: Desktop Agent Bridging Discussion Group
• A meeting for discussing the bridging (communication between) Desktop Agents/platforms that use them, allowing interop to span across multiple.
• Thursday 25^th April:  FDC3 Standard Working Group
• The next interaction of the main governance meeting for FDC3.

To have any of these meetings series added to your calendar, please email he...@finos.org.

K

Kris West

Director, Consulting Services

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

Finsemble and Glue42 are now interop.io