One or more schemas can be stored in directory-like structures called namespaces. A CIM namespace is a directory-like structure that can contain other namespaces, classes, instances, and qualifier types. The names of objects within a namespace must be unique.
In Solaris WBEM Services, when a WBEM client application connects to a particular namespace, all subsequent operations occur within that namespace. When connected to a namespace, the client can access the classes and instances in that namespace (if they exist) and in any namespaces contained in that namespace. For example, if you create a namespace called child in the root\cimv2 namespace, you could connect to root\cimv2 and access the classes and instances in the root\cimv2 and root\cimv2\child namespaces.
An application can connect to a namespace within a namespace. This is similar to changing to a subdirectory within a directory. Once the application connects to the new namespace, all subsequent operations occur within that namespace. If you open a new connection to root\cimv2\child, you can access any classes and instances in that namespace but cannot access the classes and instances in the parent namespace, root\cimv2.
root – The top-level namespace that contains other namespaces.
root\cimv2 – Contains the default CIM classes and instances that represent objects on your system, such as, LogicalDisk and Netcard. This is the default namespace.
root\security – Contains the security classes used by the CIM Object Manager to represent access rights for users and namespaces.
root\snmp – Contains the classes for the SNMP Provider and the SNMP Adapter for WBEM.
root\system – Contains CIM Object Manager information and provider paths.