<?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, Metadata Maturity and the Case for Taxonomy</title>
	<atom:link href="http://thecontentwrangler.com/2010/01/07/dita-metadata-maturity-and-the-case-for-taxonomy/feed/" rel="self" type="application/rss+xml" />
	<link>http://thecontentwrangler.com/2010/01/07/dita-metadata-maturity-and-the-case-for-taxonomy/</link>
	<description>Content is a business asset worthy of being managed</description>
	<lastBuildDate>Fri, 18 May 2012 01:51:49 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Mark Lewis</title>
		<link>http://thecontentwrangler.com/2010/01/07/dita-metadata-maturity-and-the-case-for-taxonomy/comment-page-1/#comment-571</link>
		<dc:creator>Mark Lewis</dc:creator>
		<pubDate>Tue, 12 Jan 2010 18:30:24 +0000</pubDate>
		<guid isPermaLink="false">http://thecontentwrangler.com/?p=3283#comment-571</guid>
		<description>An excellent and timely article.

I&#039;d like to emphasize that successful retrieval of content is going to be a combination of a well planned retrieval metadata strategy and a flexibile and robust query tool. Optimally, you would like to have a query designer. One that would let you create queries like: Find all the paragraphs whose audience is set to &quot;engineering&quot;. Find all the paragraphs in a Task Result whose audience is set to &quot;engineering&quot;. Find all the paragraphs in a Task Result whose audience is set to &quot;engineering&quot; and return the results as a list of topics. Find all the paragraphs in a Task Result whose audience is set to &quot;engineering&quot; and return the results as a map of topics. Findability will come from having both good metadata and a good query tool.

When is a technical writer like a database administrator? When their content is in XML.

Mark Lewis
&quot;DITA Metrics&quot;</description>
		<content:encoded><![CDATA[<p>An excellent and timely article.</p>
<p>I&#8217;d like to emphasize that successful retrieval of content is going to be a combination of a well planned retrieval metadata strategy and a flexibile and robust query tool. Optimally, you would like to have a query designer. One that would let you create queries like: Find all the paragraphs whose audience is set to &#8220;engineering&#8221;. Find all the paragraphs in a Task Result whose audience is set to &#8220;engineering&#8221;. Find all the paragraphs in a Task Result whose audience is set to &#8220;engineering&#8221; and return the results as a list of topics. Find all the paragraphs in a Task Result whose audience is set to &#8220;engineering&#8221; and return the results as a map of topics. Findability will come from having both good metadata and a good query tool.</p>
<p>When is a technical writer like a database administrator? When their content is in XML.</p>
<p>Mark Lewis<br />
&#8220;DITA Metrics&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

