search

MICommunity / psimi

Automatically exported from code.google.com/p/psimi
Creative Commons Attribution 4.0 International
5 stars 3 forks source link

Fix imports in psi-mi #17

Closed cmungall closed 8 years ago

cmungall commented 8 years ago

See https://github.com/owlcs/owlapi/issues/523

You should always use purls for imports, e.g

import: http://purl.obolibrary.org/obo/pato.obo import: http://purl.obolibrary.org/obo/uo.obo

In fact we recommend that these are OWL.

import: http://purl.obolibrary.org/obo/pato.owl import: http://purl.obolibrary.org/obo/uo.owl

You can use an OboEdit catalog to have OE resolve these to a local obo cache. But really you should stop using OE, we do not support it any more. Contact me if you have problems

colin-combe commented 8 years ago

This PSI-MI project is not really in use, and something should be done with it to stop it continuing to be a source of confusion. This PSI-MI project was only used to extract everything from google code.

Is https://github.com/MICommunity/PSI-JAMI the project that the issue you mention applies to?

I suggest moving this PSIMI project somewhere rather than deleting it? It preserved the revision history whereas some of the other moves from google code haven't.

cmungall commented 8 years ago

Looks like it should have actually been psi-ms...

On 10 May 2016, at 1:08, Colin wrote:

This PSI-MI project is not really in use, and something should be done with it to stop it continuing to be a source of confusion. This PSI-MI project was only used to extract everything from google code.

Is https://github.com/MICommunity/PSI-JAMI the project that the issue you mention applies to?

I suggest moving this PSIMI project somewhere rather than deleting it? It preserved the revision history whereas some of the other moves from google code haven't.

You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/MICommunity/psimi/issues/17#issuecomment-218087401