-
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 local reflexivity axioms more mereological relations #151
Comments
Well argued - although abhorrence is a bit strong & both options have potentially counter-intuitive aspects. Issue to resolve if we make part_of reflexive:
For any of these structures, there are many parts that are not regions - they do not share the basic structural organization of the whole. The pattern I've been using in each of these cases (I haven't added all classes in every case, but could). X If we move to reflexivity, we have 2 options:
The viable solution may vary from case to case. In the case of integument we could probably do without the general class (not added + I'm not sure what it would be called). In the case of membranes maybe we could lose the region class. This would leave regions classified as membrane: e.g. synaptic membrane is_a membrane, and we can still have a part relationship to plasma membrane even if we lose a term that groups plasma membrane regions. But there are a few cases where these terms are used in axioms: cytosol/cytoskeleton/cytoplasm feels a bit more problematic. Maybe ditch the region class and use the general class and use this to classify regions and whole X of cell.... Also to note:
|
Something else to consider: Representing Phenotypes in OWL presents I have had reflexive |
I came to RO to file a ticket asking why part of was not declared as reflexive and found this issue and #78. For what it is worth, I have been operating for years under the assumption that part of is reflexive. We have recently been defining classes in the Plant Phenology Ontology which depend on the reflexivity of has part, although we have been able to work around it without the axiom in RO. I don't fully understand the local reflexivity axioms (I don't know what "SubClassOf: P Self" means), but I do get the argument for why full reflexivity can be problematic. I appreciate the concern that was raised about changing the formal definition of part of. Seems like adding the local reflexivity axioms would necessitate a new ID for the relations it is added to, but I know that would cause some serious pain. On the other hand, since many of us have been using part of (and similar) as if it were reflexive, I also appreciate the argument that adding the axioms would be consistent with how is has been used. I agree with @cmungall that "an additional axiom as powerful as this one would have to approved by all ontologies using it". |
What do you mean when you say you've been using it as if reflexive. Can
you give examples & practical consequences?
…On 10 Aug 2017 10:24 pm, "Ramona Walls" ***@***.***> wrote:
I came to RO to file a ticket asking why part of was not declared as
reflexive and found this issue and #78
<#78>. For what it is
worth, I have been operating for years under the assumption that part of is
reflexive. We have recently been defining classes in the Plant Phenology
Ontology which depend on the reflexivity of has part, although we have been
able to work around it without the axiom in RO.
I don't fully understand the local reflexivity axioms (I don't know what
"SubClassOf: P Self" means), but I do get the argument for why full
reflexivity can be problematic.
I appreciate the concern that was raised about changing the formal
definition of part of. Seems like adding the local reflexivity axioms would
necessitate a new ID for the relations it is added to, but I know that
would cause some serious pain. On the other hand, since many of us have
been using part of (and similar) as if it were reflexive, I also appreciate
the argument that adding the axioms would be consistent with how is has
been used. I agree with @cmungall <https://github.com/cmungall> that "an
additional axiom as powerful as this one would have to approved by all
ontologies using it".
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#151 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAG4x_Ubk3pDfh4HVvm__7gXAASj1GYLks5sW-V0gaJpZM4L3vVU>
.
|
I was afraid you'd ask that. :) I will provide some examples, but in general, I mean that in the PO, PPO, and other ontologies I have worked on, when I use a part of relation, I have assumed it is reflexive. Generally, I have not made highly axiomatized ontologies (e.g., in PO), so the consequences are few, but the thinking was always based on it being reflexive. |
Like @ramonawalls I also operated for a long time assuming |
Can this be closed? |
this has to remain open until there is clear resolution |
Revisiting I think on balance reflexivity simply causes too many problems
Above I make some arguments about why reflexivity makes certain axiomatization clearer but I think this is best handled another way. E.g. inheres_in_part_of can simply have a (FOL) definition that refers to an unnamed reflexive part-of or has a union condition. So if we give up local reflexivity do we want to go one step further and assume it irreflexive/proper. This would undoubtedly cause some issues just now but it would be worth exploring these to see if they are cryptic incoherencies in some other way. If we decided this we would roll out very slowly. So my summary of the choices
|
Are the direct relations assumed not to be reflexive? It seems that the answer should/would be "yes". |
Here are the 4 options again. For now let us restrict this to the part-of relation in RO (BFO:0000050)
Can advocates for each state their preference and some reasons for that preference? Or if you are lazy just click the emoji |
I doubt there are more than 3 people in all of OBO that understand this issue.. |
I think you underestimate the OBO community, Nico. There is a difference between understanding and caring. :) |
Valid arguments in favor of each choice. Since I have managed to make things work with the way they are now (formally uncommitted) I can live with keeping it that way. My second choice would be locally reflexive, thus I added two reactions. Basically, I am working with mostly working application ontologies these days, so I can make whatever you decide work for me. Thanks for your continued work on this issue. |
@ramonawalls I agree with your sentiment (above), and (like you) I would support local reflexivity as a second choice. I also added two reactions :) |
The BFO reference declares mereological relations as reflexive:
This is implicitly local_ reflexivity.
Additionally, every treatment of mereology treats the mereological relations as part-of. We may consider relations such as develops-from mereological in a 4D sense. One reason for this is simply mathematical elegance.
It may seem that we can have our cake and eat it. For every mereological relation
R
, we can have this be reflexive, and declare a second relationproper_R
. However, while this is "free" in any FOL system, it comes with a cost in OWL due to expressivity constraints. We can express thatR
is reflexive, we can makeproper_R
a subproperty ofR
, but we cannot infer downwards.If we don't inflate the number of relations, then we must choose an interpretation for our
R
- is it reflexive or proper?Arguments for (local) reflexivity
Already considered reflexive
It's declared reflexive in the BFO reference, and in the original RO paper, and there has never been an formal retraction of the axiom, so we'd be changing the semantics by making it not reflexive.
Intuition
While on the one hand it may be counter-intuitive for an object to be part of itself, the proper-part-of relation is not intuitive either. E.g.
'John - 1 atom' proper-part-of John
.Logical validation
Local reflexivity is highly useful for error-checking, see these examples in uberon, obtained by adding reflexivity to part-of.
For example, consider the current version of uberon that has two classes:
This is odd because all roof plates are in the neural tube (according to the model takes). The existence of two classes here is an unintended error. This has been lurking for some time, but was revealed when the reflexivity axiom was added:
The entailment of an equivalence is a bonus here for error checking, and has resulted in a ZFA ticket. It's likely the classes will be merged.
But errors of this sort are never revealed if PPO is not reflexive. This is because in all models RPNTs are RPs with one or more atoms removed. This is certainly not our intention! Yet these interpretations remain cryptically.
Another example from the same ticket:
The solution here was to merge
Filtering redundant axioms
If we feed the following into an OWL-based redundancy removal procedure, e.g.
robot reduce
there is no redundancy unless part-of is declared reflexive. We consider this problematic; the main point of reduction is to make a structure that is more user-friendly, and having multiply-labeled edges violates this (the OBO basic profile explicitly prohibits this). For this particular axiomatic structure the solution may simply be an ad-hoc rule to remove the part-of. This will not work for all cases however.
Why is this particularly important? It is very important if we move towards heavy use of GCIs to infer parthood. Examples of this can be seen in the OBA DP for inference of part-ofs.
Materialization of these part-of parents can be done via
robot materialize
. However, the basic materialization produces many redundant paths. If reduction is performed with reflexivity of part-of, everything works out of the box. Without this, we end up with a basic existential graph that is formally non-redundant (due to the one-atom distinction), yet massively redundant for user purposes. We can always implement standard transitive reduction over the resulting graph but this is unsatisfactory.It could be argued that this is very application specific, but in fact it is a manifestation of the fact that proper-R is an abhorrence that admits counter-intuitive models
Related tickets
The text was updated successfully, but these errors were encountered: