The metadata attributes specify properties of the content that can be used to determine how the content should be processed. Specialized metadata attributes can be defined to enable specific business-processing needs, such as semantic processing and data mining.
Metadata attributes typically are used for the following purposes:
Typically @audience, @platform, @product,
@otherprops, @props, @deliveryTarget, and
specializations of the @props attributes are used for filtering; the same
attributes plus the @rev attribute are used for flagging. The
@status and @importance attributes, as well as custom
attributes specialized from @base, are used for application-specific
behavior, such as identifying metadata to aid in search and retrieval.
The following conditional-processing attributes are available on most elements:
@product@platform@audience@deliveryTarget@print attribute.The @deliveryTarget attribute is
specialized from the @props attribute. It is defined in the
deliveryTargetAttDomain, which is integrated into all OASIS-provided document-type
shells. If this domain is not integrated into a given document-type shell, the
@deliveryTarget attribute will not be available.
@rev@otherprops@propsOther attributes are still considered metadata on an element, but they are not designed for filtering or flagging.
@importance@status@base@outputclass@outputclass attribute does not
provide a formal type declaration or the structural consistency of specialization,
it should be used sparingly, usually only as a temporary measure while a
specialization is developed. For example, <uicontrol>
elements that define button labels could be distinguished by adding an
@outputclass attribute:
<uicontrol outputclass="button">Cancel</uicontrol>The
value of the @outputclass attribute can be used to trigger XSLT or
CSS rules, while providing a mapping to be used for future migration to a more
specialized set of user interface elements.