HP WBEM Services Software Developer's Kit for HP-UX Provider and Client Developer's Guide A.01
CIM Naming Guidelines
namespaces
Appendix A114
this namespace are distinct from those which have are considered to be
special purpose, for example those for the purpose of security or some
specialized system view.
The name of the Managed System namespace corresponds to the context
within which the managed objects are placed (for example platform
vendor, OS), and the major version of the CIM schema supported. For
systems manufactured by the fictitious ACME Corporation, the default
namespace within which CIM version 2.x derived objects are placed
could be root/ACMEv2. When CIM version 3.x is released, an additional
namespace would be created called root/ACMEv3.
Windows-basedplatforms using WMI present an interesting exception in
that they all have a root/CIMv2 namespace. For these platforms, the
root/CIMv2 namespace is populated with Microsoft-supported operating
system objects. However, the root/ACMEv2 namespace should also exist
on these platforms for all other ACME-supported objects, ACME
extensions to the DMTF CIM schema.
Special Purpose namespaces
In addition to these the namespaces supplied with HP WBEM Services
for HP-UX, other namespaces will need to be defined for special purpose
applications. Client management applications may wish to create special
namespaces to store host-specific information that relates to their
application. Providers may specify special-purpose namespaces to group
special objects that are not for general-purpose use, or to support unique
security authorization requirements.
In these cases, the most important guideline is to make the name as
descriptive as possible. Putting the special namespace in the implied
context of a System namespace (for example root/ACMEv2/special) can
assist in clarifying the purpose of the namespace. Other examples
include:
• root/ACMEv2/Par — namespace for partition
• root/ACMEv2/cluster —namespace for a cluster-related objects on
an ACME system
• root/ACMEv2/bigapp — BigApp-specific objects on an ACME system
• root/MgmtAppA — namespace for a non-platform specific client
(Management App A)