<?xml version="1.0" encoding="UTF-8"?>
<!--
DMTF - Distributed Management Task Force, Inc. - http://www.dmtf.org

Release URLs:
http://schemas.dmtf.org/wbem/messageregistry/1/dsp2022_1.2.0.xml
http://schemas.dmtf.org/wbem/messageregistry/1/dsp2022_1.2.xml

Document number: DSP2022
Date: 2012-01-24
Version: 1.2.0
Document status: DMTF Informational

Title: Sample Message Registry

Document type: Technical Note (XML Instance Document)
Document language: E

Abstract: This document is a sample DMTF message registry.

Contact group: DMTF Infrastructure Sub-Committee, infrastructure-sc@dmtf.org

Acknowledgements: DMTF acknowledges the contributions of the following individuals to this document:
* Jim Davis (WBEM Solutions)
* Steve Hand (Symantec)
* Andreas Maier (IBM) (Editor)
* Linda Martinez (Dell)

Copyright (C) 2008,2012 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 for uses consistent with this
purpose, 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.

Change log:
1.0.0 - 2009-07-28 - Released as Informational
1.1.0 - 2009-10-15 - Released as Informational
1.2.0b - 2011-09-20 - Member review
1.2.0 - 2012-01-24 - Released as Informational
-->
<?xml-stylesheet href="http://schemas.dmtf.org/wbem/messageregistry/1/dsp8000_1.2.xsl" type="text/xsl"?>
<!--
Note:  The href attribute above specifies the URL of the official publication location of the XSLT stylesheet.
When working with a local copy of this file, change the href attribute to reference a local copy of the XSLT stylesheet.
Background: For security reasons, Web browsers typically require that the XSLT stylesheet is located on the same host
as the file referencing it (i.e. this file). Using XML Catalog resolution to a local URL cannot be used either, since
Web browsers typically do not support XML Catalogs.
-->
<REGISTRY xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.dmtf.org/wbem/messageregistry/1" xsi:schemaLocation="http://schemas.dmtf.org/wbem/messageregistry/1 http://schemas.dmtf.org/wbem/messageregistry/1/dsp0228_1.2.xsd">
    <REGISTRY_DECLARATION>
        <IDENTIFICATION ID="DSP2022" NAME="Sample Message Registry" LANGUAGE="en" VERSION="1.2.0"/>
        <CIM_SCHEMA VERSION="2.30"/>
        <OWNING_ENTITY>DMTF</OWNING_ENTITY>
        <DESCRIPTION>This is a sample message registry that includes some examples of common messages
            that can be produced by all CIM/WBEM implementations.</DESCRIPTION>
    </REGISTRY_DECLARATION>
    <REGISTRY_ENTRIES>
        <MESSAGE NAME="Parameter Error">
            <MESSAGE_ID PREFIX="XMP" SEQUENCE_NUMBER="0001"/>
            <MESSAGE_DESCRIPTION>An example of a message with fixed values for use in an extended error (CIM_Error).</MESSAGE_DESCRIPTION>
            <MESSAGE_COMPONENTS>
                <STATIC_ELEMENT>Parameter </STATIC_ELEMENT>
                <DYNAMIC_ELEMENT NAME="Position" DATATYPE="uint16">
                    <DESCRIPTION>The position the errant argument appears in the declaration of the
                        method, from left to right</DESCRIPTION>
                </DYNAMIC_ELEMENT>
                <STATIC_ELEMENT> of the </STATIC_ELEMENT>
                <DYNAMIC_ELEMENT NAME="Method Type" DATATYPE="string">
                    <POSSIBLE_VALUE>extrinsic</POSSIBLE_VALUE>
                    <POSSIBLE_VALUE>intrinsic</POSSIBLE_VALUE>
                </DYNAMIC_ELEMENT>
                <STATIC_ELEMENT> method, </STATIC_ELEMENT>
                <DYNAMIC_ELEMENT NAME="Method Name" DATATYPE="string"/>
                <STATIC_ELEMENT> , is invalid because </STATIC_ELEMENT>
                <DYNAMIC_ELEMENT NAME="Reason for invalid parameter" DATATYPE="string">
                    <POSSIBLE_VALUE>parameter value out of range</POSSIBLE_VALUE>
                    <POSSIBLE_VALUE>invalid combination</POSSIBLE_VALUE>
                    <POSSIBLE_VALUE>null parameter is not permitted</POSSIBLE_VALUE>
                    <POSSIBLE_VALUE>non-null value is not permitted</POSSIBLE_VALUE>
                    <POSSIBLE_VALUE>empty string is not permitted</POSSIBLE_VALUE>
                    <POSSIBLE_VALUE>empty array is not permitted</POSSIBLE_VALUE>
                </DYNAMIC_ELEMENT>
                <STATIC_ELEMENT>. Please fix the parameter at position </STATIC_ELEMENT>
                <REPEAT_DYNAMIC_ELEMENT NAME="Position"/>
                <STATIC_ELEMENT> and retry. </STATIC_ELEMENT>
                <DYNAMIC_ELEMENT NAME="Protocol Error Code" SOURCE_PROPERTY="CIM_Error.CIMStatusCode" DATATYPE="string" EXPECTED_IN_MESSAGE="false">
                    <DESCRIPTION>Protocol specific error code reported from operation.</DESCRIPTION>
                </DYNAMIC_ELEMENT>
            </MESSAGE_COMPONENTS>
            <FIXED_MESSAGE_INSTANCE_VALUES TYPE="ERROR">
                <CIMSTATUSCODE> 4 <DESCRIPTION>CIM_ERR_INVALID_PARAMETER</DESCRIPTION>
                </CIMSTATUSCODE>
                <ERROR_TYPE> 4 <DESCRIPTION>Software Error</DESCRIPTION>
                </ERROR_TYPE>
                <ERROR_SOURCE EXISTENCE_IS="discouraged">
                    <DESCRIPTION> It is discouraged from specifying any reference here. </DESCRIPTION>
                </ERROR_SOURCE>
                <PERCEIVED_SEVERITY> 2 <DESCRIPTION>Low</DESCRIPTION>
                </PERCEIVED_SEVERITY>
            </FIXED_MESSAGE_INSTANCE_VALUES>
        </MESSAGE>
        <MESSAGE NAME="Shutdown Started">
            <MESSAGE_ID PREFIX="XMP" SEQUENCE_NUMBER="0002"/>
            <MESSAGE_DESCRIPTION>An example of a message with fixed values for use in an alert indication (CIM_AlertIndication).</MESSAGE_DESCRIPTION>
            <MESSAGE_COMPONENTS>
                <STATIC_ELEMENT> The computer system is shutting down in </STATIC_ELEMENT>
                <DYNAMIC_ELEMENT NAME="seconds to shutdown" DATATYPE="uint32">
                    <DESCRIPTION>The number of seconds before the system is shutdown.</DESCRIPTION>
                </DYNAMIC_ELEMENT>
                <STATIC_ELEMENT> seconds. </STATIC_ELEMENT>
            </MESSAGE_COMPONENTS>
            <FIXED_MESSAGE_INSTANCE_VALUES TYPE="ALERT">
                <ALERTING_MANAGED_ELEMENT EXISTENCE_IS="required">
                    <DESCRIPTION> The object name must reference the top-most computer system
                        that is shutting down. If the computer system is cluster, then the cluster
                        computer system must be referenced. </DESCRIPTION>
                </ALERTING_MANAGED_ELEMENT>
                <ALERT_TYPE> 5 <DESCRIPTION>Device Alert</DESCRIPTION>
                </ALERT_TYPE>
                <PERCEIVED_SEVERITY> 4 <DESCRIPTION>High</DESCRIPTION>
                </PERCEIVED_SEVERITY>
            </FIXED_MESSAGE_INSTANCE_VALUES>
        </MESSAGE>
        <MESSAGE NAME="Component overheat">
            <MESSAGE_ID PREFIX="XMP" SEQUENCE_NUMBER="0003"/><MESSAGE_DESCRIPTION>An example of a message with fixed values for use in an extended error (CIM_Error) and in an alert indication (CIM_AlertIndication).</MESSAGE_DESCRIPTION>
            <MESSAGE_COMPONENTS>
                <STATIC_ELEMENT>A component has overheated. </STATIC_ELEMENT>
                <DYNAMIC_ELEMENT NAME="Component Type" DATATYPE="string">
                    <POSSIBLE_VALUE>The entire device is affected. Device wide failure has already
                        or can be expected shortly. </POSSIBLE_VALUE>
                    <POSSIBLE_VALUE>Only a single component is affected. Corrective action may be
                        taken. </POSSIBLE_VALUE>
                </DYNAMIC_ELEMENT>
                <STATIC_ELEMENT> The OperationalStatus reported is: </STATIC_ELEMENT>
                <DYNAMIC_ELEMENT NAME="OperationalStatus" DATATYPE="string" IS_ARRAY="true"/>
            </MESSAGE_COMPONENTS>
            <FIXED_MESSAGE_INSTANCE_VALUES TYPE="ALERT">
                <ALERTING_MANAGED_ELEMENT EXISTENCE_IS="required">
                    <DESCRIPTION> The object name must reference the physical element most affected
                        by the over temperature message. </DESCRIPTION>
                </ALERTING_MANAGED_ELEMENT>
                <ALERT_TYPE> 6 <DESCRIPTION>Environmental Alert</DESCRIPTION>
                </ALERT_TYPE>
                <PERCEIVED_SEVERITY> 4 <DESCRIPTION>High</DESCRIPTION>
                </PERCEIVED_SEVERITY>
            </FIXED_MESSAGE_INSTANCE_VALUES>
            <FIXED_MESSAGE_INSTANCE_VALUES TYPE="ERROR">
                <CIMSTATUSCODE> 1 <DESCRIPTION>CIM_ERR_FAILED</DESCRIPTION>
                </CIMSTATUSCODE>
                <ERROR_TYPE> 6 <DESCRIPTION>Environment Error</DESCRIPTION>
                </ERROR_TYPE>
                <ERROR_SOURCE EXISTENCE_IS="required">
                    <DESCRIPTION> The object name must reference the physical element most affected
                        by the over temperature message. </DESCRIPTION>
                </ERROR_SOURCE>
                <PERCEIVED_SEVERITY> 4 <DESCRIPTION>High</DESCRIPTION>
                </PERCEIVED_SEVERITY>
            </FIXED_MESSAGE_INSTANCE_VALUES>
        </MESSAGE>
        <MESSAGE NAME="WBEM Management Interface is not available">
            <MESSAGE_ID PREFIX="XMP" SEQUENCE_NUMBER="0004"/>
            <MESSAGE_DESCRIPTION>An example of a message that declares no fixed values.</MESSAGE_DESCRIPTION>
            <MESSAGE_COMPONENTS>
                <STATIC_ELEMENT>The management interface for the device is not available.</STATIC_ELEMENT>
            </MESSAGE_COMPONENTS>
        </MESSAGE>
        <MESSAGE NAME="Device path removed">
            <MESSAGE_ID PREFIX="XMP" SEQUENCE_NUMBER="0005"/>
            <MESSAGE_DESCRIPTION>An example of a message with fixed values for use in an informational message (CIM_Message).</MESSAGE_DESCRIPTION>
            <MESSAGE_COMPONENTS>
                <STATIC_ELEMENT>The path to device </STATIC_ELEMENT>
                <DYNAMIC_ELEMENT NAME="device number" DATATYPE="string">
                    <DESCRIPTION>The device number, as a four-digit upper case hexadecimal string.</DESCRIPTION>
                </DYNAMIC_ELEMENT>
                <STATIC_ELEMENT> was removed.</STATIC_ELEMENT>
            </MESSAGE_COMPONENTS>
            <FIXED_MESSAGE_INSTANCE_VALUES TYPE="MESSAGE"/>
        </MESSAGE>
        <MESSAGE NAME="Device path removed (with hidden dynamic element)">
            <MESSAGE_ID PREFIX="XMP" SEQUENCE_NUMBER="0006"/>
            <MESSAGE_DESCRIPTION>An example of a message with a normal and a hidden dynamic element.</MESSAGE_DESCRIPTION>
            <MESSAGE_COMPONENTS>
                <STATIC_ELEMENT>The path to device </STATIC_ELEMENT>
                <DYNAMIC_ELEMENT NAME="device number" DATATYPE="string">
                    <DESCRIPTION>The device number, as a four-digit upper case hexadecimal string.</DESCRIPTION>
                </DYNAMIC_ELEMENT>
                <STATIC_ELEMENT> was removed.</STATIC_ELEMENT>
                <DYNAMIC_ELEMENT NAME="internal device identifier" DATATYPE="string" EXPECTED_IN_MESSAGE="false">
                    <DESCRIPTION>The internal device identifier (as a hidden dynamic element, so it shows up as an entry in the MessageArguments array property but not in the expanded message string of the Message property).</DESCRIPTION>
                </DYNAMIC_ELEMENT>
            </MESSAGE_COMPONENTS>
            <FIXED_MESSAGE_INSTANCE_VALUES TYPE="MESSAGE"/>
        </MESSAGE>
        <MESSAGE NAME="Device path removed (with display values for a dynamic element)">
            <MESSAGE_ID PREFIX="XMP" SEQUENCE_NUMBER="0007"/>
            <MESSAGE_DESCRIPTION>An example of a message with a normal dynamic element and a dynamic element with display values.</MESSAGE_DESCRIPTION>
            <MESSAGE_COMPONENTS>
                <STATIC_ELEMENT>The path to device </STATIC_ELEMENT>
                <DYNAMIC_ELEMENT NAME="device number" DATATYPE="string">
                    <DESCRIPTION>The device number, as a four-digit upper case hexadecimal string.</DESCRIPTION>
                </DYNAMIC_ELEMENT>
                <STATIC_ELEMENT> of type </STATIC_ELEMENT>
                <DYNAMIC_ELEMENT NAME="device type" DATATYPE="string" USE_DISPLAY_VALUE="true">
                    <DESCRIPTION>The device type, as a human readable string.</DESCRIPTION>
                    <POSSIBLE_VALUE> 0 <DESCRIPTION>Device type is unknown</DESCRIPTION><DISPLAY_VALUE>unknown</DISPLAY_VALUE></POSSIBLE_VALUE>
                    <POSSIBLE_VALUE> 1 <DESCRIPTION>Device type disk (of any sort)</DESCRIPTION><DISPLAY_VALUE>disk</DISPLAY_VALUE></POSSIBLE_VALUE>
                    <POSSIBLE_VALUE> 2 <DESCRIPTION>Device type network interface (of any sort)</DESCRIPTION><DISPLAY_VALUE>network interface</DISPLAY_VALUE></POSSIBLE_VALUE>
                </DYNAMIC_ELEMENT>
                <STATIC_ELEMENT> was removed.</STATIC_ELEMENT>
            </MESSAGE_COMPONENTS>
            <FIXED_MESSAGE_INSTANCE_VALUES TYPE="MESSAGE"/>
        </MESSAGE>
    </REGISTRY_ENTRIES>
</REGISTRY>
