by Eric Armstrong, Blog
Archive - 2007
What are the key principles of the DITA architecture?
Forum topic: Submitted by carolgeyer on Mon, 2007-09-17 18:42.
- Topic orientation: Information covering one subject with a specific intent
- Topic granularity: Discrete, self-contained units accessed independently
- Topic sets: Deliverables assembled from a pool of available topics
- Strong typing: Required structures with well-defined semantics for each kind of information — such as a Task with steps
Why use topics?
Forum topic: Submitted by carolgeyer on Mon, 2007-09-17 18:39.
Topics are the basis for high-quality information. They should be short enough to be easily readable, but long enough to make sense on their own.
By organizing your content into topics, you can achieve several goals simultaneously:
By organizing your content into topics, you can achieve several goals simultaneously:
What is a topic?
Forum topic: Submitted by carolgeyer on Mon, 2007-09-17 18:38.
A topic is a chunk of information organized around a single subject. Structurally, it is a title followed by text and images, optionally organized into sections. Topics can be of many different types, the most common being concepts, tasks, and reference.
Building a Bridge: DITA, DocBook, and ODF
News: Submitted by carolgeyer on Mon, 2007-09-17 12:55.
Why use maps?
Forum topic: Submitted by carolgeyer on Thu, 2007-09-13 21:00. Last updated on Fri, 2007-09-14 20:07.
Maps separate the context of your information deliverable from its content. In a typical HTML-based web site, any change to the appearance or navigation of the site typically means making updates to dozens or more individual HTML pages. DITA enables all the navigation (sequences, hierarchies, relationtions) to be managed from a DITA map, which allows authors to manage navigation from a single structure, and then generate new web pages as needed.