opengeospatial / opengeospatial/bblocks
Remove status information from bblock names
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 4
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
bblocks should not have status in names e.g. "unstable" - that alone makes them unusable.
The tooling now supports reference resolution according to a configurable sub-register import list, meaning they can move from register to register according to status.
NB. OAS 3.0 down-compiled schemas will need to be republished as they are limited to absolute URIs but 3.1 with relative links can be re-used directly from a new location. (Further engineering testing in testbeds is recommended)
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
Start by reviewing the bblock naming conventions and the tooling's configurable sub-register reference resolution. Check the OAS 3.0 and 3.1 schema handling described in the issue, including the need to republish down-compiled schemas. Done means status terms are removed from bblock names and the affected schemas remain usable from their intended locations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100