Diff for Making the Business Case for DITA

Fri, 2008-04-18 00:43 by Bob DoyleFri, 2008-04-18 00:45 by Bob Doyle
< previous diffnext diff >
Changes to Body
Line 1Line 1
-
<p>
+
<p class="rightalign">
-
&lt;p class=&quot;rightalign&quot;&gt;<br />
+
<a href="/wiki/is-content-management-important">Content management</a> <br />
-
&lt;a href=&quot;/wiki/is-content-management-important&quot;&gt;Content management&lt;/a&gt; &lt;br /&gt;<br />
+
<a href="/wiki/is-structure-important">Structure</a> <br />
-
&lt;a href=&quot;/wiki/is-structure-important&quot;&gt;Structure&lt;/a&gt; &lt;br /&gt;<br />
+
<a href="/wiki/is-content-reuse-important">Content reuse</a> <br />
-
&lt;a href=&quot;/wiki/is-content-reuse-important&quot;&gt;Content reuse&lt;/a&gt; &lt;br /&gt;<br />
+
<a href="/wiki/is-single-sourcing-important">Single source</a> <br />
-
&lt;a href=&quot;/wiki/is-single-sourcing-important&quot;&gt;Single source&lt;/a&gt; &lt;br /&gt;<br />
+
<a href="/wiki/is-translation-important">Translation</a> <br />
-
&lt;a href=&quot;/wiki/is-translation-important&quot;&gt;Translation&lt;/a&gt; &lt;br /&gt;<br />
+
<a href="/wiki/do-you-markup-your-content">Metadata markup</a> <br />
-
&lt;a href=&quot;/wiki/do-you-markup-your-content&quot;&gt;Metadata markup&lt;/a&gt; &lt;br /&gt;<br />
+
<a href="/wiki/is-your-content-modular">Modularity</a> <br />
-
&lt;a href=&quot;/wiki/is-your-content-modular&quot;&gt;Modularity&lt;/a&gt; &lt;br /&gt;<br />
+
<a href="/wiki/is-your-content-conditional">Conditional processing</a> <br />
-
&lt;a href=&quot;/wiki/is-your-content-conditional&quot;&gt;Conditional processing&lt;/a&gt; &lt;br /&gt;<br />
+
<a href="/wiki/is-your-content-task-oriented-and-minimalist">Task-oriented and Minimalism</a> <br />
-
&lt;a href=&quot;/wiki/is-your-content-task-oriented-and-minimalist&quot;&gt;Task-oriented and Minimalism&lt;/a&gt; &lt;br /&gt;<br />
+
<a href="/wiki/is-standardization-important">Standardization</a> <br />
-
&lt;a href=&quot;/wiki/is-standardization-important&quot;&gt;Standardization&lt;/a&gt; &lt;br /&gt;<br />
+
-
&lt;/p&gt;
+
 
</p>
 
</p>
 
<p>
 
<p>
Revision of Fri, 2008-04-18 00:45:

Making the Business Case for DITA

Content management
Structure
Content reuse
Single source
Translation
Metadata markup
Modularity
Conditional processing
Task-oriented and Minimalism
Standardization

To make the business case for DITA, you must align its many powerful features with specific needs in your business or organization.

DITA has many features based on decades of research in methods for technical documentation - like modularity, structured writing, information typing, minimalism, inheritance, specialization, simplified XML, single-source, topic-based, ready-made metadata, conditional processing, component publishing, task-orientation, content reuse, multi-channel, and translation-friendly. See History of DITA.

Few organizations are likely to use all the features of DITA, but you should go through our checklist to determine which features could provide a significant return on investment in your particular business case. Use those features with positive returns in building your arguments for DITA.

We are developing a ten-question DITA Quotient to help organizations get a quantitative measure of the importance of DITA for their current content.
XML.org Focus Areas: BPEL | DITA | ebXML | IDtrust | OpenDocument | SAML | UBL | UDDI
OASIS sites: OASIS | Cover Pages | XML.org | AMQP | CGM Open | eGov | Emergency | IDtrust | LegalXML | Open CSA | OSLC | WS-I

dita-bird_0.jpg

Hosted by:

OASIS

Sponsored by:

adobe-systems-incorporated_0_0_0.png

ibm.gif

Sponsored links:

Adobe DITA CCMS