Bridge BFO role to CHEBI role.

[balhoff]

Addresses issue #467. This is also taken care of by the range declaration for has role, however we are still not applying range reasoning in very many places due to most people still using ELK 0.4.3.

[matentzn]

Is RO the right place for this kind of alignment? I would imagine that once we move to ODK, much of this kind of axiomatisation should move to COB, right? In any case, I think its the right move, but this is probably one for @cmungall to judge.

[matentzn]

Also: since our CI pipelines use Elk 0.4.3, this wont really solve our "role part of material entity" problem, right?

[balhoff]

Also: since our CI pipelines use Elk 0.4.3, this wont really solve our "role part of material entity" problem, right?

This is meant to solve that, at least in part. has role has a range axiom that would make this less needed if the reasoner supported ranges.

[cmungall]

@balhoff will change this to be consistent with COB (chebi:role subClassOf characteristic)

@cmungall will make it easier to obtain the COB bridging file which will be th ultimate source of truth for this

[balhoff]

Changed to be subclass of PATO:quality, which is what I think is meant by "characteristic" above.

[cmungall]

correct https://github.com/OBOFoundry/COB/blob/master/src/ontology/components/cob-to-external.tsv#L120