Skip to content
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

Add new occupational_exposure_to_material pattern #252

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

rays22
Copy link

@rays22 rays22 commented Jan 24, 2024

Fix #250


equivalentTo:
text: "'exposure_event'
and ('has_exposure_stimulus' some ('occupation' and %s))"
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
and ('has_exposure_stimulus' some ('occupation' and %s))"
and ('has_exposure_stimulus' some 'occupation')
and ('has_exposure_stimulus' some %s)
"

This suggestion is based on feedback on another EQ here: obophenotype/bio-attribute-ontology#312 (comment)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The previous intersection is definitely wrong and will lead to unsats

Separation is better but I don't think occupation is a stimulus. @diatomsRcool how does an exposure scientist think about this? Do we need a context relation?

Or we could simply have a more specific genus of "occupational exposure"

Copy link
Author

@rays22 rays22 Jan 26, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The previous intersection is definitely wrong and will lead to unsats

Sorry, but I am not familiar with the distributive properties of these axioms. Before I uploaded the DOSDP pattern I had checked in Protege (ELK 0.5.0) with the three examples in occupational_exposure_to_material.tsv, but I did not find any unsats. However, I accept that my EQ still could be wrong and mean something different from what I intended:) ...

For example, here is the new occupational fume exposure:
occupational_fume_exposure

Separation is better but I don't think occupation is a stimulus. @diatomsRcool how does an exposure scientist think about this? Do we need a context relation?

FYI: My inspiration for using 'occupation' as a stimulus is coming from https://github.com/EnvironmentOntology/environmental-exposure-ontology/blob/master/src/patterns/dosdp-patterns/exposure_to_occupation.yaml

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Occupational exposures have been a thorn in my side for a bit. I guess now there is no ignoring any longer. Chris is right. Occupations aren't really exposures. More like contexts for exposures. An exposure to lead could be part of an occupation or something like that. I'm not sure what the correct relation would be. Is there a context relation?

The exposure to occupation pattern that is currently in ECTO was developed so that we could compose complex exposures for things like working in a battery factory which would be combinations of exposures to many different things. Lauren's use case needed that. Let's make a different pattern for this.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it be crazy to do:

equivalentTo:
  text: "'occupational_exposure_event'
        and ('has_exposure_stimulus' some %s)"

or even simpler:

equivalentTo:
  text: "'occupational_exposure_event'
        and %s"

So you can say something like "occupational exposure event" and "fume exposure", or, if there are use cases for the first option, "occupational exposure event" and has_exposure_stimulus some "fume"?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, this is what I meant by

Or we could simply have a more specific genus of "occupational exposure"

Regardless of how it's axiomatized there is the lopsided xmas tree antipattern here. "occupational X exposure" will be a child of "X exposure" as expected. But do we need to make non-occupational children? Someone annotating to an unadorned "X exposure" may have an implicit assumption of directness.

A slightly radically different way of doing this is to interpret the root ecto term as being direct, and axiomatized occupational exposure as "occupational exposure and has-part some ". This gives us more fine grained control in weeding out occupational exposures in queries but at the expense of making it harder to do the inclusive query

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The use cases I've been working with so far would need a priority placed on being able to query an exposure to lead across all different types of mixed exposures rather than querying occupational exposures specifically

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is an occupational exposure not a direct exposure?

I am pretty sure we are overthinking this. Maybe its best to conceptualise ECTO as a vocabulary with a sane hierarchy (where occupational exposure classifies under exposure, and exposure has no implicit assumption of "directness"). We should probably not even export the logical definitions in the main release product; just the relaxed version with the stimuli and perhaps the route.

For now, I am not convinved that But do we need to make non-occupational children is enough of a concern to avoid the "more specific genus of "occupational exposure"" solution...


equivalentTo:
text: "'exposure_event'
and ('has_exposure_stimulus' some ('occupation' and %s))"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The previous intersection is definitely wrong and will lead to unsats

Separation is better but I don't think occupation is a stimulus. @diatomsRcool how does an exposure scientist think about this? Do we need a context relation?

Or we could simply have a more specific genus of "occupational exposure"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Create pattern for "occupational exposure"
4 participants