Often, the DIDO Platforms use proprietary languages, libraries, and interfaces which ultimately affect the Interoperability, Portability and maintainability of end user solutions built upon the proprietary solutions causing Vendor Lock-In. The response from the DIDO Platforms is often “our product is Open Source Software (OSS)” therefore it is a standard or our specification is a de facto Standard. While there is some legitimacy in these responses, it is not adequate for long term (30+ year) lifecycles or for Mission Critical Systems.

Additionally, the use of “languages, libraries, and interfaces” require a labor force that is highly trained and skilled in specialized general computing rather than the trained and skilled in the business domain. In other words, the end-user must find people who are educated and trained in their specific domain (i.e., finance, accounting, taxes, supply chain, environment, public records, etc.) as well as having the computing skills to use the languages, libraries and interfaces for each DIDO Platform.

The Command Line Interface is the instructions for how to parse a command line interpreter of the Database/DIDO’s data.

The Command Line Interpreter is the implementation of the command line interface allowing users to interact with the Database/DIDO’s data.

Solidity and Web3 are great concepts, however solidify requires you to hire someone trained specifically in programming to create and maintain smart contracts. The CLI allows the user (person or application) to interact with the DIDO Platform by entering text commands similar to SQL at a prompt and receive a response as human readable text.

History likes to repeat itself, the Semantic Querying Language (SQL) is a standard built in response to the growing complexity of multiple database providers each providing their own specific api to interact with their databases in the 1970s. The same is starting to happen within the DIDO community and a similar problem can be solved in a similar manner. Keep It Simple Stupid (KISS)