<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" media="screen" href="/styles/xslt/rss.xslt"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:c9="http://channel9.msdn.com">
<channel>
	<title>Comment Feed for Channel 9 - Plagiarism</title>
	<atom:link rel="self" type="application/rss+xml" href="http://channel9.msdn.com/Blogs/kevinsch/Plagiarism/RSS"></atom:link>
	<image>
		<url>http://mschnlnine.vo.llnwd.net/d1/Dev/App_Themes/C9/images/feedimage.png</url>
		<title>Channel 9 - Plagiarism</title>
		<link></link>
	</image>
	<description>The Globe and Mail discusses plagiarism (and other forms of academic corruption) in China.The Internet, search engines, digital libraries and citation services have been a huge boon to scholarly work. But they also have a dark side, in that they make plagiarism exceedingly easy. And policing it by faculty is equally hard.A cottage industry has sprung out of the desire to help police against plagiarism, with tools that instructors can use to verify the originality of submitted work. Actually, to be very precise these tools could verify that something is not original, but they can never actually verify the true originality of a piece of work.But of course, this is all a war of escalation. The plagiarists will get more clever, and the policing tools will get more clever in lock-step. Why? Because there&#39;s money to be made on both sides.Should we simply resign ourselves to this fate? Or is there a way out of this war of escalation?</description>
	<link></link>
	<language>en</language>
	<pubDate>Tue, 21 May 2013 08:17:10 GMT</pubDate>
	<lastBuildDate>Tue, 21 May 2013 08:17:10 GMT</lastBuildDate>
	<generator>Rev9</generator>
</channel>
</rss>