Support OGC-API Processes - Part 3: Workflows

[fmigneault]

Description

Posting a workflow as a Nested Process definition of processes could be supported.
This would align with Part 3 ad-hoc Workflows, but used for immediate execution rather than deployment.

{
  "process": "https://server.com/processes/ProcessID",
  "inputs": {
    "in": {
      "process": "https://server.com/processes/OtherNested",
      "inputs": {
        "data": 123
      }
    }
  }
}

This feature addresses only the Nested Processes (and derived requirements). The other Part 3 features such as Input/Output Collections are tracked by :

• Support OGC-API Processes - Part 3: Collection Inputs #682
• Support OGC-API Processes - Part 3: Collection Outputs #683

ToDo:

• update the ogcapi_proc_part3 conformance items accordingly.
• support the Nested Processes as process: <uri> construct #747
• support properties input/output field modifier #750
• Consider filter operations with filter-lang=cql-text|cql-json using CQL2 #640
• support Remote Processes requirement (de facto in our case)

References

• http://www.opengis.net/spec/ogcapi-processes-3/1.0/req/workflows
• https://github.com/opengeospatial/ogcapi-processes/tree/master/extensions/workflows
• https://github.com/opengeospatial/ogcapi-processes/tree/master/extensions/workflows/requirements/nested-processes
• https://docs.ogc.org/DRAFTS/21-009.html#_requirement_class_nested_processes