ISO/IEC 10165-1:1993 情報技術—オープンシステム相互接続—管理情報サービス—管理情報の構造：管理情報モデル | ページ 6

3.8.1

action

An operation on a managed object, the semantics of which are defined as part of the managed object class definition.

3.8.2

actual class

The managed object class of which a managed object is an instance, as distinct from an allomorphic class of that managed object.

3.8.3

allomorphic class (of a managed object)

A class, other than the managed object's actual class, which a managed object can be managed as, using allomorphism.

3.8.4

allomorphism

The ability of a managed object that is an instance of a given class to be managed as an instance of one or more other managed object classes.

3.8.5

attribute group

A group of attributes which have been assigned a single identifier for ease of access.

3.8.6

attribute identifier

An identifier used to distinguish an attribute of a managed object class from all other attributes.

3.8.7

attribute type

A named definition of a specific kind of attribute, including definitions of its syntax (type) and semantics. An attribute is an instance of an attribute type.

3.8.8

attribute value assertion

A statement, which may be true or false, concerning the value of an attribute.

3.8.9

attribute value set

A set of values, members of which are valid values of an attribute.

3.8.10

behaviour

The way in which managed objects, name bindings, attributes, notifications and actions interact with the actual resources they model and with each other.

3.8.11

characteristic

An element of a managed object class definition; that is an attribute definition, an attribute group definition, a notification definition, a behaviour definition, a parameter definition or a package definition.

3.8.12

conditional package

A package which is present in a given managed object if the condition given in its managed object class definition is satisfied.

3.8.13

containment

A structuring relationship for managed objects in which the existence of a managed object is dependent on the existence of a containing managed object.

3.8.14

distinguished name

The name of an object formed from the sequence of the RDNs of the object and each of its superior objects.

3.8.15

encapsulation

A relation between a managed object and its attributes and behaviour, which represents the property that attributes and behaviour may be observed only through management operations on the managed object or notifications emitted by it.

3.8.16

inheritance

The conceptual mechanism by which attributes, notifications, operations and behaviour are acquired by a subclass from its superclass.

3.8.17

inheritance hierarchy

A hierarchical arrangement of managed object classes where the hierarchy is organized on the basis of the class specialization.

3.8.18

initial value managed object

A managed object that serves as a source for the derivation of initial values of another managed object.

3.8.19

instantiation

The process of creating a managed object according to a managed object class definition.

3.8.20

managed object boundary

The conceptual location where aspects of an underlying resource are made visible to management and which bounds the scope of the managed object's definition.

3.8.21

mandatory package

A package which must be present in all instances of a given managed object class.

3.8.22

multiple inheritance

A conceptual mechanism that allows a subclass to acquire attributes, notifications, operations and behaviour from more than one superclass.

3.8.23

name binding

A relation between object classes which specifies that an object of one identified class may be the superior of an object of another named class. A name binding definition also includes other information about the relation, and may be defined to also apply to subclasses of the superior or the subordinate class or both.

3.8.24

naming schema

A collection of name bindings.

3.8.25

naming tree

A hierarchical arrangement of objects where the hierarchy is organized on the basis of the name binding relationship. An object used to name another managed object is higher in the hierarchy than the named object. The naming object is referred to as the superior of the named object, which is referred to as the subordinate.

3.8.26

package

A collection of attributes, notifications, operations and/or behaviour which is treated as a single module in the specification of a managed object class. Packages may be specified as being mandatory or conditional when referenced in a managed object class definition.

3.8.27

parameter

A value of a type which has associated semantics and is associated with an object identifier and other information where the value of the type may be carried in protocol.

3.8.28

permitted value set

An attribute value set which includes all of the values which an attribute of a specified attribute type is permitted to take.

3.8.29

relative distinguished name

An attribute value assertion that a particular attribute has a particular value used to identify one object out of all those immediately subordinate to a given object. It serves as a component of a distinguished name of an object.

3.8.30

required value set

An attribute value set which includes all of the values which an attribute of a specified attribute type is required to take.

3.8.31

specialization

The technique of deriving a new managed object class from one or more existing managed object classes by inheritance and by the addition of new characteristics.

3.8.32

subclass

A class derived from another class by specialization.

3.8.33

superclass

A class used in deriving another class by specialization.

3.8.34

superior object

See 3.8.25

3.8.35

subordinate object

See 3.8.25

3.8.36

uninstantiable managed object class

A class that is not intended to be instantiated, either by a systems management operation or by a local operation within the open system.