Interoperability at a high level is not standardized. As technology moves from the laboratory to monetized products and services, each company is developing its own high level strategy. At a lower level, the base standards upon which AI is developed and deployed rely on those used in data processing with few new additions thus far.
- Serialized IEEE fixed and floating point arrays
- CSV files
- Tab-delimited files
- XML conforming to a schema
- Target specific executables
- JVM bytecode
- Various framework dependent ways of storing tensors
Communications between components are generally based on some protocol, including these.
- RestFUL transactions using HTTPS client and server software
- MQTT — Message Queue Telemetry Transport is a lightweight messaging protocol for industrial and mobile applications.
Where full life cycle tooling provides for these standards and protocols, the documentation of the tool set will provide information on their use. Where they are lacking, custom software is developed in house. In more progressive corporations, the missing interoperability code, which used to be called glue code, is now more often open source projects.
The trick is to pick well maintained components, not only for run time but also for development time, for laboratory experimentation, and proof of concept work. These are the old names for the selected full life cycle components.
- Tool chain
- Technology stack
The description for the network of interoperable pieces in an efficient development, deployment, and continuous improvement system does not yet have a universal term. If a term were to be invented, its wording should feature the fact that AI engineers grab items as from the many drawers of a master machinist's tool chest and the fact that these tools interconnect in complex topological configurations in many cases. Consider these terms for development and run time respectively. They are descriptively accurate and hopefully something at least similar will gain acceptance.
- Tool cluster
- Component topology
What coordinates the logical, signal, and training parameter transmission between these tools and components are the transmission and transaction protocols and the directors, architects, and team leaders who work out how they will be used in the context of the products or services being developed. Although people have attempted to nail down development and productization processes in everything from cars to mobile applications, not everyone agrees to them, so there will probably remain a vast search space when putting together a technology based business and its selection of tools, methodologies, and intended product and service lines.