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

process vs. processual entity #2301

Open
wdduncan opened this issue Feb 11, 2022 · 14 comments
Open

process vs. processual entity #2301

wdduncan opened this issue Feb 11, 2022 · 14 comments
Assignees
Labels

Comments

@wdduncan
Copy link
Collaborator

@cmungall @matentzn @dosumis @addiehl @diatomsRcool @johnwjudkins

Ontobee shows UBERON has both process and processual entity classes. Is the processual entity intended to be the same as BFO1.1 processual entity?

Ontobee didn't provide a definition for BFO1.1 processual entity, but I seem to recall the definition being what is stated for UBERON processual entity. I'd have to do some digging to confirm/disconfirm.

However, UBERON does have a process class that uses the BFO process IRI. So, this makes me wonder:

  • What is the difference between processual entity and process? So, it is unclear why they are siblings.
  • Is processual entity meant to be subclass of process?
  • Is process meant to be a subclass of processual entity?

I think it would be great if this was made clear.
Perhaps related to #1640

@shawntanzk
Copy link
Collaborator

added to agenda, will try to get an response to this

@ghost
Copy link

ghost commented Jun 27, 2022

Discussed at the Uberon meeting...
@addiehl recommends that 'processual entity' should be merged with 'process' since they are likely representing the same thing and both may be present accidentally.

@wdduncan
Copy link
Collaborator Author

@bvarner-ebi Good. I agree with him. Somewhere else (not that it matters) I think I recommended the same as @addiehl

@shawntanzk
Copy link
Collaborator

As this is an upper ontology change - will need sign-off from @cmungall
Will bring it to his attention :) thanks!

@cmungall
Copy link
Member

Let's solve this one here: OBOFoundry/COB#40

@github-actions
Copy link

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.

@github-actions github-actions bot added the Stale label Feb 22, 2023
@wdduncan
Copy link
Collaborator Author

This ticket has been open for a while. Any plans to address it?

@github-actions github-actions bot removed the Stale label Feb 23, 2023
@anitacaron anitacaron assigned cmungall and unassigned shawntanzk Feb 27, 2023
@github-actions
Copy link

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.

@github-actions github-actions bot added the Stale label Aug 27, 2023
@dosumis
Copy link
Contributor

dosumis commented Aug 27, 2023

Somehow missed this the first time around:

Background - we wanted this for developmental stages - which need to allow for occurrent with arbitrary temporal boundaries. In standard stage series divides development up into stages whose stage boundaries are defined by whatever morphological features are easy to score. This is, I think, different from a process like glycolysis or signal transduction.

image

@wdduncan
Copy link
Collaborator Author

processual entity is a BFO 1.1 concept, and in BFO 1.1 process is a child of processual entity.

image

Mixing BFO 1.1 and BFO 2.0 concepts in this way introduces potential ambiguities in that it is unclear how to decide whether a class should be a bfo2:process, bfo1.1:processual entity, or (perhaps) bfo1.1:process.

At present life cycle stage , is textually defined as being a kind of spatiotemporal region, which of course is not consistent to it being a child processual entity.

As far as I can tell from the definition of bfo2:process, life cycle stage can be a child of it, although linguistically it may sound a bit odd. Making such a change would address the potential ambiguities mentioned above.

@github-actions github-actions bot removed the Stale label Aug 28, 2023
@uberon
Copy link

uberon commented Aug 28, 2023 via email

@wdduncan
Copy link
Collaborator Author

We need to be able to put stages in a different bucket than GO bps.

Yes, not every process is GO bps. Not sure why or if this precludes life stage from being a child of bfo2:process.

I guess this grouping will have to remain in uberon until
OBOFoundry/COB#40 is resolved which has become
entangled with a lot of philosophical upper ontology discussion

If you are waiting on the COB issue to resolve, I fear you will be waiting a very, very, long time. Better to move ahead on this now.

Copy link

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.

@github-actions github-actions bot added the Stale label Feb 25, 2024
@wdduncan
Copy link
Collaborator Author

Any update on this?

@github-actions github-actions bot removed the Stale label Feb 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants