<?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: Random Remarks on Creative Commons and the Public Domain</title>
	<atom:link href="http://blogs.law.harvard.edu/cmusings/2003/04/09/random-remarks-on-creative-commons-and-the-public-domain/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.law.harvard.edu/cmusings/2003/04/09/random-remarks-on-creative-commons-and-the-public-domain/</link>
	<description>by Derek Slater</description>
	<lastBuildDate>Fri, 05 Dec 2008 12:07:35 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Bob</title>
		<link>http://blogs.law.harvard.edu/cmusings/2003/04/09/random-remarks-on-creative-commons-and-the-public-domain/comment-page-1/#comment-4345</link>
		<dc:creator>Bob</dc:creator>
		<pubDate>Fri, 11 Apr 2003 02:28:09 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/cmusings/2003/04/09/random-remarks-on-creative-commons-a#comment-4345</guid>
		<description>&lt;a&gt;&lt;/a&gt;

I&#039;m not big on desktop rss readers, Eric. They use too many cpu resources when you probably already have your browser open anyway, and could just be using it, and too much bandwidth (you might be pulling down huge files just to get a few tidbits of info).... Back in the day, I was a beta tester for Carmen&#039;s Headline Viewer, which was magnificent for its time (this was 1999 or 2000 I think) and probably greatly improved now, but I always just wanted to just get that information easier yet....

You&#039;re right, LiveJournal looks very interesting... I&#039;m going off to explore it further now.... Thanks</description>
		<content:encoded><![CDATA[<p><a></a></p>
<p>I&#8217;m not big on desktop rss readers, Eric. They use too many cpu resources when you probably already have your browser open anyway, and could just be using it, and too much bandwidth (you might be pulling down huge files just to get a few tidbits of info)&#8230;. Back in the day, I was a beta tester for Carmen&#8217;s Headline Viewer, which was magnificent for its time (this was 1999 or 2000 I think) and probably greatly improved now, but I always just wanted to just get that information easier yet&#8230;.</p>
<p>You&#8217;re right, LiveJournal looks very interesting&#8230; I&#8217;m going off to explore it further now&#8230;. Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Eisenhart</title>
		<link>http://blogs.law.harvard.edu/cmusings/2003/04/09/random-remarks-on-creative-commons-and-the-public-domain/comment-page-1/#comment-4344</link>
		<dc:creator>Eric Eisenhart</dc:creator>
		<pubDate>Thu, 10 Apr 2003 19:15:21 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/cmusings/2003/04/09/random-remarks-on-creative-commons-a#comment-4344</guid>
		<description>&lt;a&gt;&lt;/a&gt;

Bob: just a clarification: I did almost nothing to make that &quot;falsch freiheit - Friends&quot; thing work; that&#039;s all handled fairly automatically by the &quot;LiveJournal&quot; software.  I pretty much just fed the software some RSS feeds URLs and clicked a few buttons and that got created.  Brad Fitz and the other LiveJournal folks deserve the credit for making the software.

There&#039;s also desktop software that does pretty much the same thing, but with a UI designed specifically for news, such as &lt;a href=&quot;http://www.nongnu.org/straw/&quot;&gt;Straw&lt;/a&gt;, &lt;a href=&quot;http://ranchero.com/netnewswire/&quot;&gt;NetNewsWire&lt;/a&gt;, and &lt;a href=&quot;http://www.feedreader.com/&quot;&gt;FeedReader&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p><a></a></p>
<p>Bob: just a clarification: I did almost nothing to make that &#8220;falsch freiheit &#8211; Friends&#8221; thing work; that&#8217;s all handled fairly automatically by the &#8220;LiveJournal&#8221; software.  I pretty much just fed the software some RSS feeds URLs and clicked a few buttons and that got created.  Brad Fitz and the other LiveJournal folks deserve the credit for making the software.</p>
<p>There&#8217;s also desktop software that does pretty much the same thing, but with a UI designed specifically for news, such as <a href="http://www.nongnu.org/straw/">Straw</a>, <a href="http://ranchero.com/netnewswire/">NetNewsWire</a>, and <a href="http://www.feedreader.com/">FeedReader</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob</title>
		<link>http://blogs.law.harvard.edu/cmusings/2003/04/09/random-remarks-on-creative-commons-and-the-public-domain/comment-page-1/#comment-4343</link>
		<dc:creator>Bob</dc:creator>
		<pubDate>Thu, 10 Apr 2003 04:43:52 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/cmusings/2003/04/09/random-remarks-on-creative-commons-a#comment-4343</guid>
		<description>&lt;a&gt;&lt;/a&gt;

Eric--just saw your &quot;falsch freiheit - Friends&quot; Nice work.... Sweet site. So I guess Derek has a reason to keek the whole content in the rss after all, since some are pulling it...</description>
		<content:encoded><![CDATA[<p><a></a></p>
<p>Eric&#8211;just saw your &#8220;falsch freiheit &#8211; Friends&#8221; Nice work&#8230;. Sweet site. So I guess Derek has a reason to keek the whole content in the rss after all, since some are pulling it&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob</title>
		<link>http://blogs.law.harvard.edu/cmusings/2003/04/09/random-remarks-on-creative-commons-and-the-public-domain/comment-page-1/#comment-4342</link>
		<dc:creator>Bob</dc:creator>
		<pubDate>Thu, 10 Apr 2003 04:35:38 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/cmusings/2003/04/09/random-remarks-on-creative-commons-a#comment-4342</guid>
		<description>&lt;a&gt;&lt;/a&gt;

Instead of having a second feed, why include the whole article content in the description tags of the rss file at all? Are you using it to build the site pages? Why not just have the single feed with titles and links, and make the license attribution only? (Although I agree that the CC license may be irrelevant with regard to titles and links....)</description>
		<content:encoded><![CDATA[<p><a></a></p>
<p>Instead of having a second feed, why include the whole article content in the description tags of the rss file at all? Are you using it to build the site pages? Why not just have the single feed with titles and links, and make the license attribution only? (Although I agree that the CC license may be irrelevant with regard to titles and links&#8230;.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Eisenhart</title>
		<link>http://blogs.law.harvard.edu/cmusings/2003/04/09/random-remarks-on-creative-commons-and-the-public-domain/comment-page-1/#comment-4341</link>
		<dc:creator>Eric Eisenhart</dc:creator>
		<pubDate>Wed, 09 Apr 2003 22:37:13 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/cmusings/2003/04/09/random-remarks-on-creative-commons-a#comment-4341</guid>
		<description>&lt;a&gt;&lt;/a&gt;

Sounds to me like you want a more open (CC attribution) license for the URL, title, etc. while keeping your current license for the main content.

But you&#039;ve just got one RSS feed, and it&#039;s all in there.

I can easily set up a &lt;a href=&quot;http://www.livejournal.com/~freiheit/friends/law&quot;&gt;re-feed&lt;/a&gt; of your blog that includes content, title and link.  This is non-commercial, automatically provides attribution and makes no attempt to license anything.  Bandwidth usage on your server from this is roughly similar to one mildly-obsessive human reader (IIRC, a hit to the rss file every hour or 4...)  OTOH, if I charged people to access that content, I think you&#039;d have good reason to be upset.

But, as you said, using the title and links for commercial purposes doesn&#039;t bother you.

IIRC, generally the title, author name and unique id (isbn, issn, page#) and other &quot;meta&quot; information is either covered by &quot;fair use&quot; or possibly even outright non-copyrightable.

&quot;Article content on this site is under a [creative commons license / cc:by-nc-sa].  Article titles are under a different [creative commons license / cc:by-sa].  URLs to articles may be considered public domain.&quot;?

(Note on the livejournal example: I had to go through some extra effort for that view, the &lt;a href=&quot;http://www.livejournal.com/~cmusings/&quot;&gt;normal view&lt;/a&gt; for somebody who&#039;s not &quot;subscribed&quot; to that specific rss feed is disclaimered and less convenient)

IMO, there is de-facto permission (of some sort; assumable from having an RSS feed.  Much like one can generally assume permission to copy a web-page to a single computer and render (modify!) the HTML into a viewable format based on the simple fact that the material in question is provided via a public HTTP server with no access controls.  Part of the problem (in both cases) is when something goes up without the knowledge of the human.  Many &quot;blogs&quot; will create an RSS feed automatically, and there&#039;s been cases of web-servers serving information when companies didn&#039;t even know the software in question had a web server.</description>
		<content:encoded><![CDATA[<p><a></a></p>
<p>Sounds to me like you want a more open (CC attribution) license for the URL, title, etc. while keeping your current license for the main content.</p>
<p>But you&#8217;ve just got one RSS feed, and it&#8217;s all in there.</p>
<p>I can easily set up a <a href="http://www.livejournal.com/~freiheit/friends/law">re-feed</a> of your blog that includes content, title and link.  This is non-commercial, automatically provides attribution and makes no attempt to license anything.  Bandwidth usage on your server from this is roughly similar to one mildly-obsessive human reader (IIRC, a hit to the rss file every hour or 4&#8230;)  OTOH, if I charged people to access that content, I think you&#8217;d have good reason to be upset.</p>
<p>But, as you said, using the title and links for commercial purposes doesn&#8217;t bother you.</p>
<p>IIRC, generally the title, author name and unique id (isbn, issn, page#) and other &#8220;meta&#8221; information is either covered by &#8220;fair use&#8221; or possibly even outright non-copyrightable.</p>
<p>&#8220;Article content on this site is under a [creative commons license / cc:by-nc-sa].  Article titles are under a different [creative commons license / cc:by-sa].  URLs to articles may be considered public domain.&#8221;?</p>
<p>(Note on the livejournal example: I had to go through some extra effort for that view, the <a href="http://www.livejournal.com/~cmusings/">normal view</a> for somebody who&#8217;s not &#8220;subscribed&#8221; to that specific rss feed is disclaimered and less convenient)</p>
<p>IMO, there is de-facto permission (of some sort; assumable from having an RSS feed.  Much like one can generally assume permission to copy a web-page to a single computer and render (modify!) the HTML into a viewable format based on the simple fact that the material in question is provided via a public HTTP server with no access controls.  Part of the problem (in both cases) is when something goes up without the knowledge of the human.  Many &#8220;blogs&#8221; will create an RSS feed automatically, and there&#8217;s been cases of web-servers serving information when companies didn&#8217;t even know the software in question had a web server.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
