Dita Wiki
DITA 1.2 errata
This page contains information about items to be considered for a DITA 1.2 errata.
XSD errata
The DITA 1.2 XSDs have had several fixes since approval of the DITA 1.2 specification. The latest version can be found at this link: http://www.oasis-open.org/committees/document.php?document_id=45018&wg_abbrev=dita
The updated XSDs include:
- Fixes for bodydiv, section, and example content models
In the catalog, <group uri="machineryIndustry/dtd/"> should be <group xml:base="machineryIndustry/dtd/">
- glossAlt should not have a mixed content model
- added fix for steps content model - remove steps-informal from strict task
- Add fn to figgroup content model
HazardStatement: Consequence must have mixed content model
- Indexing Domain: remove indexterm from index-sort-as content model
LearningPlanbody - section need to be unbounded
- Add conbodydiv and refbodydiv elements
- Ditabase: add abbreviate domain, fix glossgroup info-types
GlossEntry: Fix glossdef content model.
DTD errata
The following errata have been reported with the DTDs:
<glossref> is supposed to have a processing-role attribute, but doesn't.
Specification document
Topic |
Issue |
Source |
Source files corrected |
Person who performed the work |
1.2 Normative references |
The following files contain external cross-references, but the @scope is not set appropriately as “external”: introduction/non-normative-references.dita and introduction/normative-references.dita |
Tarun Garg |
|
|
2.1.2.1.7 Topic domains: Basic DITA |
The topic lists three domains as part of base. However, the task requirements and delay resolution domains also are part of the base. |
|
|
|
2.1.2.2.3 DITA map elements |
The syntax for the @anchorref attribute on the <map> element is incorrect. |
Kris Eberlein |
|
|
2.1.2.2.5 Subject scheme maps |
Several of the <subjectdef> tags in the examples do not have end tags; should also add </subjectScheme> to an example. |
|
|
|
2.1.2.2.5 Subject scheme maps |
In XHTML, the TOC does not match the topic title; this is not a problem in the PDF. |
|
|
|
2.1.3.4.4 Summary of addressing elements |
Typo in the table row for "Elements that take @keyref but not @href"; "matchin" should be "matching" |
|
|
|
2.1.3.9.1 The @xml:lang attribute |
The example at the end states "...the @xml:lang value "fr" is applied to the note with the id attribute "mynote"." However, the id="mynote" attribute is missing from the note; it should be present on the first note in the example: |
|
|
|
2.1.4.4 Constraints |
Typo: <shortdec> should be <shortdesc> |
|
|
|
2.2.3 Topic domains: Technical content |
Hazard Statement domain is listed in the table, but it is part of the base (not Technical Content) |
|
|
|
3.1.8.1 val |
The following example should use att="platform", not att="otherprops": |
|
|
|
3.4.2.5 The conaction attribute |
Typo: "may delete empty the element that with the" should be "may delete the empty element with the" |
|
|
|
B.1.1 Changes from DITA 1.1 to 1.2 |
Extraneous period: " ... for example., Eclipse information centers." Also need to verify that the Eclipse usage is at least described as an example, if we are going to reference it at all. |
|
|
|
Multiple topics |
The task requirements domain (taskreq-d) was renamed from Machine Industry Domain (mitask-d). This was fixed in terminology, DTDs, and Schemas, but the class attributes in the language spec still show mitask-d. |
|
|
|
? |
There's a minor typo in langref/keydef.dita, mapgropup-d should be mapgroup-d. |
|
|
|
? |
The <coderef> element shows a - instead of + in the class attribute; should be + (it is a domain element). DTD/Schemas are correct. |
|
|
|
Packaging |
Make a ZIP file of the XHTML optimized for local use available as part of the official standard. |
Robin Cover |
|
|
3.2.6.3.2 msgblock |
Topic says that msgblock can contain msgph, but it cannot. Expect this to be allowed in 1.3. |
Noted on dita-users |
|
|
2.1.4.4.4 Examples of constraint declaration modules |
The example on applying multiple constraints to a single vocabulary module is missing a semicolon after the word %title. |
http://lists.oasis-open.org/archives/dita/201012/msg00008.html |
|
|
2.1.4.2.1 DTD document-type shell: Coding requirements |
Constraint entity names are inconsistent in the definition (suffix -c-mod) and example (suffix -c-def). The examples are correct. |
http://lists.oasis-open.org/archives/dita/201012/msg00043.html |
|
|
2.1.2.3.4 Cascading of attributes and metadata in a DITA map |
Typo: in the section "Rules for cascading in the map" there is a missing quote in the sample <topicref toc="yes> |
Robert noticed while scanning the spec |
|
|
2.1.1.4 File naming conventions |
Clarification on filename convention for DTD constraint modules |
Eric Sirois and Eliot Kimber http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201101/msg00053.html |
|
|
Language spec topics |
The "Contained by" table has the wrong heading -- it says "Content model" but should actually be "Elements" or something similar. |
Noticed by Bruce Nevin |
|
|
3.1.2.2.7 topicsetref |
The second figure in the example section has a mismatch; the title of the figure and the sample both refer to reuse within the same map, but the text description calls it reuse by another map. |
Kris Eberlein noticed |
|
|
various (reused language spec attribute) |
Locktitle attribute wording is not clear; see http://www.oasis-open.org/apps/org/workgroup/dita/email/archives/201202/msg00052.html and minutes from Feb 21 2012 |
email from Eliot Kimber |
|
|