There are object properties (aka relations) reused in MOP that are defined in BFO. As the OBO community uses the BFO2.0 classes only version these relations are not being resolved via their IRI. In order to be compliant with the OBO principles these relations should thus be replaced by RO equivalents.
The following relations need to be changed in MOP (individual issues need to be made for each):
“has dispositions at all times” (BFO_0000162) should be changed to “has disposition” (RO_0000091)
‘has participant’ (BFO_0000057) should be changed to ‘has participant’ (RO_0000057)
its sup-properties 'has participant beginning to exist' (BFO_0000077) & 'has participant ceasing to exist' (BFO_0000078) should be changed to something suitable in the ‘has participant’ branch of RO, or a term request should be made
a possible candidate for 'has participant ceasing to exist' might be "has primary input" (RO_0004009)
a possible candidate for 'has participant beginning to exist' might be "has primary output" (RO_0004008)
There are object properties (aka relations) reused in MOP that are defined in BFO. As the OBO community uses the BFO2.0 classes only version these relations are not being resolved via their IRI. In order to be compliant with the OBO principles these relations should thus be replaced by RO equivalents. The following relations need to be changed in MOP (individual issues need to be made for each):