The mandatory class statement identifies the source of the group and the group version. All groups using the same class string must share the same attribute definitions in the group, including attribute type, access, storage (defined following) and IDs. The attribute name, description, and value may be different, however. Class statement assists management applications in determining the semantics of the group's attributes.
The class statement syntax is:
class = "class string"
By convention, class string is encoded as
"defining body|specific name|version"
Specifies the name of the organization defining the group. For example,"DMTF", "IEEE", "Acme Computer"
Indicates the contents of the group. For example, "Server Stats", "Toaster Controls".
Indicates the version of the group definition. For example, "1", "A", "FIRST ONE EVER".
Essentially, the class string is an opaque string, and any convention can be used. However, since applications and Service Layers may rely on this convention for obtaining information through the List Component command, component providers are encouraged to use this convention.
It is an error to specify the same class string for two groups, if the group definitions are different. Management applications can count on identical group definitions for identical class strings.
Note: "DMTF|Sample|1.0" is not the same as "DMTF | Sample | 1.0" as one has spaces around the vertical bars and the other does not.
Implementations that provide a subset of the attributes defined by a class can just omit the definitions for the unsupported attributes. A better method is to use the unsupported keyword in the attribute definition (defined following). Management applications must be sufficiently robust to deal with subsets of a class.
Only one class statement is allowed per group.
|
Copyright © 2013 CA.
All rights reserved.
|
|