DITA 1.3 adds a number of new features and refinements to DITA.
@audience
, @platform
, @product
,
and @otherprops
) now accept grouped values, using the same syntax for
generalized attribute values within @props
and @base
.<steps>
element from <task>
to be reused
in place of an <ol>
within a <remedy>
section of the troubleshooting document type.@type
attribute of the <note>
element<steptroubleshooting>
, which is designed to contain
information that might assist users when a step does not produce the expected result
or complete successfully<tasktroubleshooting>
, which is designed to contain
information that might assist users when a task does not produce the expected result
or complete successfully<resourceid>
:@appid
@ux-context-string
@ux-source-priority
@ux-windowref
<ux-window>
, designed to
specify a window or viewport in which an online help topic or Web page is
displayedAdded the following new domains:
<learningObjectMap>
<learningObjectMapRef>
<learningGroupMap>
<learningGroupMapRef>
<div>
element. This element enables
arbitrary grouping of content within a topic. It is primarily intended as a way to
group content for content referencing or as a basis for specialization.@deliveryTarget
, to replace the now-deprecated
@print
attribute. Users can set controlled values for the
@deliveryTarget
attribute by using a subject scheme map.@orient
to <table>
and
@rotate
to <entry>
. These new attributes enable
authors to control formatting more precisely for print-based output formats.@scope
and @headers
attributes to
the <entry>
element in tables. These new attributes are intended for
extremely complex tables where accessibility cannot be handled based on existing header
markup.@cascade
, to better control
how metadata attributes cascade within a DITA map<draft-comment>
in more places<text>
in more places<data>
to allow
additional phrase level markup. @style
attribute on <prop>
and <revprop>
elements in
DITAVAL files.<ph>
within
<indexterm>
. This makes it possible to use specializations of the
<ph>
element, such as <sup>
and
<sub>
, within index entries.@keyref
for <object>
and <param>
<data>
to the content model for
lists@format
and
@scope
attributes@rev
attribute to
<title>
<cite>
to the content model of
<title>
and similar elements<xref>
to the content model for
<shortdesc>
<sort-as>
, to the
utilities domain<line-through>
and
<overline>
to the highlighting domain