.
Document Number: DSP1117
Date: 2011-08-31
Version: 1.0.0a
Initiative Registration Profile
IMPORTANT: This specification is not a standard. It does not necessarily reflect the views of the DMTF or all of its members. Because this document is a Work in Progress, this specification may still change, perhaps profoundly. This document is available for public review and comment until the stated expiration date. This document expires on: 2012-02-28. Target version for DMTF Standard: 1.0.0. Provide any comments through the DMTF Feedback Portal: http://www.dmtf.org/standards/feedback |
Document Type: Specification
Document Status: Work in Progress
Document Language: en-US
Copyright © 2011 Distributed Management Task Force, Inc. (DMTF). All rights reserved.
DMTF is a not-for-profit association of industry members dedicated to promoting enterprise and systems management and interoperability. Members and non-members may reproduce DMTF specifications and documents, provided that correct attribution is given. As DMTF specifications may be revised from time to time, the particular version and release date should always be noted.
Implementation of certain elements of this standard or proposed standard may be subject to third party patent rights, including provisional patent rights (herein "patent rights"). DMTF makes no representations to users of the standard as to the existence of such rights, and is not responsible to recognize, disclose, or identify any or all such third party patent right, owners or claimants, nor for any incomplete or inaccurate identification or disclosure of such rights, owners or claimants. DMTF shall have no liability to any party, in any manner or circumstance, under any legal theory whatsoever, for failure to recognize, disclose, or identify any such third party patent rights, or for such party’s reliance on the standard or incorporation thereof in its product, protocols or testing procedures. DMTF shall have no liability to any party implementing such standard, whether such implementation is foreseeable or not, nor to any patent owner or claimant, and shall have no liability or responsibility for costs or losses incurred if a standard is withdrawn or modified after publication, and shall be indemnified and held harmless by any party implementing the standard from any and all claims of infringement by a patent owner for such implementations.
For information about patents held by third-parties which have notified the DMTF that, in their opinion, such patent may relate to or impact implementations of DMTF standards, visit http://www.dmtf.org/about/policies/disclosures.php.
This document was prepared by the DMTF Architecture Working Group
DMTF is a not-for-profit association of industry members dedicated to promoting enterprise and systems management and interoperability. For information about the DMTF, see http://www.dmtf.org.
DMTF acknowledges the following individuals for their contributions to this document:
This document defines the CIM model for discovering implemented initiatives in a managed environment. The information in this document is intended to be sufficient for a provider or consumer of this data to identify unambiguously the classes, properties, methods, and values that need to be instantiated and manipulated.
The target audience for this specification is implementers who are writing CIM-based providers or consumers of management interfaces that represent the components described in this document.
The following typographical conventions are used in this document:
Constraints in this document are specified using OCL (see OCL 2.0).
OCL statements are in monospaced font.
The Initiative Registration profile is an autonomous profile that provides for discovering implemented initiatives, and optionally the profiles implemented in the context of these initiatives.
The following referenced documents are indispensable for the application of this document. For dated or versioned references, only the edition cited (including any corrigenda or DMTF update versions) applies. For references without a date or version, the latest published edition of the referenced document (including any corrigenda or DMTF update versions) applies.
DMTF DSP0004, CIM Infrastructure Specification 2.6,
http://www.dmtf.org/standards/published_documents/DSP0004_2.6.pdf
DMTF DSP0223, Generic Operations 1.0,
http://www.dmtf.org/standards/published_documents/DSP0223_1.0.pdf
DMTF DSP1001, Management Profile Specification Usage Guide 1.1,
http://www.dmtf.org/standards/published_documents/DSP1001_1.1.pdf
DMTF DSP1033, Profile Registration Profile 1.1,
http://www.dmtf.org/standards/published_documents/dsp1033_1.1.html
OMG formal/06-05-01, Object Constraint Language 2.0,
http://www.omg.org/spec/OCL/2.0/
ISO/IEC Directives, Part 2, Rules for the structure and drafting of International Standards,
http://isotc.iso.org/livelink/livelink?func=ll&objId=4230456&objAction=browse&sort=subtype
In this document, some terms have a specific meaning beyond the normal English meaning. Those terms are defined in this clause.
The terms "shall" ("required"), "shall not", "should" ("recommended"), "should not" ("not recommended"), "may", "need not" ("not required"), "can" and "cannot" in this document are to be interpreted as described in ISO/IEC Directives, Part2, Annex H. The terms in parenthesis are alternatives for the preceding term, for use in exceptional cases when the preceding term cannot be used for linguistic reasons. Note that ISO/IEC Directives, Part2, Annex H specifies additional alternatives. Occurrences of such additional alternatives shall be interpreted in their normal English meaning in this document.
The terms "clause", "subclause", "paragraph", "annex" in this document are to be interpreted as described in ISO/IEC Directives, Part2, Clause 5.
The terms "normative" and "informative" in this document are to be interpreted as described in ISO/IEC Directives, Part2, Clause 3. In this document, clauses, subclauses or annexes indicated with "(informative)" as well as notes and examples do not contain normative content.
The terms defined in DSP0004, DSP0223, and DSP1001 apply to this document.
The following additional terms are defined in this document.
initiative
A named and versioned amount of management functionality with conformance requirements. The conformance requirements for implementing an initiative are described in an initiative specification, based on management profiles and other specifications. Initiatives may be defined by DMTF, other standards organizations, or vendors. An example for an initiative defined by DMTF is DASH.
initiative specification
A specification defining conformance requirements for implementing an initiative. Also called "initiative wrapper specification". An example for an initiative specification is DSP0232, defining conformance requirements for the DASH initiative.
interop namespace
A CIM namespace for interoperability, as defined in DSP1033.
profile
A management profile, as defined in DSP1001.
The abbreviations defined in DSP0004, DSP0223, and DSP1001 apply to this document.
The following additional abbreviations are defined in this document.
DASH
Desktop and Mobile Architecture for System Hardware, an initiative defined by DMTF; its conformance requirements are described in DSP0232.
Profile name: Initiative Registration
Version: 1.0.0
Organization: DMTF
Abstract indicator: False
Profile type: Autonomous
Schema: DMTF CIM 2.22 (experimental)
Central class adaptation: RegisteredInitiative
Scoping class adaptation: RegisteredInitiative
The Initiative Registration profile is an autonomous profile that provides for discovering implemented initiatives, and optionally the profiles implemented in the context of these initiatives.
The following table identifies the profile references defined in this profile.
| Profile reference name | Profile name | Organization | Version | Relationship | Description |
|---|---|---|---|---|---|
| InitiativeProfile | Profile Registration | DMTF | 1.0 | Mandatory | Used to represent the implementation of a profile in context of an initiative implementation. |
| ProfileRegistration | Profile Registration | DMTF | 1.0 | Mandatory | Used to represent the implementation of this profile. |
The following table identifies the features defined in this profile.
| Feature | Requirement | Description |
|---|---|---|
| InitiativeProfiles | Optional | See InitiativeProfiles. |
| PulledEnumerations | Optional | See PulledEnumerations. |
The following table identifies the class adaptations defined in this profile.
| Adaptation | Elements | Requirement | Description |
|---|---|---|---|
| Instantiated, embedded and abstract adaptations | |||
| RegisteredProfile | CIM_RegisteredProfile | Mandatory | See RegisteredProfile. |
| RegisteredInitiative | CIM_RegisteredSpecification | Mandatory | See RegisteredInitiative. |
| ProfileOfInitiative | CIM_ReferencedSpecification | Conditional | See ProfileOfInitiative. |
| InitiativeProfile | CIM_RegisteredProfile | Conditional | See InitiativeProfile. |
| Indications and exceptions | |||
| This profile does not define any such adaptations. | |||
The following table identifies the use cases and state descriptions defined in this profile.
| Name | Description |
|---|---|
| State description SimpleObjectDiagram | See SimpleObjectDiagram. |
| Use case DetermineAllInitiatives | See DetermineAllInitiatives. |
| Use case DetermineInitiativesOfProfile | See DetermineInitiativesOfProfile. |
| Use case DetermineProfilesOfInitiative | See DetermineProfilesOfInitiative. |
The following DMTF collaboration structure diagram shows all class adaptations defined in this profile, and all profiles referenced by this profile.
DMTF collaboration structure diagram
The RegisteredInitiative adaptation is the central (and scoping) adaptation of this profile; its instances represent initiatives to which implementations conform.
If the InitiativeProfiles feature is implemented for an initiative, the profiles implemented in context of that initiative are represented by InitiativeProfile instances associated through ProfileOfInitiative. The InitiativeProfile instances assume the role of the InitiativeProfile::RegisteredProfile adaptation, so the profile implementations can be discovered using the mechanisms described in DSP1033.
Finally, conformance to this profile is indicated by a RegisteredProfile instance.
Implementing this feature provides support for representing the relationship between implemented initiatives and the profiles implemented in context of these initiatives.
The requirement level for this feature is optional.
This feature can be made available to clients at the granularity of RegisteredInitiative instances.
Availability of this feature can be discovered by clients as follows.
It can be concluded that the feature is available for a RegisteredInitiative instance if:
The following OCL derivation constraint evaluates to a Boolean value of True.
OCL context: A RegisteredInitiative instance.
derive: self.ProfileOfInitiative::Antecedent->size() > 0 |
Explanation:
There is at least one ProfileOfInitiative instance referencing the RegisteredInitiative instance representing the implemented initiative.
The following profile elements are conditional on the implementation of this feature:
Implementing this feature provides support for pulled enumeration operations (e.g. the generic operation OpenClassInstancePaths). Which operations are to be supported on a class adaptation is defined through operation requirements on the class adaptation.
The requirement level for this feature is optional.
This feature can be made available to clients at the granularity of an implementation of this profile.
Availability of this feature cannot be discovered by clients (other than trying the functionality provided by the feature).
The following profile elements are conditional on the implementation of this feature:
This profile defines operation requirements based on DSP0223.
For adaptations of ordinary classes and of associations the requirements for operations are defined in adaptation-specific subclauses of the "Adaptations" clause.
For association traversal operation requirements that are specified only in the elements table of an adaptation (i.e. without operation-specific subclauses), the names of the association adaptations to be traversed are listed in the elements table.
The default initialization requirement level for property requirements is optional.
The default modification requirement level for property requirements is optional.
This profile repeats the effective values of certain Boolean qualifiers as part of property, method parameter, or method return value requirements. The following convention is established: If the name of a qualifier is listed, its effective value is True; if the qualifier name is not listed, its effective value is False. The convention is applied in the following cases:
This adaptation models implementations of this profile.
The implementation type of this adaptation is instantiated ordinary adaptation.
The requirement level for this adaptation is mandatory.
The following table identifies the element requirements for this adaptation.
| Element | Requirement | Description |
|---|---|---|
| Base adaptations | ||
| ProfileRegistration::RegisteredProfile | Mandatory | See ProfileRegistration::RegisteredProfile. |
| Properties | ||
| RegisteredName | Mandatory | Required, see RegisteredName. |
| RegisteredOrganization | Mandatory | Required, see RegisteredOrganization. |
| RegisteredVersion | Mandatory | Required, see RegisteredVersion. |
The presentation requirement level of this property is mandatory.
The implementation shall satisfy the following constraint for this property:
OCL constraint with context of a RegisteredProfile instance:
inv: self.RegisteredName = 'Initiative Registration' |
The presentation requirement level of this property is mandatory.
The implementation shall satisfy the following constraint for this property:
OCL constraint with context of a RegisteredProfile instance:
inv: self.RegisteredOrganization = 2 /* DMTF */ |
The presentation requirement level of this property is mandatory.
The implementation shall satisfy the following constraint for this property:
OCL constraint with context of a RegisteredProfile instance:
inv: self.RegisteredVersion = '1.0.0a' |
This adaptation models initiatives to which this implementation conforms; each such initiative shall have an initiative specification describing it.
This adaptation shall be exposed in the interop namespace of the WBEM server that implements the initiative.
The implementation type of this adaptation is instantiated ordinary adaptation.
The requirement level for this adaptation is mandatory.
The following table identifies the element requirements for this adaptation.
| Element | Requirement | Description |
|---|---|---|
| Base adaptations | ||
| ProfileRegistration::CentralElement | Mandatory | See ProfileRegistration::CentralElement. |
| ProfileRegistration::ScopingElement | Mandatory | See ProfileRegistration::ScopingElement. |
| Properties | ||
| InstanceID | Mandatory | Key, see schema definition. |
| SpecificationType | Mandatory | See SpecificationType. |
| RegisteredOrganization | Mandatory | Required, see RegisteredOrganization. |
| RegisteredName | Mandatory | Required, see RegisteredName. |
| RegisteredVersion | Mandatory | Required, see RegisteredVersion. |
| AdvertiseTypes | Mandatory | Required, see schema definition. |
| AdvertiseTypeDescriptions | Mandatory | See schema definition. |
| Operations | ||
| GetInstance( ) | Mandatory | See DSP0223. |
| GetClassInstancesWithPath( ) | Mandatory | See DSP0223. |
| GetClassInstancePaths( ) | Mandatory | See DSP0223. |
| OpenClassInstancesWithPath( ) | Conditional | See OpenClassInstancesWithPath( ). |
| OpenClassInstancePaths( ) | Conditional | See OpenClassInstancePaths( ). |
| GetAssociatedInstancesWithPath( ) for ProfileOfInitiative | Conditional | See GetAssociatedInstancesWithPath( ) for ProfileOfInitiative. |
| GetAssociatedInstancePaths( ) for ProfileOfInitiative | Conditional | See GetAssociatedInstancePaths( ) for ProfileOfInitiative. |
| OpenAssociatedInstancesWithPath( ) for ProfileOfInitiative | Conditional | See OpenAssociatedInstancesWithPath( ) for ProfileOfInitiative. |
| OpenAssociatedInstancePaths( ) for ProfileOfInitiative | Conditional | See OpenAssociatedInstancePaths( ) for ProfileOfInitiative. |
The presentation requirement level of this property is mandatory.
The implementation shall satisfy the following constraint for this property:
OCL constraint with context of a RegisteredInitiative instance:
inv: self.SpecificationType = 3 /* Initiative Wrapper */ |
Explanation:
This property shall have a value of 3, indicating that the instance represents an initiative specification.
The presentation requirement level of this property is mandatory.
The value of this property shall be the organization owning the initiative specification of the initiative represented by an instance of this adaptation.
The presentation requirement level of this property is mandatory.
The value of this property shall be the name of the initiative as defined in the initiative specification of the initiative represented by an instance of this adaptation.
The presentation requirement level of this property is mandatory.
The value of this property shall be the version of the initiative specification of the initiative represented by an instance of this adaptation.
For general requirements on the implementation of this operation, see DSP0223.
The requirement level for this operation is conditional, with the following condition:
The PulledEnumerations feature is implemented.
For general requirements on the implementation of this operation, see DSP0223.
The requirement level for this operation is conditional, with the following condition:
The PulledEnumerations feature is implemented.
For general requirements on the implementation of this operation, see DSP0223.
The requirement level for this operation is conditional, with the following condition:
The InitiativeProfiles feature is implemented.
This operation requirement applies to the following association adaptations:
For general requirements on the implementation of this operation, see DSP0223.
The requirement level for this operation is conditional, with the following condition:
The InitiativeProfiles feature is implemented.
This operation requirement applies to the following association adaptations:
For general requirements on the implementation of this operation, see DSP0223.
The requirement level for this operation is conditional, with the following condition:
All of the following is true:
This operation requirement applies to the following association adaptations:
For general requirements on the implementation of this operation, see DSP0223.
The requirement level for this operation is conditional, with the following condition:
All of the following is true:
This operation requirement applies to the following association adaptations:
This adaptation models the relationship between implemented initiatives represented by RegisteredInitiative instances and the profiles implemented in context of these initiatives that are represented by InitiativeProfile instances.
This adaptation shall be exposed in the interop namespace of the WBEM server that implements the initiative.
The implementation type of this adaptation is instantiated association adaptation.
The requirement level for this adaptation is conditional, with the following condition:
The InitiativeProfiles feature is implemented.
The following table identifies the element requirements for this adaptation.
| Element | Requirement | Description |
|---|---|---|
| Properties | ||
| Antecedent | Mandatory | Key, see Antecedent. |
| Dependent | Mandatory | Key, see Dependent. |
The presentation requirement level of this property is mandatory.
The implementation shall satisfy the following constraints for this reference property:
Referenced instances shall be of class adaptation InitiativeProfile.
The multiplicity of [0 .. *] defined in the schema is not further constrained.
The presentation requirement level of this property is mandatory.
The implementation shall satisfy the following constraints for this reference property:
Referenced instances shall be of class adaptation RegisteredInitiative.
The multiplicity of [0 .. *] defined in the schema is not further constrained.
This adaptation models the relationship between an initiative and a profile implemented in context of that initiative. The profile shall be referenced in the initiative specification of that initiative.
The implementation type of this adaptation is instantiated ordinary adaptation.
The requirement level for this adaptation is conditional, with the following condition:
The InitiativeProfiles feature is implemented.
The following table identifies the element requirements for this adaptation.
| Element | Requirement | Description |
|---|---|---|
| Base adaptations | ||
| InitiativeProfile::RegisteredProfile | Mandatory | See InitiativeProfile::RegisteredProfile. |
| Operations | ||
| GetAssociatedInstancesWithPath( ) for ProfileOfInitiative | Conditional | See GetAssociatedInstancesWithPath( ) for ProfileOfInitiative. |
| GetAssociatedInstancePaths( ) for ProfileOfInitiative | Conditional | See GetAssociatedInstancePaths( ) for ProfileOfInitiative. |
| OpenAssociatedInstancesWithPath( ) for ProfileOfInitiative | Conditional | See OpenAssociatedInstancesWithPath( ) for ProfileOfInitiative. |
| OpenAssociatedInstancePaths( ) for ProfileOfInitiative | Conditional | See OpenAssociatedInstancePaths( ) for ProfileOfInitiative. |
For general requirements on the implementation of this operation, see DSP0223.
The requirement level for this operation is conditional, with the following condition:
The InitiativeProfiles feature is implemented.
This operation requirement applies to the following association adaptations:
For general requirements on the implementation of this operation, see DSP0223.
The requirement level for this operation is conditional, with the following condition:
The InitiativeProfiles feature is implemented.
This operation requirement applies to the following association adaptations:
For general requirements on the implementation of this operation, see DSP0223.
The requirement level for this operation is conditional, with the following condition:
All of the following is true:
This operation requirement applies to the following association adaptations:
For general requirements on the implementation of this operation, see DSP0223.
The requirement level for this operation is conditional, with the following condition:
All of the following is true:
This operation requirement applies to the following association adaptations:
The following object diagram shows a conformant implementation of this profile, with one initiative and two profiles advertized as conformant to the initiative, implementing the InitiativeProfiles feature.
Simple object diagram
The dash instance represents that the implementation conforms to the DASH initiative, version 1.0.0.
The two profiles that have been implemented in context of that initiative are represented by the profile1 and profile2 instances. Because the InitiativeProfiles feature has been implemented, the profile1 and profile2 instances are associated with the dash instance via ProfileOfInitiative association instances.
Conformance to this profile is indicated by the irp instance, using the mechanisms described in DSP1033. Since this profile is an autonomous profile, the central and scoping path methodologies fall together and a client can always expect a ProfileRegistration::ElementConformsToProfile association between RegisteredInitiative and RegisteredProfile.
Determine all initiatives implemented in a WBEM server, and their versions.
This use case has the following preconditions:
The main flow for this use case consists of the following single step:
Enumerate CIM_RegisteredSpecification instances in the interop namespace of the WBEM server, restricting the result set to instances where SpecificationType = 3 (Initiative Wrapper).
The resulting instances conform to the RegisteredInitiative adaptation and represent all initiatives implemented on the WBEM server that implemented this profile. The RegisteredName and RegisteredVersion properties of the returned CIM_RegisteredSpecification instances identify initiative name and version.
Note that there may be initiatives implemented in the WBEM server but for which this profile was not implemented. Such initiatives may not be represented in the result set of this use case.
Determine to which initiatives a given implemented profile conforms.
This use case has the following preconditions:
The main flow for this use case consists of the following single step:
From the given CIM_RegisteredProfile instance, traverse the CIM_ReferencedSpecification association, restricting the associated instances to those of class CIM_RegisteredSpecification where SpecificationType = 3 (Initiative Wrapper).
The resulting CIM_RegisteredSpecification instances conform to the RegisteredInitiative adaptation and represent the initiatives to which the given profile advertizes conformance.
Note that there may be initiatives to which the given profile conforms but for which this profile or the InitiativeProfiles feature was not implemented. Such initiatives may not be represented in the result set of this use case.
Determine which profiles are implemented conforming to a given implemented initiative.
This use case has the following preconditions:
The main flow for this use case consists of the following single step:
From the given CIM_RegisteredSpecification instance, traverse the CIM_ReferencedSpecification association, restricting the associated instances to those of class CIM_RegisteredProfile.
The resulting CIM_RegisteredProfile instances conform to the InitiativeProfile adaptation and represent the profiles that advertize conformance to the given initiative.
Note that there may be profiles that conform to the given initiative but for which the InitiativeProfiles feature was not implemented. Such profiles will not be part of the result set of this use case.
| Version | Date | Description |
|---|---|---|
| 1.0.0a | 2011-08-31 | Released as Work in Progress |
The following documents may provide additional background.
DMTF DSP0232, DASH Implementation Requirements 1.0,
http://www.dmtf.org/standards/published_documents/DSP0232_1.0.pdf