A RegisteredSpecification is used to advertise the implementation of a specification within a WBEM server. The specification may be authored by the DMTF or another standards organization. In this context, specification is used to describe a named and versioned set of constraints. There may be a one to one correspondence between the set of constraints and the document in which they are published. An example of a one to one correspondence is the mechanism used by the DMTF to publish its profiles. An example of one to many documents to specifications is an SMI-S book published by SNIA.
CIM_RegisteredSpecification properties
CIM_RegisteredSpecification has 12 properties (8 Local, 4 Derived)
'A free-form string providing additional information related to the AdvertiseTypes. A description shall be provided for each occurrence of AdvertiseTypes. entry in this array corresponds to the entry in the AdvertiseTypes array at the same index. It is not expected that additional descriptions are needed if the Type is set to "Not Advertised" or "SLP". However, as the SLP template expands, or as other advertisement mechanisms are defined, support for additional descriptions may be needed. This array is defined to support this.'
'This property signifies the requested network advertisement for specification information. It is used by the advertising services of the WBEM infrastructure to determine what should be advertised, via what mechanisms. The property is an array so that the specification may be advertised using several mechanisms. Note: If this property is null/uninitialized, shall be equivalent to specifying the value 2, "Not Advertised".'
'OtherRegisteredOrganization shall be a a free-form string providing a description of the organization if 1, "Other" is specified for the RegisteredOrganization.'
'OtherSpecificationType shall be a a free-form string providing a description of the specification type if 1, "Other" is specified for the SpecificationType.'
OtherSpecificationType property is in 1 class (CIM_RegisteredSpecification) of ROOT\interop\ms_409 and in 2 namespaces
'The name of this registered specification. Since multiple versions can exist for the same RegisteredName, the combination of RegisteredName, RegisteredOrganization, and RegisteredVersion shall uniquely identify the registered specification within the scope of the organization. The value of this property shall correspond to the name given to the set of versioned constraings by a specification or standard. The value does not identify the name of the document or publishing media, unless it happens to be the same as the name given to the versioned constraints.'
['Other', 'DMTF', 'CompTIA', 'Consortium for Service Innovation', 'FAST', 'GGF', 'INTAP', 'itSMF', 'NAC', 'Northwest Energy Efficiency Alliance', 'SNIA', 'TM Forum', 'The Open Group', 'ANSI', 'IEEE', 'IETF', 'INCITS', 'ISO', 'W3C', 'OGF', 'The Green Grid', 'DMTF Reserved']
'The version describing the creation or last modificationof the specification. The string representing the version shall be in the form: M + "." + N + "." + U Where: M - The major version (in numeric form). N - The minor version (in numeric form). U - The update (e.g. errata, patch, ..., in numeric form).'
'A user-friendly name for the object. This property allows each instance to define a user-friendly name in addition to its key properties, identity data, and description information. Note that the Name property of ManagedSystemElement is also defined as a user-friendly name. But, it is often subclassed to be a Key. It is not reasonable that the same property can convey both identity and a user-friendly name, without inconsistencies. Where Name exists and is not a Key (such as for instances of LogicalDevice), the same information can be present in both the Name and ElementName properties.'
'Within the scope of the instantiating Namespace, InstanceID opaquely and uniquely identifies an instance of this class. In order to ensure uniqueness within the NameSpace, the value of InstanceID shall be constructed using the following 'preferred' algorithm: : Where and are separated by a colon ':', and where shall include a copyrighted, trademarked or otherwise unique name that is owned by the business entity creating/defining the InstanceID, or is a registered ID that is assigned to the business entity by a recognized global authority. (This is similar to the _ structure of Schema class names.) In addition, to ensure uniqueness, shall not contain a colon (':'). The first colon to appear in InstanceID shall appear between and . is chosen by the organizational entity and should not be re-used to identify different underlying (real-world) elements. For DMTF defined instances, shall be set to 'CIM'.'
'A RegisteredSpecification is used to advertise the implementation of a specification within a WBEM server. The specification may be authored by the DMTF or another standards organization. In this context, specification is used to describe a named and versioned set of constraints. There may be a one to one correspondence between the set of constraints and the document in which they are published. An example of a one to one correspondence is the mechanism used by the DMTF to publish its profiles. An example of one to many documents to specifications is an SMI-S book published by SNIA.'