<?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: Indirect liability concept to be introduced in the Japanese copyright law?</title>
	<atom:link href="http://chosaq.net/archives/2006/12/indirect-liability-concept-to-be-introduced-in-the-japanese-copyright-law.html/feed" rel="self" type="application/rss+xml" />
	<link>http://chosaq.net/archives/2006/12/indirect-liability-concept-to-be-introduced-in-the-japanese-copyright-law.html</link>
	<description>A research blog tracking copyright related policy &#038; technology developments in Japan. By Andreas Bovens.</description>
	<lastBuildDate>Sat, 18 Jul 2009 11:59:26 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: chosaq &#187; A commons-inspired critique of Japan&#8217;s IP strategy</title>
		<link>http://chosaq.net/archives/2006/12/indirect-liability-concept-to-be-introduced-in-the-japanese-copyright-law.html/comment-page-1#comment-2082</link>
		<dc:creator>chosaq &#187; A commons-inspired critique of Japan&#8217;s IP strategy</dc:creator>
		<pubDate>Thu, 25 Jan 2007 07:48:30 +0000</pubDate>
		<guid isPermaLink="false">http://chosaq.net/archives/2006/12/indirect-liability-concept-to-be-introduced-in-the-japanese-copyright-law.html#comment-2082</guid>
		<description>[...] A couple of entries ago, I already had a look at the fuzzy indirect liability concept introduced in the Japanese government&#8217;s Intellectual Property Strategic Program 2006. [...]</description>
		<content:encoded><![CDATA[<p>[...] A couple of entries ago, I already had a look at the fuzzy indirect liability concept introduced in the Japanese government&#8217;s Intellectual Property Strategic Program 2006. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
