<?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: OCLC&#8217;s new Policy for Use and Transfer of WorldCat Records</title>
	<atom:link href="http://blog.ecorrado.us/2008/11/03/oclcs-new-policy-for-use-and-transfer-of-worldcat-records/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.ecorrado.us/2008/11/03/oclcs-new-policy-for-use-and-transfer-of-worldcat-records/</link>
	<description>Ramblings about library technology, open source software, and other adventures!</description>
	<lastBuildDate>Fri, 12 Mar 2010 20:59:34 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: paul walk&#8217;s weblog &#187; Blog Archive &#187; Smoke and mirrors, or good intentions?</title>
		<link>http://blog.ecorrado.us/2008/11/03/oclcs-new-policy-for-use-and-transfer-of-worldcat-records/comment-page-1/#comment-15813</link>
		<dc:creator>paul walk&#8217;s weblog &#187; Blog Archive &#187; Smoke and mirrors, or good intentions?</dc:creator>
		<pubDate>Fri, 20 Feb 2009 12:06:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ecorrado.us/?p=498#comment-15813</guid>
		<description>[...] revisit the arguments here - there was significant commentary criticising the changes (e.g 1 2 3 4 5) and a response from Karen Calhoun: essentially the concerns revolved around the perception [...]</description>
		<content:encoded><![CDATA[<p>[...] revisit the arguments here &#8211; there was significant commentary criticising the changes (e.g 1 2 3 4 5) and a response from Karen Calhoun: essentially the concerns revolved around the perception [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Copyright Advisory Network &#187; Blog Archive &#187; OCLC licensing saga</title>
		<link>http://blog.ecorrado.us/2008/11/03/oclcs-new-policy-for-use-and-transfer-of-worldcat-records/comment-page-1/#comment-9888</link>
		<dc:creator>Copyright Advisory Network &#187; Blog Archive &#187; OCLC licensing saga</dc:creator>
		<pubDate>Fri, 12 Dec 2008 19:41:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ecorrado.us/?p=498#comment-9888</guid>
		<description>[...] blog.ecorrado.us: OCLC&#8217;s new Policy for Use and Transfer of WorldCat Records [...]</description>
		<content:encoded><![CDATA[<p>[...] blog.ecorrado.us: OCLC&#8217;s new Policy for Use and Transfer of WorldCat Records [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Molly Kleinman &#187; Blog Archive &#187; The OCLC data licensing saga: Adapt or die</title>
		<link>http://blog.ecorrado.us/2008/11/03/oclcs-new-policy-for-use-and-transfer-of-worldcat-records/comment-page-1/#comment-8415</link>
		<dc:creator>Molly Kleinman &#187; Blog Archive &#187; The OCLC data licensing saga: Adapt or die</dc:creator>
		<pubDate>Tue, 25 Nov 2008 00:15:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ecorrado.us/?p=498#comment-8415</guid>
		<description>[...] blog.ecorrado.us: OCLC&#8217;s new Policy for Use and Transfer of WorldCat Records [...]</description>
		<content:encoded><![CDATA[<p>[...] blog.ecorrado.us: OCLC&#8217;s new Policy for Use and Transfer of WorldCat Records [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: blog.ecorrado.us &#187; Karen Calhoun on OCLC&#8217;s Updated Record Use Policy</title>
		<link>http://blog.ecorrado.us/2008/11/03/oclcs-new-policy-for-use-and-transfer-of-worldcat-records/comment-page-1/#comment-6666</link>
		<dc:creator>blog.ecorrado.us &#187; Karen Calhoun on OCLC&#8217;s Updated Record Use Policy</dc:creator>
		<pubDate>Wed, 05 Nov 2008 22:54:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ecorrado.us/?p=498#comment-6666</guid>
		<description>[...] never disagreed with the need for the new policy, just how it was being implemented and some of the terms and restrictions put on [...]</description>
		<content:encoded><![CDATA[<p>[...] never disagreed with the need for the new policy, just how it was being implemented and some of the terms and restrictions put on [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: blog.ecorrado.us &#187; New OCLC Policy on WorldCat Records Re-released</title>
		<link>http://blog.ecorrado.us/2008/11/03/oclcs-new-policy-for-use-and-transfer-of-worldcat-records/comment-page-1/#comment-6645</link>
		<dc:creator>blog.ecorrado.us &#187; New OCLC Policy on WorldCat Records Re-released</dc:creator>
		<pubDate>Wed, 05 Nov 2008 17:41:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ecorrado.us/?p=498#comment-6645</guid>
		<description>[...] version that libraries need to be aware of. While I was hopeful that the re-released policy would address some of my concerns, outside of the attribution clause, I don&#8217;t really see any improvements.   posted by ecorrado [...]</description>
		<content:encoded><![CDATA[<p>[...] version that libraries need to be aware of. While I was hopeful that the re-released policy would address some of my concerns, outside of the attribution clause, I don&#8217;t really see any improvements.   posted by ecorrado [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ecorrado</title>
		<link>http://blog.ecorrado.us/2008/11/03/oclcs-new-policy-for-use-and-transfer-of-worldcat-records/comment-page-1/#comment-6395</link>
		<dc:creator>ecorrado</dc:creator>
		<pubDate>Tue, 04 Nov 2008 02:05:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ecorrado.us/?p=498#comment-6395</guid>
		<description>Good points Jonathan. I think you are right that there are things libraries could do. I just don&#039;t see enough of them getting together to do anything that will lead to significant changes at this time. I really don&#039;t know what our agreement for submitting records to OCLC is. At some point I should probably look into it. The terms and conditions that we get all our content (including metadata) are going to have a strong influence on how relevant libraries remain in the future.</description>
		<content:encoded><![CDATA[<p>Good points Jonathan. I think you are right that there are things libraries could do. I just don&#8217;t see enough of them getting together to do anything that will lead to significant changes at this time. I really don&#8217;t know what our agreement for submitting records to OCLC is. At some point I should probably look into it. The terms and conditions that we get all our content (including metadata) are going to have a strong influence on how relevant libraries remain in the future.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Rochkind</title>
		<link>http://blog.ecorrado.us/2008/11/03/oclcs-new-policy-for-use-and-transfer-of-worldcat-records/comment-page-1/#comment-6392</link>
		<dc:creator>Jonathan Rochkind</dc:creator>
		<pubDate>Tue, 04 Nov 2008 01:12:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ecorrado.us/?p=498#comment-6392</guid>
		<description>One thing libraries could do, if they had the will, was start including their own license (or revocation of rights) on original cataloging data. What if every record of original cataloging had a 996 included saying that the originating institution relinquished/licensed all rights under an Open Data Commons license?  That would be a crimp in OCLC&#039;s plans. There&#039;s no reason a library couldn&#039;t retroactively release historical original cataloging under Open Data Commons too. 

When you have a record that may have been touched by many institutions, that makes things more complicated of course. 

But OCLC likely doesn&#039;t own this data in the first place, the bulk of it was contributed by member libraries (and by LC)--that&#039;s why their trying to get quasi-ownership privileges by licensing terms, rather than by actually asserting ownership. 

http://www.opendatacommons.org/</description>
		<content:encoded><![CDATA[<p>One thing libraries could do, if they had the will, was start including their own license (or revocation of rights) on original cataloging data. What if every record of original cataloging had a 996 included saying that the originating institution relinquished/licensed all rights under an Open Data Commons license?  That would be a crimp in OCLC&#8217;s plans. There&#8217;s no reason a library couldn&#8217;t retroactively release historical original cataloging under Open Data Commons too. </p>
<p>When you have a record that may have been touched by many institutions, that makes things more complicated of course. </p>
<p>But OCLC likely doesn&#8217;t own this data in the first place, the bulk of it was contributed by member libraries (and by LC)&#8211;that&#8217;s why their trying to get quasi-ownership privileges by licensing terms, rather than by actually asserting ownership. </p>
<p><a href="http://www.opendatacommons.org/" rel="nofollow">http://www.opendatacommons.org/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: viral nature of OCLC usage policy&#8211;like open source? No. &#171; Bibliographic Wilderness</title>
		<link>http://blog.ecorrado.us/2008/11/03/oclcs-new-policy-for-use-and-transfer-of-worldcat-records/comment-page-1/#comment-6389</link>
		<dc:creator>viral nature of OCLC usage policy&#8211;like open source? No. &#171; Bibliographic Wilderness</dc:creator>
		<pubDate>Mon, 03 Nov 2008 23:53:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ecorrado.us/?p=498#comment-6389</guid>
		<description>[...] open source?&#160;No. November 3, 2008 Posted by jrochkind in General.  trackback  Note: The &#8220;viral&#8221; nature of the proposed (then quickly hidden again; why not let us comment on a public draft?) OCLC record [...]</description>
		<content:encoded><![CDATA[<p>[...] open source?&nbsp;No. November 3, 2008 Posted by jrochkind in General.  trackback  Note: The &#8220;viral&#8221; nature of the proposed (then quickly hidden again; why not let us comment on a public draft?) OCLC record [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
