White Papers

6 Version 1.2.0
3 Terms and Definitions 167
For the purposes of this document, the following terms and definitions apply. 168
3.1 169
conditionalIndicates requirements to be followed strictly in order to conform to the document 170
when the specified conditions are met. 171
3.2 172
mandatory - Indicates requirements to be followed strictly in order to conform to the document and from 173
which no deviation is permitted. 174
3.3 175
may - Indicates a course of action permissible within the limits of the document. 176
3.4 177
optional– Indicates a course of action permissible within the limits of the document. 178
3.5 179
referencing profile – Indicates a profile that owns the definition of this class and can include a reference 180
to this profile in its “Related Profiles” table. 181
3.6 182
ShallIndicates requirements to be followed strictly in order to conform to the document and from which 183
no deviation is permitted. 184
3.7 185
FQDD Fully Qualified Device Descriptor is used to identify a particular component in a system. 186
3.8 187
Interop Namespace: root/interop 188
Interop Namespace: root/interop is where instrumentation instantiates classes to advertise its capabilities 189
for client discovery. 190
3.9 191
Implementation Namespace: root/dcim 192
Implementation Namespace: root/dcim is where instrumentation instantiates classes relevant to executing 193
core management tasks. 194
3.10 195
ENUMERATE - Refers to WS-MAN ENUMERATE operation as described in Section 8.2 of 196
DSP0226_V1.1 and Section 9.1 of DSP0227_V1.0 197
3.11 198
GET - Refers to WS-MAN GET operation as defined in Section 7.3 of DSP00226_V1.1 and Section 199
7.1 of DSP0227_V1.0 200
201