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

routes as processes and medium as material entities #9

Open
diatomsRcool opened this issue Aug 20, 2019 · 9 comments
Open

routes as processes and medium as material entities #9

diatomsRcool opened this issue Aug 20, 2019 · 9 comments

Comments

@diatomsRcool
Copy link
Collaborator

I notice while browsing ExO in ontobee that route is a direct children of Thing. Can we make routes a direct child of BFO process? and exposure medium a child of BFO material entity?

It would help my use case.

@cjgrondin
Copy link
Contributor

uncertainty about making routes and events subclass of BFO process; not sure we need to do that; need to think about this

@ddooley
Copy link

ddooley commented Jan 31, 2022

It would be great if ExO is BFO compatible to type its top level classes under at least 1 BFO class. That way on integration of ExO with other ontologies for an application etc. everything organizes nicely rather than floating to top level.

@cjgrondin
Copy link
Contributor

Making top level classes of ExO compatible with BFO sounds reasonable to me. Currently, there are four top level classes of ExO: exposure stressor, exposure_receptor, exposure event and exposure outcome.
exposure event is_a BFO process
Would it work to make each term of exposure stressor and exposure_receptor a BFO entity?
What about exposure outcome?

@diatomsRcool
Copy link
Collaborator Author

The stressor can be anything, so that may need to be named entity. The receptor is going to be an organism, organism part, or group of organisms and so would be material entity. The outcome can be a disease or phenotype - that would be a continuant. Open to other suggestions.

@cjgrondin
Copy link
Contributor

cjgrondin commented Feb 1, 2022

Could exposure outcome be an occurrent "an entity that unfolds itself in time or it is the instantaneous boundary of such an entity" instead of a continuant "an entity that persists, endures, or continues to exist through time while maintaining its identity"?

@diatomsRcool
Copy link
Collaborator Author

The exposure event itself is definitely an occurrent. When I check to see how diseases and phenotypes are grounded in BFO, they are listed as continuants. Are there any other types of outcomes we want?

@cjgrondin
Copy link
Contributor

cjgrondin commented Feb 2, 2022

When developing ExO, the working group included several outcomes to an exposure event: biological response (disease, phenotype, etc), public policy, and intervention (described in PMID: 22324457).
Also, yes, exposure event is_a BFO: process, which is a child term of occurrent

@diatomsRcool
Copy link
Collaborator Author

interesting....
I wouldn't have thought about public policy and intervention as exposure outcomes. It is true and important, but I would model it differently.
Do you have an example of how people are using ExO to model a public policy or intervention as an exposure outcome?

@ddooley
Copy link

ddooley commented Feb 4, 2022

It seems like there's opportunity (unless someone has done it) to develop some language around policy design (as a process, bearing on behavioural change) in response to evidence generated from exposure studies. But that seems like a longer chain of modelling! P.s. OBI/ECO was just workshopping a revision to clarify experimental evidence".

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

No branches or pull requests

3 participants