<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: DITA to take over the world&#8230;</title>
	<atom:link href="http://blog.siliconpublishing.com/2010/06/dita-to-take-over-the-world/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.siliconpublishing.com/2010/06/dita-to-take-over-the-world/</link>
	<description>Max Dunn&#039;s electronic publishing blog: reconciling information and rendition technologies</description>
	<lastBuildDate>Fri, 19 Nov 2010 09:35:27 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Don Day</title>
		<link>http://blog.siliconpublishing.com/2010/06/dita-to-take-over-the-world/comment-page-1/#comment-361</link>
		<dc:creator>Don Day</dc:creator>
		<pubDate>Fri, 25 Jun 2010 15:33:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.publishingsilicon.com/?p=171#comment-361</guid>
		<description>I&#039;m 100% in agreement with your thesis, Max. DITA was informed on by the experiences and requirements of the technical documentation community, but designed to be general and extensible at the same time. Today, the end-to-end tools for DITA technical writers offer users a good choice of mature, robust capabilities.

There are many other possible applications for DITA, a few of which are represented by the standing Subcommittees of the OASIS DITA Technical Committee, such as Learning Content, Pharmaceutics, and Machine Industry. I am anxious to see tools and services reach out to the unique needs of those communities, and many others as well.

I expect the DITA 1.2 era will see greater use of refactoring and specialization to adapt DITA for those unique applications. Watch for DITA to be taken up by companies as a content standard across the enterprise, such as for policies and procedures, project records, and white papers.

There are some exciting new uses coming up!
--
Don Day,
Chair, OASIS DITA Technical Committee</description>
		<content:encoded><![CDATA[<p>I&#8217;m 100% in agreement with your thesis, Max. DITA was informed on by the experiences and requirements of the technical documentation community, but designed to be general and extensible at the same time. Today, the end-to-end tools for DITA technical writers offer users a good choice of mature, robust capabilities.</p>
<p>There are many other possible applications for DITA, a few of which are represented by the standing Subcommittees of the OASIS DITA Technical Committee, such as Learning Content, Pharmaceutics, and Machine Industry. I am anxious to see tools and services reach out to the unique needs of those communities, and many others as well.</p>
<p>I expect the DITA 1.2 era will see greater use of refactoring and specialization to adapt DITA for those unique applications. Watch for DITA to be taken up by companies as a content standard across the enterprise, such as for policies and procedures, project records, and white papers.</p>
<p>There are some exciting new uses coming up!<br />
&#8211;<br />
Don Day,<br />
Chair, OASIS DITA Technical Committee</p>
]]></content:encoded>
	</item>
</channel>
</rss>

