I was more curious about the versioning and tagging mechanisms that Protege
supports out-of-the-box. Given your first recommendation, is it correct to
say that Protege does NOT support versioning and tagging out-of-the-box and
that this functionality will have to be provided by other tools?
There have been some versioning related plugins in the past. For example there is an ontology diff plugin. I don’t know of anything that has allowed tagging though. To me this implies some sort of version control repository.
My advice to use GitHub is based on the fact that it’s successfully being used for other ontologies and because it’s an off the shelf, robust solution for this. We also have plans to support some kind of further integration with Git and GitHub, so that you can see diffs for entities in the UI etc.
If you’re able to use or try out WebProtege, it has a simple change tracking system where the complete history is tracked for a project and you can download a project as it was at any time in the past. You can see who has done what and you can revert changes. A current limitation is that WebProtege doesn’t have any kind of branching support though. You should at least take a look at it though and see if it meets your needs.