-
Notifications
You must be signed in to change notification settings - Fork 58
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
Version 2.0 IRIs do not resolve as URLs #549
Comments
@mark-jensen Your sentence:
explicitly states something everyone needs to know: how to use CCO. The README file should state, in no uncertain terms, that CCO v2.0 currently has to be used by downloading its modules, not by trying to reference it via URLs. I'm assuming, from the way you wrote, that a solution isn't imminent. Even if it's as little as a month away, users should be aware of how to use CCO now. And when the solution is implemented, the README file should explain it. If you are too busy, I'll submit something. Just let me know. |
@swartik I updated the main readme and linked to this issue. Thanks. I plan to start a discussion about the use cases for having resolvable IRIs. I'll tag you when ready and look forward to hear about how and why you use CCO via web vs downloading. |
I look forward to having the IRIs be dereferencable again. |
The new IRIs in v2.0 do not resolve as URLs to an ontology file via the web. We are woking on a solution that will improve on the previous implementation. Stay tuned. And thanks for your patience.
In the meantime, we encourage you to work with a local copy of CCO by either downloading the merged version of CCO or the full release, or forking or cloning the repository directly to your computer. For most users, we encourage use of the merged version.
v/r
CCO Governance and Development
The text was updated successfully, but these errors were encountered: