http://tc.eserver.org/dir/Articles/Information-Design/DocBook/DITA A listing of the most recently indexed works about Articles and Information Design and DocBook and DITA in the field of technical communication. en-us Copyright (c) 2005-08 by the EServer. All rights reserved. tclib-editorial@eserver.org (TC Library Editorial Board) webmaster@eserver.org (Geoffrey Sauer) http://tc.eserver.org/images/newlogo.gif http://tc.eserver.org/dir/Articles/Information-Design/DocBook/DITA http://tc.eserver.org/32086.html http://tc.eserver.org/32086.html First of all, understand that you don’t have to learn it. Every year more and more toolds come out that help place a layer between you and the native XML. In a few years time you will hardly even realise there is XML underneath. http://tc.eserver.org/31156.html http://tc.eserver.org/31156.html DocBook and DITA both have their places. They're both excellent for single sourcing. DocBook is better for what I call monolithic single sourcing, while DITA is better suited for discrete single sourcing. http://tc.eserver.org/31157.html http://tc.eserver.org/31157.html If you follow the latest trends or have been to a conference recently, you may find the idea of choosing an XML schema puzzling. Isn't the question really, 'How should I customize DITA to do what I want'? While there are many good reasons to choose DITA, it's not the only schema in town. http://tc.eserver.org/29287.html http://tc.eserver.org/29287.html If you line DocBook and DITA up, I think DITA can point to four technical differences that are arguably features in its favor.