2.1 Written specification

The table lists the changes that have been made to the written portion of the DITA 1.3 specification.

Topic Original text Revised text
1.6 Formatting conventions in errata versions of the specification None [A new topic that explains how content that has been modified in errata versions of the specification is highlighted with coloring and visual indicators.]
2.2.2.3 DITA map elements [Explanation of <topicsetref>] Enables authors to reference a navigation branch that is defined in another DITA map. Enables authors to reference a navigation branch that is defined in the current map or in another DITA map.
2.3.4.2 Key scopes A key scope is defined by a <map> or <topicref> element that specifies the @keyscope attribute. The @keyscope attribute specifies the names of the scope, separated by spaces. A key scope is defined by a <map> or <topicref> element that specifies the @keyscope attribute. The @keyscope attribute specifies the names of the scope, separated by spaces. The legal characters for a key scope name are the same as those for keys.
2.4.2 Content reference (conref) None

Related concept:

2.5.5.4 Weak and strong constraints

2.4.4.6.2 Example: Multiple <ditavalref> elements on a branch
<map> <topicref href="intro.dita"/> <!-- Begining of installing
              branch --> <topicref href="install.dita"> <ditavalref href="win.ditaval"/>
              <ditavalref href="mac.ditaval"> <ditavalmeta>
              <dvrResourceSuffix>-apple</dvrResourceSuffix> </ditavalmeta> </ditavalref>
              <ditavalref href="linux.ditaval"> <ditavalmeta>
              <dvrResourceSuffix>-linux</dvrResourceSuffix> </ditavalmeta> </ditavalref>
              <topicref href="do-stuff.dita"> <topicref href="mac-specific-stuff.dita"
              platform="mac"/> </topicref> <!-- End of installing branch -->
              <topicref href="cleanup.dita"/> </topicref> </map>
<map> <topicref href="intro.dita"/> <!-- Begining of installing
              branch --> <topicref href="install.dita"> <ditavalref href="win.ditaval"/>
              <ditavalref href="mac.ditaval"> <ditavalmeta>
              <dvrResourceSuffix>-apple</dvrResourceSuffix> </ditavalmeta> </ditavalref>
              <ditavalref href="linux.ditaval"> <ditavalmeta>
              <dvrResourceSuffix>-linux</dvrResourceSuffix> </ditavalmeta> </ditavalref>
              <topicref href="do-stuff.dita"> <!-- more topics and nested branches -->
              <topicref href="mac-specific-stuff.dita" platform="mac"/> </topicref> <!--
                End of installing branch --> <topicref href="cleanup.dita"/> </topicref>
              </map>
2.5.5.6.6 Example: Correct the constraint for the machinery task None [New example topic]
2.6.3.1 DTD: Overview of coding requirements DITA coding practices for DTDs rely heavily on entities to implement specialization and constrraints. DITA coding practices for DTDs rely heavily on entities to implement specialization and constrraints constraints.
2.7.1.3 General task topic None [Added an additional row to the table that compares the structure of the general and strict task topics]

tasktroubleshooting (optional, one only) | tasktroubleshooting (optional, one only)

2.7.1.4 Task topic (strict task) None
<tasktroubleshooting>
Describes actions that a user might take if the task does not produce the expected results.
3 Language reference: Technical content edition Each element defined in the techical content specializations Each element defined in the techicaltechnical content specializations
3 Language reference: All-inclusive edition Each element defined in the techical content specializations Each element defined in the techicaltechnical content specializations
3.2.3.1 <table> The following attributes are available on this element: Universal attribute group, @outputclass, @display, and @scale from Display attribute group, and the attributes defined below. The following attributes are available on this element: Universal attribute group, @outputclass, @display @frame, and @scale from Display attribute group, and the attributes defined below.
3.3.1.11 <ux-window>
&lt;ux-window id="p76" name="ux-tablet" top="5%" left="5%" height="90%" width="90%" 
    features="status=no,toolbar=no,menubar=no,location=no" relative="no"
    full-screen="no" />
&lt;ux-window id="p76" name="ux-tablet" top="5%1cm" left="5%1cm" height="90%4cm" width="90%3cm" 
    features="status=no,toolbar=no,menubar=no,location=no" relative="no"
    full-screen="no" />
3.4.3.1 <exportanchors> The <exportanchors> element canbe used within a topic prolog, in which case the defined IDs apply to IDs within that topic (excluding sub-topics). The <exportanchors> element can be used within a topic prolog, in which case the defined IDs apply to IDs within that topic (excluding sub-topics).
3.5.4.2 <ditavalmeta> The <ditavalmeta> element also can contain other information, such as author and navigation title, that might be useful for map architects but is not rendered in the output. The <ditavalmeta> element also can contain other information, such as author and navigation title, that might be useful for map architects but is not rendered in the output.
3.10 Technical content elements Elements in the technical content section include the original Concept, Task, and Reference specializations, as well as the Bookmap and Glossary specializations added with DITA 1.1. It also includes domains designed primarily for technical content, such as the task requirements and software domains. Elements in the technical content section include the original Concept, Task, and Reference specializations, as well as the Bookmap and Glossary specializations added with DITA 1.1 in later releases. It also includes domains designed primarily for technical content, such as the task requirements and software domains.
3.10.4 Troubleshooting elements Short description needed Short description needed Troubleshooting topics document corrective action such as troubleshooting or alarm clearing.
3.10.4.1 <troubleshooting> The <troubleshooting> element is the top-level element for a troubleshooting topic. Troubleshooting topics document corrective action such as troubleshooting or alarm clearing. Troubleshooting topics begin with a description of a condition that the reader might want to correct, followed by one or more cause-remedy pairs. Each cause-remedy pair is a potential solution to the trouble described in the condition. The <troubleshooting> element is the top-level element for a troubleshooting topic. Troubleshooting topics document corrective action such as troubleshooting or alarm clearing. Troubleshooting topics begin with a description of a condition that the reader might want to correct, followed by one or more cause-remedy pairs. Each cause-remedy pair is a potential solution to the trouble described in the condition.

Return to main page.