ontology
ontology copied to clipboard
Restructure `SMES`
Description of the issue
Separated from #1262: The class SMES
is currently defined as:
Superconducting magnetic energy storage (SMES) systems store energy in the magnetic field created by the flow of direct current in a superconducting coil which has been cryogenically cooled to a temperature below its superconducting critical temperature. A typical smes system includes three parts: superconducting coil, power conditioning system and cryogenically cooled refrigerator. Once the superconducting coil is charged, the current will not decay and the magnetic energy can be stored indefinitely.
This needs an improvement as it not only describes the storage object but also its parts and some processes.
Ideas of solution
If you already have ideas for the solution describe them here
Workflow checklist
- [ ] I discussed the issue with someone else than me before working on a solution
- [ ] I already read the latest version of the workflow for this repository
- [ ] The goal of this ontology is clear to me
I am aware that
- [ ] every entry in the ontology should have a definition
- [ ] classes should arise from concepts rather than from words
I propose to change the definition to: A superconducting magnetic energy storage (SMES) is an energy storage object that stores electrical energy in the magnetic field of a superconducting magnet. All the other parts of the old definition are imho irrelevant for the domain. If needed, we can add them later as separate concepts.
Also, we should use superconducting magnet energy storage
as label and SMES
as alternative label.
@OpenEnergyPlatform/oeo-domain-expert-energy-modelling : Any objections against redefining SMES to: A superconducting magnetic energy storage (SMES) is an energy storage object that stores electrical energy in the magnetic field of a superconducting magnet.?
I agree to your suggestions, this sums up the important aspects of SMES that distinguish it from other energy storage objects and thus is sufficient for the OEO.
Okay, then I will implement this.