These duplicated relations are an artifact of OBO-Edit's saving of combined ontology files, or perhaps the OORT tool, and unfortunately require hand editing to eliminate, which does not always occur as part of the release process. In any case, I believe this is a relatively minor problem as the relations are equivalent. If I am involved in the next release of CL, I will try to ensure no duplicate relations are present.
Thanks,
Alex
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the reply Alex. It is an issue as even though the relations are semantically equivalent, they have different URIs. Which means if I use one in my query I won't retrieve axioms using the other, and I won't be able to query across resources.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Status: open Group: GO-Cell-XP Labels: obsoletion request Created: Thu May 31, 2012 09:51 PM UTC by Melanie Courtot Last Updated: Thu May 31, 2012 09:51 PM UTC Owner: Alexander Diehl
CL has
- two 'part_of' relations: a BFO one and a PRO one
- two 'derives_from': one from CL one from PRO
- two 'regulates'
Hi Melanie,
These duplicated relations are an artifact of OBO-Edit's saving of combined ontology files, or perhaps the OORT tool, and unfortunately require hand editing to eliminate, which does not always occur as part of the release process. In any case, I believe this is a relatively minor problem as the relations are equivalent. If I am involved in the next release of CL, I will try to ensure no duplicate relations are present.
Thanks,
Alex
Thanks for the reply Alex. It is an issue as even though the relations are semantically equivalent, they have different URIs. Which means if I use one in my query I won't retrieve axioms using the other, and I won't be able to query across resources.
Can you close this? Fixed some time ago
On 2 Dec 2014, at 13:05, Nicole Vasilevsky wrote:
Related
Cell Ontology (CL) requests:
#198Closing, per Chris' request. :)