<?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: Patentability of software patent claims</title>
	<atom:link href="http://www.startupsip.com/2012/09/05/patentability-of-software-patent-claims/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.startupsip.com/2012/09/05/patentability-of-software-patent-claims/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=patentability-of-software-patent-claims</link>
	<description>Examining the IP strategy of today&#039;s hottest startups.</description>
	<lastBuildDate>Thu, 07 Feb 2013 11:35:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<!--Theme by MyThemeShop.com-->
	<item>
		<title>By: Ben Hoyle</title>
		<link>http://www.startupsip.com/2012/09/05/patentability-of-software-patent-claims/#comment-275</link>
		<dc:creator>Ben Hoyle</dc:creator>
		<pubDate>Thu, 20 Sep 2012 15:02:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.startupsip.com/?p=887#comment-275</guid>
		<description><![CDATA[The sentiment appears to mirror the &quot;further technical effect&quot; approach found in Europe and the UK: i.e. a technical effect over and above a standard computer implementing a computerised method.

I agree though that the reference to &quot;repetitive calculations&quot; is a bit misleading and could be phrased better. However, I am not holding out hope of clarification from the Supreme Court any time soon.

In the meantime, I guess when drafting an application the key is to avoid the &quot;abstract method description + boilerplate computer architecture&quot; template that was used for many business method and software patents in the early 00s. From what I have seen of the recent US decisions, a technical (e.g. engineering/computer science-level) description that emphasises the differences from a manual method should help avoid patentability objections.]]></description>
		<content:encoded><![CDATA[<p>The sentiment appears to mirror the &#8220;further technical effect&#8221; approach found in Europe and the UK: i.e. a technical effect over and above a standard computer implementing a computerised method.</p>
<p>I agree though that the reference to &#8220;repetitive calculations&#8221; is a bit misleading and could be phrased better. However, I am not holding out hope of clarification from the Supreme Court any time soon.</p>
<p>In the meantime, I guess when drafting an application the key is to avoid the &#8220;abstract method description + boilerplate computer architecture&#8221; template that was used for many business method and software patents in the early 00s. From what I have seen of the recent US decisions, a technical (e.g. engineering/computer science-level) description that emphasises the differences from a manual method should help avoid patentability objections.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thinking about the design behind Design Patents - Startups and IP StrategyStartups and IP Strategy</title>
		<link>http://www.startupsip.com/2012/09/05/patentability-of-software-patent-claims/#comment-152</link>
		<dc:creator>Thinking about the design behind Design Patents - Startups and IP StrategyStartups and IP Strategy</dc:creator>
		<pubDate>Mon, 10 Sep 2012 13:08:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.startupsip.com/?p=887#comment-152</guid>
		<description><![CDATA[[...] Contact        &#171; Patentability of software patent claims [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Contact        &laquo; Patentability of software patent claims [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
