Repository navigation
Conversation
This was referenced Jul 11, 2026
jdsika
force-pushed
the
docs/shaclgen-rule-constraints
branch
from
September 11, 2026 12:53
ada76d6 to
5123d41
Compare
jdsika
changed the base branch from
fix/shaclgen-rule-converter-audit-findings
to
feat/shaclgen-compositional-rule-fallback
September 11, 2026 12:53
This was referenced Sep 11, 2026
Author
|
Mirrored upstream as linkml#3991. |
jdsika
force-pushed
the
feat/shaclgen-compositional-rule-fallback
branch
from
October 2, 2026 11:16
59544b4 to
1b1c775
Compare
jdsika
force-pushed
the
docs/shaclgen-rule-constraints
branch
from
October 2, 2026 11:16
5123d41 to
608f99c
Compare
jdsika
force-pushed
the
feat/shaclgen-compositional-rule-fallback
branch
from
October 2, 2026 11:22
1b1c775 to
d035e8c
Compare
jdsika
force-pushed
the
docs/shaclgen-rule-constraints
branch
from
October 2, 2026 11:22
608f99c to
7197a7e
Compare
jdsika
force-pushed
the
feat/shaclgen-compositional-rule-fallback
branch
from
October 6, 2026 17:47
d035e8c to
c89faac
Compare
jdsika
force-pushed
the
docs/shaclgen-rule-constraints
branch
from
October 6, 2026 18:19
7197a7e to
442dd51
Compare
The SHACL generator translates LinkML rules into sh:sparql constraints, but its documentation did not mention them. Describe the two named patterns and the composed translation with the operators it supports, the semantics shared with the JSON Schema generator (presence, every value versus has_member, value comparison, numeric bounds), inheritance, open_world, --no-emit-rules and the skip warnings, with an example generated by the generator. Replace the dangling "See above for implementation status" in the rules section of advanced.md with links to the JSON Schema and SHACL generator pages.
jdsika
force-pushed
the
docs/shaclgen-rule-constraints
branch
from
October 6, 2026 18:20
442dd51 to
6a78f26
Compare
This was referenced Oct 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Mirror of linkml#3991, same head. Review there; this PR tracks the fork stack.
Summary
This PR documents the translation of LinkML rules into SHACL-SPARQL in
docs/generators/shacl.rst, which did not mention it. It also replaces the dangling "See above for implementation status" in the rules section ofdocs/schemas/advanced.mdwith links to the JSON Schema and SHACL generator pages.The new section covers:
has_member;meaning, the boolean lexical forms);open_world,--no-emit-rules, and the rule that a rule is skipped with a warning rather than partially translated;gen-shaclfrom this stack, and what its results report (sh:resultPath,sh:value).Corrections to the earlier version
open_worldis honoured.=, notNOT IN.sh:sparqlconstraints withoutadvanced=True.Verification
gen-shacl, and its documented results were checked with pyshacl.make htmlpasses withSPHINXOPTS="-W --keep-going", as indocs-test.Documentation only.
Upstream stack: linkml#3989 → linkml#3990 → linkml#3991 (docs).
Fork stack: #19 → #20 → #23 (docs); #35 (tests) is also based on #20.