1 kumpf 1.2 // ===================================================================
2 // Title: Core Capabilities 2.7
3 // Filename: Core27_Capabilities.mof
4 // Version: 2.7.0
5 // Release: Final
6 // Date: 03/31/03
7 // ===================================================================
8 // Copyright 2002-2003 Distributed Management Task Force, Inc. (DMTF).
9 // All rights reserved.
10 // DMTF is a not-for-profit association of industry members dedicated
11 // to promoting enterprise and systems management and interoperability.
12 // DMTF specifications and documents may be reproduced for uses
13 // consistent with this purpose by members and non-members,
14 // provided that correct attribution is given.
15 // As DMTF specifications may be revised from time to time,
16 // the particular version and release date should always be noted.
17 //
18 // Implementation of certain elements of this standard or proposed
19 // standard may be subject to third party patent rights, including
20 // provisional patent rights (herein "patent rights"). DMTF makes
21 // no representations to users of the standard as to the existence
22 kumpf 1.2 // of such rights, and is not responsible to recognize, disclose, or
23 // identify any or all such third party patent right, owners or
24 // claimants, nor for any incomplete or inaccurate identification or
25 // disclosure of such rights, owners or claimants. DMTF shall have no
26 // liability to any party, in any manner or circumstance, under any
27 // legal theory whatsoever, for failure to recognize, disclose, or
28 // identify any such third party patent rights, or for such party's
29 // reliance on the standard or incorporation thereof in its product,
30 // protocols or testing procedures. DMTF shall have no liability to
31 // any party implementing such standard, whether such implementation
32 // is foreseeable or not, nor to any patent owner or claimant, and shall
33 // have no liability or responsibility for costs or losses incurred if
34 // a standard is withdrawn or modified after publication, and shall be
35 // indemnified and held harmless by any party implementing the
36 // standard from any and all claims of infringement by a patent owner
37 // for such implementations.
38 //
39 // For information about patents held by third-parties which have
40 // notified the DMTF that, in their opinion, such patent may relate to
41 // or impact implementations of DMTF standards, visit
42 // http://www.dmtf.org/about/policies/disclosures.php.
43 kumpf 1.2 // ===================================================================
44 // Description: The Core Model defines basic management concepts.
45 // This file defines the management concepts related
46 // to the Capabilities of a ManagedElement.
47 //
48 // The object classes below are listed in an order that
49 // avoids forward references. Required objects, defined
50 // by other working groups, are omitted.
51 // ==================================================================
52 // Change Log for v2.7
53 // CR968 - Remove the Experimental qualifier
54 // CR994 - Updates to InstanceID description.
55 //
56 // Change Log for v2.7
57 // CR 730 - Introduce Capabilites and ElementCapabilities
58 // ==================================================================
59
60 #pragma locale ("en_US")
61
62
63 // ==================================================================
64 kumpf 1.2 // Capabilities
65 // ==================================================================
66 [Abstract, Version ("2.7.0"), Description (
67 "Capabilities is an abstract class whose subclasses "
68 "describe abilities and/or potential for use. For "
69 "example, one may describe the maximum number of VLANs that "
70 "can be supported on a system using a subclass of "
71 "Capabilities. Capabilities are tied to the elements "
72 "which they describe using the ElementCapabilities "
73 "association. Note that the cardinality of the ManagedElement "
74 "reference is Min(1), Max(1). This cardinality mandates the "
75 "instantiation of the ElementCapabilities association for the "
76 "referenced instance of Capabilities. ElementCapabilities "
77 "describes the existence requirements and context for the "
78 "referenced instance of ManagedElement. Specifically, the "
79 "ManagedElement MUST exist and provides the context for the "
80 "Capabilities. Note that Capabilities do not indicate "
81 "what IS configured or operational, but what CAN or CANNOT "
82 "exist, be defined or be used. Note that it is possible to "
83 "describe both supported and excluded abilities and functions "
84 "(both capabilities and limitations) using this class.") ]
85 kumpf 1.2 class CIM_Capabilities : CIM_ManagedElement {
86
87 [Key, Description (
88 "Within the scope of the instantiating Namespace, InstanceID "
89 "opaquely and uniquely identifies an instance of this class. "
90 "In order to ensure uniqueness within the NameSpace, the "
91 "value of InstanceID SHOULD be constructed using the "
92 "following 'preferred' algorithm: \n"
93 " <OrgID>:<LocalID> \n"
94 "Where <OrgID> and <LocalID> are separated by a colon ':', "
95 "and where <OrgID> MUST include a copyrighted, trademarked "
96 "or otherwise unique name that is owned by the business entity "
97 "creating/defining the InstanceID, or is a registered ID that is "
98 "assigned to the business entity by a recognized global "
99 "authority (This is similar to the <Schema Name>_<Class Name> "
100 "structure of Schema class names.) In addition, to ensure "
101 "uniqueness <OrgID> MUST NOT contain a colon (':'). When using "
102 "this algorithm, the first colon to appear in "
103 "InstanceID MUST appear between <OrgID> and <LocalID>. \n"
104 " <LocalID> is chosen by the business entity and SHOULD not be "
105 "re-used to identify different underlying (real-world) elements. "
106 kumpf 1.2 "If the above 'preferred' algorithm is not used, the defining "
107 "entity MUST assure that the resultant InstanceID is not "
108 "re-used across any InstanceIDs produced by this or other "
109 "providers for this instance's NameSpace. \n"
110 "For DMTF defined instances, the 'preferred' algorithm MUST be "
111 "used with the <OrgID> set to 'CIM'.") ]
112 string InstanceID;
113
114 [Override ("ElementName"), Required, Description (
115 "The user friendly name for this instance of Capabilities. "
116 "In addition, the user friendly name can be used as a "
117 "index property for a search of query. (Note: Name "
118 "does not have to be unique within a namespace.)") ]
119 string ElementName;
120 };
121
122
123 // ===================================================================
124 // ElementCapabilities
125 // ===================================================================
126 [Association, Version ("2.7.0"), Description (
127 kumpf 1.2 "ElementCapabilities represents the association between "
128 "ManagedElements and their Capabilities. "
129 "Note that the cardinality of the ManagedElement "
130 "reference is Min(1), Max(1). This cardinality mandates the "
131 "instantiation of the ElementCapabilities association for the "
132 "referenced instance of Capabilities. ElementCapabilities "
133 "describes the existence requirements and context for the "
134 "referenced instance of ManagedElement. Specifically, the "
135 "ManagedElement MUST exist and provides the context for the "
136 "Capabilities.") ]
137 class CIM_ElementCapabilities {
138
139 [Key, Min(1), Max(1), Description (
140 "The managed element.") ]
141 CIM_ManagedElement REF ManagedElement;
142
143 [Key, Description (
144 "The Capabilities object associated with the element.") ]
145 CIM_Capabilities REF Capabilities;
146 };
147
148 kumpf 1.2
149 // ===================================================================
150 // end of file
151 // ===================================================================
|