Skip to content

Making BCIO Schedule Ontology more usable across interventions #1233

@micaelasantilli

Description

@micaelasantilli

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions