CIM Issues #4030
class CompositeSwitchType <<CIMDataType>> problems Incons
Description
class CompositeSwitchType <<CIMDataType>> problems
Inconsistent use of strong type. Normally we don't create new types for each use of string. There is no normative use for this type and its likely meaningless outside the scope of orginator of data, or could simply be a description. Concrete and immediate problems are the lack of "unit" and "multiplier" attributes as are "required" for each CIMDatatype class. The jCleanCim validator correctly complains about this inconsistent use of CIMDatatype. (From issue 13_44).
Proposed Solution
Delete or model something more meaningful. At least change the type of the CompositeSwitch.compositeSwitchType to be primitive String and delete the CIMDatatype that is not reused.
Decision
2011-04-20 - decision to change to String. Delete the CompositeSwitchType datatype. Rename attribute to "type".
2011-04-19 KDD - implemented fixes so validator would pass but no name changes in 61970cim15v22. Renames will have to wait until CIM16.
2011-12-07 KDD - deleted CompositeSwitchKind and changed attribute compositeSwitchType to be type String. Larger rework of CompositeSwitch will wait for driving use case.
2012-11-07 WG 13 - Agreed to changes previously made to address this issue. Issue closed.
No data to display