HP WBEM Services Software Developer's Kit for HP-UX Provider and Client Developer's Guide A.01

CIM Naming Guidelines
namespaces
Appendix A 113
namespaces
namespaces are the contexts within which schemas are defined. Within a
given namespace, the instances of the classes defined are guaranteed to
be unique. Different namespaces may be created to group related
information, to define separate views of managed resources, or to limit
client authorization to access certain objects. Consistent naming
conventions for namespaces enables client applications to easily find the
context within which their required management information will be
available.
General Syntax
For WBEM-compliant CIM Object Managers (CIM Servers), the
namespaceís name is the part of the namespace path within the context
of a namespace type (for example http://) and a CIM Server host (for
example coyote.rdrunner.com). The full namespace path is the
concatenation of the namespaceís type, the CIM Server host, a forward
slash (/), and the namespaceís name (for example
http://coyote.rdrunner.com/root/ACMEv2).
The namespaceís name has syntax much like that of UNIX directories
with their slash-delimited (/) sub-directories. However, namespaces with
similar prefixes do not necessarily have hierarchical relationships as in
UNIX. Thus, a/b/c can exist without a/b, and deleting namespace e/f
does not imply deletion of e/f/g. Also, CIM namespaces are case
insensitive, so the names root, Root, and ROOT are equivalent. One
exception is WMI, the WBEM implementation for Windows platforms,
where namespaces are hierarchical. For the Windows platform, this
exception implies that a/b must be created before a/b/c, and successful
deletion of a/b requires deletion of a/b/c.
Managed System namespace
A Managed System namespace is the namespace on a managed node
wherein a client can expect to find the general system information. This
namespace contains DMTF-defined classes and derived subclasses that
describe the systemís general purpose managed elements. The classes in