opengeospatial / opengeospatial/CoverageJSON
Migration to full OGC Standard 4: Switch from IETF normative terminology to ISO terminology
Open
Nobody has claimed this yet.
Editorial
Long Term
Priority 3
- Dominant language
- HTML
- Stars
- 15
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
CoverageJSON spec says use IETF, which allows MUST, MUST NOT, SHALL, SHALL NOT, etc.
OGC normally uses the ISO Directive that states only SHALL and SHALL NOT must be used ;-)
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 locating the CoverageJSON specification text that cites IETF normative terminology. Review its uses of MUST, MUST NOT, SHALL, and SHALL NOT against the ISO Directive, and update the specification so its normative language follows the OGC convention throughout.
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