<?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: The OCLC Kerfuffle: In which I write much but come to few conclusions</title>
	<atom:link href="http://pegasuslibrarian.com/2008/11/oclc-kerfuffle-in-which-i-write-much.html/feed" rel="self" type="application/rss+xml" />
	<link>http://pegasuslibrarian.com/2008/11/oclc-kerfuffle-in-which-i-write-much.html</link>
	<description>Learning in Libraries and Loving It</description>
	<lastBuildDate>Fri, 04 May 2012 00:51:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Iris</title>
		<link>http://pegasuslibrarian.com/2008/11/oclc-kerfuffle-in-which-i-write-much.html/comment-page-1#comment-1213</link>
		<dc:creator>Iris</dc:creator>
		<pubDate>Fri, 21 Nov 2008 21:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://pegasuslibrarian.com/2008/11/the-oclc-kerfuffle-in-which-i-write-much-but-come-to-few-conclusions/#comment-1213</guid>
		<description>That *is* a good question, Dorothea. I look forward to someone more astute than I am to answer it.&lt;br/&gt;&lt;br/&gt;And I think you&#039;ve hit on the major source of my discomfort with section 13, Steve. Vagueness of this sort requires trust that will always be tinged with a tiny bit of fear, and that tiny bit of fear will stifle creativity. I see that same thing happen with fair use decisions all the time, and even &lt;a HREF=&quot;http://www.copyright.gov/title17/92chap1.html#107&quot; REL=&quot;nofollow&quot;&gt;section 107&lt;/a&gt; of copyright law (which is famously vague) gives a few concrete examples of things that are permissible when it says that &quot;multiple copies for classroom use&quot; count as fair. OCLC&#039;s section 13 only gives negative examples, leaving very little room to imagine viable Reasonable Uses.</description>
		<content:encoded><![CDATA[<p>That *is* a good question, Dorothea. I look forward to someone more astute than I am to answer it.</p>
<p>And I think you&#8217;ve hit on the major source of my discomfort with section 13, Steve. Vagueness of this sort requires trust that will always be tinged with a tiny bit of fear, and that tiny bit of fear will stifle creativity. I see that same thing happen with fair use decisions all the time, and even <a HREF="http://www.copyright.gov/title17/92chap1.html#107" REL="nofollow">section 107</a> of copyright law (which is famously vague) gives a few concrete examples of things that are permissible when it says that &#8220;multiple copies for classroom use&#8221; count as fair. OCLC&#8217;s section 13 only gives negative examples, leaving very little room to imagine viable Reasonable Uses.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Lawson</title>
		<link>http://pegasuslibrarian.com/2008/11/oclc-kerfuffle-in-which-i-write-much.html/comment-page-1#comment-1212</link>
		<dc:creator>Steve Lawson</dc:creator>
		<pubDate>Thu, 20 Nov 2008 21:56:00 +0000</pubDate>
		<guid isPermaLink="false">http://pegasuslibrarian.com/2008/11/the-oclc-kerfuffle-in-which-i-write-much-but-come-to-few-conclusions/#comment-1212</guid>
		<description>As usual, you and I find ourselves in a similar boat. Two things I didn&#039;t really work into my post: &lt;br/&gt;&lt;br/&gt;Has anyone who is not an OCLC employee come forward to say &quot;this is really necessary and good, and helpful to OCLC member libraries and/or the public at large?&quot; &lt;br/&gt;&lt;br/&gt;The policy and especially the section 13 that you highlight seems to depend on a certain amount of trust that OCLC won&#039;t all of a sudden try to shut down projects it doesn&#039;t like. And I dislike legalistic policies that depend on a &quot;oh, just trust that we won&#039;t enforce that to the full.&quot;</description>
		<content:encoded><![CDATA[<p>As usual, you and I find ourselves in a similar boat. Two things I didn&#8217;t really work into my post: </p>
<p>Has anyone who is not an OCLC employee come forward to say &#8220;this is really necessary and good, and helpful to OCLC member libraries and/or the public at large?&#8221; </p>
<p>The policy and especially the section 13 that you highlight seems to depend on a certain amount of trust that OCLC won&#8217;t all of a sudden try to shut down projects it doesn&#8217;t like. And I dislike legalistic policies that depend on a &#8220;oh, just trust that we won&#8217;t enforce that to the full.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dorothea</title>
		<link>http://pegasuslibrarian.com/2008/11/oclc-kerfuffle-in-which-i-write-much.html/comment-page-1#comment-1211</link>
		<dc:creator>Dorothea</dc:creator>
		<pubDate>Thu, 20 Nov 2008 20:54:00 +0000</pubDate>
		<guid isPermaLink="false">http://pegasuslibrarian.com/2008/11/the-oclc-kerfuffle-in-which-i-write-much-but-come-to-few-conclusions/#comment-1211</guid>
		<description>What IS our investment in our data, and what returns ought we to expect on it? I think that&#039;s the clarifying question here.</description>
		<content:encoded><![CDATA[<p>What IS our investment in our data, and what returns ought we to expect on it? I think that&#8217;s the clarifying question here.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

