opengeospatial / opengeospatial/CoverageJSON
Migration to full OGC Standard 3: Migrate documentation from ASCIIDoc to Metanorma
Nobody has claimed this yet.
- 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:
3. Use the OGC Standard ASCIIDoc/Metanorma template. This is 80% done. We would need to clarify and number Requirements, Recommendations and Permissions, and agree conformance classes for how the Requirements should be grouped.
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
No file or test is named. Start by locating the current ASCIIDoc/Metanorma documentation and compare it with the OGC Standard template; done means Requirements, Recommendations, and Permissions are clarified and numbered, with agreed conformance classes grouping the Requirements.
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