1 krisbash 1.1 // Copyright (c) 2005 DMTF.  All rights reserved.
 2              // <change cr="SysDevCR00707.002" type ="add">CPUBS corrections to CoreCollection.mof</change>
 3              // <change cr="ArchCR00066.004" type="add">Add UmlPackagePath
 4              // qualifier values to CIM Schema.</change>
 5              // ==================================================================
 6              //  CIM_CollectionOfMSEs 
 7              // ==================================================================
 8                 [Abstract, Version ( "2.10.0" ), 
 9                  UMLPackagePath ( "CIM::Core::Collection" ), 
10                  Description ( 
11                     "The CollectionOfMSEs object allows the grouping of Managed "
12                     "SystemElements for various identification purposes and to "
13                     "reduce the complexity of associating Settings and "
14                     "Configurations. It is abstract to require further definition "
15                     "and semantic refinement in subclasses. The CollectionOfMSEs "
16                     "object does not carry any state or status information, but "
17                     "represents only a grouping or \'bag\' of Elements. For this "
18                     "reason, it is incorrect to subclass groups that have state or "
19                     "status from CollectionOfMSEs. An example is CIM_Redundancy "
20                     "Group (which is subclassed from LogicalElement). \n"
21                     "Collections typically aggregate similar (\'like\') objects,but "
22 krisbash 1.1        "they are not required to do so. Collections simply identify "
23                     "\'bags\' and might represent an optimization. This purpose is "
24                     "especially true with respect to their association to Settings "
25                     "and Configurations. Without Collections, you would need to "
26                     "define individual ElementSetting and ElementConfiguration "
27                     "associations, to tie Settings and Configuration objects to "
28                     "individual ManagedSystemElements. There might be duplication "
29                     "when assigning the same Setting to multiple objects. In "
30                     "addition, using the Collection object allows the determination "
31                     "that the Setting and Configuration associations are indeed the "
32                     "same for the Collection\'s members. This information would "
33                     "otherwise be obtained by defining the Collection in a "
34                     "proprietary manner, and then querying the ElementSetting and "
35                     "ElementConfiguration associations to determine if the "
36                     "Collection set is completely covered." )]
37              class CIM_CollectionOfMSEs : CIM_Collection {
38              
39                    [Description ( 
40                        "The identification of the Collection object. When "
41                        "subclassed, the CollectionID property can be overridden "
42                        "to be a Key property." ), 
43 krisbash 1.1        MaxLen ( 256 )]
44                 string CollectionID;
45              };