FDC3 Standard v2.2 released!

1 view
Skip to first unread message

West, Kristopher (Enterprise Engineering, Technology)

unread,
Apr 9, 2025, 2:01:51 PMApr 9
to noreply-spamdigest via FDC3 Project, fdc3-par...@finos.org, anno...@finos.org
The FDC3 Maintainers are happy to announce the release of version 2.2 of the FDC3 Standard!

Release notes: https://github.com/finos/FDC3/releases/tag/v2.2 

FDC3 2.2 brings long awaited support for FDC3 in Web Browsers, allowing web apps with FDC3 support to be truly vendor-agnostic and interop with other applications through any conformant Desktop Agent.

FDC3 support in Web Browsers was enabled through the creation of a (JSON) Desktop Agent Communication Protocol (DACP), that could be used to develop vendor-agnostic adaptors for other FDC3 language bindings in future, and a connection protocol implemented by a getAgent() function for use in web applications. The FDC3 NPM module provides an implementation of getAgent() for web apps to use to connect to any conformant Desktop Agent and a reference implementation of a web-based Desktop Agent  is provided as part of the FDC3 toolbox (and is used to test getAgent()).

2.2 also marks the adoption of an official .NET binding for FDC3 that can viewed in the FDC3 documentation:


We've also made a number of infrastructure improvements in 2.2, including switching the TypeScript NPM module to ESM, with an alternative commonJS module to provide backwards compatibility: 

We're also publishing a number of new sub-modules that can be imported individually:


For a more detailed overview see the release notes, changelog or the maintainers presentation from  the recent FDC3 General meeting on youtube or the FINOS blog.

Finally, on behalf of the FDC3 maintainers I'd like to thank all of the contributors to FDC3 2.2, whether you contributed through meetings, on issues, via PRs or other supporting activities, we couldn't do it without you!

If you'd like to get involved in future versions of FDC3, check out this post from FINOS on LinkedIn, attend our meetings or raise an issue on GitHub.

K

--

Kris West (he/him)
Principal Engineer | Open Source Program Office (OSPO)
kristopher.west@natwest.com | +44 7715104292
250 Bishopsgate, London, EC2M 4AA
natwestgroup.com

The information classification of this email is Confidential unless otherwise stated.
Do you have a question?
Join us on Discourse https://natwest.discourse.group (Open Source | InnerSource)



National Westminster Bank plc. Registered in England No. 929027. Registered Office: 250 Bishopsgate, London EC2M 4AA. National Westminster Bank plc is authorised by the Prudential Regulation Authority, and regulated by the Financial Conduct Authority and the Prudential Regulation Authority.
The Royal Bank of Scotland plc. Registered in Scotland No. 83026. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB. The Royal Bank of Scotland plc is authorised by the Prudential Regulation Authority, and regulated by the Financial Conduct Authority and the Prudential Regulation Authority.
The Royal Bank of Scotland plc and National Westminster Bank plc are authorised to act as agent for each other.
The Royal Bank of Scotland plc and National Westminster Bank plc are UK chartered banks and are not chartered or licensed as banks by the United States or any individual state.
This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer. Internet e-mails are not necessarily secure. The Royal Bank of Scotland plc, National Westminster Bank plc or any affiliated entity (“NatWest” or “us”) does not accept responsibility for changes made to this message after it was sent. NatWest may monitor e-mails for business and operational purposes. By replying to this message you give your consent to the monitoring of your e-mail communications with us. Whilst all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely affect its systems or data. No responsibility is accepted by NatWest in this regard and the recipient should carry out such virus and other checks as it considers appropriate. 
Reply all
Reply to author
Forward
0 new messages