uberon
uberon copied to clipboard
Fix problematic relation URIs
There are several problematic URIs for relationships defined in UBERON:
URI number of edges with this URI
http://purl.obolibrary.org/obo/uberon/core#proximally_connected_to 27
http://purl.obolibrary.org/obo/uberon/core#extends_fibers_into 16
http://purl.obolibrary.org/obo/uberon/core#channel_for 16
http://purl.obolibrary.org/obo/uberon/core#distally_connected_to 13
http://purl.obolibrary.org/obo/uberon/core#channels_into 7
http://purl.obolibrary.org/obo/uberon/core#channels_from 6
http://purl.obolibrary.org/obo/uberon/core#subdivision_of 5
http://purl.obolibrary.org/obo/uberon/core#protects 4
http://purl.obolibrary.org/obo/uberon/core#posteriorly_connected_to 2
http://purl.obolibrary.org/obo/uberon/core#evolved_from 2
http://purl.obolibrary.org/obo/uberon/core#anteriorly_connected_to 2
In https://obo-communitygroup.slack.com/archives/C023P0Z304T/p1662990715744149?thread_ts=1662990299.268959&cid=C023P0Z304T, Nico stated that there are two allowed flavors for terms:
- http://purl.obolibrary.org/obo/IDSPACE_XXXXXX
- http://purl.obolibrary.org/obo/idspace#xxxxxx (only for properties)
Related to https://github.com/obophenotype/uberon/issues/2445
This is due to the ontology ID in the OBO file. should be uberon, not uberon/core
This is part of the general issue of not having numerical identifiers, which we'll fix soon. The complete list is here https://github.com/obophenotype/uberon/issues/2827
This issue has not seen any activity in the past 6 months; it will be closed automatically one year from now if no action is taken.