DITA, DTDs, FrameMaker, and other tools
A couple of people have asked lately what the difference is between a DTD and DITA, and in one case FrameMaker vs XML, so I thought the topic of schemas was worth discussion. Here, we’ll cover what a DTD really means, how to compare it to a DITA schema, and figure out where an authoring tool like FrameMaker fits in the picture.
On the scale of big-picture vs small-picture comparisons, the scale is:
- First: structured and unstructured content
- Second: DTD and DITA
- Third: FrameMaker and other authoring tools
We’ll start in the middle, with DTDs and DITA, and in future posts, discuss the first and third comparisons.
DTD and DITA
DTD stands for Document Type Definition. This is actually a misnomer, because the DTD doesn’t define the document type, it defines the document’s structure, so should be called Document Structure Definition. This file, which works in the background, enforces the structure of a document.
For example, you decide that a procedure in a User Guide has 1 heading, followed by 1 paragraph, followed by numbered steps, which could each contain a table, note, or graphic. Your DTD would enforce this standard by limiting the options that an author could choose at any given point.
Similarly, DITA is a Topic Structure Definition. Because DITA is topic-based, not document-based, this file enforces the structure of each topic. DITA comes with four topic types, and can be specialized as needed.
An easy way to explain DITA is to compare it to online help. If you were to learn how to write online help from a theoretical point of view, you would learn about writing concept topics, task topics, and reference topics, and how to link between them. These would be structured into a TOC. These are the exact topics in DITA: task, topic reference, plus a catch-all “generic” topic. And in the DITA vocabulary, a TOC is a DITA map.
Next post: Structured vs unstructured content
Comments
Leave a Reply
Recent Posts
- Public-sector content, web development and content strategy, and career cautions for writers
- The ROI of content
- Is it time for a content strategy maturity model?
- Getting ROI by Using Lean in Content Production
- Defining Content in the Age of Technology
- Turning Copy into Content
- Copy and content: a tale of two realities
- Content that RAITES
- The Brief Content Audit
- Why content strategy: explaining its value proposition
Categories
Tags
accessibility ann rockley career development CMS content as asset content convergence content lifecycle content management content strategy convergence deliverables DITA Duo Consulting experience design Flash integration intelligent content interaction design management marketing mentors open standards plain language politics processes professional development ROI search section 508 services single-sourcing social media STC structured content syndication taxonomy TechCraft translation Twitter usability user-centered design user-generated content user experience value XMLPopular
- Using topic-based writing to meet aggressive deadlines
- Content strategy and the new face of documentation
- Flash pages, skip intros, and other annoying content
- A practical definition of content
- Content strategy includes convergence, integration, and syndication
- Why social media seems easy but is (evidently) harder than it looks
- Abilities and aptitudes for a content strategist
- Redefining content strategy
- Strategies for adopting structured content
- CMS selection practices need maturation
Random Posts
- The Bailie Daily is out! http://t.co/8Cfucuyt 49 mins ago
- Evidently, in a restaurant, one should eat peanuts with chopsticks. #crossculturalrelationship 17 hrs ago
- The park across the street has come alive again. Today, soccer games, then a cricket match. Is spring here yet? 19 hrs ago
- The Bailie Daily is out! http://t.co/8Cfucuyt ▸ Top stories today via @livlab @mulegirl @johnnyholland 1 day ago
- More updates...















Latest Tweets
RSS feed
Twitter