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.

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

Vocabulary versioning? #43

Open
awagner-mainz opened this issue Oct 7, 2019 · 3 comments
Open

Vocabulary versioning? #43

awagner-mainz opened this issue Oct 7, 2019 · 3 comments

Comments

@awagner-mainz
Copy link

Would it make sense to provide a mechanism for vocabulary versioning like described here?: NatLibFi/Skosmos#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.

@acka47
Copy link
Member

acka47 commented Nov 7, 2019

Thanks for the input and please excuse the belated response. Here are the requirements from NatLibFi/Skosmos#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.

@awagner-mainz
Copy link
Author

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

@acka47
Copy link
Member

acka47 commented Nov 20, 2020

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backlog
Development

No branches or pull requests

2 participants