You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: