<?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: Implementing the Public Domain Dedication</title>
	<atom:link href="http://opendatacommons.org/2007/12/20/implementing-the-public-domain-dedication/feed/" rel="self" type="application/rss+xml" />
	<link>http://opendatacommons.org/2007/12/20/implementing-the-public-domain-dedication/</link>
	<description>Legal tools for Open Data</description>
	<lastBuildDate>Fri, 25 Jun 2010 08:53:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Dissecting CCZero</title>
		<link>http://opendatacommons.org/2007/12/20/implementing-the-public-domain-dedication/#comment-92</link>
		<dc:creator>Dissecting CCZero</dc:creator>
		<pubDate>Wed, 16 Jan 2008 19:35:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.opendatacommons.org/2007/12/20/implementing-the-public-domain-dedication/#comment-92</guid>
		<description>&lt;p&gt;[...] I mentioned on the Open Data Commons site that I thought that any application of a legal tool involving a public domain waiver should have a “signed writing” to make sure that people really knew what they were doing by dedicating a work to the public domain and also so that the dedication would fit existing or likely legal standards. (Read that post here). [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] I mentioned on the Open Data Commons site that I thought that any application of a legal tool involving a public domain waiver should have a “signed writing” to make sure that people really knew what they were doing by dedicating a work to the public domain and also so that the dedication would fit existing or likely legal standards. (Read that post here). [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

