opengeospatial / opengeospatial/ogcapi-features
"Other parts" section ...
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 386
- Forks
- 92
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 15
Description
It might be a good idea to, in each part of a multi-part standard, include an "Other parts" section that points to the other parts of the standard. For example, looking at OGC API Features - Part 1 - Core I can infer there are mutliple parts (from the "Part 1") and there is some mention in the text that other parts exist BUT there is no explicit section that references the other parts. This should be a section near the front of the document so that someone looking at it can see that there is also a Part 2 for CRS handling, a Part 3 (when it becomes a standard) for filtering, a Part 4 (when it becomes a standard) for transactions, etc.
Although OGC has gone to great length to create pages on the OGC site that links these parts together I think it would be a good idea if the related parts where themselves cross-linked somehow in a very explicit and obvious way.
Contributor guide
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 files or tests are named in the issue. Start by locating the document sources for the multi-part OGC API Features standard and checking how its introductory sections are organized. Done means each relevant part explicitly links to the other parts, including planned parts where appropriate.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100