operatorQuery allows for any number of inputs of any type to be provided. An implementation is very difficult to provide a friendly experience.

Would be valuable if guidance is provided for common usage patterns, including:

• Yes/No prompt
• Confirmation prompt (Message Box)
• Pick from a list (enum/dropdown/picklist)
• Input string, number, arrays
• Considerations for rich dialogs
• Password/credential prompts

SpacePython defines its own time object. It should instead utilize native time/date functionality. This would make procedures be easier to author and better integrate with existing and third-party libraries.

The data model should harmonize spacecraft and ground assets and therefore the language model should simplify/make this consistent as much as possible.

SpacePython is missing critical functions to be able to perform vital capability required for a real-time command and control system.

Functions that provide parameter and type information are lacking or insufficient in the language.

SpacePython is missing critical functions to be able to perform vital capability required for a real-time command and control system.

Functions that allow retrieval of metadata from a previous directive/command that was issued do not exist in the language.

SpacePython is missing critical functions to be able to perform vital capability required for a real-time command and control system.

Functions that create ground system events do not currently exist in the language.

SpacePython is missing critical functions to be able to perform vital capability required for a real-time command and control system.

Functions that enabling the establishment and release of command locks are missing from the language.

SpacePython is missing critical functions to be able to perform vital capability required for a real-time command and control system.

Functions that allow determining the current status/flags of a parameter (including the severity) are not available in the language at this time.

SpacePython is missing critical functions to be able to perform vital capability required for a real-time command and control system.

Functions that perform telemetry and limit checks are missing from the language at this time.

The user interface (operatorQuery) function is embedded in the middle of the SpacePython implementation and is not able to be separately implemented.

The method of prompting for a value may vary (such as for a web user interface versus a desktop application) and this variance is independence of the implementing provider for the SOLM language module.

SpacePython 1.1 requires that the reference implementation is modified/tailored by an implementing project/customer. As such, it does not have a loosely coupled implementation where the interface and implementation are separate.