OBOFoundry / Operations-Committee-RETIRED

Automatically exported from code.google.com/p/obo-foundry-operations-committee
1 stars 0 forks source link

CHMO and BFO links on obofoundry table #143

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Dear obo-admin,
    I found some broken links in the ontology listings.

Page: http://www.obofoundry.org/cgi-bin/detail.cgi?id=CHMO
Correct owl: http://rsc-cmo.googlecode.com/svn/trunk/cmo-xp.owl
Correct obo: http://rsc-cmo.googlecode.com/svn/trunk/cmo-xp.obo

Page: http://www.obofoundry.org/cgi-bin/detail.cgi?id=bfo
Correct owl: http://bfo.googlecode.com/svn/releases/2014-05-03/owl-group/bfo.owl
I was not able to find it in obo format..

Best regards,
Daniele

-- 
Daniele Paganelli, Ph.D.
Researcher
Expert System Solutions S.r.l.
Via Virgilio 58/L - 41100 Modena (ITALY)
Tel: +39 0598860020 - Fax: +39 0598860024
Email: d.paganelli@expertsystemsolutions.it
Web: www.expertsystemsolutions.it

Original issue reported on code.google.com by mcour...@gmail.com on 25 Jun 2014 at 5:26

GoogleCodeExporter commented 9 years ago
CHMO: sent email to Colin to redirect OWL PURL and create OBO one.

BFO: need to check ontologies.txt to see where the links disappeared....

Original comment by mcour...@gmail.com on 25 Jun 2014 at 5:26

GoogleCodeExporter commented 9 years ago
Correct OWL for BFO would be http://purl.obolibrary.org/obo/bfo.owl
I think, in general, that we want to consistently point to the purl IRIs

Original comment by alanruttenberg@gmail.com on 27 Jun 2014 at 5:29

GoogleCodeExporter commented 9 years ago
We do use the PURLs: in the case of CHMO I suspect a case of developers 
changing the file name and not updating the corresponding PURL, but am waiting 
for Colin to confirm.
For BFO the current version in the obofoundry table is 1.1 rather than 2.0, so 
we could either replace it with 2.0 or create a new entry for the latter. Note 
that this raises the issue of which version is the "official" one, maybe 
something that the group as a whole should address?

Original comment by mcour...@gmail.com on 27 Jun 2014 at 4:19

GoogleCodeExporter commented 9 years ago
Hello,

Don't seem to have replied to this; apologies!

I'm afraid I've lost my OCLC password again (office move, change of computer, 
only website in universe that doesn't have a "forgotten password" mechanism) so 
I can't check what the PURLs are until someone at OCLC gets back to me. If they 
point to:

https://code.google.com/p/rsc-cmo/source/browse/trunk/chmo.obo
https://code.google.com/p/rsc-cmo/source/browse/trunk/chmo.owl

then all is well.

Colin.

Original comment by batchelorc@rsc.org on 4 Jul 2014 at 10:51

GoogleCodeExporter commented 9 years ago
I created a PURL for the ono:

id: /obo/chmo.obo Modify record Show history
type: 302
target: http://rsc-cmo.googlecode.com/svn/trunk/chmo.obo

The owl one was correct, but as mentioned in the initial post the files had 
been renamed in the googlecode. Should all be sorted out for CHMO :)

Original comment by mcour...@gmail.com on 4 Jul 2014 at 4:29

GoogleCodeExporter commented 9 years ago
Closed. Emailed Daniele (OP) for status update.

Original comment by mcour...@gmail.com on 23 Jul 2014 at 11:08