<?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: Adding Electronic Signatures to Contracts</title>
	<atom:link href="http://www.adamsdrafting.com/2007/02/02/signing-contracts-electronically/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adamsdrafting.com/2007/02/02/signing-contracts-electronically/</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: Rob McFarlane</title>
		<link>http://www.adamsdrafting.com/2007/02/02/signing-contracts-electronically/comment-page-1/#comment-3991</link>
		<dc:creator>Rob McFarlane</dc:creator>
		<pubDate>Mon, 30 Apr 2007 22:47:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2007/02/02/signing-contracts-electronically/#comment-3991</guid>
		<description>One of the suggetions that I was told about the copying of electronic scanned signatures was to minimize the scanned in signature, save it, and then blow it up larger so that it looked fuzzy or distorted.  The idea was that if it was re-used it would be obvious to any third party that it was not a proper signature.  I am hesitant about using the signature nevertheless, even with these measures, even though some customers are requesting e-filing of competitive bid documentation.</description>
		<content:encoded><![CDATA[<p>One of the suggetions that I was told about the copying of electronic scanned signatures was to minimize the scanned in signature, save it, and then blow it up larger so that it looked fuzzy or distorted.  The idea was that if it was re-used it would be obvious to any third party that it was not a proper signature.  I am hesitant about using the signature nevertheless, even with these measures, even though some customers are requesting e-filing of competitive bid documentation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Fleming</title>
		<link>http://www.adamsdrafting.com/2007/02/02/signing-contracts-electronically/comment-page-1/#comment-2345</link>
		<dc:creator>Michael Fleming</dc:creator>
		<pubDate>Mon, 05 Feb 2007 18:39:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2007/02/02/signing-contracts-electronically/#comment-2345</guid>
		<description>Although it&#039;s a distinction I&#039;m not sure all would necessarily recognize, I&#039;d distinguish Dennis&#039; discussion of how to take an electronic document and &#039;sign&#039; it by application of some technology such as Adobe&#039;s versus a discussion of so-called &#039;electronic contracts&#039; (e.g., the ubiquitous click-through agreement).
  
When I saw the original headline about &#039;signing contracts electronically&#039; I immediately presumed Ken was going to discuss the latter subject, not
the former.  (Ken later changed the headline to clarify the point.)

My take: From a purely legal perspective, the Adobe technology is not all that interesting -- It&#039;s just a better pencil, not a paradigm shift.

That said... I note that &#039;signature&#039; under the UCC, UETA, eSign and many other statutes, does not require anything so elaborate as Adobe&#039;s system to be a &#039;signature&#039; for legal purposes.  Simply typing X at the bottom of an email, so long as it is intended by the person who did that X&#039;ing to be his signature, makes it legally a &#039;signature.&#039; Adobe&#039;s contribution to the technology does not make it any more of a &#039;signature&#039; -- It might add to a third-party&#039;s potential willingness to ACCEPT that as so-and-so&#039;s signature, but it doesn&#039;t alter the legal status of something as having been a signature.  

In other words, what&#039;s a &#039;signature&#039; is purely an investigation into the intent of the purported signer, and not of the technology (or lack thereof) used to create that signature.</description>
		<content:encoded><![CDATA[<p>Although it&#8217;s a distinction I&#8217;m not sure all would necessarily recognize, I&#8217;d distinguish Dennis&#8217; discussion of how to take an electronic document and &#8216;sign&#8217; it by application of some technology such as Adobe&#8217;s versus a discussion of so-called &#8216;electronic contracts&#8217; (e.g., the ubiquitous click-through agreement).</p>
<p>When I saw the original headline about &#8216;signing contracts electronically&#8217; I immediately presumed Ken was going to discuss the latter subject, not<br />
the former.  (Ken later changed the headline to clarify the point.)</p>
<p>My take: From a purely legal perspective, the Adobe technology is not all that interesting &#8212; It&#8217;s just a better pencil, not a paradigm shift.</p>
<p>That said&#8230; I note that &#8216;signature&#8217; under the UCC, UETA, eSign and many other statutes, does not require anything so elaborate as Adobe&#8217;s system to be a &#8216;signature&#8217; for legal purposes.  Simply typing X at the bottom of an email, so long as it is intended by the person who did that X&#8217;ing to be his signature, makes it legally a &#8216;signature.&#8217; Adobe&#8217;s contribution to the technology does not make it any more of a &#8216;signature&#8217; &#8212; It might add to a third-party&#8217;s potential willingness to ACCEPT that as so-and-so&#8217;s signature, but it doesn&#8217;t alter the legal status of something as having been a signature.  </p>
<p>In other words, what&#8217;s a &#8216;signature&#8217; is purely an investigation into the intent of the purported signer, and not of the technology (or lack thereof) used to create that signature.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://www.adamsdrafting.com/2007/02/02/signing-contracts-electronically/comment-page-1/#comment-2269</link>
		<dc:creator>David</dc:creator>
		<pubDate>Sat, 03 Feb 2007 05:24:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2007/02/02/signing-contracts-electronically/#comment-2269</guid>
		<description>Images of your handwritten signature are easily copied electronically.  There&#039;s no way to protect it from copying once it&#039;s displayed on someone&#039;s computer (simple image capture using imaging software) or when printed and then scanned back in.

Once you have the image, you can then paste it into as many different documents as you want -- for electronic look-alikes, or for then printing back onto paper documents.

You might do well to read:

http://www.yozons.com/pub/features/signatures3.jsp

Good luck!</description>
		<content:encoded><![CDATA[<p>Images of your handwritten signature are easily copied electronically.  There&#8217;s no way to protect it from copying once it&#8217;s displayed on someone&#8217;s computer (simple image capture using imaging software) or when printed and then scanned back in.</p>
<p>Once you have the image, you can then paste it into as many different documents as you want &#8212; for electronic look-alikes, or for then printing back onto paper documents.</p>
<p>You might do well to read:</p>
<p><a href="http://www.yozons.com/pub/features/signatures3.jsp" rel="nofollow">http://www.yozons.com/pub/features/signatures3.jsp</a></p>
<p>Good luck!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

