opengeospatial / opengeospatial/CoverageJSON
Migration to full OGC Standard 2: Define an Abstract Test Suite in Annex A
Open
Nobody has claimed this yet.
Long Term
Priority 3
V1.0.0
- Dominant language
- HTML
- Stars
- 15
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
For migration from an OGC Community Standard to a full OGC Standard, several things must happen:
- Define an Abstract Test Suite (ATS) in an Annex A, indicating how the Conformance Classes and their assertions would be tested.
This is mostly done, as most tests would be validation against the CoverageJSON Schema. Some tests could be just by inspection.
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
Review the current CoverageJSON specification, its conformance classes, assertions, and schema before editing. Define Annex A as an Abstract Test Suite, covering schema validation and any assertions that require inspection; done means the standard explains how each conformance requirement would be tested.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100