Implement rated voltage

[ColinHDev]

Summary of the discussion

As discussed in the 103rd oeo-dev meeting and in #2107, there should be an information content entity representing the categorization of voltage into various levels.

Type of change (CHANGELOG.md)

Add

• Performance Specification from CCO
• rated voltage from CHIO
  • subclass of Performance Specification
  • definition: A Performance Specification that prescribes the intended operating voltage of some electrical artifact.
• low rated voltage
  • subclass axioms:
    • rated voltage
    • prescribes value 'low electricity grid voltage level'
  • definition: A low rated voltage is a rated voltage usually used for the local distribution of electricity. Electricity at this voltage can be converted to a medium rated voltage. The usual producers feeding electricity into the grid at this voltage are smaller wind farms and solar installations. Households are the usual consumers receiving electricity at this voltage.
• medium rated voltage
  • subclass axioms:
    • rated voltage
    • prescribes value 'medium electricity grid voltage level'
  • definition: A medium rated voltage is a rated voltage usually used for the regional distribution of electricity. Electricity at this voltage can be converted to a high or low rated voltage. The usual producers feeding electricity into the grid at this voltage are wind and solar farms. Industries can be consumers receiving electricity at this voltage.
• high rated voltage
  • subclass axioms:
    • rated voltage
    • prescribes value 'high electricity grid voltage level'
  • definition: A high rated voltage is a rated voltage usually used for the interregional distribution of electricity. Electricity at this voltage can be converted to an extra high or medium rated voltage. The usual producers feeding electricity into the grid at this voltage are natural gas and hydro power plants. Large-scale industries can be consumers receiving electricity at this voltage.
• extra high rated voltage
  • subclass axioms:
    • rated voltage
    • prescribes value 'extra high electricity grid voltage level'
  • definition: An extra high rated voltage is a rated voltage usually used for the transmission of electricity. This is the usual voltage for electricity imports and exports. Electricity at this voltage can be converted to a high rated voltage. The usual producers feeding electricity into the grid at this voltage are coal and nuclear power plants, as well as offshore wind farms and hydro power plants.

Update

• electricity grid voltage level
  • added subclass axiom 'prescribed by' some 'rated voltage'
• electricity grid component
  • added subclass axiom 'is subject of' some 'rated voltage'

Workflow checklist

Automation

Closes #2107

PR-Assignee

• 🐙 Follow the Pull Request Workflow
• 📝 Update the CHANGELOG.md
• 📙 Add #'s to term tracker annotation

Reviewer

• 🐙 Follow the Reviewer Guide
• 🐙 Provided feedback and show sufficient appreciation for the work done

[ColinHDev]

@stap-m
So, I've imported Performance Specification so far. In the CCO it has the following two parent classes:

1. Directive Information Content Entity: A Directive Information Content Entity that prescribes some aspect of the behavior of a participant in a Process given one or more operating conditions.
   • I've just used our Directive Information Entity: An information content entity whose concretizations indicate to their bearer how to realize them in a process. I think, both definitions are similar enough, to use our class as a replacement
2. 'describes condition' some entity: __
   • describes condition: p describes_condition c iff p is an instance of a Performance Specification, and p has part d, and d is an instance of a Descriptive Information Content Entity, and p prescribes an entity s, and d describes c, and c is an entity that is causally relevant to s existing as prescribed by p. is a sub-property of is about, which we currently don't have
   • Should I import it as well to add this axiom? Otherwise, I think we could just remove it, because describes condition is specially tailored towards Performance Specification. I wouldn't see the point in replacing the axiom with is about some entity

[stap-m]

Let's not import describes condition, but comment in Performance Specification, that we left out this axiom (oeo-import-edits).