What's happening in the world of FDC3?
This week, Desktop Agent Bridging, FDC3 2.1 and a published success story from Luxoft take center stage.
At the start of June, I wrote the FDC3 blog article about FDC3 Language Bindings, which was a hot topic following the BMO hackathon, where we saw new language bindings for Java and Python to add to the C# one contributed earlier in the year by Brian Ingenito.
As I discussed then, one of the problems was that there was no agreement on a common FDC3 protocol, which meant that Desktop Agent-agnostic language bindings couldn't be created.
However, a big piece of the puzzle fell into place this week since the FDC3 Participants community voted to accept Desktop Agent Bridging as a new, optional and experimental part of the FDC3 standard.
Through the magic of AsyncApI (think OpenAPI but for message buses) we now have a protocol and we can start to think about building this into our FDC3 libraries.
I expect this to be a big focus post-FDC3 2.1. And speaking of which…
Once Desktop Agent Bridging is merged into the main part of the FDC3 standard we’ll be well on our way to publishing FDC3 2.1. There are still plenty of issues open on this, but the maintainer team and others are working hard to get these closed off.
In a future blog, I’ll dive further into the details about what’s included in FDC3 - stay tuned!
… and finally, it’s always nice when someone pulls back the curtain to show how FDC3 works behind the scenes (or, behind the corporate firewall, if you will).
Check out this article by FINOS member Luxoft about how they’re integrating FDC3 for their clients:
A New Era of Seamless Integration with Luxoft
Does anyone else have a good success story to share? I’ll be happy to amplify your work here.
See you next time!
Cheers,
Rob
Author: Rob Moffat
Interested in this FINOS open source project, or any of our other projects? Click the link below to see how to get involved in the FINOS Community.