-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update bridging relations in cross-species bridges #3466
Conversation
Update the SSSOM/T-OWL ruleset producing the bridges so that an exact cross-species exact match yields the two following axioms: <subject> EquivalentTo: <object> and (in_taxon some <taxon>) <subject> SubClassOf: part_of some <taxon> (part_of being replaced by occurs_in if the subject is an occurrent) instead of <subject> EquivalentTo: <object> and (part_of some <taxon>) The two-axioms form has always been the intention for those bridges (see discussion in #2428), the one-axiom form that we have used so far was only because of technical limitations.
Now that the equivalence axioms in cross-species bridges use 'in taxon' instead of 'part of' or 'occurs in', the unfolding step when building the composite ontologies need to unfold on that relation as well.
We need 'occurrent part of' as it a parent of FBdv's 'substage of' (FBdv:00018001); without that relation, there is no link between 'substage of' and 'part of', which means that the property chain 'part of' o 'in taxon' SubPropertyOf: 'in taxon' cannot apply to 'substage of' relationships. This is turn means that some relations between FBdv terms cannot be properly translated into class expressions when generating Composite Metazoan.
Update the documentation about the bridges and the composite ontologies to reflect the fact that bridging equivalence axioms now use the 'in taxon' relation, rather than 'part of'.
This needs a @cmungall glance, I am not a good reviewer for this; I can help find someone that is. |
The PR makes complete logical sense, and this was indeed the original
intent.
However, representing this unilaterally in Uberon could cause confusion.
Queries that work for UBERON may fail for GO or CL.
But even assuming we can move forward in unison, I now think there is value
in using different relations for different use cases. Granted this is not
the underlying basis for RO, so there are valid cases either way. Would be
good to gather opinions for others. I can expand on with some examples
later.
One of my concerns is increasing raggedness in the part-of lattice. User
sees 'flexor pollicis longus muscle' as a part of Human in OLS. They open
up Human in OLS expecting to see all human parts. They get confused when
there is just some tiny collection of terms.
…On Thu, Jan 23, 2025 at 3:12 PM Nico Matentzoglu ***@***.***> wrote:
This needs a @cmungall <https://github.com/cmungall> glance, I am not a
good reviewer for this; I can help find someone that is.
—
Reply to this email directly, view it on GitHub
<#3466 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAMMOKVE42LB7VC3PFGDQT2MFZMXAVCNFSM6AAAAABVX7NAHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJRGIYDEMJQGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Not sure I follow you. The relations updated by this PR would not go into UBERON itself -- they would only go into the bridges (and from there into the collected/composite products). Or are you referring to queries on Ubergraph (which does use the Uberon-provided bridges)? If so, note that this PR also updates the CL bridges - since they are maintained here in Uberon.
I don’t think it is realistic for Uberon to provide several versions of the bridges or of the collected/composite ontologies, each using slightly different axioms to accommodate for potentially different use cases. If people have use cases that require different bridging axioms that the ones we provide in the pre-built bridges, they now have the possibility of downloading the Uberon SSSOM mapping set and generate their own bridges. |
On Fri, Jan 24, 2025 at 9:28 AM Damien Goutte-Gattat < ***@***.***> wrote:
Queries that work for UBERON may fail for GO or CL.
Not sure I follow you. The relations updated by this PR would not go into
UBERON itself -- they would only go into the bridges (and from there into
the collected/composite products).
Or are you referring to queries on Ubergraph (which does use the
Uberon-provided bridges)? If so, note that this PR also updates the CL
bridges - since they are maintained here in Uberon.
Good point, I forgot about CL
But the broader issue is we give users the expectations that they can
traverse anatomy to taxon via part-of in one anatomy/product, they might
reasonably expect they can do it in another (e.g GO-CC)
But even assuming we can move forward in unison, I now think there is value
in using different relations for different use cases.
I don’t think it is realistic for Uberon to provide several versions of
the bridges or of the collected/composite ontologies, each using slightly
different axioms to accommodate for potentially different use cases.
If people have use cases that require different bridging axioms that the
one we provide in the pre-built bridges, they now have the possibility of
downloading the Uberon SSSOM mapping set and generate their own bridges.
Agreed, and sorry I wasn't clear. I didn't mean to suggest different
versions, that would be complicated.
I just meant that I think it's fine if in-taxon is the anatomy->taxon
relation in all cases, and part-of is anatomy->anatomy. The two kinds of
traversals represent different use cases. Even if from a BFO/COB/OBO
Realist perspective NCBITaxon is an anatomy ontology (just one that
subclasses the 'whole organism' class)
… —
Reply to this email directly, view it on GitHub
<#3466 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAMMONMQ6D2M6LYVVHPUWL2MJZ4VAVCNFSM6AAAAABVX7NAHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJTGA2DKNBVHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
OK, it’s clearer now, thanks. But then I’m afraid I still don’t understand your concern with this PR. Currently (without this PR), in-taxon is not used in the bridge files at all. All links between a Uberon term and its taxon-specific counterpart use part-of (or occurs-in, for terms representing developmental stages). So, part-of is both for anatomy-to-anatomy (e.g. from cell type to tissue, from tissue to organ, etc.) and for anatomy-to-taxon (e.g., FBbt’s ovary is a Uberon ovary that is part-of some Drosophila melanogaster). The point of this PR is precisely to no longer use part-of (or, again, occurs-in for developmental stages) for anatomy-to-taxon (in cross-species bridging equivalence axioms), but only in-taxon (e.g., FBbt’s ovary is a Uberon ovary that is in-taxon some Drosophila melanogaster) -- to me this seems closer to what you actually want, compared to the current situation. |
AHA it all makes sense now, thanks for your patience, I should have read more closely. Approving now! |
This PR changes the axioms that make up the cross-species bridge ontologies.
Currently, foreign (taxon-specific) terms are bridged to their Uberon counterparts by a single equivalence axiom that looks like this:
or like this (if the term represents an occurrent, such as a developmental stage)
However, this has only been intended as a temporary situation. The original intention was for each foreign term to be bridged by a pair of axioms as follows:
if the term represents a continuant, or
if the term represents an occurrent.
The two-axioms form had been left aside in favour of the single-axiom form solely for technical reasons, because the bridging pipeline at the time was too difficult to update to accommodate for such a change. This is no longer true, so this PR now implements the two-axioms form.
The Composite Metazoan pipeline is updated accordingly to “unfold“ over 'in taxon' rather than over 'part of' or 'occurs in'.
closes #3409
closes #3378