CIM Issues #4218
Add Inheritance from Naming Class For Top Level Classes: F
Status:
Closed
Priority:
Normal
Author/Contact Info:
H. Cai
Base Release:
Solution to be Applied To:
Solution Version:
CIM10
Solution Applied By:
Completion Date:
CIM Keywords:
Breaking Change:
No
Breaking Change Description:
CIM Impacted Groups:
WG13
Requestor:
Standard(s):
Version:
Clause:
Sub-Clause:
Paragraph:
Table:
Originally Closed in Version:
CIM10
Origination Date:
01/25/2001
Origination ID:
40
Originally Assigned To:
Description
Add Inheritance from Naming Class For Top Level Classes:
FossilFuel
RemoteSource
EnergyTransaction
AreaReserveSpec
TieLine
ProfileData
TransmissionPath
ServiceReservation
BaseVoltage
PerUnits
61970Quality
Season
Decision
WG13: Agree to fix those in Part 301. Issue to discuss - when to use Naming class (generic) vs. keeping specialized type for name (e.g., fossilFuelName. What is intended scope of Naming class? 3/12 - agree to these changes that are in Part 301 (except BaseVoltage and PerUnits (which don't have names) and 61970Quality (removed from model earlier)
No data to display