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

Determine convention for naming future releases #8

Open
hlapp opened this issue May 31, 2017 · 1 comment
Open

Determine convention for naming future releases #8

hlapp opened this issue May 31, 2017 · 1 comment
Labels

Comments

@hlapp
Copy link
Contributor

hlapp commented May 31, 2017

In the past CDAO used the release date (as YYYY-MM-DD) for constructing a prefix for owl:versionIRI. There are some problems with that pattern (such as being bare of any compatibility semantics), and there is semantic versioning that is increasingly widely adopted for software.

See thread on obo-discuss for fuller explanation and (hopefully) ensuing discussion.

@hlapp hlapp added the question label May 31, 2017
@hlapp
Copy link
Contributor Author

hlapp commented Jun 27, 2019

It seems that given the prevailing sentiments and conclusions from the thread linked above, and given OBO policy on versioning, we should best stick with the YYYY-MM-DD convention. I therefore propose to close this issue.

If no objections are voiced in the next few days, I'll go ahead and close. I'll leave it unlocked so later comments can be logged, and if justified we can still reopen later.

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

No branches or pull requests

1 participant