Project would benefit from clear vision for versioning

I think especially with the new approach of having templates and potentially community templates, this project needs a clear vision on how versioning is going to be performed.
Versioning of ontologies, templates and previously validated files.

Did anyone sketch out what should happen in cases where the community extends existing schemata and then the base schemata are updated. Or when the ontologies for column validators are updated.

The issue names no files, tests, or entry points. Begin by inventorying how ontologies, templates, community extensions, and previously validated files are currently handled; done means an agreed, documented versioning policy covering schema updates and validator ontology updates.

Written by the indexing model from the issue text.