<?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: Karen Calhoun on OCLC&#8217;s Updated Record Use Policy</title>
	<atom:link href="http://blog.ecorrado.us/2008/11/05/karen-calhoun-on-worldcat/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.ecorrado.us/2008/11/05/karen-calhoun-on-worldcat/</link>
	<description>Ramblings about library technology, open source software, and other adventures!</description>
	<lastBuildDate>Fri, 28 Oct 2011 05:59:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: ecorrado</title>
		<link>http://blog.ecorrado.us/2008/11/05/karen-calhoun-on-worldcat/comment-page-1/#comment-6802</link>
		<dc:creator>ecorrado</dc:creator>
		<pubDate>Thu, 06 Nov 2008 21:03:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ecorrado.us/?p=544#comment-6802</guid>
		<description>Tim,

I see your point. I still think it is an improvement for it not to be required though. I am undecided what I would recommend that we do at Binghamton University at this time. I think I need to see how this shakes out a little more. One of the things I really didn&#039;t like about the notice requirements is it looked like they were only going to link to the current version of the policy. I am happy to see that Karen Calhoun forwarded this concern of mine to the Study Group and David Whitehair has posted that they &lt;a href=&quot;http://community.oclc.org/metalogue/archives/2008/11/notes-on-oclcs-updated-record.html#comment-770&quot; rel=&quot;nofollow&quot;&gt;will add versioning information to the 996 field&lt;/a&gt;. Between the now &quot;encouraged&quot; nature of the 996 and the versioning I am a lot more happy with the attribution issue. Of course, that doesn&#039;t help fix the other concerns I have, but it is a start.</description>
		<content:encoded><![CDATA[<p>Tim,</p>
<p>I see your point. I still think it is an improvement for it not to be required though. I am undecided what I would recommend that we do at Binghamton University at this time. I think I need to see how this shakes out a little more. One of the things I really didn&#8217;t like about the notice requirements is it looked like they were only going to link to the current version of the policy. I am happy to see that Karen Calhoun forwarded this concern of mine to the Study Group and David Whitehair has posted that they <a href="http://community.oclc.org/metalogue/archives/2008/11/notes-on-oclcs-updated-record.html#comment-770" rel="nofollow">will add versioning information to the 996 field</a>. Between the now &#8220;encouraged&#8221; nature of the 996 and the versioning I am a lot more happy with the attribution issue. Of course, that doesn&#8217;t help fix the other concerns I have, but it is a start.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://blog.ecorrado.us/2008/11/05/karen-calhoun-on-worldcat/comment-page-1/#comment-6668</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Wed, 05 Nov 2008 23:28:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ecorrado.us/?p=544#comment-6668</guid>
		<description>I&#039;m undecided on the notice requirements. It looks to me like whether notice is given or not, the terms remain in effect. In such a situation, it&#039;s better to know what&#039;s going on and to what records than to have ambiguous records floating around.

Do you see my point?</description>
		<content:encoded><![CDATA[<p>I&#8217;m undecided on the notice requirements. It looks to me like whether notice is given or not, the terms remain in effect. In such a situation, it&#8217;s better to know what&#8217;s going on and to what records than to have ambiguous records floating around.</p>
<p>Do you see my point?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

