Class Hierarchy
Class Attributes
Class Qualifiers
Properties
Methods
Associations in which the class can participate
Sub Profiling Summary
CIM_ConcreteIdentity --> CIM_LogicalIdentity --> [top]
Class Declaration Attributes Name Value SUPERCLASS CIM_LogicalIdentity NAME CIM_ConcreteIdentity
Class CIM_ConcreteIdentity Qualifiers Name Type Value From Class Version string 2.10.0 CIM_ConcreteIdentity Description string CIM_ConcreteIdentity associates two elements that represent different aspects of the same underlying entity. It is defined as a concrete subclass of the abstract CIM_LogicalIdentity class, to be used in place of many specific subclasses of LogicalIdentity that add no semantics, that is, subclasses that do not clarify the type of identity, update cardinalities, or add or remove qualifiers. Note that when you define additional semantics for LogicalIdentity, this class should not be subclassed. Specific semantics continue to be defined as subclasses of the abstract CIM_LogicalIdentity. ConcreteIdentity is limited in its use as a concrete form of a general identity relationship. It was deemed more prudent to create this concrete subclass than to change LogicalIdentity from an abstract to a concrete class. LogicalIdentity already had multiple abstract subclasses in the CIM Schema, and wider industry usage and impact could not be anticipated. CIM_ConcreteIdentity Association boolean true CIM_ConcreteIdentity Association boolean true CIM_LogicalIdentity Description string CIM_LogicalIdentity is an abstract and generic association, indicating that two ManagedElements represent different aspects of the same underlying entity. This relationship conveys what could be defined with multiple inheritance. In most scenarios, the Identity relationship is determined by the equivalence of Keys or some other identifying properties of the related Elements. This relationship is reasonable in several scenarios. For example, it could be used to represent that a LogicalDevice is both a ’ bus ’ entity and a ’ functional ’ entity. A Device could be both a USB (bus) and a Keyboard (functional) entity. CIM_LogicalIdentity
Properties Name Type Value Qualifiers ClassOrigin SystemElement CIM_ManagedElement ref Override
Description
KeyCIM_ConcreteIdentity SameElement CIM_ManagedElement ref Override
Description
KeyCIM_ConcreteIdentity Property Qualifiers
Property SystemElement Qualifiers Name Type Value From Class Override string SystemElement CIM_ConcreteIdentity Description string One aspect of the ManagedElement. The use of ’ System ’ in the name does not limit the scope of the association. This name is an artifact of the original definition of the association. CIM_ConcreteIdentity Key boolean true CIM_ConcreteIdentity
Property SameElement Qualifiers Name Type Value From Class Override string SameElement CIM_ConcreteIdentity Description string Another aspect of the ManagedElement. CIM_ConcreteIdentity Key boolean true CIM_ConcreteIdentity
Property SystemElement Qualifiers Name Type Value From Class Key boolean true CIM_LogicalIdentity Description string SystemElement represents one aspect of the Managed Element. The use of ’ System ’ in the role name does not limit the scope of the association. The role name was defined in the original association, where the referenced elements were limited to LogicalElements. Since that time, it has been found valuable to instantiate these types of relationships for ManagedElements, such as Collections. So, the referenced elements of the association were redefined to be ManagedElements. Unfortunately, the role name could not be changed without deprecating the entire association. This was not deemed necessary just to correct the role name. CIM_LogicalIdentity
Property SameElement Qualifiers Name Type Value From Class Key boolean true CIM_LogicalIdentity Description string SameElement represents an alternate aspect of the ManagedElement. CIM_LogicalIdentity
Method Qualifiers
Parameters
Parameter Qualifiers