# Class CIM_RegisteredProfile
extends CIM_RegisteredSpecification

A RegisteredProfile describes a set of CIM Schema classes with required properties and/or methods, necessary to manage a real-world entity or to support a usage scenario, in an interoperable fashion. RegisteredProfiles can be defined by the DMTF or other standards organizations. Note that this class should not be confused with CIM_Profile, which collects SettingData instances, to be applied as a 'configuration profile' for an element. A RegisteredProfile is a named 'standard' for CIM-based management of a particular System, subsystem, Service or other entity, for a specified set of uses. It is a complete, standalone definition, as opposed to the subclass RegisteredSubProfile, which requires a scoping profile for context. The uses for a RegisteredProfile or SubProfile MUST be specified in the document that defines the profile. Examples of Profiles are to manage various aspects of an Operating System, Storage Array, or Database. The name of the profile is defined and scoped by its authoring organization.

### Table of Contents
Hierarchy
Direct Known Subclasses
Class Qualifiers
Class Properties
Class Methods

## Class Hierarchy

CIM_ManagedElement
|
+--CIM_RegisteredSpecification
|
+--CIM_RegisteredProfile

## Direct Known Subclasses

CIM_RegisteredSubProfile

## Class Qualifiers

Name | Data Type | Value
--- | --- | ---
Description | string | A RegisteredProfile describes a set of CIM Schema classes with required properties and/or methods, necessary to manage a real-world entity or to support a usage scenario, in an interoperable fashion. RegisteredProfiles can be defined by the DMTF or other standards organizations. Note that this class should not be confused with CIM_Profile, which collects SettingData instances, to be applied as a 'configuration profile' for an element. A RegisteredProfile is a named 'standard' for CIM-based management of a particular System, subsystem, Service or other entity, for a specified set of uses. It is a complete, standalone definition, as opposed to the subclass RegisteredSubProfile, which requires a scoping profile for context. The uses for a RegisteredProfile or SubProfile MUST be specified in the document that defines the profile. Examples of Profiles are to manage various aspects of an Operating System, Storage Array, or Database. The name of the profile is defined and scoped by its authoring organization.
UMLPackagePath | string | CIM::Interop
Version | string | 2.39.0

## Class Properties

### Local Class Properties

Name | Data Type | Default Value | Qualifiers
--- | --- | --- | ---
Name | Data Type | Value
SpecificationType | uint16 |
Description | string | If this property has a value other than null, the value shall be 2
ModelCorrespondence | string | CIM_RegisteredSpecification.OtherSpecificationType
Override | string | SpecificationType
ValueMap | string | 2
Values | string | Profile
ImplementedFeatures | string[] |
Description | string | Profiles may gather a set of provisions together that are implemented, (or not implemented), as a whole by a conformant implementation. Such sets are known as profile features. If a profile does not define features, then this property shall be null. If not null, an implementation shall put the profile defined feature name of each implemented feature in a separate entry of this array.

### Inherited Properties

Name | Data Type
--- | ---
Caption | string
Description | string
ElementName | string
Generation | uint64
InstanceID | string
OtherRegisteredOrganization | string
OtherSpecificationType | string
RegisteredName | string
RegisteredOrganization | uint16
RegisteredVersion | string
AdvertiseTypeDescriptions | string[]
AdvertiseTypes | uint16[]

## Class Methods