-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #11 from semanticarts/improve-readme
Fixes #10. Fixes #13 - Greatly improved the README file and tweaked a few annotations. - Fixed an import statement. - Only importing versionIRIs. - Added example annotations
- Loading branch information
Showing
3 changed files
with
34 additions
and
14 deletions.
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,11 @@ | ||
# versioning-ontology | ||
Generic concepts for doing semantic versioning for a suite of artifacts for semantic systems in production. | ||
This ontology represents generic concepts for doing semantic versioning and dependency tracking for a suite of artifacts for semantic systems in production. Versioned artifacts are given semantic version numbers of the form "N.N.N" (as described in https://semver.org/). This ontology provides the ability to state that a particular version of one ontology depends on the semantic version number of another ontology being in a certain range. For example, version 6.3.0 of a disease taxonomy depends on: | ||
1. the version of a disease ontology being at least 3.1.0 and less than 4.0.0. | ||
2. the version of gist core being between at least 12.1.0 and less than 13.0.0. | ||
|
||
The need for specifying such dependencies arises when ontologies use terms from imported ontologies. | ||
|
||
Three SPARQL queries are provided to perform the following tasks: | ||
1. Find all versioned artifacts and their dependencies. | ||
2. Find all cases where a version dependency requirement is not met. Return result in English. | ||
3. Find all cases where a version dependency requirement is not met. Return result as a SHACL report. |
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 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