Skip to content

Overview

Overview#

ENERO Foundry developed a shared set of principles to ensure that ontologies are logically well-formed, scientifically accurate, and interoperable. Our commitment to FAIR and open science drives the development of reusable knowledge structures for the energy domain. We consider the OBO principles and the Technical principles from IOF.

Discussion#

The definitions and details of the principles are being discussed in the GitHub Discussions of the ENERO Foundry.
We welcome your feedback and contributions.

Principles#

  1. Openness
  2. Common Format
  3. Release and Versioning
  4. Documentation
  5. Collaboration and Responsiveness
  6. Scope
  7. Foundational Ontology
  8. Identifier and Naming Conventions
  9. Textual Definitions
  10. Usage of AI

On each principle page, several informational sections are presented:

Summary#

A brief description of what the principle means and how it should be implemented.

Purpose#

The rationale for including the principle in the ENERO Foundry. Background information on why the principle was formulated the way it is.

Implementation#

A list of implementation guidelines for the principle. The following terminology is used:

  • MUST or MUST NOT: a requirement for an ontology to comply with this principle.
  • SHOULD or SHOULD NOT: a recommendation and a suggestion for best practices in ontology development.
  • MAY: an option for ontology developers to select what works best for their ontology.

They are to be interpreted as described in RFC 2119.

Examples#

Examples of ontology implementations that comply with the principle.

Counter-Examples#

Examples of ontology implementations that do not comply with the principle.