Maintenance Scenarios¶
Three scenarios are anticipated in which maintenance of CEON and the use case ontologies will be necessary.
Scenario 1 — Reuse and Extension¶
CEON or the use case ontologies may be reused in future initiatives for purposes such as knowledge representation, data documentation, and standardization within the circular economy domain. This reuse could involve:
- Extending CEON's existing module structure
- Aligning with other ontologies through existing or new alignments provided by Onto-DESIDE
Primary focus
Maintenance in this scenario focuses on adding specialisations of existing modules, ensuring comprehensive documentation, and providing usage examples — rather than implementing substantial structural changes.
Scenario 2 — New or Evolving Requirements¶
New domain requirements may arise or existing ones may evolve, necessitating updates to the content or structure of CEON. Maintenance in this context should:
- Adhere to established ontology evolution and engineering methodologies
- Ensure changes are systematically validated, implemented, and documented
See Methodological Support for the recommended approaches.
Scenario 3 — Bug Fixes¶
Bugs or issues detected during usage of CEON should be resolved through the standard GitHub issue and pull request workflow described in Technical Support.
Reporting issues
Issues can be reported directly on the CEON GitHub repository.
Applicability¶
All three scenarios apply equally to:
- The CEON core modules
- The three use case ontologies: Textile, Electronics, and Construction