opengeospatial / opengeospatial/CoverageJSON
Can we separate the specification text into normative or informative?
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 15
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
OGC Standard documents usually have a background in-depth description in Section 6, followed by normative text in Section 7.
Is this too much work? The current spec seems to have normative and informative text completely intermingled.
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 CoverageJSON specification's Sections 6 and 7 and inventory which passages are normative versus informative. Establish the intended section boundaries, then update the specification so the two kinds of text are separated; done means the rendered document clearly distinguishes them without losing content.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100