OEM User's Guide

OEM External Specification
OEM User’s Guide—520330-001
A-72
Object Name Standards
Object Name Standards
There is a wide range of possible object names and name space conventions. Although a
completely unstructured set of naming conventions is possible, this approach could lead
to chaos for both users and clients. If each client adopted its own naming convention, it
would be impossible for clients to share information about objects and classes that are
identified with different naming rules.
For clients to present a unified front for shared objects, they must use a common set of
name space conventions. Objects representing Compaq NonStop™ Kernel entities
should adhere to standard NonStop™ Kernel hierarchical notation, and objects
representing Windows or UNIX entities should adhere to those hierarchical name space
representations.
For OEM, the name space should provide the following:
•
Hierarchical object class relationships
•
Logical names of object class instances
•
Association of operations with object classes
•
Association of client callbacks with object classes
•
Possibility for icon associations with object classes
These rules are voluntary constraints so that clients can share objects and class names.
These are not limitations, and the name space constraints can be enhanced in the future
as needed. The following sections summarize the abstract OEM name space conventions
to be used by clients when communicating with the OEM.