The requirement mentions:
|
[.component,class=part] |
|
-- |
|
The name of this URI query parameter SHALL be the identifier of the corresponding process input as defined in the <<sc_process_description,process description>>. |
|
-- |
|
|
|
[.component,class=part] |
|
-- |
|
The name of this URI query parameter SHALL be case in-sensitive. |
|
-- |
If an input is named myInput or DATA_INPUT, it cannot simultaneously respect being the ID defined in the process description and allow case-insensitive name.
Because these query parameters refer specifically to certain IDs, they should instead be case-sensitive.
At best, there could be a permission allowing servers to let case-insensitive auto-resolutions, but I think it makes more sense to require case-sensitive matching for robustness, since KVP can be mapped to the equivalent JSON content more reliably. A server that wants to enforce this robust ID match should be allowed to refuse the request and respond with 400 Bad Request or similar.
The requirement mentions:
ogcapi-processes/core/requirements/kvp-execute/REQ_input-query-parameters.adoc
Lines 13 to 21 in 638340b
If an input is named
myInputorDATA_INPUT, it cannot simultaneously respect being the ID defined in the process description and allow case-insensitive name.Because these query parameters refer specifically to certain IDs, they should instead be case-sensitive.
At best, there could be a permission allowing servers to let case-insensitive auto-resolutions, but I think it makes more sense to require case-sensitive matching for robustness, since KVP can be mapped to the equivalent JSON content more reliably. A server that wants to enforce this robust ID match should be allowed to refuse the request and respond with 400 Bad Request or similar.