Ontology: Check definition of Hydropower and WaterTurbine

[Izzet91]

• [ ] 1. Splitting Hydropower in Hydro and Ocean as two different Types of EnergyCarrier

• [x] 2. WaterTurbine replaced with OceanPowerPlant and HydroPowerPlant
  note: not replaced but all exist now

• [x] 3. Subclasses of OceanPowerplant are WavePowerPlant and TidalPowerPlant

• [ ] 4. Subclasses of HydroPowerplant are ReservoirPowerPlant and RunOfRiverPowerplant

• [x] 5. Subclasses of ReservoirPowerPlant are StorageHydropowerPlant, PumpstoragePowerPlant and PumpstoragePowerPlantWithNaturalInflux

• [ ] 5.OceanPowerplant uses some Ocean

• [ ] 6.HydroPowerplant uses some Hydro

To 5. A Storage Powerplant has no Pump system. Pumpstorage Power Plants can have a natural influx but also not.

[stap-m]

Splitting Hydropower in Hydro and Ocean as two different Types of EnergyCarrier

In my understanding, the energyCarrier is 'water', maybe with subclasses 'wave', 'tide'.

[Ludee]

It makes sense to seperate the 'water' used in HydroPowerplants and 'water' used in OceanPowerplants:
option 1: water -> ocean; river / ocean -> tidal; wave
option 2: water -> river, tidal, wave

[stap-m]

option 2: water -> river, tidal, wave

I'd prefer option 2 and use 'tide' instead of 'tidal' since the carrier is the tide.

Actually, I also thougt about the 'river' option in my comment above, but was indecisive with the term, so I left it out. Maybe 'flow' or 'river flow' as an alternative, since it is the moving, that carries the energy?!

[stap-m]

Refering to #41, I'd like to propose something completely different:

• [x] 1. energyCarrier is_a BFO: disposition / BFO: specifically dependent continuant

• [x] 2. BFO: object water has_disposition energyCarrier --> we avoid loosing single inhertiance, since water is _not just_ an energyCarrier, nor is biogas etc.

• [ ] 3. tide, wave etc are BFO: fiat object parts of water, also having_disposition energyCarrier

@gnn what do you think?

[akleinau]

current state:

• EnergyCarrier: disposition
• PortionOfWater has disposition some EnergyCarrier
• Wave: PortionOfWater
• Ocean: PortionOfWater
• Tide, Flow: Process
• HydroEnergy: Energy
• WaterTurbine: Turbine; HydroPowerplant, Oceanpowerplant: ArtificialObject
• TidalPowerplant, WavePowerplant: OceanPowerplant
• ReservoirPowerplant: HydroPowerplant; RunOfRiverPowerplant: HydroelectricPowerplant
• all subclasses of ReservoirPowerplant are there

Missing:

• unify Powerplants, there are two hierarchies right now (will make new issue)
• powerplants dont have energyCarrier relationships yet
• overthink classification of Tide, Flow, Wave, Ocean and maybe river/ riverFlow

[akleinau]

related to #78

[stap-m]

How do we proceed here regarding the release? Temporarily delete all classes that are not fairly defined and reinclude them when we've discussed the "water" issues?

[akleinau]

yes sounds reasonable

[akleinau]

I propose to delete:

• tide wave ocean
• tide
• flow
• wave

[l-emele]

I am fine with deleting these,

[stap-m]

I remove the milestone accordingly.

[l-emele]

I suggest that we close this issue and concentrate the discussion in issue #78 .