It was discussed in today’s BeSci meeting that these changes will be implemented in the BCI Schedule ontology. We will create new entities for all these classes to make them broader and more usable across different types of interventions.
For the time being, we agreed not to obsolete the BCI‑specific classes.
For the GMHO classes that have been added to the file, we suggested that equivalent classes should be created in the BCIO. GMHO should then import these classes from BCIO, as BCIO is more widely known.
This links to issue: 1165
BCIO-schedule-hierarchy 2026-04-20.xlsx
It was discussed in today’s BeSci meeting that these changes will be implemented in the BCI Schedule ontology. We will create new entities for all these classes to make them broader and more usable across different types of interventions.
For the time being, we agreed not to obsolete the BCI‑specific classes.
For the GMHO classes that have been added to the file, we suggested that equivalent classes should be created in the BCIO. GMHO should then import these classes from BCIO, as BCIO is more widely known.
This links to issue: 1165
BCIO-schedule-hierarchy 2026-04-20.xlsx