<?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: Free Pacer? - The implications (guest post)</title>
	<atom:link href="http://blog.justiceserved.com/?feed=rss2&#038;p=487" rel="self" type="application/rss+xml" />
	<link>http://blog.justiceserved.com/?p=487</link>
	<description>A blog from Justice Served.</description>
	<pubDate>Thu, 09 Sep 2010 20:05:09 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: G. Thomas Sandbach</title>
		<link>http://blog.justiceserved.com/?p=487#comment-3629</link>
		<dc:creator>G. Thomas Sandbach</dc:creator>
		<pubDate>Mon, 19 Oct 2009 16:01:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.justiceserved.com/?p=487#comment-3629</guid>
		<description>@Rasmussen - Thanks for your comments. I apologize for understating the ability of automated redaction tools to identify and redact specific types of data. I am not an expert in redaction, but common sense suggests some potential factors bear on redaction success rates:

- Data to be redacted. Generalized data types are easier to recognize than specific data types. Recognizing proper names is different than finding all proper names. Not all dates are birth dates. As a result, in order to redact home addresses, but not those of businesses, the tool must be able to understand these data items in context. 

- Document types. Context is easier to recognize in some documents than in others. In forms, for instance, a field may be labeled "DOB", enabling software to identify a date in proximity as a birth date. I'm sure that the identification task becomes more difficult as contents become more complex. Registration forms present less of a challenge than depositions, for instance.

- Accuracy. The white papers on your website suggest that redaction of a given document can provide different (and predictable) levels of confidence in the results of data to be redacted. Those confidence levels would apparently reflect a combination of the success of the automated tool and the amount of verification necessary to produce a finished product. 

My initial statement obviously failed to reflect that level of complexity.</description>
		<content:encoded><![CDATA[<p>@Rasmussen - Thanks for your comments. I apologize for understating the ability of automated redaction tools to identify and redact specific types of data. I am not an expert in redaction, but common sense suggests some potential factors bear on redaction success rates:</p>
<p>- Data to be redacted. Generalized data types are easier to recognize than specific data types. Recognizing proper names is different than finding all proper names. Not all dates are birth dates. As a result, in order to redact home addresses, but not those of businesses, the tool must be able to understand these data items in context. </p>
<p>- Document types. Context is easier to recognize in some documents than in others. In forms, for instance, a field may be labeled &#8220;DOB&#8221;, enabling software to identify a date in proximity as a birth date. I&#8217;m sure that the identification task becomes more difficult as contents become more complex. Registration forms present less of a challenge than depositions, for instance.</p>
<p>- Accuracy. The white papers on your website suggest that redaction of a given document can provide different (and predictable) levels of confidence in the results of data to be redacted. Those confidence levels would apparently reflect a combination of the success of the automated tool and the amount of verification necessary to produce a finished product. </p>
<p>My initial statement obviously failed to reflect that level of complexity.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: david rasmussen</title>
		<link>http://blog.justiceserved.com/?p=487#comment-3547</link>
		<dc:creator>david rasmussen</dc:creator>
		<pubDate>Tue, 06 Oct 2009 02:53:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.justiceserved.com/?p=487#comment-3547</guid>
		<description>Extract Systems has been providing redaction software to courts and other public and private entities for a long time.  The author incorrectly states that tools "don’t currently exist to identify and redact children’s names, account numbers, birth dates and home addresses".  These and more, are exactly the fields we DO redact (automatically).  For example, we handled 22 distinct field types for the New York Secretary of State.  Full disclosure... I am employed by Extract Systems.  For more information see www.extractsystems.com.</description>
		<content:encoded><![CDATA[<p>Extract Systems has been providing redaction software to courts and other public and private entities for a long time.  The author incorrectly states that tools &#8220;don’t currently exist to identify and redact children’s names, account numbers, birth dates and home addresses&#8221;.  These and more, are exactly the fields we DO redact (automatically).  For example, we handled 22 distinct field types for the New York Secretary of State.  Full disclosure&#8230; I am employed by Extract Systems.  For more information see <a href="http://www.extractsystems.com" rel="nofollow">http://www.extractsystems.com</a>.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
