<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Edelman, Mark</title>	<link>http://tc.eserver.org/authors/Edelman,_Mark</link>
	<description>A bibliography of works by Edelman, Mark in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Edelman, Mark</title>
		<link>http://tc.eserver.org/dir/Edelman,_Mark</link>
	</image>
	<item>
		<title>Standard Operating Procedures and the Technical Writer</title>
		<link>http://tc.eserver.org/19681.html</link>
		<guid>http://tc.eserver.org/19681.html</guid>
		<description>Standard operating procedures (SOPs) are sequences of steps for workers to follow to complete tasks. Owing to industry standards and government regulations, SOPs are increasingly in demand. The pharmaceutical sector is a case in point: Companies are expected to conform to GxP (good practices in manufacturing, testing, and other areas). A big part of GxP is the standardization and documentation of production tasks. The ISO 9000 conventions used in other industries have similar requirements. SOPs are typically required for activities such as operating or calibrating a machine, backing up data, testing samples, and requesting approvals of changes in systems.</description>
	</item>
	<item>
		<title>The Value Added by Technical Communicators</title>
		<link>http://tc.eserver.org/14696.html</link>
		<guid>http://tc.eserver.org/14696.html</guid>
		<description>Edelman lists several arguments technical communicators can use to specify the value they add to an organization.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Edelman,_Mark.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>