Always include a BFO import

CommonCoreOntology / CommonCoreOntologies

The Common Core Ontology Repository holds the current released version of the Common Core Ontology suite.

Other

163 stars 47 forks source link

Always include a BFO import #227

Open alanruttenberg opened 3 months ago

alanruttenberg commented 3 months ago

AFAICT the only ontology that explicitly imports BFO is the extended relation ontology. If that doesn't happen to be imported when you open one of the component files then there are BFO ids displayed in Protege. Since they all use BFO, I think they should all explicitly import BFO.

cameronmore commented 3 months ago

I agree. If I'm deploying CCO in an application, I will have custom imports and slims, and further domain modules, etc, so including the import doesn't seem like it would cause build issues for those using the ontologies. If I'm using a CCO module, I'm not sure why I wouldn't want BFO as well.