<?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"
	>
<channel>
	<title>Comments on: Slip up in federal filing leads to $5,000 sanction</title>
	<atom:link href="http://minnlawyer.com/minnlawyerblog//2009/10/23/slip-up-in-federal-filing-leads-to-5000-sanction/feed/" rel="self" type="application/rss+xml" />
	<link>http://minnlawyer.com/minnlawyerblog/2009/10/23/slip-up-in-federal-filing-leads-to-5000-sanction/</link>
	<description>If it’s legal, you can discuss it here</description>
	<pubDate>Fri, 30 Jul 2010 15:46:30 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Newly Minted 2009</title>
		<link>http://minnlawyer.com/minnlawyerblog/2009/10/23/slip-up-in-federal-filing-leads-to-5000-sanction/#comment-969</link>
		<dc:creator>Newly Minted 2009</dc:creator>
		<pubDate>Mon, 26 Oct 2009 19:35:19 +0000</pubDate>
		<guid isPermaLink="false">http://minnlawyerblog.com/?p=3887#comment-969</guid>
		<description>that's pretty funny Mark;  thanks for the laugh!</description>
		<content:encoded><![CDATA[<p>that&#8217;s pretty funny Mark;  thanks for the laugh!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Cohen</title>
		<link>http://minnlawyer.com/minnlawyerblog/2009/10/23/slip-up-in-federal-filing-leads-to-5000-sanction/#comment-968</link>
		<dc:creator>Mark Cohen</dc:creator>
		<pubDate>Mon, 26 Oct 2009 18:24:24 +0000</pubDate>
		<guid isPermaLink="false">http://minnlawyerblog.com/?p=3887#comment-968</guid>
		<description>LOL!  Although your comment does remind me of the software we use for HR purposes, which assumes you are acting with nefarious intent if you use the word "pretty" in a performance review (as in "a pretty good job, or "a pretty important element"). When I use the word, I invariably get asked, "Are you sure you really want to say that?"  The program no doubt fails to see the humor of my mental response, which is always "pretty sure" ....</description>
		<content:encoded><![CDATA[<p>LOL!  Although your comment does remind me of the software we use for HR purposes, which assumes you are acting with nefarious intent if you use the word &#8220;pretty&#8221; in a performance review (as in &#8220;a pretty good job, or &#8220;a pretty important element&#8221;). When I use the word, I invariably get asked, &#8220;Are you sure you really want to say that?&#8221;  The program no doubt fails to see the humor of my mental response, which is always &#8220;pretty sure&#8221; &#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Newly Minted 2009</title>
		<link>http://minnlawyer.com/minnlawyerblog/2009/10/23/slip-up-in-federal-filing-leads-to-5000-sanction/#comment-967</link>
		<dc:creator>Newly Minted 2009</dc:creator>
		<pubDate>Mon, 26 Oct 2009 18:18:08 +0000</pubDate>
		<guid isPermaLink="false">http://minnlawyerblog.com/?p=3887#comment-967</guid>
		<description>Anon, maybe this is a job for Microsoft Word's "Clippy."

http://upload.wikimedia.org/wikipedia/en/d/db/Clippy-letter.PNG

"It appears you're writing a motion and have included an SSN.  Would you like me to:
[ ] follow the FRCP
[ ] notify the professional responsibility board
[ ] . . . "</description>
		<content:encoded><![CDATA[<p>Anon, maybe this is a job for Microsoft Word&#8217;s &#8220;Clippy.&#8221;</p>
<p><a href="http://upload.wikimedia.org/wikipedia/en/d/db/Clippy-letter.PNG" rel="nofollow">http://upload.wikimedia.org/wikipedia/en/d/db/Clippy-letter.PNG</a></p>
<p>&#8220;It appears you&#8217;re writing a motion and have included an SSN.  Would you like me to:<br />
[ ] follow the FRCP<br />
[ ] notify the professional responsibility board<br />
[ ] . . . &#8220;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: anon</title>
		<link>http://minnlawyer.com/minnlawyerblog/2009/10/23/slip-up-in-federal-filing-leads-to-5000-sanction/#comment-966</link>
		<dc:creator>anon</dc:creator>
		<pubDate>Mon, 26 Oct 2009 11:37:55 +0000</pubDate>
		<guid isPermaLink="false">http://minnlawyerblog.com/?p=3887#comment-966</guid>
		<description>Newly, I'm guessing getting the gov to change their system might be tough. How about selling a program to law firms (like RKMC) that could scan their PDFs for SSNs to avoid sanctions and bad publicity?</description>
		<content:encoded><![CDATA[<p>Newly, I&#8217;m guessing getting the gov to change their system might be tough. How about selling a program to law firms (like RKMC) that could scan their PDFs for SSNs to avoid sanctions and bad publicity?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Newly Minted 2009</title>
		<link>http://minnlawyer.com/minnlawyerblog/2009/10/23/slip-up-in-federal-filing-leads-to-5000-sanction/#comment-965</link>
		<dc:creator>Newly Minted 2009</dc:creator>
		<pubDate>Sat, 24 Oct 2009 23:44:57 +0000</pubDate>
		<guid isPermaLink="false">http://minnlawyerblog.com/?p=3887#comment-965</guid>
		<description>Well, Anon, we can shift the burden on the filers.  True.  But everyone makes mistakes.  Particularly partners who have associates they are relying on to file things for them.  Why penalize these honorable souls for simple mistakes when we could, via technology, provide a warning?
I'm not kidding when I say that for $5k I could easily detect social security numbers.  Any programmer worth their salt could implement this in a few dozen hours.  That it hasn't been done is a testament for shifting the burden to attorneys.
Now granted, the attorney must follow the FRCP;  but here we have the ultimate case of where the rule is easily coded and could prevent the kind of embarrassment we see here.
Ultimately I have a lot of sympathy for Vincent Moccio:  there's no reason the software could detect this and warn the filer, provided the PDF is not merely an un-OCR'd scan.</description>
		<content:encoded><![CDATA[<p>Well, Anon, we can shift the burden on the filers.  True.  But everyone makes mistakes.  Particularly partners who have associates they are relying on to file things for them.  Why penalize these honorable souls for simple mistakes when we could, via technology, provide a warning?<br />
I&#8217;m not kidding when I say that for $5k I could easily detect social security numbers.  Any programmer worth their salt could implement this in a few dozen hours.  That it hasn&#8217;t been done is a testament for shifting the burden to attorneys.<br />
Now granted, the attorney must follow the FRCP;  but here we have the ultimate case of where the rule is easily coded and could prevent the kind of embarrassment we see here.<br />
Ultimately I have a lot of sympathy for Vincent Moccio:  there&#8217;s no reason the software could detect this and warn the filer, provided the PDF is not merely an un-OCR&#8217;d scan.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Maury Landsman</title>
		<link>http://minnlawyer.com/minnlawyerblog/2009/10/23/slip-up-in-federal-filing-leads-to-5000-sanction/#comment-959</link>
		<dc:creator>Maury Landsman</dc:creator>
		<pubDate>Sat, 24 Oct 2009 18:36:25 +0000</pubDate>
		<guid isPermaLink="false">http://minnlawyerblog.com/?p=3887#comment-959</guid>
		<description>If I remember correctly, there is some case law "In re Tutu Wells" in the 3rd Circuit holding that  a district court cannot order sanctions paid to a non-party community organization. The case has a long history so that may not still be good law.</description>
		<content:encoded><![CDATA[<p>If I remember correctly, there is some case law &#8220;In re Tutu Wells&#8221; in the 3rd Circuit holding that  a district court cannot order sanctions paid to a non-party community organization. The case has a long history so that may not still be good law.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anon</title>
		<link>http://minnlawyer.com/minnlawyerblog/2009/10/23/slip-up-in-federal-filing-leads-to-5000-sanction/#comment-960</link>
		<dc:creator>Anon</dc:creator>
		<pubDate>Sat, 24 Oct 2009 12:38:17 +0000</pubDate>
		<guid isPermaLink="false">http://minnlawyerblog.com/?p=3887#comment-960</guid>
		<description>One could certainly automate the system to OCR PDFs to search for SSNs and reject filings that include them. On the other hand, who wants to pay for that?  (And it is certain to cost more than estimated.)

Isn't it much easier to do just what the Court's done and shift the burden onto filers?  RKMC is a great firm that's done very well for a long time and can afford to be the poster-child here, both financially and reputationally.</description>
		<content:encoded><![CDATA[<p>One could certainly automate the system to OCR PDFs to search for SSNs and reject filings that include them. On the other hand, who wants to pay for that?  (And it is certain to cost more than estimated.)</p>
<p>Isn&#8217;t it much easier to do just what the Court&#8217;s done and shift the burden onto filers?  RKMC is a great firm that&#8217;s done very well for a long time and can afford to be the poster-child here, both financially and reputationally.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Newly Minted 2009</title>
		<link>http://minnlawyer.com/minnlawyerblog/2009/10/23/slip-up-in-federal-filing-leads-to-5000-sanction/#comment-964</link>
		<dc:creator>Newly Minted 2009</dc:creator>
		<pubDate>Fri, 23 Oct 2009 17:46:04 +0000</pubDate>
		<guid isPermaLink="false">http://minnlawyerblog.com/?p=3887#comment-964</guid>
		<description>It may still work for PDFs.

Some (most?) PDFs have text stored in them that can be scanned.  For example, if they are generated from a word processor or other such tool.  (On a Macintosh, one can print to a PDF;  that preserves text.)  So in that case, it would still work.

If the PDF's are only images, such as from a scanner, without any optical character recognition done, then it would not be able to detect possible social security #s.</description>
		<content:encoded><![CDATA[<p>It may still work for PDFs.</p>
<p>Some (most?) PDFs have text stored in them that can be scanned.  For example, if they are generated from a word processor or other such tool.  (On a Macintosh, one can print to a PDF;  that preserves text.)  So in that case, it would still work.</p>
<p>If the PDF&#8217;s are only images, such as from a scanner, without any optical character recognition done, then it would not be able to detect possible social security #s.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ECF filer</title>
		<link>http://minnlawyer.com/minnlawyerblog/2009/10/23/slip-up-in-federal-filing-leads-to-5000-sanction/#comment-963</link>
		<dc:creator>ECF filer</dc:creator>
		<pubDate>Fri, 23 Oct 2009 17:18:45 +0000</pubDate>
		<guid isPermaLink="false">http://minnlawyerblog.com/?p=3887#comment-963</guid>
		<description>Newly Minted, the ECF filing system requires you to file PDFs. :)</description>
		<content:encoded><![CDATA[<p>Newly Minted, the ECF filing system requires you to file PDFs. <img src='http://minnlawyer.com/minnlawyerblog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Newly Minted 2009</title>
		<link>http://minnlawyer.com/minnlawyerblog/2009/10/23/slip-up-in-federal-filing-leads-to-5000-sanction/#comment-962</link>
		<dc:creator>Newly Minted 2009</dc:creator>
		<pubDate>Fri, 23 Oct 2009 17:14:59 +0000</pubDate>
		<guid isPermaLink="false">http://minnlawyerblog.com/?p=3887#comment-962</guid>
		<description>Come to think  of it, maybe I should just contact the Gov't and get myself some work ... ;-)</description>
		<content:encoded><![CDATA[<p>Come to think  of it, maybe I should just contact the Gov&#8217;t and get myself some work &#8230; <img src='http://minnlawyer.com/minnlawyerblog/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
</channel>
</rss>