A message registry is a normative expression of the CIM Errors and CIM AlertIndications. A registry consists of a list of values for the properties which define message CIM Instances. It is recommended that a message registry be created in a single source language; the DMTF will publish English registries only. It is not recommended that the dynamic elements contain translatable text because it would make localization of the message registry difficult. It is also not recommended that the CIM Message string property be used for localization. List of details about the registry The name, version, and language of the registry. The name must be unique within the name of the owning entity (value of the NAME attribute of OWNING_ENTITY element). The value for language shall follow the HTTP/1.1 Specification description of Language Tags ftp://ftp.isi.edu/in-notes/rfc2616.txt. The name and version of the specification document that the registry was created for The version of the cim schema that the registry is dependent on The name of the entity that maintains and owns the message registry and the name of the group within the owning organization to contact about the message registry. For registries owned by the DMTF, the NAME must be 'DMTF' and the CONTACT_GROUP shall be the name of the official working group that has developed the registry. The NAME must be unique within all message registries since it is used as a scoping entity for other elements. If the NAME and CONTACT_GROUP are the same, the CONTACT_GROUP is not necessary. These attributes shall be used to construct the CIM OwningEntity property value in the form "@NAME@CONTACT_GROUP". The name, email, and organization of the message registry editor(s). The list of messages defined in this registry The normative expression of what values define the message. The description provides general guidelines for the purpose of the standard message, what information it is designed to convey, and its general usage. A profile may further define or constraint the usage of the message within the domain of the profile. There can be at most two FIXED_MESSAGE_INSTANCE_VALUES elements defined, one for an ERROR and one for an ALERT. There may be no FIXED_MESSAGE_INSTANCE_VALUES elements defined. A moniker used as a short description of the message. The name does not have to unique for all message, only the message ID does. But the name proves useful for any discussion about the message. For this purpose, the name should be as unique and descriptive as possible. For example, "HTTP Header malformed in POST Operation" is a better name that simply "protocol error". The MESSAGE_ID consists of a PREFIX and SEQUENCE_NUMBER attribute that shall be used as a unique identifier for the message amongst all message registries owned by a particular OWNING_ENTITY. If the OWNING_ENTITY NAME attribute is DMTF, then the PREFIX should be the abbreviation of the official working group name that has developed the message registry. The attributes shall be used to construct the CIM MessageID property value by concatenating the PREFIXand SEQUENCE_NUMBER attribute values as they are specified. It is recommended that the SEQUENCE_NUMBER is padded with leading zeros to a total length of at least four digits. The description provides general guidelines for the purpose of the standard message, what information it is designed to convey, and its general usage. A profile may further define or constraint the usage of the message within the domain of the profile. The combination of the static element values and the dynamic element values shall be used to produce the CIM Message string property. The elements shall be used to create the CIM Message property in the order that they appear in the MESSAGE_COMPONENTS entity, top to bottom. See the description of each static and dynamic element type for more information about how to construct each element. Dynamic elements shall contain not translated text because it would make localization of the message registry difficult. Each dynamic element is an element in the CIM MessageArguments string array. The elements shall be used to create the CIM MessageArguments string array property in the order that they appear in the MESSAGE_COMPONENTS entity, top to bottom. The value of this element changes based on circumstances. There shall be only one dynamic element of a particular name for a particular message. It is not recommended that the dynamic element contain translatable text because it would make localization of the message registry difficult. Used to indicate a CIM Schema property that must be used as the source for the value of the dynamic element. The format shall be CIM Class.Property for example CIM_Fan.ElementName The DATATYPE defines what data type the element of the MessageArgument property shall be coercible into. Even though the MessageArgument elements of type string, this attribute constrains the contents of that string. For example, if the DATATYPE is set to 'sint8', the value of the dynamic element or the value of one of the element of the dynamic element if that dynamic element is an array shall be a positive integer of appropriate number of digits. Another example, if the DATATYPE is set to 'reference', then the value of the dynamic element ought to contain the appropriate elements for a reference property. This attribute defines whether this dynamic element is itself an array. The type of each element of this array is of the type defined in the DATATYPE attribute. The value of this dynamic element within the MessageArgument array shall contain elements delimited by commas, The presentation of the value of this dynamic element within the Message property should to have the elements of the dynamic element delimited by commas and surrounded by curly brackets. This attribute defines whether this dynamic element should appear in the Message property. If the attribute is false, the purpose of this dynamic element is to convey additional details about the message that are not intended for the end user reading the message. This element is used to have the same dynamic element repeated in the MessageArguments property again after this dynamic element is used in this message once. Simply, this element refers to the previously defined dynamic element by referring to the NAME attribute so that it does not have to be redefined. This element has the same characteristics as the dynamic element of the same, including whether it is expected in the Message property. A possible value defines what values a DYMANIC_ELEMENT can take on. Each static element may be used literally along with the DYNAMIC_ELEMENTS to create the CIM Message string property or different static text may be used as long as the same meaning is conveyed. The value of this element does not change based on circumstances. This entity lists the properties of the message CIM instance that must take on a particular value and have a particular, specified meaning. The messages can have other properties set, but this message declaration makes no assertions as to their nature. The type is used to define the class type of the instances whose values are being constrained. ERROR means that the FIXED_MESSAGE_INSTANCE_VALUES element is constraining CIM_Error properties. ALERT means that the FIXED_MESSAGE_INSTANCE_VALUES element is constraining CIM_AlertIndication properties. Because there is a FIXED_MESSAGE_INSTANCE_VALUES of one type does not mean that messages of another type can not be produced. Such a situation simply means that no assertions are made about message properties of the unspecified type. PERCEIVED_SEVERITY is one of the values of the PerceivedSeverity property of CIM_AlertIndication. When it appears in a Message Registry, PERCEIVED_SEVERITY is advisory. Implementations may use another value in instances of CIM_AlertIndication.