<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Does Data Matching Qualify as Identity Resolution?</title>
	<link>http://identityresolutiondaily.com/452/does-data-matching-qualify-as-identity-resolution/</link>
	<description>All About Identity and Entity Resolution</description>
	<pubDate>Sun, 12 Feb 2012 12:29:27 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2</generator>

	<item>
		<title>By: Bob Barker</title>
		<link>http://identityresolutiondaily.com/452/does-data-matching-qualify-as-identity-resolution/#comment-615</link>
		<author>Bob Barker</author>
		<pubDate>Wed, 21 Jan 2009 20:08:07 +0000</pubDate>
		<guid>http://identityresolutiondaily.com/452/does-data-matching-qualify-as-identity-resolution/#comment-615</guid>
		<description>There's too much to say here, so I'm going to respond to this in another post.</description>
		<content:encoded><![CDATA[<p>There&#8217;s too much to say here, so I&#8217;m going to respond to this in another post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Allen</title>
		<link>http://identityresolutiondaily.com/452/does-data-matching-qualify-as-identity-resolution/#comment-614</link>
		<author>Tom Allen</author>
		<pubDate>Wed, 21 Jan 2009 05:11:10 +0000</pubDate>
		<guid>http://identityresolutiondaily.com/452/does-data-matching-qualify-as-identity-resolution/#comment-614</guid>
		<description>Interesting.  So what Identity Resolution consists of is a bunch of data standardization tables and a matching tool?  Seems like a name equivalence table and a color equivalence table and any of the off the shelf matching tools would solve your problem.  That is a pretty trivial solution to a pretty complicated problem.  Thanks for you insight</description>
		<content:encoded><![CDATA[<p>Interesting.  So what Identity Resolution consists of is a bunch of data standardization tables and a matching tool?  Seems like a name equivalence table and a color equivalence table and any of the off the shelf matching tools would solve your problem.  That is a pretty trivial solution to a pretty complicated problem.  Thanks for you insight</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Power</title>
		<link>http://identityresolutiondaily.com/452/does-data-matching-qualify-as-identity-resolution/#comment-610</link>
		<author>Dan Power</author>
		<pubDate>Wed, 14 Jan 2009 19:39:35 +0000</pubDate>
		<guid>http://identityresolutiondaily.com/452/does-data-matching-qualify-as-identity-resolution/#comment-610</guid>
		<description>Interesting post, Doug. 

I got very familiar with D&#38;B's matching capabilities during the three years I was there, and it always struck me that "matching" was one of those simple words that meant different things to different people. 

I think you're right that the simpler data matching tools are trying to position themselves "up market" as full-fledged identity resolution engines, but there's a world of difference between a match engine (some of which can have very simple capabilities) and the Infoglide identity resolution engine. 

What's interesting to me now is, when does a simple matching tool (such as the ones built into the typical MDM hubs) suffice, and when do you have to put that aside for the more robust capabilities such as those that Infoglide provides. 

One application would be for anything mission critical - a Terrorist Watch List, or a Enterprise Master Patient Index - that type of thing. 

But I think another indicator is sheer volume.  If a simpler match engine fails to match even 10% of your records, and you've got a million records total, then you've got to deal (somehow) with 100,000 exceptions. That can be pretty daunting! 

So people in the MDM space should be on the lookout for the indicators that a simpler match engine won't suffice, and be aware of more sophisticated products like Infoglide. 

Best regards --- Dan</description>
		<content:encoded><![CDATA[<p>Interesting post, Doug. </p>
<p>I got very familiar with D&amp;B&#8217;s matching capabilities during the three years I was there, and it always struck me that &#8220;matching&#8221; was one of those simple words that meant different things to different people. </p>
<p>I think you&#8217;re right that the simpler data matching tools are trying to position themselves &#8220;up market&#8221; as full-fledged identity resolution engines, but there&#8217;s a world of difference between a match engine (some of which can have very simple capabilities) and the Infoglide identity resolution engine. </p>
<p>What&#8217;s interesting to me now is, when does a simple matching tool (such as the ones built into the typical MDM hubs) suffice, and when do you have to put that aside for the more robust capabilities such as those that Infoglide provides. </p>
<p>One application would be for anything mission critical - a Terrorist Watch List, or a Enterprise Master Patient Index - that type of thing. </p>
<p>But I think another indicator is sheer volume.  If a simpler match engine fails to match even 10% of your records, and you&#8217;ve got a million records total, then you&#8217;ve got to deal (somehow) with 100,000 exceptions. That can be pretty daunting! </p>
<p>So people in the MDM space should be on the lookout for the indicators that a simpler match engine won&#8217;t suffice, and be aware of more sophisticated products like Infoglide. </p>
<p>Best regards &#8212; Dan</p>
]]></content:encoded>
	</item>
</channel>
</rss>

