opengeospatial / opengeospatial/ogcapi-processes
Part 4: jobID vs id and processID vs process
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
process in openEO is an object, so this conflicts.
Generally, make sure that we have in all places the right terms:
- jobID vs id (=> id)
- processID (string) vs process (any)
Originally posted by @m-mohr in https://github.com/opengeospatial/ogcapi-processes/pull/437#discussion_r1789924208
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 the terminology discussion quoted from PR #437 and inventory the specification locations that use jobID/id and processID/process. Apply the requested terminology consistently across the affected locations, then review the API wording to confirm that identifiers and process objects are no longer conflated.
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
- Mostly clear
- Newbie friendliness
- 35/100