1 karl 1.1 // ===================================================================
2 // Title: Core Capabilities 2.7
3 // Filename: Core27_Capabilities.mof
4 // Version: 2.7.0
5 // Release: Preliminary
6 // Date: 07/01/02
7 // ===================================================================
8 // Copyright 2002 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 karl 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 karl 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.7
53 // CR 730 - Introduce Capabilites and ElementCapabilities
54 // ==================================================================
55
56 #pragma locale ("en_US")
57
58
59 // ==================================================================
60 // Capabilities
61 // ==================================================================
62 [Abstract, Experimental, Version ("2.7.0"), Description (
63 "Capabilities is an abstract class whose subclasses "
64 karl 1.1 "describe abilities and/or potential for use. For "
65 "example, one may describe the maximum number of VLANs that "
66 "can be supported on a system using a subclass of "
67 "Capabilities. Capabilities are tied to the elements "
68 "which they describe using the ElementCapabilities "
69 "association. Note that the cardinality of the ManagedElement "
70 "reference is Min(1), Max(1). This cardinality mandates the "
71 "instantiation of the ElementCapabilities association for the "
72 "referenced instance of Capabilities. ElementCapabilities "
73 "describes the existence requirements and context for the "
74 "referenced instance of ManagedElement. Specifically, the "
75 "ManagedElement MUST exist and provides the context for the "
76 "Capabilities. Note that Capabilities do not indicate "
77 "what IS configured or operational, but what CAN or CANNOT "
78 "exist, be defined or be used. Note that it is possible to "
79 "describe both supported and excluded abilities and functions "
80 "(both capabilities and limitations) using this class.") ]
81 class CIM_Capabilities : CIM_ManagedElement {
82
83 [Key, Description (
84 "InstanceID opaquely identifies a unique instance of "
85 karl 1.1 "Capabilities. The InstanceID must be unique within a "
86 "namespace. In order to ensure uniqueness, the value of "
87 "InstanceID SHOULD be constructed in the following manner: \n"
88 "<Vendor ID><ID> \n"
89 " <Vendor ID> MUST include a copyrighted, trademarked "
90 "or otherwise unique name that is owned by the business "
91 "entity or a registered ID that is assigned to the business "
92 "entity that is defining the InstanceID. (This is similar to "
93 "the <Schema Name>_<Class Name> structure of Schema class "
94 "names.) The purpose of <Vendor ID> is to ensure that <ID> "
95 "is truly unique across multiple vendor implementations. "
96 "If such a name is not used, the defining entity MUST assure "
97 "that the <ID> portion of the Instance ID is unique when "
98 "compared with other instance providers. For DMTF defined "
99 "instances, the <Vendor ID> is 'CIM'. \n"
100 " <ID> MUST include a vendor specified unique "
101 "identifier.") ]
102 string InstanceID;
103
104 [Override ("ElementName"), Required, Description (
105 "The user friendly name for this instance of Capabilities. "
106 karl 1.1 "In addition, the user friendly name can be used as a "
107 "index property for a search of query. (Note: Name "
108 "does not have to be unique within a namespace.)") ]
109 string ElementName;
110 };
111
112
113 // ===================================================================
114 // ElementCapabilities
115 // ===================================================================
116 [Association, Experimental, Version ("2.7.0"), Description (
117 "ElementCapabilities represents the association between "
118 "ManagedElements and their Capabilities. "
119 "Note that the cardinality of the ManagedElement "
120 "reference is Min(1), Max(1). This cardinality mandates the "
121 "instantiation of the ElementCapabilities association for the "
122 "referenced instance of Capabilities. ElementCapabilities "
123 "describes the existence requirements and context for the "
124 "referenced instance of ManagedElement. Specifically, the "
125 "ManagedElement MUST exist and provides the context for the "
126 "Capabilities.") ]
127 karl 1.1 class CIM_ElementCapabilities {
128
129 [Key, Min(1), Max(1), Description (
130 "The managed element.") ]
131 CIM_ManagedElement REF ManagedElement;
132
133 [Key, Description (
134 "The Capabilities object associated with the element.") ]
135 CIM_Capabilities REF Capabilities;
136 };
137
138
139 // ===================================================================
140 // end of file
141 // ===================================================================
|