New issue 118 by MBrochhausen: IAO not accesible using Protege (at least on
a pc)
http://code.google.com/p/information-artifact-ontology/issues/detail?id=118
Hi
since this morning I am unable to import iao into an ontology from my
desktop pc.
Is this know? Does anyone know the reason for the problem?
Best,
Mathias
Comment #1 on issue 118 by MBrochhausen: IAO not accesible using Protege
(No comment was entered for this change.)
After enquiring about specifics with Matthias, he mentioned it was a problem with his desktop pc and the file he created, before closing the issue.
I tried just now and am able to open http://purl.obolibrary.org/obo/iao.owl with no issue, using P4.1 on a mac osx machine.
Could you give us more details about what you are trying to do, and/or send me any specific file, so that I can see if I can reproduce the issue?
Cheers,
Melanie
> --
> informatio...@googlegroups.com
> To change settings, visit
> http://groups.google.com/group/information-ontology
---
Mélanie Courtot
MSFHR/PCIRN trainee, TFL- BCCRC
675 West 10th Avenue
Vancouver, BC
V5Z 1L3, Canada
I am able to reproduce your issue on the mac. Opening the IAO file on its own doesn't present any issue, problems start when I try to import IDO for example.
I believe the issue to be caused by IDO and IAO both importing ontology-metadata.owl, but different versions. This creates a problem when Protege tries and load the second one, thus an exception "Could not rename ontology, an ontology by that name already exists"
IDO gets http://purl.obolibrary.org/obo/iao/2010-10-26/ontology-metadata.owl
IAO gets http://purl.obolibrary.org/obo/iao/2009-11-06/ontology-metadata.owl (via iao-main.owl)
OGMS gets http://purl.obolibrary.org/obo/iao/dev/ontology-metadata.owl (directly from the dev trunk)
I tried adding a versionInfo to the 2010-10-26 but that doesn't help.
I need to check what is the expected behaviour when trying to load different versions of the same ontology, and probably contact the Protege team.
As an aside, there are differences between the different versions, such as addition of curation status instances, which are part of a collection, and I expect that to create another set of issues (2 different collections with different instances should create a conflict by saying that 2 instances have to be the same despite being declared disjoint)
I will also try and contact different resources maintainers to get them to homogenize.
This is an interesting issue, and I am not sure how to deal with it; it will mostly depend on what the spec says about multiple versions with same ontology URI.
I'll let you know what I can find, or maybe somebody else has an idea?
Cheers,
Melanie
For those who would like to try, I attach the minimum file reproducing the behavior Mauricio describes.
Melanie