DMTF
This message registry defines messages that represent standard text fragments for use by management profiles defined
using DSP8028 ("machine readable profiles"). It is therefore called a "text registry". This text registry allows for
centralizing text fragments used commonly in management profiles owned by DMTF.
Other standards organizations or vendors owning management profiles may choose to define their own text registries for
management profiles.
For all messages, the expanded message text (that is, the combination of static and dynamic elements as one string) is
interpreted as XHTML with MRP extensions, as defined in DSP8028 for the "XHTMLWithLinks" element. Any relative URLs
specifying resolvable locations are interpreted as being relative to the profile (that is, the MRP XML file) specifying
the message.
Management profiles can easily be transferred between organizations, if the following rules are satisfied by the text
registries they use:
(1) The message prefix (PREFIX attribute) for all messages in the text registry is "MRPT".
(2) Messages with sequence numbers in the range of 0000..4999 are compatible to those in this text registry (DSP8008),
by having the same sequence number (SEQUENCE_NUMBER attribute), same name (NAME attribute), same meaning, and same
dynamic elements.
(3) Messages with sequence numbers in the range of 5000..9999 do not need to be compatible to those in this text
registry (DSP8008).
The messages in this text registry are uniquely identifiable in two ways:
(1) by message ID (concatenation of PREFIX and SEQUENCE_NUMBER attributes)
(2) by message name (NAME attribute)
Machine readable profiles (MRP) use the message name to identify messages in this text registry.
For this reason, the values of the NAME attribute (of the MESSAGE element) shall be unique within the registry.
Copyright text.
Copyright ©
Year or range of years including any separators between them (usually the minus/dash), to which the copyright applies. Any year shall be represented as a (4-digit) decimal number using the proleptic Gregorian calendar, as defined in section 3.2.1, "The Gregorian calendar", of ISO 8601:2004.
Examples: "2011" or "2009-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.
The logo of the organization owning the profile, for displaying on the title page of the profile document.
Introduction text for the "Acknowledgments" clause, as defined in DSP8052 for the /DocumentControlInformation/Acknowledgments/Introduction element.
DMTF acknowledges the following individuals for their contributions to this document:
Text defining typographical conventions as a part of the document conventions, as defined in DSP8050 for the /DocumentControlInformation/Conventions element.
The following typographical conventions are used in this document:
Document titles are marked in italics.
Important terms that are used for the first time are marked in italics.
Terms include a link to the term definition in the "Terms and definitions" clause, enabling easy navigation to the term definition.
Text defining ABNF usage conventions as a part of the document conventions, as defined in DSP8050 for the /DocumentControlInformation/Conventions element.
Format definitions in this document are specified using ABNF (see RFC5234), with the following deviations:
Literal strings are to be interpreted as case-sensitive Unicode characters, as opposed to the definition in RFC5234 that interprets literal strings as case-insensitive US-ASCII characters.
ABNF rules are in monospaced font.
Text defining OCL usage conventions as a part of the document conventions, as defined in DSP8050 for the /DocumentControlInformation/Conventions element.
Constraints in this document are specified using OCL (see OCL 2.0).
OCL statements are in monospaced font.
Text defining conventions for deprecated material as a part of the document conventions, as defined in DSP8050 for the /DocumentControlInformation/Conventions element.
Deprecated material is not recommended for use in new development efforts. Existing and new implementations may use this material, but they shall move to the favored approach as soon as possible. CIM services shall implement any deprecated elements as required by this document in order to achieve backwards compatibility. Although CIM clients may use deprecated elements, they are directed to use the favored elements instead.
Deprecated material should contain references to the last published version that included the deprecated material as normative material and to a description of the favored approach.
The following typographical convention indicates deprecated material:
DEPRECATED
Deprecated material appears here.
DEPRECATED
In places where this typographical convention cannot be used (for example, tables or figures), the "DEPRECATED" label is used alone.
Text defining conventions for experimental material as a part of the document conventions, as defined in DSP8050 for the /DocumentControlInformation/Conventions element.
Experimental material has yet to receive sufficient review to satisfy the adoption requirements set forth by the DMTF. Experimental material is included in this document as an aid to implementers who are interested in likely future developments. Experimental material may change as implementation experience is gained. It is likely that experimental material will be included in an upcoming revision of the document. Until that time, experimental material is purely informational.
The following typographical convention indicates experimental material:
EXPERIMENTAL
Experimental material appears here.
EXPERIMENTAL
In places where this typographical convention cannot be used (for example, tables or figures), the "EXPERIMENTAL" label is used alone.
Introduction text for the "Normative references" clause, as defined in DSP8052 for the /NormativeReferences/Introduction element.
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.
Introduction text for the "Bibliography" annex, as defined in DSP8052 for the /Bibliography/Introduction element.
The following documents may provide additional background.
Introduction text for the "Terms and definitions" clause, as defined in DSP8051 for the /TermsAndDefinitions/Introduction element.
In this document, some terms have a specific meaning beyond the normal English meaning.
Those terms are defined in this clause.
Text that defines provisional keywords (e.g., "shall") by referencing their definition elsewhere, as defined in DSP8051 for the /TermsAndDefinitions/TermReference element.
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.
Text that defines terms for document clauses (e.g., "clause") by referencing their definition elsewhere, as defined in DSP8051 for the /TermsAndDefinitions/TermReference element.
The terms "clause", "subclause", "paragraph", "annex" in this document are to be interpreted as described in
ISO/IEC Directives, Part2,
Clause 5.
Text that defines terms for normative and informative by referencing their definition elsewhere, as defined in DSP8051 for the /TermsAndDefinitions/TermReference element.
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.
Introduction text for the "Symbols and abbreviations" clause, as defined in DSP8051 for the /SymbolsAndAbbreviations/Introduction element.
Text for the "Foreword" clause, as defined in DSP8050 for
the /DocumentControlInformation/Foreword element.
This document was prepared by the DMTF
Name of the DMTF working group that prepared the profile, for example "Architecture Working Group".
If more than one working group is to be listed, this text fragment cannot be used.
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.