Create a release product that uses COB as upper ontology

[cmungall]

This could be staged:

• RO core
• Rest of RO

The fundamental challenges as I see them concern existing axiomatization (in particular D/R constraints, which are frequently to above-the-shoreline (aka ATS) BFO terms) are laid out in:

• https://docs.google.com/presentation/d/1VU9nS_QBy-OLv2WjlbBeX_lD2mU4vVH4Oqqm5yGNMKc/edit#slide=id.p

Please read these thoroughly before commenting.

In the last slide I lay out different options:

1. expressionize the ATS terms (expressionizer)
2. replace ATS terms with UnionOfs
3. modify axioms, potentially changing meaning, and inject back onto existing BFO/RO IDs (this is what we are doing right now)
4. modify axioms but do not reuse IDs if meaning changes - i.e. start making a new RO in COB

[wdduncan]

Need someone to do the PR.

[cmungall]

No PR until we decide which of the 4 actions (which requires very careful reading of the slides)

[pfabry]

The presentation includes a fifth action, namely to retain the ATS terms. I understand that this particular issue is not be the best place to discuss it, or that this point may have already been settled—in which case, I apologize. However, is there truly a significant benefit to removing occurrent, continuant, and specifically dependent continuant, especially given that independent continuant and generically dependent continuant are already mentioned in COB?