1 karl 1.1 // ===================================================================
2 // Title: Core Software 2.7
3 // Filename: Core27_Software.mof
4 // Version: 2.7.0
5 // Release: Preliminary
6 // Date: 09/20/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 SoftwareIdentity class,
46 // representing software assets/inventory/units of
47 // existence.
48 //
49 // The object classes below are listed in an order that
50 // avoids forward references. Required objects, defined
51 // by other working groups, are omitted.
52 // ==================================================================
53 // Change Log for v2.7
54 // CR753 - Add SoftwareIdentity
55 // CR904 - Added missing brackets to SoftwareIdentity.
56 // ClassificationDescriptions array
57 // ===================================================================
58
59 #pragma locale ("en_US")
60
61
62 // ==================================================================
63 // SoftwareIdentity
64 karl 1.1 // ==================================================================
65 [Experimental, Version ("2.7.0"), Description (
66 " SoftwareIdentity represents software, viewed as an asset "
67 "and/or individually identifiable entity (similar to Physical"
68 "Element). It does NOT indicate whether the software is installed, "
69 "executing, etc. (The latter is the role of the SoftwareFeature/"
70 "SoftwareElement classes and the Application Model.) Since "
71 "software may be acquired, SoftwareIdentity can be associated "
72 "with a Product using the ProductSoftwareComponent relationship. \n"
73 " Note that the Application Model manages the deployment and "
74 "installation of software via the classes, SoftwareFeatures and "
75 "SoftwareElements. The deployment/installation concepts are "
76 "related to the asset/identity one. In fact, a SoftwareIdentity "
77 "may correspond to a Product, or to one or more SoftwareFeatures "
78 "or SoftwareElements - depending on the granularity of these "
79 "classes and the deployment model. The correspondence of Software"
80 "Identity to Product, SoftwareFeature or SoftwareElement is "
81 "indicated using the ConcreteIdentity association. Note that "
82 "there may not be sufficient detail or instrumentation to "
83 "instantiate ConcreteIdentity. And, if the association is "
84 "instantiated, some duplication of information may result. For "
85 karl 1.1 "example, the Vendor described in the instances of Product and "
86 "SoftwareIdentity MAY be the same. However, this is not "
87 "necessarily true, and it is why vendor and similar information "
88 "are duplicated in this class. \n"
89 " Note that ConcreteIdentity can also be used to describe "
90 "the relationship of the software to any LogicalFiles "
91 "that result from installing it. As above, there may not be "
92 "sufficient detail or instrumentation to instantiate this "
93 "association.") ]
94 class CIM_SoftwareIdentity : CIM_LogicalElement {
95
96 [Key, Description (
97 "InstanceID opaquely identifies a unique instance of "
98 "SoftwareIdentity. The InstanceID must be unique within a "
99 "namespace. In order to ensure uniqueness, the value of "
100 "InstanceID SHOULD be constructed in the following manner: \n"
101 "<Vendor ID><ID> \n"
102 " <Vendor ID> MUST include a copyrighted, trademarked "
103 "or otherwise unique name that is owned by the business "
104 "entity or a registered ID that is assigned to the business "
105 "entity that is defining the InstanceID. (This is similar to "
106 karl 1.1 "the <Schema Name>_<Class Name> structure of Schema class "
107 "names.) The purpose of <Vendor ID> is to ensure that <ID> is "
108 "truly unique across multiple vendor implementations. If such "
109 "a name is not used, the defining entity MUST assure that the "
110 "<ID> portion of the Instance ID is unique when compared with "
111 "other instance providers. For DMTF defined instances, the "
112 "<Vendor ID> is 'CIM'. \n"
113 " <ID> MUST include a vendor specified unique "
114 "identifier.") ]
115 string InstanceID;
116
117 [Description (
118 "The major number component of the software's version "
119 "information - for example, '12' from version "
120 "12.1(3)T. This property is defined as a numeric value "
121 "to allow the determination of 'newer' vs. 'older' releases. "
122 "A 'newer' major release is indicated by a larger numeric "
123 "value.") ]
124 uint16 MajorVersion;
125
126 [Description (
127 karl 1.1 "The minor number component of the software's version "
128 "information - for example, '1' from version "
129 "12.1(3)T. This property is defined as a numeric value "
130 "to allow the determination of 'newer' vs. 'older' releases. "
131 "A 'newer' minor release is indicated by a larger numeric "
132 "value.") ]
133 uint16 MinorVersion;
134
135 [Description (
136 "The revision or maintenance release component of the "
137 "software's version information - for example, '3' from "
138 "version 12.1(3)T. This property is defined as a numeric value "
139 "to allow the determination of 'newer' vs. 'older' releases. "
140 "A 'newer' revision is indicated by a larger numeric "
141 "value.") ]
142 uint16 RevisionNumber;
143
144 [Description (
145 "The build number of the software.") ]
146 uint16 BuildNumber;
147
148 karl 1.1 [Description (
149 "A string representing the complete software version "
150 "information - for example, '12.1(3)T'. This string and "
151 "the numeric major/minor/revision/build properties are "
152 "complementary. Since vastly different representations and "
153 "semantics exist for versions, it is not assumed that "
154 "one representation is sufficient to permit a client to "
155 "perform computations (i.e., the values are numeric) and "
156 "a user to recognize the software's version (i.e., the "
157 "values are understandable and readable). Hence, both "
158 "numeric and string representations of version are provided.") ]
159 string VersionString;
160
161 [Description (
162 "Specifies the target operating systems of the software. "
163 "Due to the extreme variability in operating systems, "
164 "this property is defined as a string array.") ]
165 string TargetOperatingSystems[];
166
167 [Description (
168 "Manufacturer of this software.") ]
169 karl 1.1 string Manufacturer;
170
171 [Description (
172 "The language editions supported by the software. The "
173 "language codes defined in ISO 639 should be used. ") ]
174 string Languages[];
175
176 [Description (
177 "An array of enumerated integers that classify this software. "
178 "For example, the software could be instrumentation (value=5) "
179 "or firmware and diagnostic software (6 and 7)."),
180 ValueMap {"0", "1", "2", "3", "4", "5", "6", "7", "8", "9"},
181 Values {"Unknown", "Other", "Driver",
182 "Configuration Software", "Application Software",
183 "Instrumentation", "Firmware/BIOS",
184 "Diagnostic Software", "Operating System", "Middleware"},
185 ArrayType ("Indexed"),
186 ModelCorrespondence {
187 "CIM_SoftwareIdentity.ClassificationDescriptions"} ]
188 uint16 Classifications[];
189
190 karl 1.1 [Description (
191 "An array of free-form strings providing more detailed "
192 "explanations for any of the entries in the Classifications "
193 "array. Note that each entry is related to one in the "
194 "Classifications array located at the same index."),
195 ArrayType ("Indexed"),
196 ModelCorrespondence {"CIM_SoftwareIdentity.Classifications"} ]
197 string ClassificationDescriptions[];
198 };
199
200
201 // ===================================================================
202 // end of file
203 // ===================================================================
|