To avoid(reduce) potential parameter name clashes, KVP employs response[f] and response[prefer].
For sake of consistency, should response[profile] be used instead of https://github.com/opengeospatial/ogcapi-processes/blob/master/core/requirements/query-param-profile/REQ_definition.adoc?
Another potential disambiguation that response[profile] would provide is between different responses, as in async case. If running KVP with:
?...
&response=collection
&response[prefer]=respond-async
&response[profile]=stac
&profile=openeo
We could obtain an openEO-aligned job status response with the resulting output being a Collection Output that adheres to STAC metadata.
Without a response[profile]/profile distinction, they cannot be requested at the same time.
To avoid(reduce) potential parameter name clashes, KVP employs
response[f]andresponse[prefer].For sake of consistency, should
response[profile]be used instead of https://github.com/opengeospatial/ogcapi-processes/blob/master/core/requirements/query-param-profile/REQ_definition.adoc?Another potential disambiguation that
response[profile]would provide is between different responses, as in async case. If running KVP with:We could obtain an openEO-aligned job status response with the resulting output being a Collection Output that adheres to STAC metadata.
Without a
response[profile]/profiledistinction, they cannot be requested at the same time.