![]() ![]() |
![]() |
File: [Pegasus] / pegasus / Schemas / CIM231 / DMTF / Core / CIM_CollectionOfMSEs.mof
(download)
Revision: 1.1, Tue Jan 24 13:49:59 2012 UTC (12 years, 5 months ago) by marek Branch: MAIN CVS Tags: preBug9676, postBug9676, TASK-TASK_PEP362_RestfulService_branch-root, TASK-TASK_PEP362_RestfulService_branch-merged_out_from_trunk, TASK-TASK_PEP362_RestfulService_branch-merged_in_to_trunk, TASK-TASK_PEP362_RestfulService_branch-merged_in_from_branch, TASK-TASK_PEP362_RestfulService_branch-branch, TASK-PEP362_RestfulService-root, TASK-PEP362_RestfulService-merged_out_to_branch, TASK-PEP362_RestfulService-merged_out_from_trunk, TASK-PEP362_RestfulService-merged_in_to_trunk, TASK-PEP362_RestfulService-merged_in_from_branch, TASK-PEP362_RestfulService-branch, TASK-PEP317_pullop-merged_out_from_trunk, TASK-PEP317_pullop-merged_in_to_trunk, RELEASE_2_14_1, RELEASE_2_14_0-RC2, RELEASE_2_14_0-RC1, RELEASE_2_14_0, RELEASE_2_14-root, RELEASE_2_14-branch, RELEASE_2_13_0-RC2, RELEASE_2_13_0-RC1, RELEASE_2_13_0-FC, RELEASE_2_13_0, RELEASE_2_13-root, RELEASE_2_13-branch, RELEASE_2_12_1-RC1, RELEASE_2_12_1, RELEASE_2_12_0-RC1, RELEASE_2_12_0-FC, RELEASE_2_12_0, RELEASE_2_12-root, RELEASE_2_12-branch, HEAD, CIMRS_WORK_20130824 Branch point for: TASK-PEP317_pullop-branch BUG#:9155 TITLE: Upgrade Pegasus to Include the CIM 2.31 Schema in CVS DESCRIPTION: |
// Copyright (c) 2005 DMTF. All rights reserved. // <change cr="SysDevCR00707.002" type ="add">CPUBS corrections to CoreCollection.mof</change> // <change cr="ArchCR00066.004" type="add">Add UmlPackagePath // qualifier values to CIM Schema.</change> // ================================================================== // CIM_CollectionOfMSEs // ================================================================== [Abstract, Version ( "2.10.0" ), UMLPackagePath ( "CIM::Core::Collection" ), Description ( "The CollectionOfMSEs object allows the grouping of Managed " "SystemElements for various identification purposes and to " "reduce the complexity of associating Settings and " "Configurations. It is abstract to require further definition " "and semantic refinement in subclasses. The CollectionOfMSEs " "object does not carry any state or status information, but " "represents only a grouping or \'bag\' of Elements. For this " "reason, it is incorrect to subclass groups that have state or " "status from CollectionOfMSEs. An example is CIM_Redundancy " "Group (which is subclassed from LogicalElement). \n" "Collections typically aggregate similar (\'like\') objects,but " "they are not required to do so. Collections simply identify " "\'bags\' and might represent an optimization. This purpose is " "especially true with respect to their association to Settings " "and Configurations. Without Collections, you would need to " "define individual ElementSetting and ElementConfiguration " "associations, to tie Settings and Configuration objects to " "individual ManagedSystemElements. There might be duplication " "when assigning the same Setting to multiple objects. In " "addition, using the Collection object allows the determination " "that the Setting and Configuration associations are indeed the " "same for the Collection\'s members. This information would " "otherwise be obtained by defining the Collection in a " "proprietary manner, and then querying the ElementSetting and " "ElementConfiguration associations to determine if the " "Collection set is completely covered." )] class CIM_CollectionOfMSEs : CIM_Collection { [Description ( "The identification of the Collection object. When " "subclassed, the CollectionID property can be overridden " "to be a Key property." ), MaxLen ( 256 )] string CollectionID; };
No CVS admin address has been configured |
Powered by ViewCVS 0.9.2 |