Full metadata for a user-defined process
Lists all information about a user-defined process, including its process graph.
Response
The user-defined process with process graph.
The identifier for the process. It MUST be unique across its namespace (e.g. predefined processes or user-defined processes).
Clients SHOULD warn the user if a user-defined process is added with the same identifier as one of the predefined process.
A short summary of what the process does.
Detailed description to explain the entity.
CommonMark 0.29 syntax MAY be used for rich text representation. In addition to the CommonMark syntax, clients can convert process IDs that are formatted as in the following example into links instead of code blocks: ``process_id()``
A list of categories.
Declares that the specified entity is deprecated with the potential to be removed in any of the next versions. It should be transitioned out of usage as soon as possible and users should refrain from using it in new implementations.
Declares that the specified entity is experimental, which means that it is likely to change or may produce unpredictable behavior. Users should refrain from using it in production, but still feel encouraged to try it out and give feedback.
Declares exceptions (errors) that might occur during execution of this process. This list is just for informative purposes and may be incomplete. This list MUST only contain exceptions that stop the execution of a process and MUST NOT contain warnings, notices or debugging messages. It is meant to primarily contain errors that have been caused by the user. It is RECOMMENDED that exceptions are referred to and explained in process or parameter descriptions.
The keys define the error code and MUST match the following pattern: ^\w+$
This schema follows the schema of the general openEO error list (see errors.json).
A process graph defines a graph-like structure as a connected set of executable processes. Each key is a unique identifier (node ID) that is used to refer to the process in the graph.