-
Notifications
You must be signed in to change notification settings - Fork 31
Description
Description of the issue
In existing classes like HVDC-line and AC-line we refer to the term current. This is also necessary to describe the differences of AC and DC charging processes that may come out of #1444
Along the same lines we have things like resistance and voltage
Ideas of solution
This should not be very complicated to implement since we already have some parallels. Using for example the water flow axioms.
water flow has process attribute some water flow rate
water flow rate has quantity value some volumetric flow rate value
We could add the axioms for electrical energy transfer:
electrical energy transfer alternative label current or electric current
electrical energy transfer has process attribute some current intensity
current intensity has quantity value some current intensity value
electrical energy transfer has process attribute some resistance
resistance has quantity value some resistance value
electrical energy transfer has process attribute some voltage
voltage has quantity value some voltage value
Definitions:
current intensity: "Current intensity is the process attribute of an electrical energy transfer which quantifies the rate of electrons flowing through it."
resistance: "Resistance is the process attribute of an electrical energy transfer which quantifies the opposition to electron flow."
voltage: "Voltage is the process attribute of an electrical energy transfer which quantifies the electron flow potential differences of its starting and ending points."
We could also add subclasses of electrical energy transfer:
Alternate current: "An alternate current is an electrical energy transfer whose charge changes during the flow"
Direct current: "A direct current is an electrical energy transfer whose charge is constant during the flow"
I was also thinking of axiomizing charge but, since alternate current changes the charge constantly this may be tricky. What we could have is still define charge as an attribute but not axiomize it.
Please let me know if you agree with these definitions, I would like to implement them asap as I need them for work.
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
Metadata
Metadata
Assignees
Labels
Type
Projects
Status