29 karl 1.2
30 <B>Association</B> \Label{ASSOCIATION} -An association is a relationship between two classes or between instances of two classes. The properties of an association class include pointers, or references, to the two classes or instances.
31
32 Class association is one of the most powerful CIM features. It provides a way to organize a
33 collection of management objects into meaningful relationships. For example, a
34 Solaris_ComputerSystem object might contain a Solaris_Disk, Processor A, and
35 Processor B. The Solaris_ComputerSystem has an association with each of the
36 objects it contains. Because this particular association is a containment association, it is
37 represented by a class called CIM_contains. The CIM_contains class contains
38 references to each of the objects that belong to the association. In this case,
39 CIM_contains has a reference to Solaris_Disk and a reference to
40 Solaris_ComputerSystem.
41
42 <B>WBEM</B> \Label{WBEM} - ATTN:
43
44 <B>DMTF</B> \Label{DMTF} - The Distributed Management Task Force (DMTF), a group representing corporations in the computer and telecommunications industries, is leading the effort to develop and disseminate standards for management of desktop environments, enterprise-wide systems, and the Internet. The goal of the DMTF is to develop an integrated approach to managing networks across platforms and protocols, resulting in cost-effective products that interoperate as flawlessly as possible. For information about DMTF initiatives and outcomes, see the DMTF web site at http://www.dmtf.org.
45
46 <B>MOF</B> \Label{MOF} - MOF is the standard language used to define elements of the Common Information Model (CIM). The MOF language specifies syntax for defining CIM classes and instances. Compilation of MOF files provides developers and administrators with a simple and fast technique for modifying the CIM Repository. For more information about MOF, see the DMTF web page at http://www.dmtf.org.
47
48 <B>XmlCIM</B> \Label{XMLCIM} - ATTN: The XML Schema describes the CIM metaschema. The CIM classes and instances are valid XML documents.
49
50 karl 1.2 A Metaschema Mapping is one where the XML schema is used to describe the CIM metaschema, and both CIM classes and instances are valid XML documents for that schema. In this case, the DTD is used to describe, in a generic fashion, the notion of a CIM class or instance. CIM element names are mapped to XML attribute or element values. An alternate mechanism maps XML documents directly to CIM schema classes and instances. In this case, CIM element names are mapped to XML element names The advantages of the XML descriptions are: Only one DTD needs to be defined Avoids the limitations of DTD's (ordering, scoping, and no inheritance) Straightforward
51
52 For more detailed information on the mapping of XML to CIM schema, see
53 http://www.dmtf.org/download/spec/xmls/CIM_XML_Mapping20.htm and
54 http://www.dmtf.org/download/spec/xmls/CIM_HTTP_Mapping10.htm.
55 1.5 Managed Object Format
56
57 <B> </B> \Label{} - ATTN:
58
59
60 <B>QUALIFIERR</B> \Label{qualifier} - Qualifiers
61 are values that provide additional information about classes, associations,
62 indications, methods, method parameters, triggers, instances, properties or
63 references. All qualifiers have a name, type, value, scope, flavor and default value. Qualifiers cannot be duplicated; there cannot be more than one qualifier of the same name for any given class, instance, or property.
64
65 Qualifiers are defined in detail in the DMTF CIM Specificaiton.
66
67 There are several types of Qualifiers as listed below:
68 <UL>
69 <LI><B>Meta-Qualifiers</B> - (ASSOCIATION,INDICATION are the MetaQualifiers) are used to refine the definition of the meta constructs in the model. These qualifiers are used to refine the actual usage of an object class or property declaration within the MOF syntax.
70
71 karl 1.2 <LI><B>StandardQualifiers</B> -(See CIM Specificaiton for a list) All CIM-compliant implementations are required to handle. Any given object will not have all of the qualifiers listed.
72
73 <LI><B>Optional Qualifiers</B> - The optional qualifiers listed in the CIM Specificaiton address situations that are not common to all CIM-compliant
74 implementations. Thus, CIM-compliant implementations can ignore optional
75 qualifiers since they are not required to interpret or understand these qualifiers.
76
77 PEGASUS Implements the following optional Qualifiers - ATTN:
78
79 <LI>User Defined Qualifiers</B> - The user can define any additional arbitrary named qualifiers. However, the CIM specificaiton recommends that
80 only defined qualifiers be used, and that the list of qualifiers be extended only if there is no other way to accomplish a particular objective.
81
82 </UL>
83 ATTN: Should we include the table of qualifiers?????
84
85 <B>Aggregation</B> \Label{Aggregation } -A strong form of an association. For example, the containment relationship between a system and the components that make up the system can be called an aggregation. An aggregation is expressed as a Qualifier on the association class. Aggregation often implies, but does not require, that the aggregated objects have mutual dependencies.
86
87 <B>Association</B> \Label{Association} - A class that expresses the relationship between two other classes. The relationship is established by the presence of two or more references in the association class pointing to the related classes.
88
89 <B>Cardinality</B> \Label{Cardinality} - A relationship between two classes that allows more than one object to be related to a single object. For example, Microsoft Office* is made up of the software elements Word, Excel, Access and PowerPoint.
90
91 <B>CIM</B> \Label{CIM} - Common Information Model is the schema of the overall managed environment. It is divided into a Core model, Common model and extended schemas. CIM Schema The schema representing the Core and Common models. Versions of this schema will be released by the DMTF over time as the schema evolves.
92 karl 1.2
93 <B>Class</B> \Label{Class} - A collection of instances, all of which support a common type; that is, a set of properties and methods. The common properties and methods are defined as features of the class. For example, the class called Modem represents all the modems present in a system. Common model A collection of models specific to a particular area, derived from the Core model. Included are the system model, the application model, the network model and the device model.
94
95 <B>Core model</B> \Label{Core model} - A subset of CIM, not specific to any platform. The Core model is set of classes and associations that establish a conceptual framework for the schema of the rest of the managed environment. Systems, applications, networks and related information are modeled as extensions to the Core model.
96
97 <B>Domain</B> \Label{Domain} - A virtual room for object names that establishes the range in which the names of objects are unique.
98
99 <B>Explicit Qualifier</B> \Label{Explicit Qualifier} - A qualifier defined separately from the definition of a class, property or other schema element (see implicit qualifier). Explicit qualifier names must be unique across the entire schema. Implicit qualifier names must be unique within the defining schema element; that is, a given schema element may not have two qualifiers with the same name.
100
101 <B>Extended schema</B> \Label{Extended schema} - A platform specific schema derived from the Common model. An example is the Win32 schema.
102
103 <B>Feature</B> \Label{Feature} - A property or method belonging to a class.
104
105 <B>Flavor</B> \Label{Flavor} - Part of a qualifier spcification indicating overriding and inheritance rules. For example, the qualifier KEY has Flavor(DisableOverride ToSubclass), meaning that every subclass must inherit it and cannot override it.
106
107 <B>Implicit Qualifier</B> \Label{Implicit Qualifier} - A qualifier defined as a part of the definition of a class, property or other schema element (see explicit qualifier).
108
109 <B>Indication</B> \Label{Indication} - A type of class usually created as a result of the occurrence of a trigger.
110
111 <B>Inheritance</B> \Label{Inheritance} - A relationship between two classes in which all the members of the subclass are required to be members of the superclass. Any member of the subclass must also support any method or property supported by the superclass. For example, Modem is a subclass of Device.
112
113 karl 1.2 <B>Instance</B> \Label{Instance} - A unit of data. An instance is a set of property values that can be uniquely identified by a key.
114
115 <B>Key</B> \Label{Key} - One or more qualified class properties that can be used to construct a name. One or more qualified object properties which uniquely identify instances of this object in a namespace.
116
117 <B>Managed Object</B> \Label{Managed Object} - The actual item in the system environment that is accessed by the provider. For example, a Network Interface Card.
118
119 <B>Meta model</B> \Label{Meta model} - A set of classes, associations and properties that expresses the types of things that can be defined in a Schema. For example, the meta model includes a class called property which defines the properties known to the system, a class called method which defines the methods known to the system, and a class called class which defines the classes known to the system.
120
121 Meta schema<B>Meta schema</B> \Label{Meta schema} - The schema of the meta model. Method A declaration of a signature; that is, the method name, return type and parameters, and, in the case of a concrete class, may imply an implementation.
122
123 <B>Model</B> \Label{Model} - A set of classes, properties and associations that allows the expression of information about a specific domain. For example, a Network may consist of Network Devices and Logical Networks. The Network Devices may have attachment associations to each other, and may have member associations to Logical Networks.
124
125 <B>Model Path</B> \Label{Model Path} - A reference to an object within a namespace.
126 Namespace An object that defines a scope within which object keys must be unique.
127
128 <B>Namespath Path</B> \Label{Namespath Path} - A reference to a namespace within an implementation that is capable of hosting CIM objects.
129
130 <B>Name</B> \Label{Name} - Combination of a Namespace path and a Model path that identifies a unique object.
131
132 <B>Trigger</B> \Label{Trigger} - The occurrence of some action such as the creation, modification or deletion of an object, access to an object, or modification or access to a property. Triggers may also be fired as a result of the passage of a specified period of time. A trigger typically results in an Indication.
133
134 karl 1.2 <BPolymorphism></B> \Label{Polymorphism} - A subclass may redefine the implementation of a method or property inherited from its superclass. The property or method is thereby redefined, even if the superclass is used to access the object. For example, Device may define availability as a string, and may return the values “powersave”, "on" or "off." The Modem subclass of Device may redefine (override) availability by returning "on," "off," but not "powersave". If all Devices are enumerated, any Device that happens to be a modem will not return the value "powersave" for the availability property.
135
136 <B>Property</B> \Label{Property} - A value used to characterize an instance of a class. For example, a Device may have aproperty called status.
137
138 <B>Provider</B> \Label{Provider} - An executable that can return or set information about a given managed object. Qualifier A value used to characterize a method, property, or class in the meta schema. For example, if a property has the qualifier KEY with the value TRUE, the property is a key for the class.
139
140 <B>Reference</B> \Label{Reference} - Special property types that are references or "pointers" to other instances.
141
142 <B>Schema</B> \Label{Schema} - A namespace and unit of ownership for a set of classes. Schemas may come in forms such as a text file, information in a repository, or diagrams in a CASE tool.
143
144 <B>Scope</B> \Label{}Scope - Part of a Qualifier specification indicating with which meta constructs the Qualifier can be used. For example, the Qualifier ABSTRACT has Scope(Class Association Indication), meaning that it can only be used with Classes, Associations and Indications.
145
146 <B>Scoping Object</B> \Label{ScopingObject} - Objects which represent a real-world managed element, which in turn propagate keys to other objects.
147
148 <B>Signature</B> \Label{Signature} - The return type and parameters supported by a method.
149
150 <B>Subclass</B> \Label{Subclass} - See Inheritance.
151
152 <B>Superclass</B> \Label{Superclass} - See Inheritance.
153
154 <B>Top Level Object</B> \Label{TopLevelObject} - A class or object that has no scoping object.
|
Return to
definitions.dxx
CVS log
Up to [Pegasus] / pegasus / doc / DevManual