<?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: Liability for Software Vulnerabilities</title>
	<atom:link href="http://www.robhyndman.com/2005/10/20/liability-for-software-vulnerabilities/feed" rel="self" type="application/rss+xml" />
	<link>http://www.robhyndman.com/2005/10/20/liability-for-software-vulnerabilities/</link>
	<description>any technology distinguishable from magic is not sufficiently advanced</description>
	<pubDate>Sat, 22 Nov 2008 03:21:20 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Tim Marman</title>
		<link>http://www.robhyndman.com/2005/10/20/liability-for-software-vulnerabilities/#comment-631</link>
		<dc:creator>Tim Marman</dc:creator>
		<pubDate>Wed, 09 Nov 2005 06:44:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.robhyndman.com/?p=869#comment-631</guid>
		<description>Within tort law, it's important to distinguish between strict liability and negligence. 

I don't think there's anything wrong with applying a negligence standard to software development. 

Alpha/beta software contains sufficient warnings and is explicitly not intended for production release. Thus, anyone who deploys such software in a production environment likely wouldn't have a cause of action. (Or we could easily make the argument that they are at least contributorily responsible).</description>
		<content:encoded><![CDATA[<p>Within tort law, it&#8217;s important to distinguish between strict liability and negligence. </p>
<p>I don&#8217;t think there&#8217;s anything wrong with applying a negligence standard to software development. </p>
<p>Alpha/beta software contains sufficient warnings and is explicitly not intended for production release. Thus, anyone who deploys such software in a production environment likely wouldn&#8217;t have a cause of action. (Or we could easily make the argument that they are at least contributorily responsible).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
