<?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: SSDI Access &#8211; Are You Ready To Rumble?</title>
	<atom:link href="http://geneabloggers.com/ssdi-access-ready-rumble/feed/" rel="self" type="application/rss+xml" />
	<link>http://geneabloggers.com/ssdi-access-ready-rumble/</link>
	<description>The ultimate site for your genealogy blog</description>
	<lastBuildDate>Sun, 19 May 2013 13:33:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Thelma Sayler</title>
		<link>http://geneabloggers.com/ssdi-access-ready-rumble/#comment-11352</link>
		<dc:creator>Thelma Sayler</dc:creator>
		<pubDate>Tue, 14 Feb 2012 00:16:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.geneabloggers.com/?p=17422#comment-11352</guid>
		<description><![CDATA[Please leave the ss and death notes as there are, thank you.]]></description>
		<content:encoded><![CDATA[<p>Please leave the ss and death notes as there are, thank you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martha Hennagin</title>
		<link>http://geneabloggers.com/ssdi-access-ready-rumble/#comment-11351</link>
		<dc:creator>Martha Hennagin</dc:creator>
		<pubDate>Tue, 07 Feb 2012 22:28:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.geneabloggers.com/?p=17422#comment-11351</guid>
		<description><![CDATA[Will they also ban obit notices?  Restrict the use of b. dates and d. deaths on headstones?  Restricting access is like a lock - it only keeps the honest man out. Identity thieves will find a way around any restriction. 

I also wonder how many identity thefts are from these records vs. credit cards and on line banking info. 

I sincerely hope a compromise can be worked out.  I can understand the SS Death Index (don&#039;t like it but understand it) but not the birth certs and death certs.]]></description>
		<content:encoded><![CDATA[<p>Will they also ban obit notices?  Restrict the use of b. dates and d. deaths on headstones?  Restricting access is like a lock &#8211; it only keeps the honest man out. Identity thieves will find a way around any restriction. </p>
<p>I also wonder how many identity thefts are from these records vs. credit cards and on line banking info. </p>
<p>I sincerely hope a compromise can be worked out.  I can understand the SS Death Index (don&#8217;t like it but understand it) but not the birth certs and death certs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lisa Marker</title>
		<link>http://geneabloggers.com/ssdi-access-ready-rumble/#comment-11350</link>
		<dc:creator>Lisa Marker</dc:creator>
		<pubDate>Tue, 07 Feb 2012 04:07:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.geneabloggers.com/?p=17422#comment-11350</guid>
		<description><![CDATA[As other people have stated, I don&#039;t need to see the actual SS number. The first three numbers are helpful to know where it was issued. After that, I don&#039;t care. 

I do agree that if we don&#039;t take some action, this will snowball until tons of records are out of grasp.]]></description>
		<content:encoded><![CDATA[<p>As other people have stated, I don&#8217;t need to see the actual SS number. The first three numbers are helpful to know where it was issued. After that, I don&#8217;t care. </p>
<p>I do agree that if we don&#8217;t take some action, this will snowball until tons of records are out of grasp.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aliza Giammatteo</title>
		<link>http://geneabloggers.com/ssdi-access-ready-rumble/#comment-11349</link>
		<dc:creator>Aliza Giammatteo</dc:creator>
		<pubDate>Tue, 07 Feb 2012 01:49:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.geneabloggers.com/?p=17422#comment-11349</guid>
		<description><![CDATA[PS -- Does anybody know when this is supposed to be decided? I haven&#039;t heard anything about that.]]></description>
		<content:encoded><![CDATA[<p>PS &#8212; Does anybody know when this is supposed to be decided? I haven&#8217;t heard anything about that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aliza Giammatteo</title>
		<link>http://geneabloggers.com/ssdi-access-ready-rumble/#comment-11348</link>
		<dc:creator>Aliza Giammatteo</dc:creator>
		<pubDate>Tue, 07 Feb 2012 01:48:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.geneabloggers.com/?p=17422#comment-11348</guid>
		<description><![CDATA[Don, 

I love that idea of replacing the number but I don&#039;t know how realistic it is as far as implementation.

And Linda, I&#039;m with you -- in my business we need to order the SS-5 so we need the number.

There&#039;s GOT to be a way to find a happy medium! Maybe we need to start thinking outside the box more.

Or maybe...if we let go of the most recent records that would be acceptable to those who take issue with how it currently stands, but most of us could still run our businesses.

I don&#039;t know...I don&#039;t have the answer either. I&#039;m just thinking out loud here.]]></description>
		<content:encoded><![CDATA[<p>Don, </p>
<p>I love that idea of replacing the number but I don&#8217;t know how realistic it is as far as implementation.</p>
<p>And Linda, I&#8217;m with you &#8212; in my business we need to order the SS-5 so we need the number.</p>
<p>There&#8217;s GOT to be a way to find a happy medium! Maybe we need to start thinking outside the box more.</p>
<p>Or maybe&#8230;if we let go of the most recent records that would be acceptable to those who take issue with how it currently stands, but most of us could still run our businesses.</p>
<p>I don&#8217;t know&#8230;I don&#8217;t have the answer either. I&#8217;m just thinking out loud here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Don</title>
		<link>http://geneabloggers.com/ssdi-access-ready-rumble/#comment-11347</link>
		<dc:creator>Don</dc:creator>
		<pubDate>Tue, 07 Feb 2012 00:35:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.geneabloggers.com/?p=17422#comment-11347</guid>
		<description><![CDATA[I would be happy to have the SSNs stripped out if it meant we could maintain access to the rest of the info.  As far as ordering the SS-5, if they replace the SSN with a new unique value they can use that to reference the record in their database, but it would be useless outside of ordering an SS-5.]]></description>
		<content:encoded><![CDATA[<p>I would be happy to have the SSNs stripped out if it meant we could maintain access to the rest of the info.  As far as ordering the SS-5, if they replace the SSN with a new unique value they can use that to reference the record in their database, but it would be useless outside of ordering an SS-5.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Linda Swisher</title>
		<link>http://geneabloggers.com/ssdi-access-ready-rumble/#comment-11346</link>
		<dc:creator>Linda Swisher</dc:creator>
		<pubDate>Mon, 06 Feb 2012 22:48:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.geneabloggers.com/?p=17422#comment-11346</guid>
		<description><![CDATA[Aliza, you are correct. Working together is key. Those in Congress don&#039;t want to be seen as a small-business killer, but they&#039;re not listening to those companies, big and small, who use the SSDI and depend on it. 

It&#039;s especially vital for genealogists to agree amongst THEMSELVES what we can and cannot live with. I&#039;ve read posts by genealogists who feel that a fair compromise is to keep the SSDI&#039;s names and information public, but eliminate the SSN itself. That may work for SOME genealogists, but it is by no means a good solution for those of us who depend on access to the entire number to narrow down places of residence, order SS-5&#039;s, etc.]]></description>
		<content:encoded><![CDATA[<p>Aliza, you are correct. Working together is key. Those in Congress don&#8217;t want to be seen as a small-business killer, but they&#8217;re not listening to those companies, big and small, who use the SSDI and depend on it. </p>
<p>It&#8217;s especially vital for genealogists to agree amongst THEMSELVES what we can and cannot live with. I&#8217;ve read posts by genealogists who feel that a fair compromise is to keep the SSDI&#8217;s names and information public, but eliminate the SSN itself. That may work for SOME genealogists, but it is by no means a good solution for those of us who depend on access to the entire number to narrow down places of residence, order SS-5&#8242;s, etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aliza Giammatteo</title>
		<link>http://geneabloggers.com/ssdi-access-ready-rumble/#comment-11345</link>
		<dc:creator>Aliza Giammatteo</dc:creator>
		<pubDate>Mon, 06 Feb 2012 22:05:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.geneabloggers.com/?p=17422#comment-11345</guid>
		<description><![CDATA[Thank you so much for your work on this issue that is so important to us professional genealogists, and amateurs alike.

There&#039;s been a lot of discussion in genealogy circles about &#039;not throwing the baby out with the bath water.&#039;

The &#039;other side&#039; may have some valid points... but we do too... and it sure would be nice if we could compromise. 

Does this really have to be an all-or-nothing thing??? Or can we find a way to work together?

For those of us with small businesses related to genealogy, this could do serious damage to our business. Sometimes it&#039;s impossible to move forward without those records so if we don&#039;t have access, we lose business. Plain and simple.

I don&#039;t think anyone in congress wants to be seen as a small business-killer. And at the same time, there are many in the genealogical community (at least the ones I&#039;ve spoken with, I won&#039;t try to speak for everyone) who don&#039;t want to be seen as heartless or uncompromising themselves -- they recognize that there could be some legitimate concerns and *some level of reform might be in order.

But the keyword there is &#039;some.&#039; Again, let&#039;s try to get rid of the black and white thinking and see if we can work together. My 2 cents.]]></description>
		<content:encoded><![CDATA[<p>Thank you so much for your work on this issue that is so important to us professional genealogists, and amateurs alike.</p>
<p>There&#8217;s been a lot of discussion in genealogy circles about &#8216;not throwing the baby out with the bath water.&#8217;</p>
<p>The &#8216;other side&#8217; may have some valid points&#8230; but we do too&#8230; and it sure would be nice if we could compromise. </p>
<p>Does this really have to be an all-or-nothing thing??? Or can we find a way to work together?</p>
<p>For those of us with small businesses related to genealogy, this could do serious damage to our business. Sometimes it&#8217;s impossible to move forward without those records so if we don&#8217;t have access, we lose business. Plain and simple.</p>
<p>I don&#8217;t think anyone in congress wants to be seen as a small business-killer. And at the same time, there are many in the genealogical community (at least the ones I&#8217;ve spoken with, I won&#8217;t try to speak for everyone) who don&#8217;t want to be seen as heartless or uncompromising themselves &#8212; they recognize that there could be some legitimate concerns and *some level of reform might be in order.</p>
<p>But the keyword there is &#8216;some.&#8217; Again, let&#8217;s try to get rid of the black and white thinking and see if we can work together. My 2 cents.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
