2. About the presenter
Founder and president, Scriptorium Publishing
Experienced with lots of different publishing
ideas, including XML and DITA
3. You've got questions...
...we've got answers
Type any questions in the Question and Answer
area of the GoToWebinar bar
Sharon Burton, MadCap Product manager, will
do her best to answer
I will provide contact information if you need to
follow up after the webinar
4. Housekeeping notes for this webinar
You are muted. Feel free to talk...but we can't hear
We’re recording this webinar for posterity.
Your information will not appear in the ﬁnal webinar.
We will send you the download link in a follow-up
email, which will also include...
A short survey. Please ﬁll it out so that we can make
future webinars better.
We should be done by the top of the hour.
We know you have a busy day.
6. What is DITA?
Darwin Information Typing Architecture
Darwin – because you can evolve new elements
from existing elements
Information Typing – content is categorized as
task, reference, concept
Architecture – includes components for reuse,
single sourcing, and generating output
Developed by IBM, maintained by OASIS
7. Why is DITA important? Is DITA
Structured authoring is creating content with
programmatic enforcement of the required
DITA is a gateway to structured authoring
8. What is DITA, really?
Built for topic-oriented authoring
A way to work in XML without having to design
your own structure?
A major buzzword in tech comm
Cost-effective way to create, publish, reuse, and
exchange structured content
20. DITA topic (simpliﬁed)
<title>One tag, two tag</title>
<p>Red tag, blue</p>
<p>Black tag, blue tag, old tag,
<p>This one has a little car</p>
<p>This one has a little star</p>
<note>Say, what a lot of tags there
21. <?xml version="1.0"?>
<!DOCTYPE dita PUBLIC "-//OASIS//DTD DITA
<topic id="aardvark" audience="internal">
<p>Aardvarks eat mostly termites. </p>
<p>Do not take the aardvarks' offer to
help deal with your termite problem. You
will <b>not</b> like the results.</p>
<note type="danger" id="nofeeding">Do not
feed animals snacks, scraps, or people
32. Business case for XML
Reuse content/reduce duplication
33. Beyond XML's business case, DITA
Reduce content modeling effort
Make content truly portable
Support content reuse
Take advantage of software support
Provide output options
Reduce overall cost of implementation
34. Reduce content modeling effort
Assume that DITA structure is a reasonable
Speed up the transition to structure
But what if DITA
Does your industry
35. Make content truly portable
Do you need to send
content to a customer,
partner, vendor, other
Will they standardize
38. Provide output options
XHTML, HTML Help, PDF, Eclipse, DocBook,
JavaHelp, troff, Word RTF through DITA Open
Starting point for output
Not suitable for production workﬂow
Customization is difﬁcult and time-consuming
DITA meets all requirements.
A business partner or customer requires DITA
Single sourcing is a requirement.
No existing content.
Can be ﬂexible with markup requirements to
make implementation faster.
Content must conform to a speciﬁc standard,
such as S1000D
Content is and should remain narrative.
Semantic requirements are industry-speciﬁc,
complex, and/or strict.