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

DINTO purl does not resolve #1

Open
cmungall opened this issue Jan 29, 2016 · 10 comments
Open

DINTO purl does not resolve #1

cmungall opened this issue Jan 29, 2016 · 10 comments

Comments

@cmungall
Copy link

Hi, we have a number of problems with this ontology for the OBO registry and its downstream applications, see: OBOFoundry/OBOFoundry.github.io#208

  1. The DINTO_2 ontology doesn't conform to http://obofoundry.org/id-policy.html - the URI must be all lowercase
  2. The URI for the ontology doesn't resolve

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.

@labda
Copy link
Owner

labda commented Feb 2, 2016

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,
Maria

@cmungall
Copy link
Author

cmungall commented Feb 2, 2016

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.

@cmungall
Copy link
Author

cmungall commented Feb 2, 2016

For hints on how to structure your github repo, see also https://douroucouli.wordpress.com/2015/12/16/creating-an-ontology-project-an-update/

@cmungall
Copy link
Author

cmungall commented Oct 4, 2016

Is DINTO still maintained?

@labda
Copy link
Owner

labda commented Oct 5, 2016

Hi Chris,

Yes, it is. How can I help you?

Maria

On 4 October 2016 at 21:38, Chris Mungall notifications@github.com wrote:

Is DINTO still maintained?


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#1 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ALAI0G7soZEDCI9Yianfd6WsDuMDgodRks5qwrk3gaJpZM4HPRiE
.

@cmungall
Copy link
Author

cmungall commented Oct 7, 2016 via email

@cmungall
Copy link
Author

cmungall commented Dec 1, 2016

We will have to remove DINTO from OBO unless this is fixed

@labda
Copy link
Owner

labda commented Dec 2, 2016

Hi Chris,
I understand. I'll fix it as soon as possible.

Cheers,
Maria

@cmungall
Copy link
Author

Any progress on this?

@cmungall
Copy link
Author

Hi Maria, any update on this?

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

No branches or pull requests

2 participants