1 tony 1.1 // ===================================================================
2 // Title: Core Capabilities 2.8
3 // Filename: Core28_Capabilities.mof
4 // Version: 2.8
5 // Status: Final
6 // Date: Jan 26, 2004
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 tony 1.1 // 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 tony 1.1 // ===================================================================
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.8 Final
53 // CR1210 - Removal of experimental qualifiers for core.
54 //
55 // Change Log for v2.8 Preliminary
56 // CR937 - Add LocalizationCapabilities
57 // CR1019 - CIM Versioning for 2.8 Preliminary
58 //
59 // Change Log for v2.7
60 // CR968 - Remove the Experimental qualifier
61 // CR994 - Updates to InstanceID description.
62 //
63 // Change Log for v2.7
64 tony 1.1 // CR 730 - Introduce Capabilites and ElementCapabilities
65 // ==================================================================
66
67 #pragma locale ("en_US")
68
69
70 // ==================================================================
71 // Capabilities
72 // ==================================================================
73 [Abstract, Version ( "2.7.0" ), Description (
74 "Capabilities is an abstract class whose subclasses describe "
75 "abilities and/or potential for use. For example, one may "
76 "describe the maximum number of VLANs that can be supported on "
77 "a system using a subclass of Capabilities. Capabilities are "
78 "tied to the elements which they describe using the "
79 "ElementCapabilities association. Note that the cardinality of "
80 "the ManagedElement reference is Min(1), Max(1). This "
81 "cardinality mandates the instantiation of the "
82 "ElementCapabilities association for the referenced instance of "
83 "Capabilities. ElementCapabilities describes the existence "
84 "requirements and context for the referenced instance of "
85 tony 1.1 "ManagedElement. Specifically, the ManagedElement MUST exist "
86 "and provides the context for the Capabilities. Note that "
87 "Capabilities do not indicate what IS configured or "
88 "operational, but what CAN or CANNOT exist, be defined or be "
89 "used. Note that it is possible to describe both supported and "
90 "excluded abilities and functions (both capabilities and "
91 "limitations) using this class.")]
92 class CIM_Capabilities : CIM_ManagedElement {
93
94 [Key, Description (
95 "Within the scope of the instantiating Namespace, InstanceID "
96 "opaquely and uniquely identifies an instance of this class. "
97 "In order to ensure uniqueness within the NameSpace, the "
98 "value of InstanceID SHOULD be constructed using the "
99 "following 'preferred' algorithm: \n"
100 "<OrgID>:<LocalID> \n"
101 "Where <OrgID> and <LocalID> are separated by a colon ':', "
102 "and where <OrgID> MUST include a copyrighted, trademarked "
103 "or otherwise unique name that is owned by the business "
104 "entity creating/defining the InstanceID, or is a registered "
105 "ID that is assigned to the business entity by a recognized "
106 tony 1.1 "global authority (This is similar to the <Schema "
107 "Name>_<Class Name> structure of Schema class names.) In "
108 "addition, to ensure uniqueness <OrgID> MUST NOT contain a "
109 "colon (':'). When using this algorithm, the first colon to "
110 "appear in InstanceID MUST appear between <OrgID> and "
111 "<LocalID>. \n"
112 "<LocalID> is chosen by the business entity and SHOULD not "
113 "be re-used to identify different underlying (real-world) "
114 "elements. If the above 'preferred' algorithm is not used, "
115 "the defining entity MUST assure that the resultant "
116 "InstanceID is not re-used across any InstanceIDs produced "
117 "by this or other providers for this instance's NameSpace. \n"
118 "For DMTF defined instances, the 'preferred' algorithm MUST "
119 "be used with the <OrgID> set to 'CIM'.")]
120 string InstanceID;
121
122 [Required, Override ( "ElementName" ), Description (
123 "The user friendly name for this instance of Capabilities. "
124 "In addition, the user friendly name can be used as a index "
125 "property for a search of query. (Note: Name does not have "
126 "to be unique within a namespace.)")]
127 tony 1.1 string ElementName;
128 };
129
130
131 // ===================================================================
132 // ElementCapabilities
133 // ===================================================================
134 [Association, Version ( "2.7.0" ), Description (
135 "ElementCapabilities represents the association between "
136 "ManagedElements and their Capabilities. Note that the "
137 "cardinality of the ManagedElement reference is Min(1), Max(1). "
138 "This cardinality mandates the instantiation of the "
139 "ElementCapabilities association for the referenced instance of "
140 "Capabilities. ElementCapabilities describes the existence "
141 "requirements and context for the referenced instance of "
142 "ManagedElement. Specifically, the ManagedElement MUST exist "
143 "and provides the context for the Capabilities.")]
144 class CIM_ElementCapabilities {
145
146 [Key, Min ( 1 ), Max ( 1 ), Description (
147 "The managed element.")]
148 tony 1.1 CIM_ManagedElement REF ManagedElement;
149
150 [Key, Description (
151 "The Capabilities object associated with the element.")]
152 CIM_Capabilities REF Capabilities;
153 };
154
155
156 // ===================================================================
157 // end of file
158 // ===================================================================
|