<?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: WorldCat API: draft ruby gem</title>
	<atom:link href="http://people.oregonstate.edu/~reeset/blog/archives/618/feed" rel="self" type="application/rss+xml" />
	<link>http://people.oregonstate.edu/~reeset/blog/archives/618</link>
	<description>On my work (programming, digital libraries, cataloging) and other stuff that perks my interest (family, cycling, etc)</description>
	<lastBuildDate>Mon, 08 Feb 2010 20:31:50 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Administrator</title>
		<link>http://people.oregonstate.edu/~reeset/blog/archives/618/comment-page-1#comment-107531</link>
		<dc:creator>Administrator</dc:creator>
		<pubDate>Mon, 23 Feb 2009 06:30:05 +0000</pubDate>
		<guid isPermaLink="false">http://oregonstate.edu/~reeset/blog/archives/618#comment-107531</guid>
		<description>One note, I should preface the above where I note: &quot;And while the project was pretty much completed, the present service terms the are attached to the API make this type of work out of bounds at present&quot; -- this is related to the restrictions on service levels and the data that is provided.  My vision for an open source version of WorldCat Local was to provide an open replacement option for the ILS utilizing WorldCat data.  And this is possible and folks have done it (David Walker I believe has integrated the WorldCat API into the Xerces project).  The main difference between that work and my interest is I want to provide the interface without need for authentication.  At present, to use the full service level, you must authenticate all users -- essentially the same way that you would for article databases.  The difference however, is that you would be talking about one&#039;s ILS and that becomes a much stickier issue -- since large swaths of users that have no relation to an organization likely use and rely on an organization&#039;s ILS interface.  So, it is these limits that I&#039;m alluding to.  And as I say, these were limits that I was aware of, though, I honestly believe will be short-lived as OCLC continues to evaluate how to make their data more available to the membership.  That seems to be the trend with their other services, so I certainly can see this eventually moving in that direction.

--TR</description>
		<content:encoded><![CDATA[<p>One note, I should preface the above where I note: &#8220;And while the project was pretty much completed, the present service terms the are attached to the API make this type of work out of bounds at present&#8221; &#8212; this is related to the restrictions on service levels and the data that is provided.  My vision for an open source version of WorldCat Local was to provide an open replacement option for the ILS utilizing WorldCat data.  And this is possible and folks have done it (David Walker I believe has integrated the WorldCat API into the Xerces project).  The main difference between that work and my interest is I want to provide the interface without need for authentication.  At present, to use the full service level, you must authenticate all users &#8212; essentially the same way that you would for article databases.  The difference however, is that you would be talking about one&#8217;s ILS and that becomes a much stickier issue &#8212; since large swaths of users that have no relation to an organization likely use and rely on an organization&#8217;s ILS interface.  So, it is these limits that I&#8217;m alluding to.  And as I say, these were limits that I was aware of, though, I honestly believe will be short-lived as OCLC continues to evaluate how to make their data more available to the membership.  That seems to be the trend with their other services, so I certainly can see this eventually moving in that direction.</p>
<p>&#8211;TR</p>
]]></content:encoded>
	</item>
</channel>
</rss>
