1 tony 1.1 // ===================================================================
2 // Title: Core Capabilities 2.8
3 // Filename: Core28_Capabilities.mof
4 // Version: 2.8
5 // Release: Preliminary
6 // Date: 05/28/2003
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 Preliminary
53 // CR937 - Add LocalizationCapabilities
54 // CR1019 - CIM Versioning for 2.8 Preliminary
55 //
56 // Change Log for v2.7
57 // CR968 - Remove the Experimental qualifier
58 // CR994 - Updates to InstanceID description.
59 //
60 // Change Log for v2.7
61 // CR 730 - Introduce Capabilites and ElementCapabilities
62 // ==================================================================
63
64 tony 1.1 #pragma locale ("en_US")
65
66
67 // ==================================================================
68 // Capabilities
69 // ==================================================================
70 [Abstract, Version ("2.7.0"), Description (
71 "Capabilities is an abstract class whose subclasses describe "
72 "abilities and/or potential for use. For example, one may "
73 "describe the maximum number of VLANs that can be supported on "
74 "a system using a subclass of Capabilities. Capabilities are "
75 "tied to the elements which they describe using the "
76 "ElementCapabilities association. Note that the cardinality of "
77 "the ManagedElement reference is Min(1), Max(1). This "
78 "cardinality mandates the instantiation of the "
79 "ElementCapabilities association for the referenced instance of "
80 "Capabilities. ElementCapabilities describes the existence "
81 "requirements and context for the referenced instance of "
82 "ManagedElement. Specifically, the ManagedElement MUST exist "
83 "and provides the context for the Capabilities. Note that "
84 "Capabilities do not indicate what IS configured or "
85 tony 1.1 "operational, but what CAN or CANNOT exist, be defined or be "
86 "used. Note that it is possible to describe both supported and "
87 "excluded abilities and functions (both capabilities and "
88 "limitations) using this class.") ]
89 class CIM_Capabilities : CIM_ManagedElement {
90
91 [Key, Description (
92 "Within the scope of the instantiating Namespace, InstanceID "
93 "opaquely and uniquely identifies an instance of this "
94 "class. In order to ensure uniqueness within the NameSpace, "
95 "the value of InstanceID SHOULD be constructed using the "
96 "following 'preferred' algorithm:\n"
97 "<OrgID>:<LocalID>\n"
98 "Where <OrgID> and <LocalID> are separated by a colon ':', "
99 "and where <OrgID> MUST include a copyrighted, trademarked "
100 "or otherwise unique name that is owned by the business "
101 "entity creating/defining the InstanceID, or is a registered "
102 "ID that is assigned to the business entity by a recognized "
103 "global authority (This is similar to the <Schema "
104 "Name>_<Class Name> structure of Schema class names.) In "
105 "addition, to ensure uniqueness <OrgID> MUST NOT contain a "
106 tony 1.1 "colon (':'). When using this algorithm, the first colon to "
107 "appear in InstanceID MUST appear between <OrgID> and "
108 "<LocalID>.\n"
109 "<LocalID> is chosen by the business entity and SHOULD not "
110 "be re-used to identify different underlying (real-world) "
111 "elements. If the above 'preferred' algorithm is not used, "
112 "the defining entity MUST assure that the resultant "
113 "InstanceID is not re-used across any InstanceIDs produced "
114 "by this or other providers for this instance's NameSpace.\n"
115 "For DMTF defined instances, the 'preferred' algorithm MUST "
116 "be used with the <OrgID> set to 'CIM'.") ]
117 string InstanceID;
118
119 [Required, Override ("ElementName"), Description (
120 "The user friendly name for this instance of Capabilities. "
121 "In addition, the user friendly name can be used as a index "
122 "property for a search of query. (Note: Name does not have "
123 "to be unique within a namespace.)") ]
124 string ElementName;
125 };
126
127 tony 1.1
128 // ===================================================================
129 // ElementCapabilities
130 // ===================================================================
131 [Association, Version ("2.7.0"), Description (
132 "ElementCapabilities represents the association between "
133 "ManagedElements and their Capabilities. Note that the "
134 "cardinality of the ManagedElement reference is Min(1), "
135 "Max(1). This cardinality mandates the instantiation of the "
136 "ElementCapabilities association for the referenced instance of "
137 "Capabilities. ElementCapabilities describes the existence "
138 "requirements and context for the referenced instance of "
139 "ManagedElement. Specifically, the ManagedElement MUST exist "
140 "and provides the context for the Capabilities.") ]
141 class CIM_ElementCapabilities {
142
143 [Key, Min (1), Max (1), Description (
144 "The managed element.") ]
145 CIM_ManagedElement REF ManagedElement;
146
147 [Key, Description (
148 tony 1.1 "The Capabilities object associated with the element.") ]
149 CIM_Capabilities REF Capabilities;
150 };
151
152 // ==================================================================
153 // LocalizationCapabilities
154 // ==================================================================
155 [Experimental, Version ("2.7.1000"), Description (
156 "Describes the input and output localization capabilities of "
157 "the entity associated via ElementCapabilities.") ]
158 class CIM_LocalizationCapabilities : CIM_Capabilities {
159
160 [Description (
161 "This property, along with locale properties in (for "
162 "example) a SettingData class, specifies the locale for data "
163 "consumed by a ManagedElement.\n"
164 "A locale indicates a particular geographical, political, or "
165 "cultural region. The SupportedInputLocales property is an "
166 "array of strings whose entries specify one or more "
167 "languages that can be used in the formulation of "
168 "information input by a client. It may be defined by the "
169 tony 1.1 "ManagedElement or client as an input parameter to a method, "
170 "as a Setting or SettingData property, or via other "
171 "mechanisms.\n"
172 "\n"
173 "The SupportedInputLocales property publishes an element's "
174 "support of various locales for input data. The first array "
175 "entry MUST define the default locale (the natural language "
176 "associated with the ManagedElement). If the "
177 "SupportedInputLocales property is empty, it is assumed that "
178 "the default locale is en_US (English).\n"
179 "Each array entry consists of three sub-strings, separated "
180 "by underscores:\n"
181 "- The first sub-string is the language code, as specified "
182 "in ISO639.\n"
183 "- The second sub-string is the country code, as specified "
184 "in ISO3166.\n"
185 "- The third sub-string is a variant, which is vendor specific.\n"
186 "For example, US English appears as: \"en_US_WIN\", where "
187 "the \"WIN\" variant would specify a Windows "
188 "browser-specific collation (if one exists). Since the "
189 "variant is not standardized, it is not commonly used and is "
190 tony 1.1 "generally limited to easily recognizable values (\"WIN\", "
191 "\"UNIX\", \"EURO\", etc.) used in standard environments.\n"
192 "The language and country codes are required; the variant "
193 "may be empty.") ]
194 string SupportedInputLocales[];
195
196 [Description (
197 "This property, along with locale properties in (for "
198 "example) a SettingData class, specifies the locale for data "
199 "produced by a ManagedElement.\n"
200 "A locale indicates a particular geographical, political, or "
201 "cultural region. The SupportedOutputLocales property is an "
202 "array of strings whose entries specify one or more "
203 "languages that can be used in the formulation of "
204 "information requested by and delivered to a client. It may "
205 "be defined by the ManagedElement or client as an input "
206 "parameter to a method, as a Setting or SettingData "
207 "property, or via other mechanisms. Note that more than one "
208 "locale may be specified in this array and later selected "
209 "for output. If multiple locales are selected, information "
210 "MUST be returned in each language specified, and indicated "
211 tony 1.1 "as supported by this Capabilities instance.\n"
212 "\n"
213 "The SupportedOutputLocales property publishes an element's "
214 "support of various locales for output data. The first "
215 "array entry MUST define the default locale (the natural "
216 "language associated with the ManagedElement). If the "
217 "SupportedOutput Locales property is empty, it is assumed "
218 "that the default locale is en_US (English).\n"
219 "Each array entry consists of three sub-strings, separated "
220 "by underscores:\n"
221 "- The first sub-string is the language code, as specified "
222 "in ISO639.\n"
223 "- The second sub-string is the country code, as specified "
224 "in ISO3166.\n"
225 "- The third sub-string is a variant, which is vendor specific.\n"
226 "For example, US English appears as: \"en_US_WIN\", where "
227 "the \"WIN\" variant would specify a Windows "
228 "browser-specific collation (if one exists). Since the "
229 "variant is not standardized, it is not commonly used and is "
230 "generally limited to easily recognizable values (\"WIN\", "
231 "\"UNIX\", \"EURO\", etc.) used in standard environments.\n"
232 tony 1.1 "The language and country codes are required; the variant "
233 "may be empty.") ]
234 string SupportedOutputLocales[];
235 };
236
237 // ===================================================================
238 // end of file
239 // ===================================================================
|
Return to
Core28_Capabilities.mof
CVS log
Up to [Pegasus] / pegasus / Schemas / CIMPrelim28