opengeospatial / opengeospatial/bblocks-postprocess
SHACL closure when ref to external container
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 6
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 3
Description
When referencing a more complex containing schema for an example, it may be desirable to include it in the SHACL closure.
This would be tedious and fragile to try to reference an absolute path to a (possibly unpublished) build artefact.
Add the build ttl automatically (unless a flag to suppress) - or better to have a flag to trigger it so its more transparent?
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 at the code path that builds the SHACL closure and inspect how external containers and build TTL artifacts are currently resolved. Run the existing test suite to identify coverage for closure generation; done means external container schemas can be included without absolute unpublished paths, with a clearly defined automatic or configurable trigger.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100