You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 <[email protected]>
1. After cloning this repository, ensure the CASE submodule is checked out. This can be done with either `git submodule init && git submodule update`, `make .git_submodule_init.done.log`, or `make check`.
7
+
2. Update the CASE submodule pointer to the new tagged release.
8
+
3. The version of CASE is also hard-coded in [`case_utils/ontology/version_info.py`](case_utils/ontology/version_info.py). Edit the variable `CURRENT_CASE_VERSION`.
9
+
4. From the top source directory, run `make clean`. This guarantees a clean state of this repository as well as the ontology submodules.
10
+
5. Still from the top source directory, run `make`.
11
+
6. Any new `.ttl` files will be created under [`case_utils/ontology/`](case_utils/ontology/). Use `git add` to add each of them. (The patch-weight of these files could overshadow manual revisions, so it is fine to commit the built files after the manual changes are committed.)
12
+
13
+
Here is a sample sequence of shell commands to run the build:
14
+
15
+
```bash
16
+
# (Starting from fresh `git clone`.)
17
+
make check
18
+
pushd dependencies/CASE
19
+
git checkout master
20
+
git pull
21
+
popd
22
+
git add dependencies/CASE
23
+
# (Here, edits should be made to case_utils/ontology/version_info.py)
24
+
make
25
+
pushd case_utils/ontology
26
+
git add case-0.6.0.ttl # Assuming CASE 0.6.0 was just released.
27
+
# and/or
28
+
git add uco-0.8.0.ttl # Assuming UCO 0.8.0 was adopted in CASE 0.6.0.
29
+
popd
30
+
make check
31
+
# Assuming `make check` passes:
32
+
git commit -m "Update CASE ontology pointer to version 0.6.0" dependencies/CASE case_utils/ontology/version_info.py
33
+
git commit -m "Build CASE 0.6.0.ttl" case_utils/ontology/case-0.6.0.ttl
Copy file name to clipboardExpand all lines: Makefile
+31-3Lines changed: 31 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,13 @@ SHELL := /bin/bash
15
15
16
16
PYTHON3 ?= $(shell which python3.9 2>/dev/null || which python3.8 2>/dev/null || which python3.7 2>/dev/null || which python3.6 2>/dev/null || which python3)
# Confirm the current monolithic file is in place.
61
+
test -r case_utils/ontology/case-$(case_version).ttl
41
62
touch $@
42
63
43
64
check: \
44
-
.git_submodule_init.done.log
65
+
.ontology.done.log
45
66
$(MAKE) \
46
67
PYTHON3=$(PYTHON3) \
47
68
--directory tests \
@@ -52,7 +73,8 @@ clean:
52
73
--directory tests \
53
74
clean
54
75
@rm -f \
55
-
.git_submodule_init.done.log
76
+
.*.done.log
77
+
@# 'clean' in the ontology directory should only happen when testing and building new ontology versions. Hence, it is not called from the top-level Makefile.
Copy file name to clipboardExpand all lines: README.md
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -86,10 +86,9 @@ This project follows [SEMVER 2.0.0](https://semver.org/) where versions are decl
86
86
87
87
## Ontology versions supported
88
88
89
-
This repository supports the CASE ontology version that is linked as a submodule [here](dependencies/CASE). Currently, the ontology versions are:
89
+
This repository supports the CASE ontology version that is linked as a submodule [here](dependencies/CASE). The CASE version is encoded as a variable (and checked in unit tests) in [`case_utils/ontology/version_info.py`](case_utils/ontology/version_info.py), and used throughout this code base, as `CURRENT_CASE_VERSION`.
90
90
91
-
* CASE - 0.5.0
92
-
* UCO - 0.7.0
91
+
For instructions on how to update the CASE version for an ontology release, see [`CONTRIBUTE.md`](CONTRIBUTE.md).
0 commit comments