finos
FDC3 Terminology Changes
Enhancement Request
Use Case:
A developer or enterprise architect new to FDC3 encounters terms like "Desktop Agent." This creates immediate confusion, as "Agent" is now synonymous with AI, misrepresenting the component's role as a runtime/broker. This ambiguity is compounded by variations like "Web Desktop Agent" and the fact that the name "FDC3" itself implies a scope limited to Finance and the Desktop, which no longer reflects its modern capabilities.
Workflow Description
The target workflow is one where a developer can read the FDC3 specification and immediately grasp the role of each architectural component due to clear, intuitive, and consistent naming. This developer can then confidently build applications that correctly interact with the FDC3 environment, embed FDC3-aware components, and use different channel types without ambiguity, leading to faster and more reliable integrations.
Workflow Examples
- Example 1 (Avoiding Confusion): An enterprise architect is evaluating FDC3. They read "Desktop Agent" and spend time investigating whether FDC3 has dependencies on AI services, only to discover it's a message broker. With a clearer term like "FDC3 Runtime," its function would be immediately understood, saving evaluation time.
Additional Information
This proposal addresses several ambiguous, outdated, or inconsistent terms within the FDC3 standard. The goal is to establish clear, intuitive naming conventions that reflect the standard's evolving capabilities and broadening adoption.
This starts with the name "FDC3" itself. While the brand is strong, its origin as an acronym (Financial Desktop Connectivity and Collaboration Consortium) is now limiting as the standard is adopted in new domains and on platforms beyond the traditional desktop. It is proposed that FDC3 be treated as a standalone brand name, decoupling it from its historical acronym. This mindset of evolving the language to match the standard's modern reality is the foundation for the specific proposals outlined below.
Key Terms for Discussion
Here is a summary of the current terms requiring review:
- FDC3 (as an acronym)
- Desktop Agent
- Sub-Agent Specification
- WCP (Web Connection Protocol) & DACP (Desktop Agent Communication Protocol)
- Private Channels
Additional terms:
- User Channels
- Workspaces, Groups, Frames, Layouts *
Proposed Terminology Changes
| Current Term/Concept | Proposed New Term / Action | Reasoning |
|---|---|---|
| FDC3 (as an acronym) | Formalize FDC3 as a brand name | Decouples the standard from its "Financial Desktop" origin, supporting broader adoption in new domains and platforms. The brand itself is already strong and well-recognized. |
| Desktop Agent | FDC3 Runtime | "Runtime" accurately describes the environment that enables FDC3 applications to run and interoperate. It avoids "Agent," which is now heavily associated with AI, preventing future confusion. |
| WCP (Web Connection Protocol) | FDC3 Web Handshake Protocol | Renaming to "Handshake Protocol" more accurately describes its single purpose: managing the initial discovery and secure connection handshake between a web application and the FDC3 Runtime. |
| DACP (Desktop Agent Comms Protocol) | FDC3 Message Protocol | Renaming to "Message Protocol" clarifies this as the main "wire protocol" used for all ongoing communication (context, intents, etc.) after a connection has been established by the Handshake Protocol (WCP). |
| Private Channels | "Unlisted Channels OR Hidden Channels" | "Unlisted" is an intuitive adjective to describe the shared characteristic of these channel types. It correctly implies they are not in the system channel list but are otherwise fully functional, avoiding ambiguity. Private is often means encryption, TLS etc. |
| Current Term/Concept | Group Suggestions | Reasoning |
|---|---|---|
| Sub-Agent | FDC3 App Component, sub-app, child app, widget, module, component, microagent | There were many suggestions during the last meeting that have been included. |
| Workspaces, Groups, Frames, Layouts | ? | Different vendors use inconsistent terms for a saved collection of applications. The FDC3 standard should formally adopt a way to describe a collection of apps. |
@kriswest first draft on this from meeting https://github.com/finos/FDC3/issues/1653
@SeeWhatsOn the maintainers had a chat about this topic yesterday and there isn't much of an appetite to take on the work that significant rename's within the API would require to execute (message schema's, types, docs and disambiguation, backwards compatibility code, training courses, website, etc.). Although the 'agent' term is used for agentic AI, there are many other usages of Agent stretching back 25-30 years and there are likely to be more in future.
Instead, we could try to improve the situation through improvements to the FDC3 landing page, getting started content and the API overview and introduce and explain our use of the term easly on. None of these pages do a great job of introducing the core concepts and our terminology - our homepage launches in 'What is it', 'Whats are the benefits' etc. but don't actually introduce the FDC3 architectural pattern and certainly not in a visual way that will help with comprehension of FDC3's core concepts or what it does/where it fits. This was criticism that @awaiken also had on the homepage and we've struggled to do anything about it. However, now could be the time to deal with this and ensure FDC3 is easier to get started on / comprehend. WDYT? Would you be up for contributing to improvements in the homepage and API overview? Certainly something I would try and help with.
We've also had this issue for creating a new getting started guide hanging around for a while, I think it related: https://github.com/finos/FDC3/issues/1395
Per our discussion in today's Browsers WG, I agreed that changing the terminology would incur a cost greater than the value it would create. However, removing the finance aspect of the FDC3 acronym and ties to finance elsewhere in the documentation that does not pertain to financial concepts (Intents and Context types) would encourage developers from other industries to take advantage of the message bus and interop features that the standard provides that are independent of the finance industry.
I queried a GenAI assistant to help in creating a backronym for FDC3 and it generated these suggestions. I'm particularly partial to number 8 myself.
You said: FDC3 is an open standard for applications on financial desktop to interoperate and exchange data with each other. The acronym currently stands for "Financial Desktop Connectivity and Collaboration Consortium". I'm considering possibilities to change what the acronym stands for to allow the message bus interoperability standard to be adopted outside of the finance industry as the connectivity part of the standard is not specific to financial applications. Provide me 10 ideas to use different underlying words in the FDC3 acronym that indicate it is an interoperability and message bus standard.
Copilot: That's a great initiative, Paul — broadening the scope of FDC3 beyond finance could unlock a lot of potential for cross-industry interoperability. Here are 10 alternative expansions of the FDC3 acronym that maintain the essence of interoperability, connectivity, and collaboration, while making it more industry-agnostic:
Generalized FDC3 Acronym Ideas
- Federated Data Connectivity & Collaboration Consortium Emphasizes distributed systems and data sharing across platforms.
- Framework for Desktop Connectivity & Communication Focuses on the technical nature of the standard as a framework.
- Flexible Data Communication & Coordination Consortium Highlights adaptability and coordination across apps.
- Federated Desktop Communication & Collaboration Keeps the desktop focus but removes financial specificity.
- Foundation for Distributed Connectivity & Collaboration Suggests a foundational layer for interoperability.
- Fast Data Connectivity & Collaboration Core Implies performance and centrality in data exchange.
- Fabric for Desktop Communication & Coordination “Fabric” evokes a woven infrastructure of interoperable apps.
- Framework for Dynamic Connectivity & Collaboration “Dynamic” suggests real-time, responsive interoperability.
- Federated Digital Communication & Collaboration Broadens the scope to digital systems beyond desktop.
- Foundation for Decentralized Communication & Collaboration Aligns with modern decentralized architectures and ecosystems.
Comments from #1702:
- What about Front-end for the F?
- A better acronym might help people comprehend (get started with) FDC3