Uh oh!
There was an error while loading. Please reload this page.
Release 0.7.0 - #68
Merged
Merged
Conversation
Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
Test with mypy --strict
References: * [ONT-410] Release CASE 0.7.1 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
References: * [ONT-410] Release CASE 0.7.1 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
References: * [ONT-410] Release CASE 0.7.1 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
Add CASE 0.7.1
A follow-on patch will regenerate Make-managed files. References: * ucoProject/UCO#430
References: * ucoProject/UCO#430 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
Use URIRefs for Facets
References: * [ONT-295] Release CASE 1.0.0 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
UCO Issue 393 added a test that assumed a file's existence during the UCO CI. That file is the UCO monolithic build, a purposefully Git- ignored build artifact. `case-utils` currently repurposes the UCO `pytest` script to ensure UCO's tests also pass when substituting the monolithic build of CASE. With Issue 393, the file reference to the UCO monolithic build needs to be handled downstream in `case-utils`. This patch adds that file by making a copy as a Git-ignored file. (A soft link could cause potential confusion due to management of the modification timestamp on the monolithic build file.) References: * ucoProject/UCO#393 * [ONT-295] Release CASE 1.0.0 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
A follow-on patch will regenerate Make-managed files. References: * ucoProject/UCO#430 * [ONT-295] Release CASE 1.0.0 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
References: * ucoProject/UCO#430 * [ONT-295] Release CASE 1.0.0 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
This patch is code motion, and has no effect on test results. Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
This patch also incorporates all necessary changes to get tests to pass. A follow-on patch will regenerate Make-managed files. References: * [ONT-295] Release CASE 1.0.0 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
References: * [ONT-295] Release CASE 1.0.0 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
Unfortunately, CASE's doesn't yet pass `mypy --strict`. References: * ucoProject/UCO#478 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
Add CASE 1.0.0
It's unclear what causes these to appear, but it is believed to be something between UCO Issue 435 where `rdf:List`s became fully duplicated in SHACL shapes, the recent release of rdflib 6.2.0, and/or potentially a bug in the rdf-toolkit normalization. References: * ucoProject/UCO#435 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
This is a downstream application of the intent of UCO Issue 424, removing an early implementation of glom_graph. References: * ucoProject/UCO#424 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
RDFS and OWL are receiving aliases for in-common spelling in adopters' code. OWL also specifically got further support in some UCO issues. This patch also adds a `Namespace` for the import of the Collections Ontology, and the new UCO namespace `configuration`. References: * ucoProject/UCO#389 * ucoProject/UCO#406 * ucoProject/UCO#432 * ucoProject/UCO#437 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
Replace glom_graph.py with rdfpipe
Add RDFS, OWL, and other Namespaces new to UCO 1.0.0
Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.