-
Notifications
You must be signed in to change notification settings - Fork 8
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
DINTO purl does not resolve #1
Comments
Dear Chris, Thank you for pointing this out. We will try to overcome these issues as soon as possible. I would be very grateful if you could tell me about the service you suggest for the ontology. Thanks, |
You can see how to register your ontology for the OBO central build here: http://obofoundry.org/faq/what-is-the-build-field.html This sounds a bit convoluted, but we could set up a job on our jenkins server that upacks the zip... but I think we need to find you a more scalable approach. You want to be able to manage your files in github without zipping them. I recommend modularization. |
For hints on how to structure your github repo, see also https://douroucouli.wordpress.com/2015/12/16/creating-an-ontology-project-an-update/ |
Is DINTO still maintained? |
Hi Chris, Yes, it is. How can I help you? Maria On 4 October 2016 at 21:38, Chris Mungall [email protected] wrote:
|
Hi Maria,
Currently the OBO purl is not resolving. Can you provide a stable URL
(for example, a raw github URL) that resolves to the latest version of
your ontology?
|
We will have to remove DINTO from OBO unless this is fixed |
Hi Chris, Cheers, |
Any progress on this? |
Hi Maria, any update on this? |
Hi, we have a number of problems with this ontology for the OBO registry and its downstream applications, see: OBOFoundry/OBOFoundry.github.io#208
For 2, there needs to be a URL from which an (unzipped) RDF/XML-OWL version of the ontology can be obtained. I note that your ontology is too large to fit into github unzipped. I can provide a service that will serve up the correct file from your github if you like.
Not required by OBO, but I recommend that you don't keep different versions of your ontology checked in to github in different folders. Git and GitHub have excellent versioning and release mechanisms I recommend using them. There are a number of different workflows here, but the simplest is that you keep the working version on master and then click on the "release" button on github when you want to make a release.
The text was updated successfully, but these errors were encountered: