You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This new rule should be defined as Rule059 (we currently have a gap available which should be filled by this one. This issue was discussed during on 26-Oct-2023 Joint WG Hybrid meetings in Minneapolis. Final decisions were made as indicated in the Redmine issue and further highlighted in detail via Richard de Groot's email (16-Oct-2023 15:24) to WG13 containing his review and rule proposal as shown below:
Concrete proposal
To make matters concrete, the following text could be considered for the "Decision" section if we decide not to reverse our decision.
---START TEXT---
18-Oct-2023
We have reviewed and updated as follows.
The attribute rule to be added to section 5.5 of the CIM Modelling Guide Document is as follows:
For the properties listed below, the attribute name must use the symbol, in lower camel case, instead of the name or unit of measurement.
Active Power (p)
Reactive Power (q)
Apparent Power (s)
Resistance (r)
Reactance (x)
Conductance (g)
Susceptance (b)
Power Factor (pf)
Voltage (u)
Current (i)
Frequency (f)
Inductance (l)
Capacitance (c)
Impedance (z)
Admittance (y)
For the properties mentioned in item 1, the symbol is appended with "2" for negative-sequence and "0" for zero-sequence properties.
Where properties mentioned in item 1 are used in a compound term (e.g. maximum voltage, nominal apparent power, natural impedance), the value name is written in full. The attribute name as a whole complies to Rule 049.
In the specific cases of BaseFrequency.frequency and BasePower.basePower, the new attribute names will be BaseFrequency.value and BasePower.value.
The text was updated successfully, but these errors were encountered:
A new rule is to be added per Redmine Issue # 6202
This new rule should be defined as Rule059 (we currently have a gap available which should be filled by this one. This issue was discussed during on 26-Oct-2023 Joint WG Hybrid meetings in Minneapolis. Final decisions were made as indicated in the Redmine issue and further highlighted in detail via Richard de Groot's email (16-Oct-2023 15:24) to WG13 containing his review and rule proposal as shown below:
The text was updated successfully, but these errors were encountered: