<?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: &#8220;Certify&#8221;</title>
	<atom:link href="http://www.adamsdrafting.com/2006/08/03/certify/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adamsdrafting.com/2006/08/03/certify/</link>
	<description></description>
	<lastBuildDate>Tue, 31 Jan 2012 01:23:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
	<item>
		<title>By: Ken Adams</title>
		<link>http://www.adamsdrafting.com/2006/08/03/certify/comment-page-1/#comment-97</link>
		<dc:creator>Ken Adams</dc:creator>
		<pubDate>Fri, 04 Aug 2006 15:30:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2006/08/03/certify/#comment-97</guid>
		<description>Mary: That we&#039;re having this exchange suggests to me that &quot;certify&quot; is vague in terms of the level of formality required. I suggest that the clearest option would be to reserve &quot;certify&quot; for when a measure of formality is required and to use a simpler word in other contexts.</description>
		<content:encoded><![CDATA[<p>Mary: That we&#8217;re having this exchange suggests to me that &#8220;certify&#8221; is vague in terms of the level of formality required. I suggest that the clearest option would be to reserve &#8220;certify&#8221; for when a measure of formality is required and to use a simpler word in other contexts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mary</title>
		<link>http://www.adamsdrafting.com/2006/08/03/certify/comment-page-1/#comment-95</link>
		<dc:creator>Mary</dc:creator>
		<pubDate>Fri, 04 Aug 2006 02:25:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2006/08/03/certify/#comment-95</guid>
		<description>In my many years as an engineer in pharmaceutical, chemical, and other industries, I have often &quot;certified&quot; that a procedure was followed, a device was successfully tested, a production process was acceptable for use, etc. The specific word &quot;certify&quot; was commonly used in the protocol, standard operating procedures, or qualification documents.

In almost all cases the certification was simply a matter of signing a one sentence statement, or signing and dating a statement on the SOP or protocol form. On some software checkouts I would make over a dozen &quot;certifications&quot;, many simply initials in blanks and an a signature on a form.

In no case was any special document cluttered with legaldegook (or engineeringdegook) required. I think that if the work &quot;certify&quot; can be used in routine SOPs, protocols, and other engineering procedures, it certainly can be used in contracts. It does not, at least to me and others in my field, imply any special formality.

Mary</description>
		<content:encoded><![CDATA[<p>In my many years as an engineer in pharmaceutical, chemical, and other industries, I have often &#8220;certified&#8221; that a procedure was followed, a device was successfully tested, a production process was acceptable for use, etc. The specific word &#8220;certify&#8221; was commonly used in the protocol, standard operating procedures, or qualification documents.</p>
<p>In almost all cases the certification was simply a matter of signing a one sentence statement, or signing and dating a statement on the SOP or protocol form. On some software checkouts I would make over a dozen &#8220;certifications&#8221;, many simply initials in blanks and an a signature on a form.</p>
<p>In no case was any special document cluttered with legaldegook (or engineeringdegook) required. I think that if the work &#8220;certify&#8221; can be used in routine SOPs, protocols, and other engineering procedures, it certainly can be used in contracts. It does not, at least to me and others in my field, imply any special formality.</p>
<p>Mary</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Adams</title>
		<link>http://www.adamsdrafting.com/2006/08/03/certify/comment-page-1/#comment-93</link>
		<dc:creator>Ken Adams</dc:creator>
		<pubDate>Thu, 03 Aug 2006 15:10:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2006/08/03/certify/#comment-93</guid>
		<description>Eric&#039;s useful comment shows that when you&#039;re redrafting a contract, it&#039;s best to have available industry-specific expertise in addition to serious drafting chops.</description>
		<content:encoded><![CDATA[<p>Eric&#8217;s useful comment shows that when you&#8217;re redrafting a contract, it&#8217;s best to have available industry-specific expertise in addition to serious drafting chops.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Goldman</title>
		<link>http://www.adamsdrafting.com/2006/08/03/certify/comment-page-1/#comment-92</link>
		<dc:creator>Eric Goldman</dc:creator>
		<pubDate>Thu, 03 Aug 2006 15:04:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2006/08/03/certify/#comment-92</guid>
		<description>I&#039;ve seen these type of post-agreement certification requirements in dozens (hundreds?) of contracts.  In my 12 years of practice, I&#039;ve never actually had anyone request one.  So in most/all cases, I think the entire clause should be omitted.  Eric.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve seen these type of post-agreement certification requirements in dozens (hundreds?) of contracts.  In my 12 years of practice, I&#8217;ve never actually had anyone request one.  So in most/all cases, I think the entire clause should be omitted.  Eric.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

