Support Workflow/Process/Job content-negotiation by profile/schema

[fmigneault]

Description

• support Content-Type: application/json with Content-Schema to identify the workflow type

  • ad-hoc workflows: Content-Schema: https://schemas.opengis.net/ogcapi/processes/part3/0.0/openapi/schemas/processes-workflows/execute-workflows.yaml (not yet published!) Referring to https://github.com/opengeospatial/ogcapi-processes/blob/master/openapi/schemas/processes-workflows/execute-workflows.yaml as described in https://geolabs.fr/dl/job-management/ogcapi-processes/extensions/job_management/standard/20-044.html#_ogc_api_processes_workflow_execute_request_body)
  • Content-Type: application/cwl+json can be used for CWL, since an IANA media-type is already available
  • Content-Schema: https://api.openeo.org/assets/pg-schema.json
    openEO: not planned for the moment - Support openEO process definition #564

• Alternate Content Negotiation by Profile approach

  • Link: <schema-uri>; rel="profile alternative proposed
  • Accept-Profile: <schema-uri> for requesting a given representation
  • Content-Type with profile parameter

• if schema/profile unsupported, respond with http://www.opengis.net/def/exceptions/ogcapi-processes-4/1.0/unsupported-schema
  (https://docs.ogc.org/DRAFTS/24-051.html#_exceptions)

• ensure the returned status aligns with the selected schema/profile type

References