Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Added editing policy #51

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Added editing policy #51

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,14 @@ VIVO Ontologies is an open source community. All are welcome to open issues, par

You can contribute using the fork, branch and pull model. Helpful descriptions of the process are available [on the VIVO wiki](https://wiki.lyrasis.org/display/VIVO/Contributing+code+with+a+fork%2C+branches%2C+and+pull+requests).

## Editing policy
* [Protégé](https://github.com/protegeproject/protege-distribution/releases) editing only: Only the following versions of Protégé are permitted for ontology editing in this repository:
* Version 5.6.4
* Updates to the allowed Protégé versions will be posted here.
* No manual editing: Direct manual editing of the ontology file using text editors or any tool other than the specified versions of Protégé is strictly prohibited. Pull requests from manual editing will be asked to be done again in Protégé.

Reason: Manual editing can result in syntax errors or unintended structural changes. Also, using Protégé only results in an owl file that is generated by the particular OWLAPI it uses. Editing and saving the file differently results in a new serialisation, which makes the diff verbose and change checking very difficult. By restricting the use of approved Protégé versions, we ensure the consistency of the ontology.

## Releases
### Semantic Versioning
This ontology adheres to the principles of Semantic Versioning (SemVer) for managing its releases. Semantic Versioning provides a standardized approach for versioning ontologies, allowing users to quickly understand the scope of changes between versions.
Expand Down