Release 1.0.0 #115
Merged
Release 1.0.0 #115
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
This fix was applied in the same manner as in this UCO commit in support of UCO CP-90: https://github.com/ucoProject/UCO/tree/242d315f9d0d838096c57b76f5d497a75dca0d13 References: * [ONT-467] (CP-43) Vocabulary datatypes are OWL-syntactically incomplete * [UCO OC-192] (CP-90) Vocabulary datatypes are OWL-syntactically incomplete Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
No effects observed on Make-managed files. References: * ucoProject/UCO#424 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
This is a downstream application of two proposals: * UCO CP-100 implemented the suggested-value enforcement pattern for semi-open vocabularies. This was a part of UCO 0.8.0. * UCO Issue 406 adjusted the implementation pattern from UCO CP-100 to account for an OWL requirement on `rdf:List` usage. This has been approved for UCO 1.0.0. A third proposal adjusting the CASE vocabulary namespace, UCO Issue 435, would also apply, but has not had an approval vote yet. Due to vote and other Git logistics, that will be handled separately. No effects were observed on Make-managed files. References: * [UCO OC-12] (CP-100) UCO's idea of "Open vocabulary" does not agree with its implementation with owl:oneOf * ucoProject/UCO#406 * ucoProject/UCO#435 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
This is a preparation for UCO Issue 387, where a third level of subdirectory depth was added. Before the UCO Git submodule pointer is updated to incorporate UCO Issue 387's resolution, the `/bin/ls` command will emit that one of its shell wildcards didn't work, and the command will exit 0. This does not fail the Make process. To avoid complexities with Git merging, the UCO submodule pointer is not updated in this patch. The Makefile shell recipe declines to use `find` due to potentially incorporating CI artifacts. References: * ucoProject/UCO#387 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
This is a downstream adoption of UCO Issue 406. The Git submodule is updated to the earliest state necessary to make use of the OWL SHACL tests. No effects were observed on Make-managed files. References: * ucoProject/UCO#406 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
A follow-on patch will fix a realized copy-paste error in the CASE implementation of the new vocabulary form. No effects were observed on Make-managed files. References: * [ONT-467] (CP-43) Vocabulary datatypes are OWL-syntactically incomplete * ucoProject/UCO#435 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
This patch corrects a nesting error in the original application of the syntax form. The syntax form now matches the form implemented in the resolution of UCO Issue 435. No effects were observed on Make-managed files. References: * [ONT-467] (CP-43) Vocabulary datatypes are OWL-syntactically incomplete * ucoProject/UCO#435 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
Replace UCO glom_graph.py reference with rdfpipe
Apply semi-open vocabulary patterns
Adapt for UCO files being under different directories
Drop IRI base
Add OWL 2 DL review with SHACL-SPARQL
Fix OWL syntax of CASE datatype
Feature issue 98
Added Changes merged at 2022-08-22 & -23, sourced from Merge PR's since 2022-06-17.
Update ChangeLog
Remove Legacy Requirements
References: * #106 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
Bump UCO pointer to current state of develop
This patch intentionally does not bump CASE's version declaration. Instead, the minimum effects on CASE are implemented to get CI to continue to pass: updating UCO version IRI references. References: * ucoProject/UCO#437 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
References: * ucoProject/UCO#437 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
This will show when the tests become too stringent. References: * ucoProject/UCO#437 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
References: * ucoProject/UCO#437 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
A follow-on patch will regenerate Make-managed files. References: * ucoProject/UCO#430 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
References: * ucoProject/UCO#430 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
Conflict resolution for the UCO submodule pointer was to track the `develop` state after merging UCO PR 483. References: * ucoProject/UCO#483
Release 0.7.1 develop
References: * ucoProject/UCO#437 * ucoProject/UCO#484 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
UCO Issue 437: Use owl:versionIRI and owl:priorVersion for CASE 1.0.0
References: * ucoProject/UCO#430 * ucoProject/UCO#467 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
Adopt graph-individual identification using IRI form
References: * [OC-44] UCO Version 1.0.0 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
|
Merging with matching rationale to this comment. |
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.
No description provided.