CIM Issues » WG14 Issues

This issue officially was revisited on 11-Mar-2024 at the IEC/UCA Joint TF13/14/16/21 Meeting @ Siemens:

Originally, there was a proposal to remove all <<Compound>>s from the CIM. At the time of the creation of this Redmine issue the topic was debated extensively and both extremes were explored. Here was the outcome at that time with corresponding decisions:

Restating once again the decisions made:

1. Compounds are acceptable but should be used judiciously. Not all serialization formats work well with Compounds (e.g. RDF CIM/XML). The idea is to lean towards not creating new <<Compound>> classes as we move forward (and if needed only on rare occasions and only upon joint TF review and mutual consensus).
2. The key concern is that there must not be multiple levels of Compound within a Compound class. This was a primary point of concern.

This is should be closed as we are not planning to remove all <<Compound>> classes.

An additional comment from the 11-Mar-2024 meetings:

Should be noted that a verification was done on the latest CIM Modeling Guidelines document. It was confirmed that a Rule283 had been introduced that reflects the decisions previously made:

Rule283
A Compound datatype may not contain an attribute with a Compound datatype.