<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Law and technology &#187; risk management</title>
	<atom:link href="http://www.burgess.co.nz/law/tag/risk-management/feed" rel="self" type="application/rss+xml" />
	<link>http://www.burgess.co.nz/law</link>
	<description>A blog on law and technology issues in New Zealand</description>
	<lastBuildDate>Tue, 13 Dec 2011 11:10:28 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Tech law update 21 July 2010</title>
		<link>http://www.burgess.co.nz/law/tech-law-update-21-july-2010</link>
		<comments>http://www.burgess.co.nz/law/tech-law-update-21-july-2010#comments</comments>
		<pubDate>Wed, 21 Jul 2010 22:04:21 +0000</pubDate>
		<dc:creator>Guy Burgess</dc:creator>
				<category><![CDATA[Updates]]></category>
		<category><![CDATA[Copyright]]></category>
		<category><![CDATA[Open source]]></category>
		<category><![CDATA[risk management]]></category>

		<guid isPermaLink="false">http://www.burgess.co.nz/law/?p=878</guid>
		<description><![CDATA[Legal risks for IT pros
InfoWorld has an article on lurking legal gotchas (and how to avoid them) for IT pros. Its list includes:

Confidentiality and privacy violations
Pornography use
Copyright and source code violations
&#8220;Financial shenanigans&#8221; &#8211; essentially fraud or other criminal activity.

The article is based on US law, but the above list is applicable in New Zealand. However [...]]]></description>
			<content:encoded><![CDATA[<h3>Legal risks for IT pros</h3>
<p>InfoWorld has an <a href="http://infoworld.com/d/adventures-in-it/it-pros-lurking-legal-gotchas-and-how-avoid-them-844">article on lurking legal gotchas</a> (and how to avoid them) for IT pros. Its list includes:</p>
<ul>
<li>Confidentiality and privacy violations</li>
<li>Pornography use</li>
<li>Copyright and source code violations</li>
<li>&#8220;Financial shenanigans&#8221; &#8211; essentially fraud or other criminal activity.</li>
</ul>
<p>The article is based on US law, but the above list is applicable in New Zealand. However an important distinction not made entirely clear is that between intentional (i.e. malicious) activity and accidental contravention. Also, in most cases employees who are honestly carrying out their job are entitled to be indemnified by their employer for any liability arising against them personally (subject to employment contracts and other factors). Independent contractors are generally liable for their own actions, however, and insurance is an important risk management practice for contractors.</p>
<h3>Open source wrangling</h3>
<p>Computerworld <a href="http://computerworld.co.nz/news.nsf/news/r-software-exploited-by-us-company-creator">reports on a controversy</a> over whether a US company has breached the GPL terms of the <a href="http://www.r-project.org/">R statistical software</a> (developed out of Auckland University and the original version of which I used in stage-1 stats). The company, Revolution Analytics, denies breaching the GPL. It uses the increasingly popular (but sometimes controversial) &#8220;<a href="http://alampitt.typepad.com/lampitt_or_leave_it/2008/08/open-core-licen.html">open core</a>&#8221; model where (for example) the core program remains licensed on <a href="http://www.revolutionanalytics.com/downloads/gpl-sources.php">open terms</a>, but other components and add-ons are under proprietary licenses. The situation highlights the sometimes murky issue of copyright ownership, assignment and licensing in large open source projects. Another example, involving OpenOffice, is <a href="http://www.h-online.com/open/features/OpenOffice-at-the-crossroads-1023702.html?page=2">reported here</a>.</p>
<h3>Copyright vs Contract law</h3>
<p>A UK government advisory board, the Strategic Advisory Board for Intellectual Property, has completed a <a href="http://www.sabip.org.uk/contractlaw-report.pdf">lengthy report (182 pages, 6MB pdf)</a> on &#8220;the relationship between copyright and contract law&#8221;. The highly academic report appears to be a last hurrah for the quango, which is <a href="http://www.musicweek.com/story.asp?sectioncode=1&amp;storycode=1041903&amp;c=1">to be axed</a>. The report is based on extensive research into &#8220;creator contracts&#8221; &#8211; i.e. supply side contracts such as those entered into by authors, musicians, artists, etc &#8211; and &#8220;user contracts&#8221; &#8211; i.e. demand side contract typically involving licensing of IP to end users. A summary of the fairly impenetrable report <a href="http://www.theregister.co.uk/2010/07/19/sabip_copyright_report/">is here</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.burgess.co.nz/law/tech-law-update-21-july-2010/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

