Skip to content

Add validation command to CASE-Utilities-Python #21

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

Merged
merged 13 commits into from
Nov 2, 2021
Merged

Conversation

ajnelson-nist
Copy link
Member

No description provided.

References:
* [AC-210] Add validation command to CASE-Utilities-Python

Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
@ajnelson-nist
Copy link
Member Author

@plbt5 , you had expressed a desire to review the interface of this command at the last Adoption Committee meeting. Do you have any revisions you think are necessary? If you don't want to review all of the code, at least the new section of README.md, and possibly the two Makefiles at tests/case_utils/case_validate/*/Makefile might be helpful.

The output of case_validate --help is currently as follows:

usage: case_validate [-h] [-d] [--built-version {none,case-0.5.0}] [--ontology-graph ONTOLOGY_GRAPH] [--abort] [-w] [-f {human,turtle,xml,json-ld,nt,n3}] [-im]
                     [-i {none,rdfs,owlrl,both}]
                     in_graph

CASE wrapper to PySHACL command line tool.

positional arguments:
  in_graph

optional arguments:
  -h, --help            show this help message and exit
  -d, --debug           Output additional runtime messages.
  --built-version {none,case-0.5.0}
                        Monolithic aggregation of CASE ontology files at certain versions. Does not require networking to use. Default is most recent CASE release.
  --ontology-graph ONTOLOGY_GRAPH
                        Combined ontology (i.e. subclass hierarchy) and shapes (SHACL) file, in any format accepted by rdflib recognized by file extension (e.g. .ttl). Will
                        supplement ontology selected by --built-version. Can be given multiple times.
  --abort               (As with pyshacl CLI) Abort on first invalid data.
  -w, --allow-warnings  (As with pyshacl CLI) Shapes marked with severity of Warning or Info will not cause result to be invalid.
  -f {human,turtle,xml,json-ld,nt,n3}, --format {human,turtle,xml,json-ld,nt,n3}
                        (ALMOST as with pyshacl CLI) Choose an output format. Default is "human". Difference: 'table' not provided.
  -im, --imports        (As with pyshacl CLI) Allow import of sub-graphs defined in statements with owl:imports.
  -i {none,rdfs,owlrl,both}, --inference {none,rdfs,owlrl,both}
                        (As with pyshacl CLI) Choose a type of inferencing to run against the Data Graph before validating. Default is "none".

@ajnelson-nist
Copy link
Member Author

Curious. e1b93f6 didn't give me any trouble in my local environment. I probably won't be able to look at that before Tuesday, unfortunately.

References:
* [AC-210] Add validation command to CASE-Utilities-Python
* [ONT-445] (CP-38) rdf-toolkit base-iri flag degenerates versionIRI
  when slash IRI form is used

Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
References:
* [AC-210] Add validation command to CASE-Utilities-Python

Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
References:
* [AC-210] Add validation command to CASE-Utilities-Python

Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
The first tests to confirm `case_validate` functionality are
reproduction of the CASE and UCO ontology repositories' `pyshacl` test
results.

References:
* [AC-210] Add validation command to CASE-Utilities-Python

Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
References:
* [AC-210] Add validation command to CASE-Utilities-Python

Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
References:
* [AC-210] Add validation command to CASE-Utilities-Python

Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
@ajnelson-nist
Copy link
Member Author

The issue was Java 11 was being used by the Github Actions environment. Applying the OC-164 revision (4a42714) fixed that issue.

One other revision has been made since the original PR, around making the ontology files not rebuild on each top-level make clean ; make run.

@ajnelson-nist ajnelson-nist self-assigned this Oct 29, 2021
References:
* [AC-210] Add validation command to CASE-Utilities-Python

Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
References:
* [AC-210] Add validation command to CASE-Utilities-Python

Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
References:
* [AC-210] Add validation command to CASE-Utilities-Python

Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
References:
* [AC-210] Add validation command to CASE-Utilities-Python

Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
References:
* [AC-210] Add validation command to CASE-Utilities-Python

Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
@ajnelson-nist ajnelson-nist merged commit 0106422 into develop Nov 2, 2021
@ajnelson-nist ajnelson-nist deleted the AC-210 branch November 2, 2021 20:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant