Remove usage of sh:declare #463
Merged
Conversation
This file contains 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
SHACL Specification Section 5.2.1 specifies a "viral" behavior of `sh:declare` throughout an OWL transitive closure. This patch removes usage of `sh:declare` as a matter of lack of authority for non-UCO prefixes. It just so happens the only place this was used was in the introduction of the OWL SHACL review mechanisms of Issue 406. A follow-on patch will regenerate Make-managed files. References: * #406 * #457 Signed-off-by: Alex Nelson <[email protected]>
References: * #406 * #457 Signed-off-by: Alex Nelson <[email protected]>
ajnelson-nist
added a commit
to casework/CASE-Examples
that referenced
this pull request
Aug 19, 2022
No effects were observed on Make-managed files. References: * ucoProject/UCO#463 Signed-off-by: Alex Nelson <[email protected]>
ajnelson-nist
added a commit
to casework/casework.github.io
that referenced
this pull request
Aug 19, 2022
A follow-on patch will regenerate Make-managed files. References: * ucoProject/UCO#463 Signed-off-by: Alex Nelson <[email protected]>
ajnelson-nist
added a commit
to casework/casework.github.io
that referenced
this pull request
Aug 19, 2022
References: * ucoProject/UCO#463 Signed-off-by: Alex Nelson <[email protected]>
ajnelson-nist
added a commit
to frederich-stine/UCO
that referenced
this pull request
Aug 19, 2022
A pattern implemented in PR 463 is to avoid `sh:declare`, and where prefixes are needed in SHACL-SPARQL queries, to inline a PREFIX clause. This patch removes one instance of `sh:prefixes` that is not addressed by PR 463. References: * ucoProject#435 * ucoProject#463 Signed-off-by: Alex Nelson <[email protected]>
|
Converting to draft while checking for CASE |
|
CI has passed in CASE's |
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.
This is filed as a bugfix Pull Request due to a discovery made in Issue #457 .
SHACL Specification Section 5.2.1 specifies a "viral" behavior of
sh:declarethroughout an OWL transitive closure. This patch removes usage ofsh:declareas a matter of lack of authority for non-UCO prefixes. It just so happens the only place this was used was in the introduction of the OWL SHACL review mechanisms of Issue 406.Coordination
unstablebranch tracking UCO'sunstableas submodule (8f6ffd4)