<?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: One bad apple&#8230;all practitioners suffer (The USPTO and Easy Access to Public Data)</title>
	<atom:link href="http://inventblog.com/2008/01/one-bad-appleall-practitioners-suffer-the-uspto-and-easy-access-to-public-data.html/feed" rel="self" type="application/rss+xml" />
	<link>http://inventblog.com/uspto/one-bad-appleall-practitioners-suffer-the-uspto-and-easy-access-to-public-data.html</link>
	<description></description>
	<lastBuildDate>Wed, 17 Mar 2010 02:09:35 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: D.C. Patent Associate</title>
		<link>http://inventblog.com/uspto/one-bad-appleall-practitioners-suffer-the-uspto-and-easy-access-to-public-data.html/comment-page-1#comment-2478</link>
		<dc:creator>D.C. Patent Associate</dc:creator>
		<pubDate>Fri, 01 Feb 2008 14:17:07 +0000</pubDate>
		<guid isPermaLink="false">http://inventblog.com/2008/01/one-bad-appleall-practitioners-suffer-the-uspto-and-easy-access-to-public-data.html#comment-2478</guid>
		<description>Based on my experience, the CATPCHA made public PAIR more accessable because it was very difficult to access prior to the change.

That said, I hope CATPCHA is only a temporary solution because data mining could be very beneficial in the long term.</description>
		<content:encoded><![CDATA[<p>Based on my experience, the CATPCHA made public PAIR more accessable because it was very difficult to access prior to the change.</p>
<p>That said, I hope CATPCHA is only a temporary solution because data mining could be very beneficial in the long term.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen M. Nipper</title>
		<link>http://inventblog.com/uspto/one-bad-appleall-practitioners-suffer-the-uspto-and-easy-access-to-public-data.html/comment-page-1#comment-2477</link>
		<dc:creator>Stephen M. Nipper</dc:creator>
		<pubDate>Thu, 31 Jan 2008 22:49:31 +0000</pubDate>
		<guid isPermaLink="false">http://inventblog.com/2008/01/one-bad-appleall-practitioners-suffer-the-uspto-and-easy-access-to-public-data.html#comment-2477</guid>
		<description>Larry:  Thanks for the link.</description>
		<content:encoded><![CDATA[<p>Larry:  Thanks for the link.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Larry Kasoff</title>
		<link>http://inventblog.com/uspto/one-bad-appleall-practitioners-suffer-the-uspto-and-easy-access-to-public-data.html/comment-page-1#comment-2476</link>
		<dc:creator>Larry Kasoff</dc:creator>
		<pubDate>Thu, 31 Jan 2008 22:17:09 +0000</pubDate>
		<guid isPermaLink="false">http://inventblog.com/2008/01/one-bad-appleall-practitioners-suffer-the-uspto-and-easy-access-to-public-data.html#comment-2476</guid>
		<description>The USPTO did post a public explanation, but you probably missed it because they didn&#039;t post it until January 11, about a week and a half after the CAPTCHA was implemented.

http://www.uspto.gov/main/homepagenews/2008jan11.htm

&quot;The reCAPTCHA deployment was an immediate response to a system outage problem caused by bots.  The USPTO continues to explore long-term solutions to address the need for open access to the data by the Intellectual Property community.&quot;</description>
		<content:encoded><![CDATA[<p>The USPTO did post a public explanation, but you probably missed it because they didn&#8217;t post it until January 11, about a week and a half after the CAPTCHA was implemented.</p>
<p><a href="http://www.uspto.gov/main/homepagenews/2008jan11.htm" rel="nofollow">http://www.uspto.gov/main/homepagenews/2008jan11.htm</a></p>
<p>&#8220;The reCAPTCHA deployment was an immediate response to a system outage problem caused by bots.  The USPTO continues to explore long-term solutions to address the need for open access to the data by the Intellectual Property community.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim</title>
		<link>http://inventblog.com/uspto/one-bad-appleall-practitioners-suffer-the-uspto-and-easy-access-to-public-data.html/comment-page-1#comment-2475</link>
		<dc:creator>Jim</dc:creator>
		<pubDate>Thu, 31 Jan 2008 19:11:45 +0000</pubDate>
		<guid isPermaLink="false">http://inventblog.com/2008/01/one-bad-appleall-practitioners-suffer-the-uspto-and-easy-access-to-public-data.html#comment-2475</guid>
		<description>Your presumption is correct, as far as I know.  PAIR was pretty much inaccessible for most of December - just a lot of timeouts and page errors (at least for  me and others in my office).  One of the secretaries in my office called the PTO and was told that they were having a problem with &quot;data mining&quot; that was overloading the site.  Things definitely seem to have improved since they put in the CAPTCHA.</description>
		<content:encoded><![CDATA[<p>Your presumption is correct, as far as I know.  PAIR was pretty much inaccessible for most of December &#8211; just a lot of timeouts and page errors (at least for  me and others in my office).  One of the secretaries in my office called the PTO and was told that they were having a problem with &#8220;data mining&#8221; that was overloading the site.  Things definitely seem to have improved since they put in the CAPTCHA.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
