1 karl  1.1 /*
 2           */
 3           /** @name CIM Objects in Pegasus
 4           
 5           The Common Information model (CIM) consists of a number of basic objects
 6           defined in the CIM specification.  This includes:
 7           <UL>
 8           <LI>Classes \Ref{CLASS}
 9           <LI>Instances of Classes \Rf{REFERENCE}
10           <LI>Qualifiers \Ref{QUALIFIER}
11           <LI>Properties
12           <LI>Methods
13           <LI>Arrays
14           </UL>
15           Pegasus implements representations of these objects in C++ classes and
16           provides methods for creation, manipulation, and deletion of the objects.
17           

18 karl  1.3 

19 karl  1.1 In addition, Pegasus implements a number of the key concepts built into CIM as objects including:
20           <UL>
21           <LI> Scope
22           <LI> Flavor

23 karl  1.2 <LI>Object Path
24           <LI>etc.

25 karl  1.1 </UL>
26           

27 karl  1.3 Much of the programming of the Pegasus object broker, clients, and in particular providers and service extensions in the Pegasus envrinment depends on the use of these C++ representations of CIM Objects and concepts.
28           
29           Each Pegasus CIM C++ Object representation includes:

30 karl  1.1 

31 karl  1.3 <UL>
32           <LI>TConstructors and destructors
33           <LI>Methods for manipulation of sub-objects.  Thus, the class and instance classes provide for manipulation of the property, qualifier, and method objects that are contained in these classes.
34           <LI>Methods for finding sub-objects. Thus, the class and instance classes provide for finding property, qualifier, and method objects within an instnace of a CIMClass or CIMInstance. These methods are generally built around defining the name of the object to be found and having an index to that object returned.
35           <LI>Methods for comparison
36           <LI>Methods for cloning
37           <LI>Methods to convert the object to XML
38           <LI>Methods to convert the object to MOF (Planned)
39           </UL>
40           There is a class for every major CIM object and concept as shown in the table in \Ref{CIM Object Table}

41 karl  1.1 */