<?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: ISO 9001 Documentation</title>
	<atom:link href="http://www.qicguru.com/business/1057-iso-9001-documentation/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.qicguru.com/business/1057-iso-9001-documentation/</link>
	<description>ISO 9001:2008/AS9100 Quality Management Information</description>
	<lastBuildDate>Sat, 15 May 2010 07:36:49 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Oussama</title>
		<link>http://www.qicguru.com/business/1057-iso-9001-documentation/comment-page-1/#comment-36</link>
		<dc:creator>Oussama</dc:creator>
		<pubDate>Mon, 11 Jan 2010 17:08:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.qicguru.com/?p=1057#comment-36</guid>
		<description>Documentation is always a problem, not so much in the control of revisions and content but in the depth and complexity of the content. In the 1980s the aviation industry worked on what was termed as Simple English. It was meant to provide a limited number of words that defined required actions without any confusion. Publications should be written in a clear and concise manner. Complex issues will require somewhat complex documentation but on the whole it should remain simple. A lot of people don&#039;t like to read, so it is better to offer them simple easy to read and com[prehend.</description>
		<content:encoded><![CDATA[<p>Documentation is always a problem, not so much in the control of revisions and content but in the depth and complexity of the content. In the 1980s the aviation industry worked on what was termed as Simple English. It was meant to provide a limited number of words that defined required actions without any confusion. Publications should be written in a clear and concise manner. Complex issues will require somewhat complex documentation but on the whole it should remain simple. A lot of people don&#8217;t like to read, so it is better to offer them simple easy to read and com[prehend.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
