DITA 1.3 support
DITA Open Toolkit 2.2 provides processing support for the OASIS DITA 1.3 specification. Initial preview support for this specification was added in version 2.0 of the toolkit; version 2.2 extends this foundation to support key scopes and branch filtering along with additional DITA 1.3 features.
Because DITA 1.3 is fully backwards compatible with previous DITA DTDs and schemas, DITA-OT 2.2 provides the 1.3 materials as the default DTDs for processing. The XML Catalog resolution maps any references for unversioned DITA doctypes to the 1.3 DTDs. All processing ordinarily dependent on the 1.0, 1.1, or 1.2 definitions continues to work as usual, and any documents that make use of the newer DITA 1.3 elements or attributes will be supported with specific new processing.
Initial Preview Support for DITA 1.3 in DITA-OT 2.0
The following DITA 1.3 features were implemented in version 2.0 of the toolkit. Issue numbers correspond to the tracking number in the GitHub issues tracker.
- Support DITA 1.3 link syntax (milestone 2) #1649
- Support DITA 1.3 cascade attribute (milestone 2) #1636
- Implement DITA 1.3 profiling (milestone 2) #1635
- Add new DITA 1.3 highlighting elements (milestone 4) #1651
- Add DITA 1.3 markup and xml domain support (milestone 4) #1652
- Add DITA 1.3 div element (milestone 4) #1654
Additional DITA 1.3 support in DITA-OT 2.2
The following DITA 1.3 features were implemented in version 2.2 of the toolkit.
- Initial implementation of DITA 1.3 branch filtering
The implementation is a separate module that is run before keyref processing. The process
- Splits branches so that each branch contains a single ditavalref
@copy-toattributes for each branch-generated <topicref>
- Filters the map based on branch filters
- Rewrites duplicate generated copy-to targets with a numbered -# suffix
- Copies and filters generated copy-to targets
- Filters topics that were not branch-generated
- Initial support for DITA 1.3 key scopes, including multiple scope names in a single
@keyscopeattribute #1979, #1648, #2004
@keyrefattribute is now supported on
- Processing order has been revised to process any same topic fragments used in conrefs before the
conref phase, to enable content references to elements in the same topic using a reference such as
<p conref="#./ID"/>as reported in #1649. #1968