HP WBEM Services Software Developer's Kit for HP-UX Provider and Client Developer's Guide A.01

Schema Design and Implementation
Schema Implementation
Chapter 346
Schema Implementation
In addition to the DMTF-specified syntax for MOF files as described in
the CIM specification and the guidance provided by the DMTF MOF
Style Guide, additional factors should be considered for the development,
testing, and on-going maintenance of MOF files.
MOF File Content Guidelines
MOF is the standard format for defining CIM objects. HP WBEM
Services for HP-UX includes a MOF compiler for loading of schema into
the CIM Server's repository (please see the man page for the cimmof
command, as well as discussion below). Tasks that can be performed
through loading MOF file via the CIM Server's MOF compiler include:
(1) defining classes (and associated superclasses), (2) defining qualifiers,
and (3) creating instances of classes.
• Class/Superclass Definitions
Classes, along with their associated superclasses, are defined in
MOF files. All superclasses should be included in the schema
definition. Order of definition is important, so superclasses must be
defined prior to their subclasses (no forward referencing). When
referencing DMTF-defined objects, include the class definitions
verbatim.
Changes to DMTF classes are implemented through the DMTF
change request (CR) process, and so should not be implemented ad
hoc by a provider implementer. HP WBEM Services for HP-UX is
installed with DTMF CIM v2.5 preloaded in the root/cimv2
namespace.
• Qualifiers
Generally speaking, there is no need to define additional qualifiers
via MOF files. Use of the existing DMTF-defined qualifiers is
sufficient. Qualifiers are defined during the creation of each
namespace in the CIM Server's repository and should not be
redefined in MOF files.
A full list of the qualifiers and their definitions can be found on the
DMTF web site, http://www.dmtf.org.