The Darwin Information Typing Architecture (DITA) is an XML-based architecture for authoring, producing, and delivering technical information. DITA divides content into small, self-contained topics that can be reused in different deliverables. The extensibility of DITA permits organizations to define specific information structures and still use standard tools to work with them. DITA is often compared against DocBook, a similar XML schema.
The DITA-OT plugin transforms a map into a single file, suitable for publication, and automatically call the xmlrpc API of the blog to publish it. The DITA Wordpress plugin adds a css (a slightly modified version of the DITA-OT commonltr.css) to your Wordpress theme to properly render the standard domains.
I’m continuing with my series about DITA. In this post, I explain parent-child page links, content re-use when the content exists in different elements, a one-folder-for-all-files organization, and a better workaround to transferring relative links to Drupal.
The Organization for the Advancement of Structured Information Standards (OASIS) has formed a new committee for encouraging the use of DITA in all areas of business. Readers can learn how to work with their organization to make the sharing of DITA content possible.
This paper helps you determine the cost portion of the ROI calculation. What are my costs now? What will my new costs be with DITA? This paper describes one model for calculating the cost of a DITA project. After doing some content analysis on your own documentation set, you can customize this cost model to suit your documentation project needs. In the end, you should be able to speak the financial language of managers and prove to them in dollar signs the value of moving to DITA.
This paper is the third in the DITA Metrics series which examines the cost and reuse values for a DITA project to determine DITA ROI. The concepts and ideas discussed are based on the cost model introduced in the first paper, DITA Metrics: Cost Metrics – Part 1. This paper provides real metrics that prove the savings that can be achieved through DITA and a solid content reuse strategy. We look at the savings trend that emerges when content referencing and warehouse topics are used to document similar products. How much does it cost to document each additional similar product? Many thanks again to Julio Vazquez for his excellent review and feedback on this paper. Thanks Julio! >Mark Lewis Keywords: DITA metrics DITA reuse math DITA economics DITA cost metrics DITA reuse metrics DITA percent reuse DITA percentage reuse DITA statistics DITA formulas single source publishing metrics single source publishing statistics Reuse calculate reuse calculation DITA Cost Calculator DITA Cost Calculations DITA Reuse Calculator DITA Reuse Calculations DITA ROI business case
This is the second installment of the DITA Metrics series which examines the cost and reuse values for a DITA project to determine DITA ROI. This paper looks at the savings trend when reusable master topics are used to document similar products. How much does it cost to document each additional similar product?
The DITA Open Toolkit is an implementation of the OASIS DITA Technical Committee's specification for Darwin Information Typing Architecture (DITA) DTDs and Schemas. The Toolkit transforms DITA content (maps and topics) into deliverable formats.
The DITA Open Toolkit is an open source implementation of the OASIS DITA Technical Committee's specification for Darwin Information Typing Architecture (DITA) DTDs and schemas. The toolkit is a major upgrade from its predecessor, the developerWorks version known as "dita132." The toolkit uses open source solution of ANT, XSLT (currently 1.0) and Java to implement transformation functions from DITA content (maps and topics) into different deliverable formats.
This paper outlines a course given by Adena Frazier of Suite Solutions--a course which is highly recommended for anyone who wants to get the most of the OT. This paper outlines the most important processes, but it leaves out many of the details, tips, and debugging notes that were included in the course. Note, too, that errors easily could have crept in, and some details are bound to change for later versions of the toolkit. (We used version 1.4.1) So it makes a lot of sense to take the course, even if you find the outline useful.
I just spent some time playing with this tool and find it a clean, quick alternative to the more complex Echidna/WinANT tool. DITAOT-GUI provides a simple interface, allowing users to select a map, DITAVAL filter, output location and output type. It bypasses the need to create a build file but therefore does not allow the use of parameters and properties to specify additional aspects of the build.
The IBM Information Architecture Workbench is an Eclipse-based freeware that I find marvellously handy for organising my thoughts and then committing those thoughts to DITA files. With it, I can model my ditamaps, generate DITA stub files* for the ditamap nodes, and edit the DITA files. Plus, if I draw a line from File A to File B, it gets registered in the ditamap's relationship table. All pretty neat and clean. It shows me, visually, how my topics are arranged in my book (and lets me move around files with a drag-and-drop action). It also shows me orphan files - those nodes that I created but did not link anywhere. And, I can edit the DITA attributes very easily in the Properties view.
I am very comfortable with using Notepad to write in DITA. But there are times when I forget if a particular DITA tag can be used at a particular place. For example, I regularly forget if <prereq> should precede <context> or follow. At such times, an XML editor that also validates your tags as you type comes in handy. XMLmind XML Editor is one such tool and comes bundled with the DITA DTDs and schemas. Its personal edition is free to use for non-commercial purposes and is, thus, great if you want a WYSIWYG DITA editor for your learning and other personal stuff.
Two of the oft-quoted benefits of DITA, the Darwin Information Typing Architecture, are 'single-sourcing' and 'content re-use'. These benefits do not only apply to the commonly-accepted definition of technical documents, but to many other forms of documents from outside the technical communicator's realm.
DITA 1.3 is scheduled to include enhancements that expand the options for implementing accessibility in tables to match the options available in HTML. While it's good to enhance the flexibility of DITA, authors also need to remember to keep table design simple.