-
Notifications
You must be signed in to change notification settings - Fork 47
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 symmetry and definition to simultaneous with
#611
Conversation
Discussion at RO meeting 2022-06-28: we should have definitions for 'simultaneous with', 'ends' and 'starts' in order to decide how they are related. Some definition may be produced via the definitions of the inverses, but some translation may be needed to make this clear. |
The comment on simultaneous_with has a proposed def: t1 simultaneous_with t2 iff:= t1 before_or_simultaneous_with t2 and not (t1 before t2). This is certainly not ideal, but I think it indicates that this is not meant to be used between processes/intervals but between points in time - where the points in time we are interested in our those that define the start and end points of an occurrent. Defined in this way, the term should not be used in Uberon (where this request originates). I think what's needed for Uberon is probably the Allen 'equals' relation: http://www.thomasalspaugh.org/pub/fnd/allen.html.We don't seem to have that at present. To be consistent with other defs, this should be something like this:
(Note - the TBD:
More generally - it would be really awesome if we could find a decent logician to review this whole branch. We decided years ago to not directly re-use Allen relations, but to use derivable relations that (we believe(d)) are more intuitive for biologists. For example our 'precedes' is a subproperty of Allen 'meets'. The general work required is to derive property heirarchy & chains (or rules) and standardise definitions - using Allen as a starting point. Here's a rather ancient attempt: https://docs.google.com/document/d/1kBv1ep_9g3sTR-SD3jqzFqhuwo9TPNF-l-9fUDbO6rM/edit?pli=1 |
From tech call Minimum:
Other parts of #611 (comment) should be opened as a new ticket for longer term modelling solutions |
I'm not sure if this is ready to be merged; @cmungall approved but @shawntanzk's comment suggests some changes? |
@dosumis @shawntanzk Can you attend the next RO call so that we can discuss this. |
This PR has not seen any activity in 90 days and has been marked as stale. If it is no longer needed, please close the PR. Otherwise, please update the PR with a status update. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I mistakenly approved before. This is actually incorrect because of the <
condition on starts/ends
Here is what I think needs to be done right now with this relation in RO:
This will be sufficient to have a PR we can merge I also completely agree with @dosumis that we should have a separate review where we encode all these relations in a stronger formalism than OWL and validate them. Note the temporal relations mirror genome ones so we can piggy back off of this: https://www.biorxiv.org/content/10.1101/006650v1 (without the complexities of reverse complementation) |
I did the changes. Just to make it clear that this relation is already transitive. This type is in the |
simultaneous with
simultaneous with
Related to obophenotype/uberon#2453