Following is raising some conflicting ambiguity for output[include] of KVP execute following problems I encountered while attempting to implement it on my end.
Because https://github.com/opengeospatial/ogcapi-processes/blob/master/core/requirements/kvp-execute/REQ_binary-input-value-qualified.adoc allows for the following:
?in[value]={"abc":123}&in[mediaType]=application/json
And that https://github.com/opengeospatial/ogcapi-processes/blob/master/core/requirements/kvp-execute/REQ_output.adoc can use the following:
?out[include]=true&out[mediaType]=image/tif
The only thing that allows differentiating [mediaType] from being applicable to an input or an output is [include]. At first glance when reading the requirements, it is not clear that [include] allows this distinction. I would suggest indicating that explicitly so clients can understand how to disambiguate them, and also why it is necessary to have [include]=true (relates to #552).
However, there is also another problematic case even if using [include] is indicated.
If an input AND output happens to be named the same (e.g.: data), there is no way to provide [mediaType] for both, nor to figure out if [mediaType] applies to the input, the output, or both.
Following is raising some conflicting ambiguity for
output[include]of KVP execute following problems I encountered while attempting to implement it on my end.Because https://github.com/opengeospatial/ogcapi-processes/blob/master/core/requirements/kvp-execute/REQ_binary-input-value-qualified.adoc allows for the following:
?in[value]={"abc":123}&in[mediaType]=application/jsonAnd that https://github.com/opengeospatial/ogcapi-processes/blob/master/core/requirements/kvp-execute/REQ_output.adoc can use the following:
?out[include]=true&out[mediaType]=image/tifThe only thing that allows differentiating
[mediaType]from being applicable to an input or an output is[include]. At first glance when reading the requirements, it is not clear that[include]allows this distinction. I would suggest indicating that explicitly so clients can understand how to disambiguate them, and also why it is necessary to have[include]=true(relates to #552).However, there is also another problematic case even if using
[include]is indicated.If an input AND output happens to be named the same (e.g.:
data), there is no way to provide[mediaType]for both, nor to figure out if[mediaType]applies to the input, the output, or both.