Extensible Typing for Workflow I/O

[christophenoel]

Summary:

We would like to introduce optional extension points that allow users to define richer typing and metadata for input parameters, artifacts, and outputs.

Use Cases:

We use Argo Workflows in Earth Observation (EO) pipelines, integrating them with standard geospatial APIs. To better align with geospatial standards, we need a way to enrich input parameters, artifacts, and outputs with typed metadata.

• Parameters: Define parameter types (e.g., integer, float, temporal, spatial), allowed values, and references to standard domains.
• Artifacts: Annotate artifacts (raster, vector, table) with format, coordinate reference systems, and domain-specific metadata.
• Outputs: Provide typed schemas so external systems (like OGC API Processes) can automatically parse and chain workflow results.

However, extension points would facilitate holding metadata for any specific domain, and help integrating with complementary tools.

Proposed Enhancement:

Add optional object fields (e..g : annotations, extensions or metadata)

Benefit:
This would improve interoperability, streamline integration with domain-specific APIs, and make workflows more portable and discoverable in Earth Observation and other specialized domains.

Love this feature request? Give it a 👍. We prioritise the proposals with the most 👍.