Content Negotiation for sub-output results

[fmigneault]

referenced in Unidata/netcdf#42 (comment)

When a process is submitted for execution with a content negotiation (or auto-resolved it by N>1 outputs requested) to results.yaml structure, the per-output format: {mediaType: ...}} can be provided to request their specific content-negotiation.

ogcapi-processes/openapi/schemas/processes-core/output.yaml

Lines 1 to 4 in a1c3cd3

	type: object
	properties:
	format:
	$ref: "format.yaml"

ogcapi-processes/openapi/schemas/processes-core/format.yaml

Lines 1 to 11 in a1c3cd3

	type: object
	properties:
	mediaType:
	type: string
	encoding:
	type: string
	schema:
	oneOf:
	- type: string
	format: url
	- type: object

However, certain media-types might require additional profile negotiation, such as distinguishing a profile=cloud-optimized or a profile=netcdf3/4. In cases like profile=cloud-optimized, they are already included in mediaType by definition, but other media-types might not officially integrate this parameter.

Therefore, it might be worth indicating a "profile" parameter along the "mediaType" within the "format".

[fmigneault]

Considering KVP, corresponding {inputID}[profile] and {outputID}[profile] should also be added.