#429: Have SHACL-SHACL warn about unsatisfiable usage of sh:in
and sh:xone
#451
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.
Closes #429 .
This patch revises part of the implementation in PR 417.
in-minListLength
was not added to the Core document, but it was referenced in SHACL-SHACL. Verbiage is added to Core in line with the text drafted for Issue 429.xone-memberShape
was added as a reference in SHACL-SHACL, but doesn't exist in the Core document.xone-members-node
is the anchor in the Core document.xone-members-node
is now used.PropertyShape
forsh:in
set a minimum required length of 1, which after discussion in Issue 429 appears to be a backward- incompatible change. A shape paralleling the original suggestion forsh:xone
is added to house that new restriction at the same warning- level severity.An implementation style point: The property shapes housing
sh:minListLength
are given IRIs after sketching a test (.../in-003.ttl
) and assuming it would be more desirable to have an IRI-identified shape in the results graph, rather than a blank node.A testing style point: Rather than running SHACL-SHACL over the whole of a test, shapes from SHACL-SHACL are copied into some focused tests (
.../{in,xone}-003.ttl
).