opengeospatial / opengeospatial/ogcapi-common
Add Monitoring Function
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 56
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
UVT Comment from API Hackathon ER
Also, UVT suggested extending the Common API to provide monitoring information in an
implementation agnostic way. This would allow various tools to interoperate in a more friendly
manner with OGC compliant services.
Contributor guide
No contributing guide indexed for this repository
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 reviewing the Common API scope and the monitoring request described in this issue. No implementation files, entry points, or tests are identified, so first determine where such a capability belongs and clarify the implementation-agnostic requirements. Done should mean an agreed monitoring function with its expected interoperability behavior defined.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100