opengeospatial / opengeospatial/ogcapi-processes
Align openEO and OAP job link relation type `monitor`
Open
Nobody has claimed this yet.
Part 4 (Job Management)
- Dominant language
- AsciiDoc
- Stars
- 63
- Forks
- 46
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 8
Description
> In openEO we use the relation type `monitor` for logs...
This seems like another incompatibility with OGC API - Processes that uses rel=monitor for the job itself: https://docs.ogc.org/is/18-062r2/18-062r2.html#req_core_job-results-success-sync
Originally posted by @fmigneault in https://github.com/opengeospatial/ogcapi-processes/issues/419#issuecomment-2397139595
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 by reading the linked OGC API - Processes job-results requirement and compare its rel=monitor meaning with the openEO use for logs. Determine the intended relation semantics and update the relevant specification text so the openEO and OGC API - Processes descriptions are consistent.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100