-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ont 251 #41
Ont 251 #41
Conversation
This patch adds Makefiles that confirm CASE ontology Turtle files are normalized according to the command specified in NORMALIZING.md. Usage: * `make` - does nothing. Nothing in the ontology currently depends on executing code to build a component. * `make check` - downloads `rdf-toolkit.jar` to the `/lib` directory in this repository, if not already present, and checks that ontology files match the output of `rdf-toolkit.jar` running against them. - `make check`, or `make .lib.done.log`, needs to be called in the root directory of this repository at least once. After that, `make check` will work in any directory at or under `/ontology`. The hash of `rdf-toolkit.jar` will be recorded in the Git history in the next commit, with a timestamp indicating when I first encountered this hash. This patch begins a resolution of ONT-251. References: * [ONT-251] Establish unit tests, possibly Continuous Integration, for ontology repository Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
The timestamp of this hash is copied from my first record of the hash published in the CASE-Examples-QC repository [1]. This is a "Trust on first use"---aka "TOFU" [1]---record, and makes no assertions on qualities of the file aside from this being the hash I recorded on first downloading it. References: [1] https://github.com/ajnelson-nist/CASE-Examples-QC/ [2] https://en.wikipedia.org/wiki/Trust_on_first_use Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
This was tested by deleting the jar file and running `make clean && make && make check` from the repository root. Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
This encodes `make check` as the mechanism for running tests. Tests are as specified in NORMALIZE.md. References: * [ONT-251] (CP-16) Establish unit tests, possibly Continuous Integration, for ontology repository Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
This workflow file was started as a copy of the CASE website repository's CI script. I forgot to update the name. Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
This ports a change tested in the CASE-Examples-QC repository: ajnelson-nist/CASE-Examples-QC#1 References: * [ONT-383] Find alternative retrieval point for rdf-toolkit.jar Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
One of the maintainers on the rdf-toolkit Github repository had committed the built jar we were using into another repository. I confirmed that the SHA-512 of this file matches what was recorded in the CASE repository. This patch implements a fallback download pattern, favoring downloading from Github, and then from files.caseontology.org. References: * [ONT-383] Find alternative retrieval point for rdf-toolkit.jar Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
References: * [ONT-251] (CP-16) Establish unit tests, possibly Continuous Integration, for ontology repository A link to the proposal file will be added to ChangeLog before the CASE 0.3.0 release. Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
This address conflicts in the Changelog file.
We seem to have a configuration error where I can't review this PR. Please consider this PR passing my review, and merge when you are ready, @plbt5 . |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm too ignorant on continuous integration to assume a viable review performed by me. Notwithstanding my ignorance I'll sign-off the PR ...
No description provided.