<?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: A look at the Policy for Use and Transfer of WorldCat Records revision</title>
	<atom:link href="http://people.oregonstate.edu/~reeset/blog/archives/582/feed" rel="self" type="application/rss+xml" />
	<link>http://people.oregonstate.edu/~reeset/blog/archives/582</link>
	<description>On my work (programming, digital libraries, cataloging) and other stuff that perks my interest (family, cycling, etc)</description>
	<lastBuildDate>Wed, 28 Oct 2009 05:56:39 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</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://people.oregonstate.edu/~reeset/blog/archives/582/comment-page-1#comment-107529</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:19 +0000</pubDate>
		<guid isPermaLink="false">http://oregonstate.edu/~reeset/blog/archives/582#comment-107529</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 that [...]</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 that [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: OCLC&#8217;s proposed new guidelines for the transfer of bibliographic records &#124; Terry&#8217;s Worklog</title>
		<link>http://people.oregonstate.edu/~reeset/blog/archives/582/comment-page-1#comment-107404</link>
		<dc:creator>OCLC&#8217;s proposed new guidelines for the transfer of bibliographic records &#124; Terry&#8217;s Worklog</dc:creator>
		<pubDate>Thu, 13 Nov 2008 10:00:57 +0000</pubDate>
		<guid isPermaLink="false">http://oregonstate.edu/~reeset/blog/archives/582#comment-107404</guid>
		<description>[...] significant changes to the document. I&#8217;ve added my comments regarding this revision here: http://oregonstate.edu/~reeset/blog/ archives/582    This entry was posted on Sunday, November 2nd, 2008 at 9:33 am and is filed under Monopolist . [...]</description>
		<content:encoded><![CDATA[<p>[...] significant changes to the document. I&#8217;ve added my comments regarding this revision here: <a href="http://oregonstate.edu/~reeset/blog/" rel="nofollow">http://oregonstate.edu/~reeset/blog/</a> archives/582    This entry was posted on Sunday, November 2nd, 2008 at 9:33 am and is filed under Monopolist . [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Administrator</title>
		<link>http://people.oregonstate.edu/~reeset/blog/archives/582/comment-page-1#comment-107394</link>
		<dc:creator>Administrator</dc:creator>
		<pubDate>Fri, 07 Nov 2008 14:42:22 +0000</pubDate>
		<guid isPermaLink="false">http://oregonstate.edu/~reeset/blog/archives/582#comment-107394</guid>
		<description>Ed, 

Yes -- in the URI as well.  I was thinking in the MARC subfields simply because it would make it much easier to parse on the MARC side of things -- but for portability outside of MARC -- you are right.</description>
		<content:encoded><![CDATA[<p>Ed, </p>
<p>Yes &#8212; in the URI as well.  I was thinking in the MARC subfields simply because it would make it much easier to parse on the MARC side of things &#8212; but for portability outside of MARC &#8212; you are right.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ed Summers</title>
		<link>http://people.oregonstate.edu/~reeset/blog/archives/582/comment-page-1#comment-107393</link>
		<dc:creator>Ed Summers</dc:creator>
		<pubDate>Fri, 07 Nov 2008 13:06:34 +0000</pubDate>
		<guid isPermaLink="false">http://oregonstate.edu/~reeset/blog/archives/582#comment-107393</guid>
		<description>Nice analysis Terry. Rather than putting the version number into a MARC subfield I would recommend they version the URI itself. This would parallel work done by Creative Commons: e.g. http://creativecommons.org/licenses/by-nc/1.0/ , http://creativecommons.org/licenses/by-nc/2.0/ , http://creativecommons.org/licenses/by-nc/3.0 .</description>
		<content:encoded><![CDATA[<p>Nice analysis Terry. Rather than putting the version number into a MARC subfield I would recommend they version the URI itself. This would parallel work done by Creative Commons: e.g. <a href="http://creativecommons.org/licenses/by-nc/1.0/" rel="nofollow">http://creativecommons.org/licenses/by-nc/1.0/</a> , <a href="http://creativecommons.org/licenses/by-nc/2.0/" rel="nofollow">http://creativecommons.org/licenses/by-nc/2.0/</a> , <a href="http://creativecommons.org/licenses/by-nc/3.0" rel="nofollow">http://creativecommons.org/licenses/by-nc/3.0</a> .</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: inkdroid &#187; Blog Archive &#187; bibliovirus</title>
		<link>http://people.oregonstate.edu/~reeset/blog/archives/582/comment-page-1#comment-107392</link>
		<dc:creator>inkdroid &#187; Blog Archive &#187; bibliovirus</dc:creator>
		<pubDate>Fri, 07 Nov 2008 13:01:29 +0000</pubDate>
		<guid isPermaLink="false">http://oregonstate.edu/~reeset/blog/archives/582#comment-107392</guid>
		<description>[...] 2008-11-07: check out Terry&#8217;s re-analysis of &#8220;the Policy&#8221; when a new version was brought back online by [...]</description>
		<content:encoded><![CDATA[<p>[...] 2008-11-07: check out Terry&#8217;s re-analysis of &#8220;the Policy&#8221; when a new version was brought back online by [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Elaine Sanchez</title>
		<link>http://people.oregonstate.edu/~reeset/blog/archives/582/comment-page-1#comment-107385</link>
		<dc:creator>Elaine Sanchez</dc:creator>
		<pubDate>Wed, 05 Nov 2008 21:33:49 +0000</pubDate>
		<guid isPermaLink="false">http://oregonstate.edu/~reeset/blog/archives/582#comment-107385</guid>
		<description>Thank you for doing this excellent work. It has all become so contractual. There is no mention of public review, which I think was until Feb. 2009. Has that changed, do you know? I also have been very concerned about the future of library services and how OCLC is becoming the bibliographic monopoly of the world, having gobbled up any and all other services (UTLASS, RLIN, WLN, etc.). I worry that OCLC intends on becoming a for-profit agency that will eventually provide most library services, thus eliminating local control, local needs -- WorldCat local is a big step into this. It&#039;s not a wise move to allow OCLC to gain so much power over our library services. One size, the OCLC size, does not and should not ever fit all. We have have to realize the quickening steps OCLC has taken to start compiling all of our services into their products, many of which are for a fee. For-Profit OCLC in 10 years, with our implicit permission because we didn&#039;t stop this, and their ownership of all our records and monopoly of our service needs, is something I&#039;m afraid of.</description>
		<content:encoded><![CDATA[<p>Thank you for doing this excellent work. It has all become so contractual. There is no mention of public review, which I think was until Feb. 2009. Has that changed, do you know? I also have been very concerned about the future of library services and how OCLC is becoming the bibliographic monopoly of the world, having gobbled up any and all other services (UTLASS, RLIN, WLN, etc.). I worry that OCLC intends on becoming a for-profit agency that will eventually provide most library services, thus eliminating local control, local needs &#8212; WorldCat local is a big step into this. It&#8217;s not a wise move to allow OCLC to gain so much power over our library services. One size, the OCLC size, does not and should not ever fit all. We have have to realize the quickening steps OCLC has taken to start compiling all of our services into their products, many of which are for a fee. For-Profit OCLC in 10 years, with our implicit permission because we didn&#8217;t stop this, and their ownership of all our records and monopoly of our service needs, is something I&#8217;m afraid of.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
