<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: Lessig on Interoperability at Wikimania 2006</title>
	<atom:link href="http://blogs.law.harvard.edu/palfrey/2006/08/04/lessig-at-wikimania-2006/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.law.harvard.edu/palfrey/2006/08/04/lessig-at-wikimania-2006/</link>
	<description>From the Berkman Center at Harvard Law School</description>
	<lastBuildDate>Wed, 18 Nov 2009 13:34:17 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: John Palfrey &#187; Blog Archive &#187; Making a Market Emerge out of Digital Copyright Uncertainty</title>
		<link>http://blogs.law.harvard.edu/palfrey/2006/08/04/lessig-at-wikimania-2006/comment-page-1/#comment-2053</link>
		<dc:creator>John Palfrey &#187; Blog Archive &#187; Making a Market Emerge out of Digital Copyright Uncertainty</dc:creator>
		<pubDate>Thu, 12 Oct 2006 00:26:18 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/palfrey/2006/08/04/lessig-at-wikimania-2006/#comment-2053</guid>
		<description>[...] Another part of the answer to this digital copyright issue might be provided by the market. One might imagine a process by which citizens who create user-generated content (think of a single YouTube video file or a syndicated vlog series, a podcast audio file or series of podcasts, a single online essay or a syndicated blog, a photo covering the perfectly captures a breaking news story or a series of evocative images, and so forth) might consistently adopt a default license (one of the CC licenses, or an &#8220;interoperable&#8221; license that enables another form of commercial distribution; I am persuaded that as much interoperability of licenses as possible is essential here) for all content that they create, with the ability also to adopt a separate license for an individual work that they may create in the future. [...]</description>
		<content:encoded><![CDATA[<p>[...] Another part of the answer to this digital copyright issue might be provided by the market. One might imagine a process by which citizens who create user-generated content (think of a single YouTube video file or a syndicated vlog series, a podcast audio file or series of podcasts, a single online essay or a syndicated blog, a photo covering the perfectly captures a breaking news story or a series of evocative images, and so forth) might consistently adopt a default license (one of the CC licenses, or an &#8220;interoperable&#8221; license that enables another form of commercial distribution; I am persuaded that as much interoperability of licenses as possible is essential here) for all content that they create, with the ability also to adopt a separate license for an individual work that they may create in the future. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Palfrey &#187; Blog Archive &#187; Microsoft&#8217;s Open Specification Promise</title>
		<link>http://blogs.law.harvard.edu/palfrey/2006/08/04/lessig-at-wikimania-2006/comment-page-1/#comment-1994</link>
		<dc:creator>John Palfrey &#187; Blog Archive &#187; Microsoft&#8217;s Open Specification Promise</dc:creator>
		<pubDate>Wed, 13 Sep 2006 16:03:05 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/palfrey/2006/08/04/lessig-at-wikimania-2006/#comment-1994</guid>
		<description>[...] Why might it not be so great? Well, I think it is a great thing, and not just because we at the Berkman Center have been looking into interoperability, with support from Microsoft and others, and learning more about how companies are taking novel steps in this sort of direction. Its limitation might take a few forms, I suppose. The promise itself has limitations &#8212; it applies to some specifications and the promise extends only to some possible IPR-related claims, of course, but that seems natural, especially with such a first step. Other possible limitations: 1) Will developers pay attention to it, and in fact believe it? 2) Will this promise itself be interoperable with other such promises? I am reminded of Prof. Lessig&#8217;s speech at Wikimania last month, when he talked about interoperable licenses. Hopefully, others will either follow this lead or help developers to understand how this meshes with other similar promises of forebearance in the marketplace. 3) I don&#8217;t know well enough whether these are the right specifications to be included in such a promise. Are there other specs that developers would like to see opened up in this fashion? [...]</description>
		<content:encoded><![CDATA[<p>[...] Why might it not be so great? Well, I think it is a great thing, and not just because we at the Berkman Center have been looking into interoperability, with support from Microsoft and others, and learning more about how companies are taking novel steps in this sort of direction. Its limitation might take a few forms, I suppose. The promise itself has limitations &#8212; it applies to some specifications and the promise extends only to some possible IPR-related claims, of course, but that seems natural, especially with such a first step. Other possible limitations: 1) Will developers pay attention to it, and in fact believe it? 2) Will this promise itself be interoperable with other such promises? I am reminded of Prof. Lessig&#8217;s speech at Wikimania last month, when he talked about interoperable licenses. Hopefully, others will either follow this lead or help developers to understand how this meshes with other similar promises of forebearance in the marketplace. 3) I don&#8217;t know well enough whether these are the right specifications to be included in such a promise. Are there other specs that developers would like to see opened up in this fashion? [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
