-
Notifications
You must be signed in to change notification settings - Fork 59
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
Need documentation on how to go from 1.4 to 2.0 #556
Comments
This was helpful, but it is insufficient for upgrading from versions 1.3 thru 1.6, to 2.0 |
It looks like the RO-ERO document is in .github -> Deployment -> Mappings |
Thanks, @CarterBeauBenson this was not obvious from the readme.md . Very helpful! Outstanding: further clarifications on how to update sequentially? |
The mapping file can be found via a link on the wiki page I created that describes for mapping between v1.4 to v1.5. The link was broken in the repo restructuring we recently did. Now fixed.
In general, for updating extensions of CCO to newer versions, I would start with a look at the release notes for each version of CCO. They provide details about any axiomatic changes to IRIs, new IRIs, and deleted IRIs. If you need more than this, please describe the extra documentation you think should be included for releases. If not, please close this issue. Also: note that we provide ROBOT-generated diff files for each release. |
Documentation request
In 1.4 to 1.5, there was a shift with using BFO instead of RO. The file "ro-ero-to-bfo2020.csv" can no longer be found. I saved it locally, but it should be findable. Anyone who hasn't updated from 1.4 to 1.5 in the last 9 months would need this.
This leads to a broader point. Since different users in the last year have been adopting 1.6, 1.7 and 2.0 in sequence (and slowly), there should be clearer documentation on how to make sure ontologies dependent on CCO don't break because they have made the necessary changes.
Could you, for example, provide a strategy for finding deprecated terms, identifying the version in which they were deprecated, so that as people develop they can ensure a smooth transition to 2.0?
The text was updated successfully, but these errors were encountered: