OEO Developer Meeting #20

Pads:
• Notes from last meeting: https://etherpad.wikimedia.org/p/oeo-dev-19
• Pad to this meeting: https://etherpad.wikimedia.org/p/oeo-dev-20
• Pad for next meeting: https://etherpad.wikimedia.org/p/oeo-dev-21

Date:
• 2021-07-01, 10:00 – 12:00

Participants: Simon, Vera, Mirjam, Christian, Ulrich, Hedda, Carsten
• moderator: Mirjam
• protocol: Hedda, all
• next meeting organisier: Hedda (supported by Mirjam and Carsten)

Preparation:
• Read last protocol: https://github.com/OpenEnergyPlatform/ontology/wiki/OEO-developermeetings
• https://etherpad.wikimedia.org/p/oeo-dev-19
• Check issues for next release: https://github.com/OpenEnergyPlatform/ontology/milestones
• Load software (GitHub, git, Protégé, DFN)

Agenda
Results from OEO-Dev-Market Meeting (June 25th)
•	Reported by Ulrich
•	Protocol to be found here: https://etherpad.wikimedia.org/p/oeo-dev-markets
•	Terms from meeting notes that are marked as "tbd domain experts":
o	Dispatch assignment: The term ‘dispatch’ refers to resource planning at a power plant by the plant’s operator.
	classification: plan specification
	dispatch assignment is a plan specification that refers to resource planning at a power plant (usually by the plant’s operator).
	oeo-social? plan specification is in "iao-module.owl" so ? 
o	Power plant portfolio: the particular combination or mix of different power plants, e.g. renewables and fossil plants within one business unit or company or trader.
	A power plant portfolio is an information content entity that describes a particular combination or mix of different power plants, e.g. renewables and fossil plants within one business unit or company or trader.
	classification: information content entity ?
	related: is traded at energy market exchange
o	YieldProfile is a generation time series of a particular renewable power plant.
	upper  class: time series
	generation time series is a time series that describes the specific electricity generation of a particular power plant.
o	DemandTrader: A trader that is the relay to agents that have a demand 
	demand in oeo: A demand is a realizable entity that is characterised by a person, organisation or object needing it for a specific purpose.
	if trader is implemented => not needed, type of trader
	upper class trader
	A demand trader is a trader that deals specifically with energy demand.
o	Full load hours
	quantity value: Full load hours are a quantity value that describe the utilization of a technical device. The value of the full load hours is obtained by dividing the annual amount of energy generated by the declared net capacity of the plant.
	axiom: has unit some hour
	implementation in oeo-physical
	technical device: all "devices" that can be switched on/off ? --> issue about device: https://github.com/OpenEnergyPlatform/ontology/issues/465
	classification:
•	process attribute of power generating process
•	or time series
•	information content entity
•	--> quantity value
o	Direct marketer is a trader who is the relay between the energy exchange and power plant operators.
	upper class: trader
	implementation in oeo-social
o	markup / markdown
	an amount added or deducted to/from the cost price to determine the selling price
	do we need this? --> next meeting
o	Product product
	something (such as a service) that is marketed or sold as a commodity
	manufactured commodity, disjoint from service
	how does this relate to service? is commodity sufficient?
	--> next meeting
•	Provider directly under “thing”
o	Please check implementation
o	--> fixed in https://github.com/OpenEnergyPlatform/ontology/pull/783
•	Future task: define "energy demand" (we already have "energy demand sector")
o	@CH open issue: define "energy demand" (we already have "energy demand sector")
New OEO-HiWi
•	Kai, Student at IER University of Stuttgart
What happened to our CI? 
•	https://github.com/OpenEnergyPlatform/ontology/discussions/777)
•	travis deprecated? It doesn't start automatically anymore.
•	travis.org is now travis.com 
•	stays free or switch to github actions?
•	ToDo: SF talks to MG
Release process
•	@Simon implementiert und releast
•	@CH macht Review 782