Open awagner-mainz opened 5 years ago
Thanks for the input and please excuse the belated response. Here are the requirements from https://github.com/NatLibFi/Skosmos/issues/677:
- Every version of the vocabulary must remain accessible/browsable.
- By default, non-expert users will browse/access the latest version of the vocabulary
- Advanced users can choose which version of the vocabulary they browse
- There is no need to display a precise "diff" between versions
- When looking at a concept page in a given version, we want to know in which other version the concept (with the same URI) is also present, and we want to be able to display another version of the concept.
We will support the first four bullet points when implementing #45. If requested we can then think about adding a link to the same concepts for other git tags.
Also Garijo/Poveda-Villalón recommend this in a certain sense in their "Best Practices for Implementing FAIR Vocabularies and Ontologies on the Web": https://arxiv.org/abs/2003.13084
This should be coupled with the built-in release managment process of GitHub, see https://docs.github.com/en/free-pro-team@latest/github/administering-a-repository/managing-releases-in-a-repository. For each release a the vocab should be built.
Would it make sense to provide a mechanism for vocabulary versioning like described here?: https://github.com/NatLibFi/Skosmos/issues/677
That's just an idea. I'm not sure about it at all (it seems to overlap with what Ilik/Koster are after), and also I am not sure what it would require in terms of github history parsing/mapping... But it seems like a nice thing to have, especially insofar as this is already linked with github.