Inconsistent parameter names across the specification

[fmigneault]

There are multiple variations of parameter naming conventions employed across different documents:

• jobID, jobId, job-id
• processID, processId, process-id
• outputID, output-name, "output name"
• inputID, input-name, "input name"

The specific convention employed does not matter that much, but it should be somewhat consistent across the specification, just to facilitate referencing to them.

[jerstlouis]

@fmigneault Note that there are different OGC API conventions for JSON schemas (camelCase) vs. query parameters (kebab-case).

See opengeospatial/ogcapi-common#224 (comment)

Not sure which kind of "parameters" you are referring to here.

Are these all path parameters as in OpenAPI? I would suggest {processId} as the convention for these.
So:

• processId: JSON object property
• {processId}: path parameter
• process-id: query parameter

[fmigneault]

I was referring to the path parameters.
All mentioned variants are observed across the various OpenAPI/Markdown/AsciiDoc documents.