-
Notifications
You must be signed in to change notification settings - Fork 18
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
Building ECTO #238
Comments
They were selected to axiomatize terms of relevance
Having said that there is historic baggage that can be removed
Npo no longer needed radiation is in Envo
If uberon is not used we should drop it(maybe originally intended for
routes)
I’m not sure it makes sense to use sdgio or pco
Maybe some of these are 2nd order dependencies
Fewer dependencies almost always better
Some of the choices just represent the ad hoc modularization in obo outside
core ontologies
There is an issue somewhere about ncit vs nbo for social activities
Apologies for brevity will answer in more depth later but I think the
answer to your q needs to be more transparent in our DPs
…On Mon, Sep 5, 2022 at 11:16 AM David Shumway ***@***.***> wrote:
How are sub-ontologies within ECTO merged? Is there documentation, wiki,
or an article describing this process?
ECTO integrates the following ontologies:
Ontologies used in composition (largely orthogonal):
- Exposure Ontology (ExO) - used as the upper ontology, for based
classes such as 'exposure', different routes such as 'ingestion'
- Chemical Entities of Biological Interest (CHEBI) - use for both
entities and roles
- Environment Ontology (ENVO) - environmental materials, processes
- NanoParticle Ontology (NPO) - radiation
- Relations Ontology (RO) - relations
- Phenotypic Quality Ontology (PATO) - qualities
- UBERON Anatomy Ontology - tissue types (not used yet)
- NCI Thesaurus (NCIT) - activities such as smoking
- Sustainable Development Goals Interface Ontology (SDGIO) - social
entities
- Population and Community Ontology (PCO) - population attributes
(e.g. overcrowding)
Was there a manual process of selecting classes of interest from each
sub-ontology? Or were the sub-ontologies included in whole? Or were ECTO
classes simply built from concepts found in the sub-ontologies (e.g. using
DOSDPs), and by so doing relevant concepts in the sub-ontologies were thus
integrated into ECTO?
—
Reply to this email directly, view it on GitHub
<#238>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAMMOPG3WCK5JD5RBYP2NDV4Y2GNANCNFSM6AAAAAAQFGJFIM>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***
.com>
|
Thanks, @cmungall!
Yes... (echo "!!!!!NPO currently skipped!") While /src/ontology/ecto.Makefile is certainly readable anyone approaching the code for the first time (here) might be a bit hard-pressed to understand the merging and DP templating processes. I assume most of the merging and templating is run either there or in src/ontology/Makefile. I see that src/ontology/Makefile uses the ODK. In terms of merging, perhaps reviewing ODK is a good place to start? (e.g. here) |
Can I just get a bit of context - why do you need to understand the Makefile? I think for this project it is generated by the ODK so yes understanding ODK would help, and I encourage all forms of learning about the ODK! But really you only need to know this if you are working on the ECTO release pipeline... |
The context would be adding new terms to ECTO as well as using ECTO as part of another domain-specific ontology. The domain is waterborne illnesses in the context of recreation or occupation. For example, swimming at the beach might lead to an exposure to e-coli. The planned source ontologies are related to illnesses, recreational and occupational activities, the environment (ENVO), environmental exposure (ECTO), sources of pollution, chemicals/organisms of interest in the domain. |
So just to clarify: in regard to adding new terms I think that's already documented in ECTO. And in terms understanding the merging process that is more in regard to simply understanding ECTO for my own purposes because it seems well built. |
Got it, that helps, thanks! I'm hoping that we will soon have docs derived from the DOSDPs, analogous to this: https://mondo.readthedocs.io/en/latest/editors-guide/patterns/ We would then have discussions about ontology dependencies at a per-pattern level, and there would be (hopefully) clear transparent guidelines If you use DOSDPs in your ontology it may make it easier to reuse patterns as well |
This is more of a discussion topic rather than issue. Is there discussion in ECTO regarding use of exposure outcomes (e.g. https://ontobee.org/ontology/ExO?iri=http://purl.obolibrary.org/obo/ExO_0000003)? For our use case outcomes to exposures are also of interest. Something like this perhaps:
From a high level, patterns in ECTO relate two or more source ontology entities, as defined in a template, by creating new entities and associated axioms via the templates. The associated source ontology entities are then included via a ROBOT extract process. Does this capture the high-level idea? Are there any classes or relations specific to ECTO rather than taken from source ontologies and if so what is the procedure for adding these? Are there any organizational changes made to the ontology after merging, for example, combining classes or reorganizing hierarchies? Is there a ROBOT diff included showing pre- and post-reasoning? |
In terms of disease outcomes perhaps these could be realized in Mondo? For example, Chan, L. E., Vasilevsky, N. A., Thessen, A., Matentzoglu, N., Duncan, W. D., Mungall, C. J., & Haendel, M. A. (2021). A Semantic Model Leveraging Pattern-based Ontology Terms to Bridge Environmental Exposures and Health Outcomes. Proceedings http://ceur-ws. org ISSN, 1613, 0073. So in regard to swimming, something like this?
In regard to the exposure event, something like this perhaps?
|
I was also wondering whether ECTO has plans / ideas around multiple routes as I see there are routes defined for some exposures. For example, from food_ingestion.tsv:
For my use case, simply adding Just saw this pattern as well...
So to summarize... And for swimming, perhaps it's similar to e.g.
So that would make
|
These are all very interesting discussion points @davidshumway , thank you for bringing them up! I wonder what the additional value would be to add the component of 'swimming' to the terms specifically. Are you hoping to have some way to aggregate exposures that occur while swimming? Or is this just adding further details to a term like As for the question regarding outcomes of an exposure, I agree with your thought that Mondo or another relevant ontology would be the most appropriate place to include those outcomes if not already represented. Outcomes do not fit within the scope of ECTO in my opinion, but certainly having the outcomes and necessary relations modeled is of importance! Are there particular outcomes you are looking for? Mostly ones related to organisms in water? |
Thanks, @laurenechan. I think swimming exposure to ecoli is a little bit unique in that a common source of ecoli in swimming waters such as at a beach would be wastewater treatment discharge whereas from a sprinkler or tap water would be less likely (?) to include this source.
I was definitely thinking of using compound exposures and wonder if this may be a suggested approach. E.g. the compound of
Related to organisms, fungi, viruses, parasites, plants. Perhaps 50-100 relevant entities. For outcomes, diseases or symptoms, so e.g. e-coli infection, abdominal pain, etc. |
I also wonder in terms of modeling outcomes to exposures, specifically regarding mondo, the following:
In Mondo, there is the relation "disease has primary infectious agent" while ECTO is modeled as "exposure to (agent)". How might these align? Perhaps this is a better question for the Mondo issue tracker?
|
@davidshumway this is a good question and likely one that would need some thought from both the ECTO and Mondo teams (and potentially other ontology groups as well depending on use cases). For diseases that have an infectious agent component, the relation in Mondo is more concrete, indicating that the infectious agent is in fact the source for the disease. Whereas within ECTO, an exposure to an infectious agent is not necessarily going to result in the infectious disease starting. Likely there is a confirmed exposure to the agent prior to the individual becoming ill, but there is no assurance that all exposures will equal disease. This one directional relation would be the case if we were to use 'infectious disease X' 'realized in response to' 'exposure to (agent)'. @nicolevasilevsky might have a better sense of what Mondo thinks is a good plan for using or not using ECTO terms in this kind of use case. An ongoing discussion about including exposures to infectious agents in ECTO vs other ontologies is occurring, and is a discussion point on another issue as well #134 , where we still don't have a firm decision for whether exposures to agents should be housed in ECTO vs elsewhere. |
How are sub-ontologies within ECTO merged? Is there documentation, wiki, or an article describing this process?
Per documentation, ECTO integrates the following ontologies:
Was there a manual process of selecting classes of interest from each sub-ontology? Or were the sub-ontologies included in whole? Or were ECTO classes simply built from concepts found in the sub-ontologies (e.g. using DOSDPs), and by so doing relevant concepts in the sub-ontologies were thus integrated into ECTO?
The text was updated successfully, but these errors were encountered: