opengeospatial / opengeospatial/ogcapi-processes
Part 4: Clarify /req/job-management/definition-get-op
Nobody has claimed this yet.
- Dominant language
- AsciiDoc
- Stars
- 63
- Forks
- 46
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 8
Description
What is the definition meant to return? The process? (e.g. CWL or openEO UDP?)
We include that directly in GET /jobs/:id - I guess that's fine and we can add an additional endpoint, but maybe this is more an optional endpoint for cases where a definition can't be embedded? And it can be explored via a link in GET /jobs/:id?
What is POST /jobs/:id?
Originally posted by @m-mohr in https://github.com/opengeospatial/ogcapi-processes/pull/437#discussion_r1789875331
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with /req/job-management/definition-get-op and read the linked discussion from pull request #437. Compare the questions about GET /jobs/:id, the proposed additional definition endpoint, and POST /jobs/:id with the surrounding job-management requirements. Done means the intended behavior and endpoint relationships are resolved and documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100