Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

openapi.json specification does not include jobList parameters #410

Open
mike-gangl opened this issue May 9, 2024 · 2 comments
Open

openapi.json specification does not include jobList parameters #410

mike-gangl opened this issue May 9, 2024 · 2 comments
Assignees
Labels

Comments

@mike-gangl
Copy link

I made the same comment on another's issue: #408 (comment)

The Job List (/jobs) endpoint contains query parameters that allow for the filtering of jobs based on

  • type
  • process_id
  • status
  • datetime
  • minDuration
  • maxDuration
  • limit

yet none of these are included in the openapi.json spec included in this repository. What's the best path forward for including those? The previous wps specification had the /processes/{process_id}/jobs endpoint for filtering based on the Process ID- i prefer this new filtering on all jobs method, but was unable to use the openapi.json files to create the appropriate endpoints.

@fmigneault
Copy link
Contributor

They are not part of the schema because they are considered "extensions" of the minimal functionalities required by "Core".

See https://docs.ogc.org/is/18-062r2/18-062r2.html#toc9

The main requirements class is:

The Core specifies requirements that all Web APIs have to implement.

Three additional conformance classes are specified that extend the basic functionality of an API:

One has to look at the /conformance endpoint and see if the server indicates that it supports
http://www.opengis.net/spec/ogcapi-processes-1/1.0/conf/job-list to expect these filtering parameters to be respected.

@bpross-52n
Copy link
Contributor

SWG meeting from 2024-06-10: This needs to be fixed in the schema. This also applies to the process list. We need to include the parameters in the paths. We also need to check the other parts of the standard.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

4 participants