Limit input representation as per process description

[fmigneault]

Description

OGC API - Processes v2.0 introduced a concept of valuePassing.

inputs:
  input:
    schema: {}
    valuePassing: ["byValue", "byReference"]

This can be used to limit which input structures can be submitted (i.e.: {"value": "..."} or {"href": "..."}.
A process that desires to handle only one representation could be deployed with a valuePassing override.
When executing the process, the submitted value would have to align with the allowed valuePassing (default all).

Since Weaver does a lot of automatic handling to map CWL inputs from submitted execution inputs, this would be implemented only by a pre-check of the submitted inputs to validate that they respect the structure. This should be done around the same place where allowed formats/media-types are validated.

Extra Consideration

A collection input would need to be considered like a byReference, or define a custom byCollection definition?

References

• https://docs.ogc.org/DRAFTS/18-062.html#_describing_a_process_input
• https://docs.ogc.org/DRAFTS/18-062.html#_value_passing