<?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: Practical DITA &#8212; Book Review</title>
	<atom:link href="http://xmlpress.net/2009/03/31/practical-dita-book-review/feed/" rel="self" type="application/rss+xml" />
	<link>http://xmlpress.net/2009/03/31/practical-dita-book-review/</link>
	<description>XML for Technical Communicators</description>
	<lastBuildDate>Mon, 08 Mar 2010 15:37:46 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: jmswisher's status on Tuesday, 16-Jun-09 21:43:25 UTC - Identi.ca</title>
		<link>http://xmlpress.net/2009/03/31/practical-dita-book-review/comment-page-1/#comment-289</link>
		<dc:creator>jmswisher's status on Tuesday, 16-Jun-09 21:43:25 UTC - Identi.ca</dc:creator>
		<pubDate>Tue, 16 Jun 2009 21:43:27 +0000</pubDate>
		<guid isPermaLink="false">http://xmlpress.net/?p=146#comment-289</guid>
		<description>[...] !wosdocs Review of &quot;Practical DITA&quot;: http://xmlpress.net/2009/03/31/practical-dita-book-review/ [...]</description>
		<content:encoded><![CDATA[<p>[...] !wosdocs Review of &quot;Practical DITA&quot;: <a href="http://xmlpress.net/2009/03/31/practical-dita-book-review/" rel="nofollow">http://xmlpress.net/2009/03/31/practical-dita-book-review/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Rice</title>
		<link>http://xmlpress.net/2009/03/31/practical-dita-book-review/comment-page-1/#comment-281</link>
		<dc:creator>Mike Rice</dc:creator>
		<pubDate>Mon, 15 Jun 2009 18:58:21 +0000</pubDate>
		<guid isPermaLink="false">http://xmlpress.net/?p=146#comment-281</guid>
		<description>I work with a large group of professional writers. The information architecture team has considered removing the presentation tags to avoid abuse. However, they may be more useful left in. 

Many of our writers have not done structured authoring, or they are such experienced writers that their first reaction to DITA is that it&#039;s too restrictive and they&#039;ll find a way to do things the way they&#039;ve always done them. To identify the need for remedial training, or even to identify the need for a specialization or different output rendering, I think we&#039;ll keep tags like i and b. Automated searches for presentation tags in DITA can make them serve as a &quot;honeypot&quot; either for tag abuse or to identify an unidentified need.</description>
		<content:encoded><![CDATA[<p>I work with a large group of professional writers. The information architecture team has considered removing the presentation tags to avoid abuse. However, they may be more useful left in. </p>
<p>Many of our writers have not done structured authoring, or they are such experienced writers that their first reaction to DITA is that it&#8217;s too restrictive and they&#8217;ll find a way to do things the way they&#8217;ve always done them. To identify the need for remedial training, or even to identify the need for a specialization or different output rendering, I think we&#8217;ll keep tags like i and b. Automated searches for presentation tags in DITA can make them serve as a &#8220;honeypot&#8221; either for tag abuse or to identify an unidentified need.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Hamilton</title>
		<link>http://xmlpress.net/2009/03/31/practical-dita-book-review/comment-page-1/#comment-18</link>
		<dc:creator>Richard Hamilton</dc:creator>
		<pubDate>Mon, 13 Apr 2009 03:43:05 +0000</pubDate>
		<guid isPermaLink="false">http://xmlpress.net/?p=146#comment-18</guid>
		<description>To: Gunnar Krause,

Thanks for your comment.

I like your idea of rendering the text in orange to call out tags that need attention. And, I agree that no standard is going to fix the world&#039;s problems. I just don&#039;t want a standard to perpetuate problems, and I think leaving tags that are solely representational does that.

There is a trade-off between allowing, then &quot;correcting,&quot; this kind of markup versus not allowing it, but possibly getting other kinds of tag abuse. Given that trade-off, I prefer the second choice, at least with professional writers, though that may put me in the minority.</description>
		<content:encoded><![CDATA[<p>To: Gunnar Krause,</p>
<p>Thanks for your comment.</p>
<p>I like your idea of rendering the text in orange to call out tags that need attention. And, I agree that no standard is going to fix the world&#8217;s problems. I just don&#8217;t want a standard to perpetuate problems, and I think leaving tags that are solely representational does that.</p>
<p>There is a trade-off between allowing, then &#8220;correcting,&#8221; this kind of markup versus not allowing it, but possibly getting other kinds of tag abuse. Given that trade-off, I prefer the second choice, at least with professional writers, though that may put me in the minority.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gunnar H. Krause</title>
		<link>http://xmlpress.net/2009/03/31/practical-dita-book-review/comment-page-1/#comment-17</link>
		<dc:creator>Gunnar H. Krause</dc:creator>
		<pubDate>Sun, 12 Apr 2009 21:41:25 +0000</pubDate>
		<guid isPermaLink="false">http://xmlpress.net/?p=146#comment-17</guid>
		<description>If something is a standard it typically contains more than anyone needs to make everyone happy. And this is the implementation task: understand the standard, take what you need to achieve your goal and drop what will be hazardous in your circumstances. Maybe you know this one: A fool with a tool stays a fool. Do not expect DITA or any standard to change the whole world to be good. The law of thermodynamics expects you to invest energy to fight the chaos. And dropping the domain that contains underline, bold, italic, superscript and subscript is even less than a specialization, it is a matter of configuration. 
By the way: I do allow these tags but I render the text in orange in the XML editor as a warning. I know that engineers who know and use these tags typically have no idea what semantically meaningful tag I expect them to use. In 80% of the abuse I can correct and in all others I have to ask. Without those tags the words would be untagged forever. Not a good solution eihter, is it?</description>
		<content:encoded><![CDATA[<p>If something is a standard it typically contains more than anyone needs to make everyone happy. And this is the implementation task: understand the standard, take what you need to achieve your goal and drop what will be hazardous in your circumstances. Maybe you know this one: A fool with a tool stays a fool. Do not expect DITA or any standard to change the whole world to be good. The law of thermodynamics expects you to invest energy to fight the chaos. And dropping the domain that contains underline, bold, italic, superscript and subscript is even less than a specialization, it is a matter of configuration.<br />
By the way: I do allow these tags but I render the text in orange in the XML editor as a warning. I know that engineers who know and use these tags typically have no idea what semantically meaningful tag I expect them to use. In 80% of the abuse I can correct and in all others I have to ask. Without those tags the words would be untagged forever. Not a good solution eihter, is it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Hamilton</title>
		<link>http://xmlpress.net/2009/03/31/practical-dita-book-review/comment-page-1/#comment-6</link>
		<dc:creator>Richard Hamilton</dc:creator>
		<pubDate>Sun, 05 Apr 2009 19:55:00 +0000</pubDate>
		<guid isPermaLink="false">http://xmlpress.net/?p=146#comment-6</guid>
		<description>To: D. Hoskins,

Thanks for your note (I edited your first comment to escape the italic and bold tags).

I see the point, though it concerns me that authors can so easily fall back on those tags. I guess if I were doing a specialization, the first thing I&#039;d do would be to remove the representational tags.  I&#039;ll check out the search you recommend.</description>
		<content:encoded><![CDATA[<p>To: D. Hoskins,</p>
<p>Thanks for your note (I edited your first comment to escape the italic and bold tags).</p>
<p>I see the point, though it concerns me that authors can so easily fall back on those tags. I guess if I were doing a specialization, the first thing I&#8217;d do would be to remove the representational tags.  I&#8217;ll check out the search you recommend.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: D. Hoskins</title>
		<link>http://xmlpress.net/2009/03/31/practical-dita-book-review/comment-page-1/#comment-5</link>
		<dc:creator>D. Hoskins</dc:creator>
		<pubDate>Thu, 02 Apr 2009 14:52:26 +0000</pubDate>
		<guid isPermaLink="false">http://xmlpress.net/?p=146#comment-5</guid>
		<description>sorry, I should have escaped those tags for italic and bold in my comment, what I was trying to convey is &quot;The reason that DITA has italic and bold and other non-semantic markup tags...&quot;</description>
		<content:encoded><![CDATA[<p>sorry, I should have escaped those tags for italic and bold in my comment, what I was trying to convey is &#8220;The reason that DITA has italic and bold and other non-semantic markup tags&#8230;&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: D. Hoskins</title>
		<link>http://xmlpress.net/2009/03/31/practical-dita-book-review/comment-page-1/#comment-4</link>
		<dc:creator>D. Hoskins</dc:creator>
		<pubDate>Thu, 02 Apr 2009 14:50:29 +0000</pubDate>
		<guid isPermaLink="false">http://xmlpress.net/?p=146#comment-4</guid>
		<description>The reason that DITA has &lt;i&gt; and &lt;b&gt; and other non-semantic markup tags is that it is deliberately built upon pre-existing HTML tags at the base level. This facilitates migrating content from web pages to DITA, even though it does not enrich the XML in a meaningful way. The web content has to be XHTML-conformant before it is migrated to DITA. You can find information on migration strategies online by searching on &quot;migrate HTML to DITA&quot;.</description>
		<content:encoded><![CDATA[<p>The reason that DITA has &lt;i> and &lt;b> and other non-semantic markup tags is that it is deliberately built upon pre-existing HTML tags at the base level. This facilitates migrating content from web pages to DITA, even though it does not enrich the XML in a meaningful way. The web content has to be XHTML-conformant before it is migrated to DITA. You can find information on migration strategies online by searching on &#8220;migrate HTML to DITA&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Managing Writers &#187; Practical DITA</title>
		<link>http://xmlpress.net/2009/03/31/practical-dita-book-review/comment-page-1/#comment-2</link>
		<dc:creator>Managing Writers &#187; Practical DITA</dc:creator>
		<pubDate>Thu, 02 Apr 2009 00:25:55 +0000</pubDate>
		<guid isPermaLink="false">http://xmlpress.net/?p=146#comment-2</guid>
		<description>[...] The short review is that if you are brand new to DITA, but understand at least a little bit about markup languages (basic HTML is probably enough), this is a good place to start. It is a short excursion through the DITA philosophy and basic usage. For my full review, go here. [...]</description>
		<content:encoded><![CDATA[<p>[...] The short review is that if you are brand new to DITA, but understand at least a little bit about markup languages (basic HTML is probably enough), this is a good place to start. It is a short excursion through the DITA philosophy and basic usage. For my full review, go here. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
