Define what "COB base" is supposed to be

[matentzn]

A base file is, in essence the ontology without any of its dependencies.

The full specification can be enjoyed here: https://oboacademy.github.io/obook/reference/base-specification/

We use base files to enable something close to "modular, decentralised ontology development", and have deployed this in many ontology pipelines.

Now for COB, its not so clear to me what a good "base" should look like. In particular, should the rewired terms be considered outside the base? This would mean that people that want to use COB will have to configure arbitrary dependencies for classes we have swapped out, say and UBERON id.

[bpeters42]

I thought COB would be an outlier, and not have a base file. The ultimate goal (to me, and confirmed in today's RO call) is for RO-CORE + OMO + COB to form a basis with no external references (apart from even more foundational standards like OWL, RDF and the like) on which other OBO ontology base files would build.