Return to Core27_Software.mof CVS log | Up to [Pegasus] / pegasus / Schemas / CIM27 |
File: [Pegasus] / pegasus / Schemas / CIM27 / Attic / Core27_Software.mof
(download)
Revision: 1.2, Wed May 21 01:19:30 2003 UTC (21 years, 1 month ago) by kumpf Branch: MAIN CVS Tags: test, pep_88, pegasus25BeforeLicenseUpdate, local, TEST, SLPPERFINST-root, SLPPERFINST-branch, RELEASE_2_4_FC_CANDIDATE_1, RELEASE_2_4_3, RELEASE_2_4_2, RELEASE_2_4_1-BETA3, RELEASE_2_4_1-BETA2, RELEASE_2_4_1-BETA1, RELEASE_2_4_1, RELEASE_2_4_0-RC3, RELEASE_2_4_0-RC2, RELEASE_2_4_0, RELEASE_2_4-root, RELEASE_2_4-branch, RELEASE_2_3_2-testfreeze, RELEASE_2_3_2-root, RELEASE_2_3_2-releasesnapshot, RELEASE_2_3_2-branch-freeze, RELEASE_2_3_2-branch, RELEASE_2_3_1-root, RELEASE_2_3_1-branch, RELEASE_2_3_0-root, RELEASE_2_3_0-msg-freeze, RELEASE_2_3_0-branch, RELEASE_2_2_1-snapshot, RELEASE_2_2_0_0-release, RELEASE_2_2_0-root, RELEASE_2_2_0-branch, RELEASE_2_2-root, PRE_LICENSE_UPDATE_2003, POST_LICENSE_UPDATE_2003, PEP217_PRE_BRANCH, PEP217_POST_BRANCH, PEP217_BRANCH, PEP213_SIZE_OPTIMIZATIONS, MONITOR_CONSOLIDATION_2_5_BRANCH, IBM_241_April1405, CQL_2_5_BRANCH, CHUNKTESTDONE_PEP140 Changes since 1.1: +213 -213 lines HP-[DME] PEP 42 Commit CIM 2.7.2 Schema. This Schema change removes the Experimental Qualifier all class definitions. It also adds the Restricted flavor to the Version and Experimental Qualifiers. |
// =================================================================== // Title: Core Software 2.7 // Filename: Core27_Software.mof // Version: 2.7.0 // Release: Final // Date: 03/31/03 // =================================================================== // Copyright 2002-2003 Distributed Management Task Force, Inc. (DMTF). // All rights reserved. // DMTF is a not-for-profit association of industry members dedicated // to promoting enterprise and systems management and interoperability. // DMTF specifications and documents may be reproduced for uses // consistent with this purpose by members and non-members, // provided that correct attribution is given. // As DMTF specifications may be revised from time to time, // the particular version and release date should always be noted. // // Implementation of certain elements of this standard or proposed // standard may be subject to third party patent rights, including // provisional patent rights (herein "patent rights"). DMTF makes // no representations to users of the standard as to the existence // of such rights, and is not responsible to recognize, disclose, or // identify any or all such third party patent right, owners or // claimants, nor for any incomplete or inaccurate identification or // disclosure of such rights, owners or claimants. DMTF shall have no // liability to any party, in any manner or circumstance, under any // legal theory whatsoever, for failure to recognize, disclose, or // identify any such third party patent rights, or for such party's // reliance on the standard or incorporation thereof in its product, // protocols or testing procedures. DMTF shall have no liability to // any party implementing such standard, whether such implementation // is foreseeable or not, nor to any patent owner or claimant, and shall // have no liability or responsibility for costs or losses incurred if // a standard is withdrawn or modified after publication, and shall be // indemnified and held harmless by any party implementing the // standard from any and all claims of infringement by a patent owner // for such implementations. // // For information about patents held by third-parties which have // notified the DMTF that, in their opinion, such patent may relate to // or impact implementations of DMTF standards, visit // http://www.dmtf.org/about/policies/disclosures.php. // =================================================================== // Description: The Core Model defines basic management concepts. // This file defines the SoftwareIdentity class, // representing software assets/inventory/units of // existence. // // The object classes below are listed in an order that // avoids forward references. Required objects, defined // by other working groups, are omitted. // ================================================================== // Change Log for v2.7 // CR968 - Remove the Experimental qualifier // CR994 - Update the description of InstanceID // // Change Log for v2.7 // CR753 - Add SoftwareIdentity // CR904 - Added missing brackets to SoftwareIdentity. // ClassificationDescriptions array // =================================================================== #pragma locale ("en_US") // ================================================================== // SoftwareIdentity // ================================================================== [Version ("2.7.0"), Description ( " SoftwareIdentity represents software, viewed as an asset " "and/or individually identifiable entity (similar to Physical" "Element). It does NOT indicate whether the software is installed, " "executing, etc. (The latter is the role of the SoftwareFeature/" "SoftwareElement classes and the Application Model.) Since " "software may be acquired, SoftwareIdentity can be associated " "with a Product using the ProductSoftwareComponent relationship. \n" " Note that the Application Model manages the deployment and " "installation of software via the classes, SoftwareFeatures and " "SoftwareElements. The deployment/installation concepts are " "related to the asset/identity one. In fact, a SoftwareIdentity " "may correspond to a Product, or to one or more SoftwareFeatures " "or SoftwareElements - depending on the granularity of these " "classes and the deployment model. The correspondence of Software" "Identity to Product, SoftwareFeature or SoftwareElement is " "indicated using the ConcreteIdentity association. Note that " "there may not be sufficient detail or instrumentation to " "instantiate ConcreteIdentity. And, if the association is " "instantiated, some duplication of information may result. For " "example, the Vendor described in the instances of Product and " "SoftwareIdentity MAY be the same. However, this is not " "necessarily true, and it is why vendor and similar information " "are duplicated in this class. \n" " Note that ConcreteIdentity can also be used to describe " "the relationship of the software to any LogicalFiles " "that result from installing it. As above, there may not be " "sufficient detail or instrumentation to instantiate this " "association.") ] class CIM_SoftwareIdentity : CIM_LogicalElement { [Key, Description ( "Within the scope of the instantiating Namespace, InstanceID " "opaquely and uniquely identifies an instance of this class. " "In order to ensure uniqueness within the NameSpace, the " "value of InstanceID SHOULD be constructed using the " "following 'preferred' algorithm: \n" " <OrgID>:<LocalID> \n" "Where <OrgID> and <LocalID> are separated by a colon ':', " "and where <OrgID> MUST include a copyrighted, trademarked " "or otherwise unique name that is owned by the business entity " "creating/defining the InstanceID, or is a registered ID that is " "assigned to the business entity by a recognized global " "authority (This is similar to the <Schema Name>_<Class Name> " "structure of Schema class names.) In addition, to ensure " "uniqueness <OrgID> MUST NOT contain a colon (':'). When using " "this algorithm, the first colon to appear in " "InstanceID MUST appear between <OrgID> and <LocalID>. \n" " <LocalID> is chosen by the business entity and SHOULD not be " "re-used to identify different underlying (real-world) elements. " "If the above 'preferred' algorithm is not used, the defining " "entity MUST assure that the resultant InstanceID is not " "re-used across any InstanceIDs produced by this or other " "providers for this instance's NameSpace. \n" "For DMTF defined instances, the 'preferred' algorithm MUST be " "used with the <OrgID> set to 'CIM'.") ] string InstanceID; [Description ( "The major number component of the software's version " "information - for example, '12' from version " "12.1(3)T. This property is defined as a numeric value " "to allow the determination of 'newer' vs. 'older' releases. " "A 'newer' major release is indicated by a larger numeric " "value.") ] uint16 MajorVersion; [Description ( "The minor number component of the software's version " "information - for example, '1' from version " "12.1(3)T. This property is defined as a numeric value " "to allow the determination of 'newer' vs. 'older' releases. " "A 'newer' minor release is indicated by a larger numeric " "value.") ] uint16 MinorVersion; [Description ( "The revision or maintenance release component of the " "software's version information - for example, '3' from " "version 12.1(3)T. This property is defined as a numeric value " "to allow the determination of 'newer' vs. 'older' releases. " "A 'newer' revision is indicated by a larger numeric " "value.") ] uint16 RevisionNumber; [Description ( "The build number of the software.") ] uint16 BuildNumber; [Description ( "A string representing the complete software version " "information - for example, '12.1(3)T'. This string and " "the numeric major/minor/revision/build properties are " "complementary. Since vastly different representations and " "semantics exist for versions, it is not assumed that " "one representation is sufficient to permit a client to " "perform computations (i.e., the values are numeric) and " "a user to recognize the software's version (i.e., the " "values are understandable and readable). Hence, both " "numeric and string representations of version are provided.") ] string VersionString; [Description ( "Specifies the target operating systems of the software. " "Due to the extreme variability in operating systems, " "this property is defined as a string array.") ] string TargetOperatingSystems[]; [Description ( "Manufacturer of this software.") ] string Manufacturer; [Description ( "The language editions supported by the software. The " "language codes defined in ISO 639 should be used. ") ] string Languages[]; [Description ( "An array of enumerated integers that classify this software. " "For example, the software could be instrumentation (value=5) " "or firmware and diagnostic software (6 and 7)."), ValueMap {"0", "1", "2", "3", "4", "5", "6", "7", "8", "9"}, Values {"Unknown", "Other", "Driver", "Configuration Software", "Application Software", "Instrumentation", "Firmware/BIOS", "Diagnostic Software", "Operating System", "Middleware"}, ArrayType ("Indexed"), ModelCorrespondence { "CIM_SoftwareIdentity.ClassificationDescriptions"} ] uint16 Classifications[]; [Description ( "An array of free-form strings providing more detailed " "explanations for any of the entries in the Classifications " "array. Note that each entry is related to one in the " "Classifications array located at the same index."), ArrayType ("Indexed"), ModelCorrespondence {"CIM_SoftwareIdentity.Classifications"} ] string ClassificationDescriptions[]; }; // =================================================================== // end of file // ===================================================================
No CVS admin address has been configured |
Powered by ViewCVS 0.9.2 |