This document defines an XML schema for representing management profiles as defined in
DSP1001 version 1.1. XML instance documents using this XML schema represent DMTF management profiles in a
"machine-readable" form. Therefore, such XML instance documents are called "machine readable profiles" (MRPs).
This XML schema imports several other XML schemas. MRP XML files need to declare the
namespaces of these imported XML schemas, but they do not need to specify any schema locations other
than the schema location of this XML schema (DSP8028).
As usual in XML, the choice of the namespace prefix in machine readable profiles is free. The set of
namespace prefixes used in the following namespace declarations is a recommendation. The set of
XML namespace URIs used in the following namespace declarations shall be specified as stated:
xmlns:mrp="http://schemas.dmtf.org/wbem/mgmtprofile/1"
xmlns:xhtml="http://www.w3.org/1999/xhtml"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
As usual in XML schema, the namespace prefixes (e.g. "mrp:") defined in these declarations can be chosen freely;
however, it is recommended to use the prefixes stated above.
It is recommended to define the XHTML namespace as the default namespace:
xmlns="http://www.w3.org/1999/xhtml"
This XML schema uses the "Venetian Blind" design pattern for the most part. In that pattern, only the XML
elements intended to be used as root elements are declared as global elements in the XML schema, and all relevant XML
types are declared as global types. There are a few exceptional cases where global elements are defined because XML
schema requires it (for example, when XSD substitution groups are used).
This XML schema maintains compatibility with respect to its XML instance documents as follows: An updated minor version
of the XML schema (for example, "m.n+1.*") shall successfully validate XML instance documents that validated successfully using
the original version of the XML schema (for example, "m.n.*"). An XML instance document that successfully validates against an
updated minor version of the XML schema may or may not validate against the original version of the XML schema. In
other words, the XML schema may introduce additional functionality as long as it does not break existing XML instance
documents.
This approach allows tools that process MRP XML files to add support for version m.n+1 by upgrading to that version
of the MRP XML schema and still process MRP XML files from an MRP XML schema version m.n with the new
XML schema. In order for such tools to test whether the MRP XML file uses a version that is too new for the tool, the
value of the "version" attribute of the "ProfileSpecification" top-level element can be inspected.
A management profile specification as defined in DSP1001 1.1, in machine readable format.
This element shall be the only root (that is, top-level) element in MRP XML files.
Internal type for a management profile specification.
A profile within the subject profile specification, as defined in DSP1001 1.1.
This element is not allowed for glossary specifications. This element is required at least once
for profile specifications.
The value of this attribute shall specify the major and minor version of DSP8028 used
by the MRP XML file.
Internal type for a profile within a profile specification.
Profile attributes of the subject profile, as defined in DSP1001 1.1.
Synopsis of the subject profile, as defined in DSP1001 1.1. The synopsis should
be suitable to be repeated outside of the profile as a short description of what the profile
provides. The XHTML shall not contain heading elements.
A description of the management domain implemented by the subject profile,
providing an overview of the model. It should describe how the classes of the profile relate to
the management domain and should use class diagrams (embedded as images). The description shall
not include normative documentation. The XHTML may contain heading elements; if it does, the
top-most heading level shall be h2 and the value of the "id" attribute of any such heading
elements (which are optional but needed for linking to the heading subclause) shall start with
"H-" and shall be unique across the profile specification.
The related profiles of the subject profile. For details about related profiles,
see DSP1001. This element can be used as a top level element in MRP include files.
The message registries that are used in the subject profile. For details about
using message registries in profiles, see DSP1001. The set of message registries shall consist
of those registries from which messages are referenced in the subject profile. This element can
be used as a top level element in MRP include files.
The metric registries that are used in the subject profile. For details about
using metric registries in profiles, see DSP1001. The set of metric registries shall consist of
those registries from which metrics are referenced in the subject profile. This element can be
used as a top level element in MRP include files.
The features defined in the subject profile. For details about features in
profiles, see DSP1001. This element can be used as a top level element in MRP include files.
The element requirements defined by the subject profile. For details about
element requirements in profiles, see DSP1001. This element can be used as a top level element
in MRP include files.
ref-doc: The use cases and state descriptions of the subject profile. This
element can be used as a top level element in MRP include files.
The actors defined by the subject profile. This set of actors shall represent
the actors referenced by the use cases defined in the subject profile. This element can be used
as a top level element in MRP include files.
Registered name of the subject profile, as defined in DSP1001 as "registered profile
name". The registered name of the profile should not end with the word "Profile". If the subject
profile document defines only one profile, the document title shall be the registered profile name,
followed by the word "Profile".
Registered organization of the subject profile, as defined in DSP1001 as "registered
profile organization". If the subject profile document defines only one profile, the organization
owning the document shall be the registered organization of the profile.
Registered version of the subject profile, as defined in DSP1001 as "registered
profile version". The value of this attribute shall be the full version (that is, major, minor and
update version identifiers) without draft level. Example: "1.1.0". If the subject profile document
defines only one profile, the version of the document shall be the registered version of the
profile.
Internal type for a name of an adaptation.
Internal type for profile attributes of a profile.
The central class adaptation of the profile. For details about the central class
adaptation of a profile, see DSP1001.
The scoping path of the profile, as defined in DSP1001. The direction of the
scoping path shall be from the central class adaptation to the scoping class adaptation. The
central and scoping class adaptations shall not be included in the specified child elements.
Autonomous profiles shall not specify this element; component profiles shall specify this
element.
An association class adaptation in the scoping path of the profile.
An associated class adaptation in the scoping path of the
profile. This will typically (but not necessarily) be the adaptation of an
ordinary class.
An association class adaptation in the scoping path of the
profile.
The scoping class adaptation of the profile. For details about the scoping class
adaptation of a profile, see DSP1001.
The CIM schemas used by the subject profile. Typically, that would be the DMTF
CIM schema only. The set of CIM schemas shall define any classes adapted by the class
adaptations defined in the subject profile.
A reference to a CIM schema.
Type of the profile (for example, Autonomous or Component).
Indicates whether the profile is abstract.
Internal type for an enumeration of possible profile types (e.g. Autonomous, Component).
Internal type for an enumeration of possible generic operations for which operation
requirements can be defined on class adaptations. Note, these names have changed in DSP0223 1.0.2; this list
reflects the new names.
Internal type for a reference to a CIM schema.
Organization owning the referenced CIM schema, as defined in DSP1001. For schemas
owned by DMTF, the value shall be "DMTF".
Name of the referenced CIM schema, as defined in DSP1001. The CIM schema name appears
as the schema prefix in the class name (for example, "CIM" or "PRS").
Version of the referenced CIM schema. As defined in DSP1001, the specified schema
version does not need to be the earliest version of the schema that meets the requirements of the
profile. The value of this attribute shall specify the major and minor version identifier, and it
may specify the update version identifier to explicitly require a minimum update version. In any
case, the latest published update version with the specified major and minor version identifier is
considered to be referenced.
Indicator for whether the experimental (if true) or final (if false) version of the
CIM schema is referenced. If an experimental version of the CIM schema is referenced, profile
documents owned by DMTF cannot have a status of "DMTF Draft Standard" or "DMTF Standard".
Internal type for a related profile.
Requirement for implementing the related profile. This element shall be
present only if the "relationship" attribute has the value "Usage".
Description of the profile relationship, if needed. The XHTML shall not
contain heading elements.
The name of the profile reference, as defined in DSP1001. The profile
reference name needs to be unique within the subject profile, as defined in DSP1001.
A reference to the normative references entry for the related profile, by
means of its "name" attribute. This attribute is required for all related profiles but the
subject profile; it is not permitted for the subject profile.
Type of relationship to the related profile.
Internal type for an enumeration of possible kinds of profile relationships.
Indicates that the subject profile uses the referenced profile. The referenced
profile is implemented in context of the subject profile according to the requirement level
specified on the profile reference.
Indicates that the subject profile is derived from (specializes) the referenced
base profile. Defining more than one base profile is deprecated in DSP1001 and will cause a
deprecation statement to appear in the HTML output created by DSP8029.
Internal type for a reference to another profile.
Registered name of the referenced profile.
Registered organization of the referenced profile.
Registered version of the referenced profile. The value of this attribute shall
specify the major and minor version identifier, it may specify the update version identifier to
explicitly require a minimum update version, and it shall not specify a draft level. In any case,
the latest published update version with the specified major and minor version identifier is
considered to be referenced.
Internal type for a feature definition in the subject profile.
A description of what the feature provides to clients, if implemented. This
should be described in terms of the management domain modeled by the profile. The XHTML may
contain heading elements; if it does, the top-most heading level shall be h4 and the value of
the "id" attribute of any such heading elements (which is optional, but needed for linking to
the heading subclause) shall start with "H-" and shall be unique across the profile
specification.
Requirement for implementing the feature, if the subject profile gets
implemented. Only Conditional, ConditionalExclusive, and Optional are allowed as requirement
levels, as defined in DSP1001.
Definition of the feature granularity, that is, the granularity by which the
feature is available to clients. The possible granularities are per instance and per profile, by
means of specifying the respective child elements. For details on feature granularities, see
DSP1001.
Definition of a feature discovery mechanism, that is, how clients can determine
whether or not the feature is available to them, taking into account the granularity of the
feature. If this element is not specified, availability of the feature cannot be discovered
(other than trying the functionality provided by the feature).
The name of the feature, as defined in DSP1001. The feature name needs to be unique
within its defining profile.
Internal type for a reference to a feature defined in the subject profile or another
profile.
References the feature by specifying the feature name.
Identifies the profile that defines the referenced feature by specifying the name of
the profile reference in the subject profile (that is, the value of the "refName" attribute of its
"mrp:RelatedProfile" element). If this attribute is omitted, the feature is defined in the subject
profile.
Internal type for a feature granularity.
Usage of this element indicates that the feature granularity is per instance of
the class adaptation specified by this element.
Name of the class adaptation for the per-instance feature granularity.
Usage of this element indicates that the feature granularity is per
implementation of the subject profile.
Internal type for an instance traversal path.
An association class adaptation in the instance traversal path. An
association traversal operation that follows the instance traversal path is assumed to be
invoked with filters on the association class name, target class name, source role name, and
target role name. Because these filter parameters are implied by the definition of the
association class adaptation, they are not specified here.
An instance traversal path defined in another profile that defines the
traversal between two class adaptations defined in the subject profile. The class adaptation
referenced by the previous "mrp:AssociationClassAdaptation" element (that is, just before
this "mrp:ProfileDefinedTraversalPath" element) shall be based on the class adaptation
referenced in the "sourceAdaptationName" attribute. The class adaptation referenced by the
next "mrp:AssociationClassAdaptation" element (that is, just after this
"mrp:ProfileDefinedTraversalPath" element) shall be based on the class adaptation referenced
in the "targetAdaptationName" attribute.
Identifies the profile that defines the traversal path, by specifying
the name of the profile reference in the subject profile (that is, the value of the
"refName" attribute of its "mrp:RelatedProfile" element).
Identifies the class adaptation in the referenced profile that is the
source of the traversal path.
Identifies the class adaptation in the referenced profile that is the
target of the traversal path.
An associated class adaptation in the instance traversal path. This is typically
(but not necessarily) an ordinary class adaptation.
Internal type for a profile reference path.
Each element represents one referenced profile. The sequence of elements
represents an indirect reference to a target profile, through intermediate profiles.
The registered name of the referenced profile.
The registered organization of the referenced profile.
Internal type for a constraint.
OCL constraint. The allowable constraint types and the OCL context (that is, what
"self" refers to) are defined in the description of the parent element of this element.
Internal type for an enumeration of the possible types of a constraint.
An OCL definition constraint, as defined in DSP0004 for the ClassConstraint
qualifier. This is not a constraint; instead, it is a building block for later usage by an OCL
constraint. This type shall be used only for OCL constraints.
The constraint describes rules about the existance of one or more CIM instances
that are always valid (that is, invariants). For OCL constraints, the OCL expression shall be an
OCL invariant constraint, as defined in DSP0004 for the ClassConstraint qualifier.
The constraint describes rules for one or more property values that are always
valid (that is, invariants). For OCL constraints, the OCL expression shall be an OCL invariant
constraint, as defined in DSP0004 for the ClassConstraint qualifier.
The constraint describes an invariant that is not covered by other enumerations
describing invariants. For OCL constraints, the OCL expression shall be an OCL invariant
constraint, as defined in DSP0004 for the ClassConstraint qualifier.
The constraint defines how to initialize a property value. For OCL constraints,
the OCL expression shall be an OCL initialization constraint for property values, as defined in
DSP0004 for the PropertyConstraint qualifier.
The constraint determines the value of a property from other information (for
example, the values of other properties). For OCL constraints, the OCL expression shall be an
OCL derivation constraint for property values, as defined in DSP0004 for the PropertyConstraint
qualifier.
The constraint describes method preconditions. (Preconditions need to be valid in
order for the method to succeed.) For OCL constraints, the OCL expression shall be an OCL
precondition constraint, as defined in DSP0004 for the MethodConstraint qualifier.
The constraint describes method postconditions. (Postconditions are guaranteed to
be valid by the method after it has succeeded.) For OCL constraints, the OCL expression shall be
an OCL postcondition constraint, as defined in DSP0004 for the MethodConstraint qualifier.
The constraint describes the method body (that is, the behavior as seen from the
outside when executing succeeds). For OCL constraints, the OCL expression shall be an OCL body
constraint, as defined in DSP0004 for the MethodConstraint qualifier.
The constraint is a feature implementation constraint.
Any case not covered by the other cases.
Internal type for an OCL expression.
The body text (that is, the actual OCL expression) of an OCL constraint, starting
with the constraint type (for example, "inv: self...."). The OCL text in this element needs to
be formatted with line breaks and should not exceed 80 characters per line; a presentation of
this OCL text for human consumption should wrap longer lines. The allowable OCL constraint types
and the OCL context (that is, what "self" refers to) is defined on the parent element of this
"mrp:Body" element. Additional OCL functions are available but not described in this XML schema
definition.
Informational description of the OCL expression defined in the OCL body text. In
case of semantic differences between this description and the OCL body text, the OCL body text
overrules this description. The XHTML shall not contain heading elements.
Internal type for defining a class adaptation in the subject profile.
Defines a base adaptation for this class adaptation. Typically, the base
adaptations themselves are defined in another profile.
Requirement for implementing this class adaptation, if the subject profile gets
implemented. This element is required if the implementation type of the class adaptation (that
is, the value of its "implementationType" attribute) is "Instantiated" or "Indication";
otherwise, this element is prohibited.
Specifying this element indicates the requirement that a concrete subclass of
the adapted abstract schema class needs to be implemented. This element may be specified only on
adaptations that adapt an abstract schema class. A typical use case for this is the
CIM_Component class in the CIM Schema.
A description of additional requirements and constraints, beyond the
general requirement that a concrete subclass of the adapted abstract schema class
needs to be implemented.
Short description of what type of managed object (in the managed environment) is
modeled by this class adaptation. The model description should determine which managed object
type is modeled by the class adaptation, enabling the implementation to identify the managed
objects that are to be represented as adaptation instances. The model description should be
limited to one sentence. The XHTML shall not contain heading elements. Example for a
VirtualNetworkPort adaptation: "This adaptation models a network interface of an active virtual
system." This includes any kind of network interface on virtual systems, but it scopes the
adaptation to active virtual systems, excluding virtual network interfaces in virtual system
configurations or definitions. A model description should be specified with any class
adaptation. If a model description is specified, it supersedes any implied model description and
shall not violate the semantics of the implied model description. If a model description is not
specified, it is implied as follows: If the adaptation has one or more direct base adaptations,
its implied model description is the combination of the (specified or implied) model
descriptions of all of its direct base adaptations. If the adaptation has no base adaptations,
its implied model description is the model description of the adapted class from the underlying
schema. If the adapted class does not specify a model description, the adaptation has no model
description. Model descriptions are not propagated along the schema class inheritance hierarchy,
because that would result in model descriptions that are too generic.
Description of anything about this class adaptation that is not covered by other
elements. A model description of what managed object types in the managed environment are
modeled by the class adaptation should be stated in the "mrp:ModelDescription" sibling element.
The XHTML may contain heading elements; if it does, the top-most heading level shall be h5 and
the value of the "id" attribute of any such heading elements (which are optional but needed for
linking to the heading subclause) shall start with "H-" and shall be unique across the profile
specification.
Description of any instance requirements for this class adaptation. An instance
requirement is a requirement for the implementation to expose instances, typically based on
managed objects in the managed environment. By default, which instances are exposed depends on
the implementation. The XHTML may contain heading elements; if it does, the top-most heading
level shall be h5 and the value of the "id" attribute of any such heading elements (which are
optional but needed for linking to the heading subclause) shall start with "H-" and shall be
unique across the profile specification.
A constraint for instances of this class adaptation. For OCL constraints, the
allowable OCL constraint types and the OCL context are defined in the description of the
ClassConstraint qualifier in DSP0004.
A property requirement, that is, requirements on a property (including
references) exposed by the class adapted by this class adaptation. For details on property
requirements, see DSP1001.
A method requirement, that is, requirements on an (extrinsic) method exposed by
the class adapted by this class adaptation. For details on method requirements, see DSP1001.
An operation requirement, that is requirements on an (intrinsic) operation
related to the class adapted by this class adaptation. For details on operation requirements,
see DSP1001. See the "name" attribute for a list of possible operations. Association traversal
operations shall be specified only on the adaptation of the class of the source instance of the
traversal. For bidirectional traversals, this means the traversal operations need to be
specified on the adaptations of both associated classes.
Name of the class adaptation, as defined in DSP1001. The class adaptation name needs
to be unique within its defining profile.
Name of the class that is adapted, including its schema prefix. The schema prefix of
the class name allows identifying the "mrp:SchemaReference" element referencing the CIM schema that
defines the class that is adapted.
Implementation type of the class adaptation. For details, see the enumeration
values.
Indicates that the class adaptation adapts an association class. This is a
duplication of information from the underlying CIM schema, for convenience and expressiveness in the
profile. The usage of this attribute shall be consistent with the adapted class defined in the
underlying CIM schema.
A class adaptation defined by the subject profile. For details on class adaptations, see
DSP1001.
Internal type for an enumeration of possible implementation types of a class adaptation.
Instances of the class implemented according to the class adaptation are
instantiated on their own, that is, they can be referenced with an instance path by a client.
Instances of the class implemented according to the class adaptation are embedded
into an embedding element; they cannot directly be referenced with an instance path by a client.
Embedding elements can be method parameters, method return values, properties, or operation
elements.
The implementation type of the class adaptation is defined by its derived
adaptations.
Instances of the indication non-exception class implemented according to the
class adaptation are embedded as elements in indication delivery operations. Indication
non-exception classes are classes that have effective qualifier values of Indication=True and
Exception=False.
Instances of the exception class implemented according to the class adaptation
are embedded into operation exceptions (typically delivered as fault responses of operations).
Exception classes are classes that have effective qualifier values of Indication=True and
Exception=True.
Internal type for a reference to a class adaptation defined in the subject profile or in
another profile.
Name of the referenced class adaptation. Can be a class adaptation name
(for DSP1001 1.1 compliant profiles), or a schema class name optionally followed by text in
parenthesis (for DSP1001 1.0 compliant profiles).
Identifies the profile that defines the referenced class adaptation, by specifying
the name of the profile reference in the subject profile (that is, the value of the "refName"
attribute of its "mrp:RelatedProfile" element). If this attribute is omitted, the subject profile
defines the class adaptation.
Internal type for a base adaptation of a class adaptation.
Requirement for applying the requirements of the base adaptation, if the
derived adaptation gets implemented.
A metric requirement on a metric related base adaptation. Each occurrence
of this element represents one metric requirement, and subsequently a requirement for
implementing one specific metric. For details on metric requirements, see DSP1001. This
element is only allowed on base adaptations referencing the DSP1053::MonitoredElement or
DSP1053::BaseMetricDefinition adaptations or an adaptation derived from them (directly
or indirectly). DSP1053 details how a metric requirement is transformed into
requirements on other adaptations, depending on whether DSP1053::MonitoredElement or
DSP1053::BaseMetricDefinition is used as a base adaptation.
An alert message requirement on an alert indication related base
adaptation. Each occurrence of this element represents one alert message requirement,
and subsequently a requirement for implementing one specific alert indication. For
details on alert message requirements, see DSP1001. This element is only allowed on base
adaptations referencing the DSP1054::AlertIndication adaptation or an adaptation derived
from it (directly or indirectly). The referenced message shall be an alert message (that
is, the message registry defines fixed instance properties with type "ALERT"). DSP1054
1.2 details how an alert message requirement is transformed into requirements on other
adaptations.
Internal type for defining requirements on a property (including references) of an
adapted class.
Requirement for implementing the property when retrieving instances containing
the property. This requirement applies only if the class adaptation that defines this property
requirement gets implemented.
Short description of which attribute of the managed object (in the managed
environment) is modeled by this property. The model description should determine which attribute
is modeled by the property, enabling the implementation to identify the attributes that are to
be represented as properties. The model description should be limited to one sentence. The XHTML
shall not contain heading elements. Example for a IPv4Address property of an EthernetPort
adaptation: "This property models the currently used IPv4 address of the network interface." A
model description should be specified with any property. If a model description is specified, it
supersedes any implied model description and shall not violate the semantics of the implied
model description. If a model description is not specified, it is implied as follows: If the
adaptation that defines the property has one or more direct base adaptations, the implied model
description of the property is the combination of the (specified or implied) model descriptions
of that property in all of its direct base adaptations. If the adaptation has no base
adaptations, the implied model description of the property is the model description of the
property exposed by the adapted class from the underlying schema. If the property exposed by the
adapted class does not specify a model description for the property, the property has no model
description. Properties exposed by a schema class include those inherited from superclasses.
Description of anything about this property that is not covered by other
elements. A model description of the property should be stated in the "mrp:ModelDescription"
sibling element. The XHTML shall not contain heading elements.
A constraint on the property. For OCL constraints, the allowable OCL constraint
types and the OCL context are defined in the description of the PropertyConstraint qualifier in
DSP0004.
Requirements for implementing client initialization of the property value on an
instance, through any operation or method that creates an instance by taking an initial value
for this property as input (for example, CreateInstance, or creation methods that take embedded
instances as input). The requirements defined by this element only apply if such an operation or
method is implemented. If this element is not specified, client initialization of the property
value on an instance is optional; if implemented, any values may be accepted.
Requirement level for implementing client initialization of this
property.
Description of anything about client modification of this property
that is not covered by other elements. The XHTML shall not contain heading elements.
Each element defines a value requirement, which is a requirement for
accepting a particular value when supplied as input; only values in the set of
allowable values for this property in any instances may be specified using this
element. The default requirement level for unspecified values (in the allowable set)
is "Optional". Unless otherwise specified (for example, in the "Description" child
element), the implementation needs to implement the semantics of the value.
Requirements for implementing client modification of the property value on an
instance, through any operation or method that modifies the instance by taking a new value for
this property as input (for example, ModifyInstance, or modifying methods that take embedded
instances as input). The requirements defined by this element only apply if such an operation or
method is implemented. If this element is not specified, client modification of the property
value on an instance is optional; if implemented, any values may be accepted.
Requirement level for implementing client modification of this
property.
Description of anything about client initialization of this property
that is not covered by other elements. The XHTML shall not contain heading elements.
Each element defines a value requirement, that is, a requirement for
accepting a particular value when supplied as input; only values in the set of
allowable values for this property in any instances may be specified using this
element. The default requirement level for unspecified values (in the allowable set)
is "Optional". Unless otherwise specified (for example, in the "Description" child
element), the implementation needs to implement the semantics of the value.
Name of the property.
Additional constraints on properties that are CIM references.
Additional constraints on properties that are embedded instances.
Null allowance.
Internal type for an abstract base type for operation requirements.
Requirement for implementing the operation, if the class adaptation that defines
this operation requirement gets implemented.
Short description of what functionality of the managed object (in the managed
environment) is modeled by this operation. The model description should determine what
functionality is modeled by the operation, enabling the implementation to identify the
functionality that is to be performed in the operation. The model description should be limited
to one sentence. The XHTML shall not contain heading elements. A model description for an
operation defined on an adaptation is implied by the definition of the operation in the
underlying operation specification. A model description using this element is only needed if
that implied model description needs to be refined. If a model description is specified, it
supersedes any implied model description and shall not violate the semantics of the implied
model description. If a model description is not specified, it is implied as follows: If the
adaptation that defines the operation has one or more direct base adaptations, the implied model
description of the operation is the combination of the (specified or implied) model descriptions
of that operation in all of its direct base adaptations. If the adaptation has no base
adaptations, the implied model description of the operation is the model description of the
operation as defined in the underlying operation specification.
Description of anything about this operation that is not covered by other
elements. A model description of the operation should be stated in the "mrp:ModelDescription"
sibling element. The XHTML shall not contain heading elements.
A constraint for the operation, beyond those defined by the operations
specification, any base adaptations, and any sibling elements of this element. For OCL
constraints, the allowable OCL constraint types and the OCL context are defined in the
description of the MethodConstraint qualifier in DSP0004, where the operation defined here takes
on the role of the method in that description.
An error reporting requirement for the operation, beyond those defined by the
operations specification, any base adaptations, and any sibling elements of this element. For
details, see the description of error reporting requirements in DSP1001.
This element determines the set of association adaptations to which the operation
requirement defined by the parent "mrp:Operation" element applies. This element may be specified
only on association traversal operations. Association traversal operations may be specified only
on adaptations referenced by the traversed association adaptations. The set of association
adaptations to which the operation requirement applies is the set of specified occurrences of
this element; if no occurrence of this element has been specified, that set of association
adaptations defaults to the set of association adaptations that reference the adaptation on
which the operation requirement is specified, minus the set of adaptations specified in sibling
"mrp:Operation" elements for the same operation. See DSP1001 for more details.
Name of the association adaptation.
Internal type for an operation requirement on a class adaptation.
Name of the operation, using the names defined in DSP0223.
Internal type for a method requirement on a class adaptation.
Requirement for implementing the method, if the class adaptation that defines
this method requirement gets implemented.
Short description of what functionality of the managed object (in the managed
environment) is modeled by this method. The model description should determine what
functionality is modeled by the method, enabling the implementation to identify the
functionality that is to be performed in the method. The model description should be limited to
one sentence. The XHTML shall not contain heading elements. A model description should be
specified with any method. If a model description is specified, it supersedes any implied model
description and shall not violate the semantics of the implied model description. If a model
description is not specified, it is implied as follows: If the adaptation that defines the
method has one or more direct base adaptations, the implied model description of the method is
the combination of the (specified or implied) model descriptions of that method in all of its
direct base adaptations. If the adaptation has no base adaptations, the implied model
description of the method is the model description of the method exposed by the adapted class
from the underlying schema. If the method exposed by the adapted class does not specify a model
description for the method, the method has no model description. Methods exposed by a schema
class include those inherited from superclasses.
Description of anything about this method that is not covered by other elements.
A model description of the method should be stated in the "mrp:ModelDescription" sibling
element. The XHTML shall not contain heading elements.
Constraint for the method. For OCL constraints, the allowable OCL constraint
types and the OCL context are defined in the description of the MethodConstraint qualifier in
DSP0004.
Describes a parameter of the method. All parameters defined by the method need to
be specified, even parameters for which the profile does not define additional requirements.
Describes the return value of the method. Needs to be specified, even when the
profile does not define additional requirements for the return value.
Each element defines an error reporting requirement for a specific error
situation. For details, see the description of error reporting requirements in DSP1001. Error
situations not covered by these elements may also be reported, as defined by the operation
specification that is used by the subject profile or by related profiles.
Name of the method (without parentheses or parameters).
Internal type for describing a parameter of a method.
Description of the parameter from a perspective of the subject profile. The XHTML
shall not contain heading elements.
Each element defines a value requirement, that is, a requirement for accepting a
particular value when supplied as input; only values in the set of allowable values for this
input parameter may be specified using this element. The element may only be specified for input
parameters. The default requirement level for unspecified values (in the allowable set) is
"Optional". Unless otherwise specified (for example, in the "Description" child element), the
implementation needs to implement the semantics of the value.
Name of the parameter.
Additional constraints on parameters that are CIM references.
Additional constraints on parameters that are embedded instances.
Internal type for describing the return value of a method.
Description of the return value (in addition to any value definitions). The XHTML
shall not contain heading elements.
Additional constraints on return values that are embedded instances.
Internal type for a reference to a message registry or to a metric registry.
Description of the registry, if needed. The XHTML shall not contain heading
elements.
The name of the registry reference (that is, the value of the "refName" attribute of
its "mrp:Registry" element, not the name or ID of the referenced registry). For details on registry
references, see DSP1001.
The unique identifier of the referenced registry as assigned by the owning
organization. For registries comforming to DSP0228 or DSP8020, this is the value of the "ID"
attribute; the fully qualified XPATH location of the "ID" attribute in both types of registry is
"/REGISTRY/REGISTRY_DECLARATION/IDENTIFICATION/@ID".
Name of the organization that owns the referenced registry. For registries comforming
to DSP0228 or DSP8020, this is the text content of the "OWNING_ENTITY" element; the fully qualified
XPATH location of the "OWNING_ENTITY" element in both types of registry is
"/REGISTRY/REGISTRY_DECLARATION/OWNING_ENTITY".
Version of the referenced registry. The value of this attribute shall specify the
major and minor version identifier, it may specify the update version identifier to explicitly
require a minimum update version, and it shall not specify a draft level. In any case, the latest
published update version with the specified major and minor version identifier is considered to be
referenced.
A reference to the normative references entry for the registry, by means of its
"name" attribute.
Internal type for an error reporting requirement.
The error situation is reported by a sequence of standard messages. Each
message in that sequence may define a CIM status code; all CIM status codes defined in the
messages within a particular error reporting requirement shall have the same value. The
sequence of messages shall start with an operation-specific message, and each subsequent
message shall be a refinement of its previous message.
The error situation is reported by a CIM status code.
The name of the CIM status code (for example, "CIM_ERR_FAILED")
Requirement for implementing support for reporting this error situation, if the
operation or method that defines this error reporting requirement gets implemented.
Description of the error situation, if not already sufficiently defined by the
CIM status code or the set of standard messages. The XHTML shall not contain heading elements.
Internal type for a value requirement.
The value, represented as a string (for example, the value of an entry in the
"ValueMap" qualifier array).
Requirement for implementing the value. The requirement applies only if the
profile element specifying the value requirement gets implemented.
Description of the semantics of the value (in addition to underlying schema or
profiles). The XHTML shall not contain heading elements.
Internal type for an enumeration of the possible CIM status code values.
Value 1: A general error occurred that is not covered by a more specific error
code.
Value 2: Access to a CIM resource is not available to the client.
Value 3: The target namespace does not exist.
Value 4: One or more parameter values passed to the method are not valid.
Value 5: The specified class does not exist.
Value 6: The requested object cannot be found. The operation can be unsupported
on behalf of the CIM server in general or on behalf of an implementation of a management
profile.
Value 7: The requested operation is not supported on behalf of the CIM server, or
on behalf of a provided class. If the operation is supported for a provided class but is not
supported for particular instances of that class, then CIM_ERR_FAILED shall be used.
Value 8: The operation cannot be invoked on this class because it has subclasses.
Value 9: The operation cannot be invoked on this class because one or more
instances of this class exist.
Value 10: The operation cannot be invoked because the specified superclass does
not exist.
Value 11: The operation cannot be invoked because an object already exists.
Value 12: The specified property does not exist.
Value 13: The value supplied is not compatible with the type.
Value 14: The query language is not recognized or supported.
Value 15: The query is not valid for the specified query language.
Value 16: The extrinsic method cannot be invoked.
Value 17: The specified extrinsic method does not exist.
Value 20: The specified namespace is not empty.
Value 21: The enumeration identified by the specified context cannot be found, is
in a closed state, does not exist, or is otherwise invalid.
Value 22: The specified operation timeout is not supported by the CIM server.
Value 23: The Pull operation has been abandoned due to execution of a concurrent
CloseEnumeration operation on the same enumeration.
Value 24: The attempt to abandon a concurrent Pull operation on the same
enumeration failed. The concurrent Pull operation proceeds normally.
Value 25: Using a filter in the enumeration is not supported by the CIM server.
Value 26: The CIM server does not support continuation on error.
Value 27: The CIM server has failed the operation based upon exceeding server
limits.
Value 28: The CIM server is shutting down and cannot process the operation.
Internal type for an alert message requirement.
Requirement level for implementing the alert indication defined by the
alert message.
Text describing the alert message requirement. This may be a refinement
of the alert message within the context of the subject profile or other information
(such as the message title). The XHTML shall not contain heading elements.
Internal type for a reference to a message defined in a message registry.
The name of the registry reference (that is, the value of the "refName" attribute of
its "mrp:Registry" element, not the name or ID of the referenced registry) referencing the message
registry that defines this message. For details on registry references, see DSP1001.
Prefix of the message. The value shall be the value of the "PREFIX" attribute of the
referenced message in the message registry. The prefix is used together with the sequence number to
uniquely identify the message within the message registry for programmatic use.
Sequence number of the message. The value shall be the value of the "SEQUENCE_NUMBER"
attribute of the referenced message in the message registry. The attribute value shall be used
unchanged, that is, no stripping or adding of leading zeros shall happen. The sequence number is
used together with the prefix to uniquely identify the message within the message registry for
programmatic use.
Internal type for a reference to a text fragment defined in a text registry.
The name of the text registry reference (that is, the value of the "regRefName"
attribute of its "mrp:TextRegistry" element, not the name or ID of the referenced text registry)
referencing the text registry that defines the referenced text fragment.
Identifier for the text fragment within the text registry. The value shall be the
value of the "NAME" attribute of the referenced text fragment in the text registry.
Internal type for a metric requirement.
Requirement level for implementing the metric, if metrics are implemented
at all.
Text describing the metric requirement. This may be a refinement of the
metric within the context of the subject profile or other information. The XHTML shall
not contain heading elements.
Internal type for a reference to a metric defined in a metric registry.
The name of the registry reference (that is, the value of the "refName" attribute of
its "mrp:Registry" element, not the name or ID of the referenced registry) referencing the metric
registry that defines this metric. For details on registry references, see DSP1001.
Identification of the metric for programmatic use, unique within the referenced
metric registry. The value shall be the content of the "LOCALID" element of the referenced metric in
the metric registry.
Internal type for a requirement level for a profile element.
A definition of the condition for a conditional requirement.
Text for any additional description of the requirement (that is, in addition to
the condition definition). The XHTML shall not contain heading elements.
Requirement level, as defined in DSP1001.
Internal type for an enumeration of the possible values of a requirement level.
Usage of Mandatory on a profile element means that the profile element is
required to be implemented. This value may be used on all types of profile elements. For
details, see DSP1001.
Usage of Conditional on a profile element means that the profile element is
required to be implemented if the condition is satisfied, and may be implemented (as specified)
otherwise. This value may be used on all types of profile elements. For details, see DSP1001.
Usage of ConditionalExclusive on a profile element means that the profile element
is required to be implemented if the condition is satisfied, and shall not be implemented
otherwise. This value may be used on all types of profile elements. For details, see DSP1001.
Usage of Optional on a profile element means that the profile element may be
implemented (as specified). This value may be used on all types of profile elements. For
details, see DSP1001.
Usage of Prohibited on a profile element means that the profile element is not
allowed to be implemented. This value may be used only on some types of profile elements. For
details, see DSP1001.
Internal type for the definition of a condition for a "Conditional" requirement level.
An item in the logical expression of conditions.
Defines a feature implementation condition, as defined in DSP1001. The condition is
satisfied if the feature is implemented.
Defines a class adaptation implementation condition, as defined in DSP1001. The condition
is satisfied if the class adaptation is implemented.
Defines a property implementation condition. The condition
is satisfied if the property is implemented. Note that implemented properties might be Null on occasion.
Name of the property.
The name of the class adaptation that defines the property.
Default: The class adaptation defining the property.
The reference name of the profile that defines the class adaptation.
Default: The subject profile.
Defines a method implementation condition. The condition
is satisfied if the method is implemented. Implemented methods never return an error
indicating that the method is not supported.
Name of the method (without any parenthesis).
The name of the class adaptation that defines the method.
Default: The class adaptation defining the method.
The reference name of the profile that defines the class adaptation.
Default: The subject profile.
Defines a managed environment condition, as defined in DSP1001. The condition shall be
stated as plain text that describes which circumstances in the managed environment cause the condition
to be satisfied. The XHTML shall not contain heading elements.
Defines a profile implementation condition, as defined in DSP1001. The condition is
satisfied if the referenced profile is implemented in the context of the referencing profile.
References the profile that is the basis for the condition, by specifying the
profile reference name (that is, the value of the "refName" attribute of its
"mrp:RelatedProfile" element).
Logical OR operator on conditions. The expression is true if and only if one or more
operands are true. Requires two or more operands. The child elements are the operands; they may be
conditions or further logical operators on conditions.
Logical XOR operator on conditions. The expression is true if and only if one or the
other of two operands are true. Requires exactly two operands. The child elements are the operands; they
may be conditions or further logical operators on conditions.
Logical AND operator on conditions. The expression is true if and only if all operands
are true. Requires two or more operands. The child elements are the operands; they may be conditions or
further logical operators on conditions.
Logical AND operator on conditions. The expression is true if and only if the first
operand being true implies the second operand being true. Requires exactly two operands. The child
elements are the operands; they may be conditions or further logical operators on conditions.
Logical AND operator on conditions. The expression is true if and only if the operand is
false. Requires exactly two operands. The child elements are the operands; they may be conditions or
further logical operators on conditions.
Internal type for a feature discovery description.
OCL-based description of how to discover the availability of the feature to a
CIM client, taking into account the feature granularity. The OCL expression shall be an OCL
derivation constraint that evaluates to a boolean expression whose value indicates whether
the feature has been implemented. The OCL expression shall be based only on elements
observable for a CIM client. (This includes the invocation of methods.) The OCL expression
shall use methods only such that they do not modify the environment. The OCL context of the
derivation constraint (that is, what "self" refers to) is as follows: For features with
granularity "Instance", an instance of the class adaptation specified in the instance
granularity definition. For features with granularity "Profile", an instance of the class
adaptation in the subject profile that is based on the RegisteredProfile class adaptation
defined in the Profile Registration Profile (DSP1033).
Text-based description of how to discover the availability of the feature to
a CIM client, taking into account the feature granularity. This element should only be used
as a fallback solution when the sibling elements do not work (e.g. too many preconditions
that are hard to describe formally).
If set to true, this designates the preferred discovery mechanism ("mrp:Discovery"
element) out of multiple mechanisms. If only one "mrp:Discovery" element is specified for a feature,
no notion of a preferred mechanism is defined. In this case, the value of this attribute shall be
tolerated and ignored. If more than one "mrp:Discovery" element is specified for a feature, one of
them should be designated as preferred, but no more than one of them shall be designated as
preferred.
If set to true, this indicates that the reverse implication of discovering a feature
implementation cannot be made: If the feature implementation test fails, it cannot be concluded that
the feature is not implemented; it can only be concluded that it is unknown whether or not it is
implemented. If set to false (the default), the reverse implication of discovering a feature
implementation can be made: If the feature implementation test fails, it can be concluded that the
feature is not implemented.
Internal type for a use case defined in a profile.
Text that describes this use case. May include goals and other notes. Also may
include object, activity, or sequence diagrams if needed. The XHTML may contain heading
elements; if it does, the top-most heading level shall be h3 and the value of the "id" attribute
of any such heading elements (which are optional but needed for linking to the heading
subclause) shall start with "H-" and shall be unique across the profile specification.
Choice of one out of multiple mechanisms to describe the flow of use cases. At
this point, only a simple step-based description mechanism is provided. Other mechanisms are
expected to be added in the future.
A simple way to describe the flow of the use case as a sequence of steps that
represents the normal path taken by the use case.
The actors that invoke this use case. In the case where clients
act in different identifiable roles, an "mrp:Actor" element representing each
role should be specified.
Reference to the "mrp:Actor" element by using the value
of its "name" attribute.
A precondition constraint for the use case, describing the
assumptions that must hold for this use case to perform successfully. If the use
case depends on the implementation of optional profile elements defined in the
subject profile or in referenced profiles, these dependencies shall be described
as precondition constraints of the use case. For OCL constraints, the allowable
OCL constraint types and the OCL context are defined in the description of the
MethodConstraint qualifier in DSP0004, where only method preconditions are
allowed, and where the use case defined here is taken for the method in that
description.
A postcondition constraint for the use case, describing what must
hold after successfully performing the use case. For OCL constraints, the
allowable OCL constraint types and the OCL context are defined in the
description of the MethodConstraint qualifier in DSP0004, where only method
postconditions are allowed, and where the use case defined here is taken for the
method in that description.
A simple way to describe the flow of the use case as a sequence
of steps that represents the normal path taken by the use case.
A step within the use case. A step should represent a
simple, self-contained activity that completes normally. Each step
may be refined by either invoking an included use case or by a
sequence of substeps.
A name of the use case, for profile-internal and cross-profile referencing. Its value
shall be unique across the use cases defined in the subject profile, as defined in DSP1001.
Intra-profile references to use cases use the value of this attribute. Cross-profile references to
use cases refer to the profile and use the value of this attribute.
Internal type for a pre- or postcondition constraint of a use case.
Description of the constraint in prose text. A text constraint may be specified
on any type of element. The XHTML shall not contain heading elements.
Internal type for a standalone state description defined in a profile.
Text that describes this diagram and embeds a picture of the diagram. The XHTML
may contain heading elements; if it does, the top-most heading level shall be h3 and the value
of the "id" attribute of any such heading elements (which are optional but needed for linking to
the heading subclause) shall start with "H-" and shall be unique across the profile
specification.
A name of the diagram, for profile-internal referencing. Its value shall be unique
across the use cases and diagrams defined in the subject profile, as defined in DSP1001.
Intra-profile references to diagrams use the value of this attribute.
Internal type for a step within a use case.
Text that describes the expected activity of this step. The description may embed
object, activity, or sequence diagrams. By default, the next step (if any) is invoked. A step
may choose to branch to another step of the same use case; this is achieved by describing the
branch in the text and by referencing the other step by informal means. The XHTML shall not
contain heading elements.
Specifies that another use case is invoked by this step.
References the included use case by specifying the value of the
"name" attribute of its "mrp:UseCase" element.
References the profile that defines the included use case by
specifying the profile reference name (that is, the value of the "refName" attribute
of its "mrp:RelatedProfile" element). If omitted, the referenced use case is defined
in the subject profile.
A set of detail steps within this step.
Internal type for an actor in a use case.
A description of the role of the actor. The XHTML shall not contain heading
elements.
An identifier for the actor within the profile, for profile-internal referencing. Its
value shall be unique across the actors defined in the subject profile.
Internal attribute group for specifying constraints on CIM elements that have a reference
type (properties, parameters).
Name of the class adaptation that is referenced. This is a constraint that any
referenced instances conform to the requirements of that class adaptation. This attribute is
required on CIM elements (properties and parameters) that have a reference type, and it is not
allowed otherwise.
Minimum multiplicity of the adaptation of the referenced class. The specified
multiplicity shall be compatible to the underlying schema and any base adaptations. This optional
attribute is only allowed on CIM elements (properties and parameters) that have a reference type.
Maximum multiplicity of the adaptation of the referenced class. The specified
multiplicity shall be compatible to the underlying schema and any base adaptations. This optional
attribute is only allowed on CIM elements (properties and parameters) that have a reference type.
Internal attribute group for specifying constraints on CIM elements that are embedded
instances.
Name of the class adaptation of the embedded instance. This attribute is required if
the CIM element is an embedded instance.
Internal type for a minimum multiplicity of an association end (reference).
Internal type for a maximum multiplicity of an association end (reference).
Internal type for description text.
Internal type for XHTML text with MRP links.
Text fragment from an XHTML text registry. In a human-readable
presentation of an XML document using this element, the expanded text of the referenced
XHTML text fragment (with any dynamic elements replaced with their values) shall be
presented according to its format.
The value for a dynamic element of the text fragment.
The character content of this element is the value of the dynamic
element of the text fragment.
Name of the dynamic element, as defined in
the text fragment using the "NAME" attribute of the
"DYNAMIC_ELEMENT" element.
XHTML 1.1 text, extended by MRP link elements. If you find that your XML editor rejects
XHTML elements after top-level MRP link elements, you can create a wrapper around the entire content
with the XHTML "p" element.
A link to a heading subclause defined in the subject profile or in a profile referenced
by the subject profile. The element value shall be the text to be displayed in the link. In a
human-readable presentation of an XML document using this element, the element value should be
represented as a hyperlink to the referenced subclause heading.
The value of the "id" attribute of the referenced heading element.
A link to a figure defined in the subject profile or in a profile referenced by the
subject profile. The figure must be defined with a div class="Figure" element. The element value shall
be the text to be displayed in the link. In a human-readable presentation of an XML document using this
element, the element value should be represented as a hyperlink to the referenced subclause heading.
The value of the "id" attribute of the referenced div class="Figure"
element.
A link to a table defined in the subject profile or in a profile referenced by the
subject profile. The element value shall be the text to be displayed in the link. In a human-readable
presentation of an XML document using this element, the element value should be represented as a
hyperlink to the referenced subclause heading.
The value of the "id" attribute of the referenced table element.
A link to a class adaptation defined in the subject profile or in a profile referenced by
the subject profile. The element value shall be the class adaptation name (as defined in the "name"
attribute of the "mrp:ClassAdaptation" element). An attribute of this element references the profile. In
a human-readable presentation of an XML document using this element, the element value should be
represented as a hyperlink to the referenced class adaptation definition.
A link to a property requirement (including CIM reference requirements) within a class
adaptation defined in the subject profile or in a profile referenced by the subject profile. The element
value shall be the property name (as defined in the "name" attribute of the "mrp:Property" element).
Attributes of this element reference the class adaptation and profile. In a human-readable presentation
of an XML document using this element, the element value should be represented as a hyperlink to the
referenced property requirement definition.
A link to a method requirement within a class adaptation defined in the subject profile
or in a profile referenced by the subject profile. The element value shall be the method name (without
or parameters, as defined in the "name" attribute of the "mrp:Method" element). Attributes
of this element reference the class adaptation and profile. In a human-readable presentation of an XML
document using this element, the element value should be represented as a hyperlink to the referenced
method requirement definition.
A link to a parameter requirement within a method requirement within a class adaptation
defined in the subject profile or in a profile referenced by the subject profile. The element value
shall be the parameter name (as defined in the "name" attribute of the "mrp:Parameter" element).
Attributes of this element reference the method, class adaptation, and profile. In a human-readable
presentation of an XML document using this element, the element value should be represented as a
hyperlink to the referenced parameter requirement definition.
A link to a return value requirement within a method requirement within a class
adaptation defined in the subject profile or in a profile referenced by the subject profile. The element
value shall be empty. Attributes of this element reference the method, class adaptation, and profile. In
a human-readable presentation of an XML document using this element, the element value should be
represented as a hyperlink to the referenced return value requirement definition.
A link to an operation requirement within a class adaptation defined in the subject
profile or in a profile referenced by the subject profile. The element value shall be the DSP0223
operation name (without parantheses or parameters, as defined in the "name" attribute of the
"mrp:Operation" element). Attributes of this element reference the class adaptation and profile. In a
human-readable presentation of an XML document using this element, the element value should be
represented as a hyperlink to the referenced operation requirement definition.
A link to a feature defined in the subject profile or in a profile referenced by the
subject profile. The element value shall be the feature name (as defined in the "name" attribute of the
"mrp:Feature" element). An attribute of this element references the profile. In a human-readable
presentation of an XML document using this element, the element value should be represented as a
hyperlink to the referenced feature definition.
A link to a profile referenced by the subject profile. The element value shall be the
profile reference name (as defined in the "refName" attribute of the "mrp:RelatedProfile" element). In a
human-readable presentation of an XML document using this element, the element value should be
represented as a hyperlink to the profile reference definition in the subject profile.
A link to a use case defined in the subject profile. The element value shall be the use
case name (as defined in the "name" attribute of the "mrp:UseCase" element). In a human-readable
presentation of an XML document using this element, the element value should be represented as a
hyperlink to the use case definition.
A link to a standalone state description defined in the subject profile. The element
value shall be the state description name (as defined in the "name" attribute of the
"mrp:StateDescription" element). In a human-readable presentation of an XML document using this element,
the element value should be presented as a hyperlink to the state description definition.
Internal attribute group for referencing a profile in links to profile elements.
The reference name of the profile that defines the linked profile element. If not
specified, the linked profile element is defined in the subject profile.
Internal attribute group for specifying a class adaptation in links to profile elements.
The name of the class adaptation that defines the linked profile element.
Internal attribute group for specifying a method in links to profile elements.
The name of the method (without parentheses or parameters) that defines the linked
profile element.
Internal attribute group for specifying an operation in links to profile elements.
The name of the association adaptation traversed by the linked operation.
Internal attribute group for specifying the name of a class adaptation in the subject profile.
The name of the class adaptation.
Internal attribute group for specifying the profile that defines a class adaptation.
The profile reference name of the profile that defines the class adaptation.
Internal attribute group for Null allowance.
Indicates whether Null is explicitly allowed on the element. This attribute shall not
conflict with the requirements of the Reference qualifier on the element (i.e. Reference=True and
nullOk=True is not valid). If this attribute is not specified and Reference=False, then Null is not
allowed for elements whose effective requirement level is Mandatory or Conditional when the
condition is met, and Null is allowed on elements with any other effective requirement levels.
The related profiles of the subject profile. For details about related profiles, see
DSP1001. This element can be used as a top level element in MRP include files.
The message registries that are used in the subject profile. For details about using
message registries in profiles, see DSP1001. The set of message registries shall consist of those
registries from which messages are referenced in the subject profile. This element can be used as a top
level element in MRP include files.
The metric registries that are used in the subject profile. For details about using
metric registries in profiles, see DSP1001. The set of metric registries shall consist of those
registries from which metrics are referenced in the subject profile. This element can be used as a top
level element in MRP include files.
The features defined in the subject profile. For details about features in profiles, see
DSP1001. This element can be used as a top level element in MRP include files.
The element requirements defined by the subject profile. For details about element
requirements in profiles, see DSP1001. This element can be used as a top level element in MRP include
files.
The use cases and state descriptions of the subject profile. This element can be used as
a top level element in MRP include files.
The actors defined by the subject profile. This set of actors shall represent the actors
referenced by the use cases defined in the subject profile. This element can be used as a top level
element in MRP include files.