CIM V2.5 Readme

 

The following describes the MOF changes from CIM V2.4 to V2.5. Errata are
labeled using the designation, (E). Errata are indicated as the first
changes in the detailed descriptions below AND included, where appropriate,
in the model specific summaries.
A minor structural change to the MOF files can be seen in CIM V2.5. Changes
to existing classes, descriptions and properties (such as addition of new
properties, wording updates and enumeration changes) are made directly to
the V2.4 MOF files, to produce the CIM V2.5 files. New classes and
associations are placed in a new MOF file. This file is named using the
convention, CIM_<model nameversion><_Add>.mof - for example,
CIM_Core25_Add.mof. The new MOF file is added to the correct model via
a "#pragma include" statement at the end of the file. For example, the
following statement would be added to the end of the CIM_Core25.mof -
#pragma include ("CIM_Core25_Add.mof"). This structure indicates
the basic difference in level of review and testing between relatively minor
modifications to existing classes, and totally new classes requiring more
extensive review, analysis and test implementation.

NOTE: The headers of the individual MOF files indicate their contents.

Specifically, Change Requests dealing with updates to existing classes will

be documented in the standard V2.x files. On the other hand, Change

Requests adding new classes and associations will be documented in the

headers to the CIM_<model nameversion><_Add>.mof file.

ERRATA:

 

CORE MODEL:

 

INDICATION MODEL:

 

SYSTEM MODEL:

 

DEVICE MODEL:

 

APPLICATION MODEL:

NETWORK MODEL:

POLICY MODEL:

SUPPORT MODEL:

DAP MODEL: