DITA 1.2 added a number of new features to DITA, including indirect addressing using map-defined keys; the ability to define content-model constraints for DITA document types; specializations for learning content and the machine industry; and taxonomies, ontologies, and controlled vocabularies. Other refinements include extended markup for glossaries and terminology.
<text>
<ph>
nor
<keyword>
are allowed. Enables reuse of text in almost any
context.<bodydiv>
<sectiondiv>
<keydef>
@role
attribute to "resource-only".<mapref>
@format
attribute to "ditamap".<topicset>
@id
attribute be specified.<topicsetref>
<topicset>
element. Enables preservation of the identity of
the referenced topic set.<anchor>
<topicref>
elements can be bound
using the <anchorref>
element.<anchorref>
<topicref>
elements onto an anchor point defined by
an <anchor>
element. Similar to a conref push but allows the
relationship to be managed dynamically by the renderer.<title>
element in
place of the @title
attribute.<title>
as an optional first
child.<navtitle>
element in place of the @navtitle
attribute.<topicref>
attribute named
@processing-role
. Indicates whether or not
a topic reference contributes to the navigation structure of the
containing map.<step>
element can include a
sequence of <step>
elements.@keyref
attribute, including the <ph>
,
<keyword>
, and
<term>
elements. When using the
@keyref
attribute, these elements can get
their effective content from the key-defining
<topicref>
element and can also be
treated as navigation links to the resource pointed to by the
key-defining <topicref>
element, if any.
For example, a <term>
element can use
@keyref
to link to the glossary entry
topics for the term.<image>
element takes the new
@scalefit
attribute, which indicates
whether or not the image should be scaled to fit the
presentation context.<draft-comment>
element is now allowed
in most contexts.<figgroup>
element now allows
<data>
as a subelement.@domains
attribute. Structural modules can
depend on and specialize elements from domains. For example, a
structural domain for reference topics for a specific
programming language could depend on the Programming domain
(pr-d) and specialize elements from that domain.<dita>
element now has the
@DITAArchVersion
attribute.