In pursuit of the ultimate techCom information architecture
Why is the result often a million little pieces even though DITA does not encourage authors to chunk information in such a way?
A lot of discussions and confusion in social media has recently, as it seems, dealt with two issues concerning the use of DITA (see for example a discussion in the DITA awareness group on linkedIn or another discussion on LinkedIn or a blog post by Tom Johnson). The first issue relates to the question if topics shall be nested or not, that is, shall DITA topics be kept as separate files or shall authors instead use a <dita> document and nest topics within it?
Self on Help
There have been many discussions within OASIS DITA committees about discovering (and removing) the impediments to DITA adoption. It's probably fair to say that the discussions have discovered there are many roadblocks, but so far haven't resulted in clear ways to remove them.
Note: while the DITA Standard itself is owned and developed by OASIS, the DITA Open Toolkit is an independent, open sourceimplementation of the standard.
DITA-OT 1.5.4 is a point release based on version 1.2 of the DITA Standard. The 1.5.4 release took place as a series of 3 week iterations, with each iteration ending in a Milestone build available for testing. The final 1.5.4 version was released December 15, 2011.
For full description of new features and fixed bugs, see 1.5.4 release notes.
It's time for the next installment of the DITA OT in the Arbortext Monster Garage.
In the first session on Arbortext and the DITA OT (last month), shop coach Mark Giffin from Mark Giffin Consulting, Inc., explained the basics of how Arbortext works with the DITA Open Toolkit.
The core developers on the DITA Open Toolkit generally try to keep several coding practices and design patterns in mind when adding to the toolkit's Java code. If you are interested in digging around in the DITA Open Toolkit, or in contributing Java patches back to the core toolkit, you may want to keep these practices in mind.
Note that this page is currently under development.